Guide
Audit repeated openings, arguments and endings across your drafts. Change the brief and evidence before polishing individual sentences.
Drafts can feel interchangeable when they repeatedly make the same editorial moves: a broad opening, an abstract problem, evenly balanced tips and a tidy conclusion. Similar structure is a useful editing signal. It is not proof that a text was written by AI, and it cannot identify an author or tool reliably.
Look at the instructions and source packets behind your own drafts. If every brief asks for the same audience, tone, word count and numbered framework, a recurring shape is unsurprising. Replacing a few familiar words leaves that shape intact.
Take five pieces from your archive and label each paragraph by its job. Use plain labels such as observation, evidence, explanation, objection, example and instruction. Ignore style for this pass.
| Check | What to mark |
|---|---|
| Opening | Specific event, reader problem, broad claim or question |
| First evidence | Paragraph where a reader can inspect support |
| Argument | The decision or conclusion the article defends |
| Friction | A counterexample, uncertainty or meaningful tradeoff |
| Ending | New implication, practical next step or repeated summary |
Lay the five outlines side by side. A repeated structure is fine when the task calls for it, as in a recurring product changelog. It becomes a problem when different reporting is forced into the same generic lesson or when evidence arrives only after the conclusion has already been announced.
Consider this hypothetical brief: “Write a thought-leadership article about customer onboarding.” It leaves the central decision, evidence and disagreement unspecified. A stronger brief might ask: “Explain why this team's first-week checklist failed to surface an access-permission problem. Use the supplied incident notes, distinguish the team's account from our inference, and show the revised escalation step.”
The second brief does not guarantee good prose. It gives the draft a particular job that a generic introduction cannot perform. Require missing evidence to be marked as missing; do not ask the model to invent a convincing anecdote or personal experience.
Rewrite the outline around the strongest available evidence. One article may need a chronology. Another needs a comparison; another needs a worked calculation. Choose the structure because it helps the reader follow this finding.
After the argument works, remove repeated throat-clearing, unnecessary symmetrical lists and conclusions that simply replay the opening. Preserve qualifications that carry meaning even if they interrupt the rhythm.
Keep two records for the next assignment: the voice decisions you want repeated, and the structural habits you want the editor to question. Judge the result by clarity and support. Trying to outguess an AI detector is a different task and does not improve the evidence in the article.