On this page5 sections
Published October 22, 2026.
Give every brief a version and an owner
Use a filename and header that show the brief version, the date, and the owner. A writer should never have to guess which document is current. Keep the current version in one approved location.
Do not use email subject lines as version control. They are not searchable and they split the history.
Record changes that affect the work
Log changes to the audience, the primary question, the outline, the word range, the sources, and the call to action. A change to any of these can invalidate work already done.
Minor copy edits do not need a new version. Material changes do. Define the threshold in the brief.
Approve the brief before drafting
The writer, the editor, and the subject expert should confirm the brief before the draft begins. Record the approval date and any open question. A brief approved after the draft is a rewrite waiting to happen.
If the brief changes mid-draft, pause and agree the new version. Do not let the writer absorb an unrecorded scope change.
Close the loop after publication
Record the published URL and any deviation from the brief. If the final article differs because the evidence changed, note why. That note improves the next brief.
Archive the approved brief with the article record.
Related reading
For the supporting routine, see this guide and this guide. To discuss the workflow, contact us.
