A Practical AI Writing Workflow: Brief, Draft, Check, Edit
Build a draft from a clear brief, preserve your source facts, and separate writing help from factual verification.
Define the reader and the decision
Before generating prose, write a one-sentence purpose: “Help a new customer understand what to bring to an appointment” or “Explain how our team handles a project handoff.” Identify the reader’s likely questions and the action the page should support. This gives an outline a job beyond filling space.
Collect approved facts in a short source note. Mark each item as confirmed, illustrative, or unknown. Do not put an unknown into a prompt as if it were established. An assistant cannot reliably recover that distinction after a vague brief.
Ask for an outline with evidence gaps
Prepare an outline for [reader] who needs to [outcome]. Use these confirmed facts: [facts]. Include the questions the reader must answer. Put [source needed] beside claims requiring evidence. Keep examples separate from factual statements. Do not add statistics, quotations, credentials, or customer results.
Review the outline before the draft. Remove sections that repeat a point or promise information you cannot provide. Add a missing practical step rather than expanding every heading to the same length. An effective outline follows the task’s sequence, not a fixed article template.
Draft in small, reviewable sections
Ask for one section at a time when the topic needs careful checking. For a service explanation, start with what the customer must do, what information is required, and what happens next. For a tutorial, include inputs, actions, expected behavior, and failure conditions.
Draft the section titled [heading] in plain language. Preserve all confirmed facts exactly. Use short paragraphs and one concrete example. Label the example as fictional. If the source note does not support a claim, leave a visible [verify] marker rather than making it sound certain.
Keeping the source note next to the section makes omissions easier to detect. Save your draft outside the chat so a plan limit, accidental refresh, or account issue does not erase your working copy.
Build a claim checklist
Extract facts that could be checked: dates, prices, measurements, named features, quotations, links, and promises. For each one, record the supporting source and the exact part that supports it. Open the source yourself. A link appended to a paragraph is not proof that every statement in that paragraph is correct.
If the source only supports a narrower claim, narrow the sentence. If no adequate source exists, remove the assertion or make the uncertainty explicit. Follow the answer-checking workflow for a more detailed evidence table.
Edit for meaning, then style
First compare the draft with the brief: does it answer the reader’s question, preserve the facts, and include the next action? Then improve style. Look for repeated introductions, empty claims such as “revolutionary results,” unnecessary adjectives, and sentences that conceal who does what.
For example, change “The provision of confirmation should be undertaken” to “Send a confirmation.” If shortening removes an important condition, restore that condition in a clear sentence. Use a text cleaner for stray whitespace, but review names and intentional formatting manually.
Use a final publication pass
- Check headings, internal links, contact details, and mobile readability.
- Ensure illustrative examples are identified and not presented as customer outcomes.
- Remove draft placeholders, internal review notes, and unsupported superlatives.
- Confirm image rights and useful alternative text.
- Match the page description to the content the reader actually receives.
Keep a short change note after publication. Update the page when facts change or feedback reveals a missing step; changing a date alone does not improve the explanation. A writing workflow succeeds when readers can complete their task with fewer misunderstandings, not when it produces more words.