AI assistance does not remove the author's responsibility for a published claim. A fluent paragraph can still contain a false statement, a missing qualification or a promise the linked page does not fulfil.
The useful question is not whether a draft was produced with AI. It is whether the final text can withstand a careful reader's scrutiny.
1. Check what each important statement claims
Separate factual observations, interpretations, predictions, opinions and recommendations. They have different evidentiary requirements. A forecast should not become a fact during editing. A company's claim should remain attributed unless independently established. A hypothetical example should not be presented as evidence that an event is common.
2. Trace consequential claims to sources
For each material statement, ask what source supports it, whether the source supports the exact wording, whether it is current, and whether the claim preserves the source's population, time period and limitations. A product website is authoritative for the company's stated positioning, not independent proof of performance.
3. Review the reader's path
Read the draft in sequence. Does the opening fulfil the title's promise? Does the argument move logically? Do examples support the point they illustrate? Does the conclusion follow from the evidence? Does the CTA match the destination?
4. Preserve the author's voice
Remove generic wording when it obscures a specific point, not merely because it resembles a phrase used elsewhere. Keep deliberate cadence, humour, metaphor, regional language and specialist terminology when they serve the work. Do not use an AI detector score as a substitute for editorial judgement.
5. Check the product promise
Compare each promise with approved product evidence and terms. Look for features described as available when planned, general availability claimed for a limited beta, absolute claims unsupported by the brief, inconsistent pricing or trial details, and headlines that promise more than the destination provides.
6. Review the medium and genre
A press release is not independent journalism. An email is part of a relationship or sequence. A paid ad has an offer and placement context. Fiction may depend on ambiguity. Technical documentation must preserve exact syntax and reader tasks. Do not apply one generic editing checklist to every format.
7. Make consequential edits inspectable
A useful suggestion points to the original passage, explains the reader cost and preserves the author's intended claim. Separate demonstrable errors from optional preferences. Ask a question when author intent could reverse the edit.
8. Review the assembled revision
Edits can create new problems in neighbouring paragraphs. Re-read the final sequence, check referents, dates, numbers, links, attribution and claim scope.
Pre-publication checklist
- Important claims have traceable support.
- Attribution and uncertainty are preserved.
- Title and opening make the same promise.
- The argument is understandable in sequence.
- Examples are not mistaken for proof.
- Product status, price and availability are accurate.
- The author's voice remains recognisable.
- Genre-specific obligations have been considered.
- Accepted edits have been reviewed in context.
- Unknowns are not disguised as facts.
AI can assist with parts of this process. It cannot take responsibility for publication away from the author.