Inspect the draft before it becomes the page.Then review the claims like an editor.
A useful AI-assisted content check is not a detector score. Preserve the approved source, inspect the text and delivery file, verify every material claim and citation, confirm the client’s disclosure requirements, and record who approved the final version. Rewrite only when changed wording is actually wanted; never treat it as proof of human authorship.
Reviewed by Can Balkaya
Published
Process
How to verify the job
01
Preserve and scope
Keep the approved source, client brief, citations and disclosure requirements beside the draft. Decide what must not change before any cleanup.
02
Inspect and edit
Inspect text and files for named hidden surfaces, then perform the normal fact, source, legal, brand and accessibility review.
03
Approve and record
Reinspect the delivery copy, record the reviewer and actions taken, and publish only the approved version.
Scope
Supported and unsupported surfaces
| Surface | Gifi action | Verification limit |
|---|---|---|
| Named metadata or invisible Unicode | Inspect, remove, and report named actions | Reinspect the returned bytes independently |
| Statistical patterns in ordinary words | Rewrite the prose | No certificate against a private detector |
| Visible logos, pixels, audio, or video | Unsupported | No removal claim |
1. Freeze the input and acceptance criteria
Save the client brief, the approved claims, source links, target query, intended audience and disclosure rule. Preserve a copy of the original draft. A rewrite is lossy by design, so nobody should be reconstructing the non-negotiable facts afterwards.
Name the surface you are checking: ordinary words, hidden Unicode, or file metadata. A statistical word-choice signal, a zero-width character and a DOCX author field are three different objects with three different standards of proof.
2. Inspect before rewriting
Paste text into the local inspector to name invisible Unicode, mixed-script confusables and punctuation changes. Drop the delivery file to preview EXIF, XMP, C2PA and document properties. This first pass should not upload the client’s content.
If the only finding is a statistical concern in the wording, decide whether new wording improves the draft. Do not use a rewrite merely to chase a classifier score, and do not describe the result as human-authored proof.
3. Run the editorial review that tools cannot replace
Open every citation. Verify names, figures, dates, quotations and product claims against the primary source. Check search intent, originality of the analysis, brand voice, accessibility, internal links and the client’s legal or industry constraints.
A clean file can still contain a false claim. A polished paragraph can still have the wrong audience. Publishing hygiene ends with an accountable editor, not with a green status from a utility.
4. Reinspect the delivery copy
Export the exact file or CMS copy that will be delivered, inspect it again, and record the named changes. Check filenames, visible comments, tracked changes and headers separately because they may be content rather than metadata.
Record the reviewer, approval date, final URL or delivery filename, and any disclosure decision. Keep client content out of the checklist record; store the audit facts, not a duplicate of the draft.
Questions this usually raises
- Should an agency require an AI-detector score before publishing?
- No. A classifier score is not a lab watermark and is not proof of authorship. Use accountable editorial criteria: source accuracy, client requirements, originality, usefulness and a named approval.
- Does a rewrite remove the need for disclosure?
- No. Changing wording does not change how the work was produced or what a contract, platform or law requires you to disclose.
- What should the audit record contain?
- The reviewer, time, surface checked, named actions, outcome and delivery reference. Do not copy the client’s text or files into the record.