Draft a long document section by section, approving each before the next

When a document is genuinely long or complex - a full policy, a business case with several options, a report with several distinct sections - the instinct is to ask for the whole thing in one prompt and edit the result afterwards. For anything that actually matters, don't. Ask for one section at a time, and check each one before asking for the next.

The reason isn't speed, it's error propagation. If the model gets your scope statement slightly wrong in section one - includes a team you meant to exclude, say - and you only catch it while reading the finished document end to end, every section after it was written consistent with the wrong scope. You're not fixing one mistake, you're now checking whether the mistake quietly shaped four other sections too, which is a much harder read than catching it in thirty seconds after section one alone.

Asking section by section turns each check into a small, specific question - "does this scope statement match what I meant?" - instead of a vague "does this whole document feel right?" once it's finished and everything reads fluently together. A finished-looking document is hard to doubt; a single paragraph you asked for two minutes ago is easy to interrogate honestly.

It costs more back-and-forth than one big prompt. For a document that's actually going to be published, referenced, or signed off, that cost is worth paying before the mistake is buried three sections deep.