From brief to published: an approval process for articles and guides

Fibvo editorial · 10 September 2026 · 5 min read

A guide to choosing a cold storage partner was drafted in March. The operations head sent comments by email, the sales director added more on WhatsApp, and the managing director rewrote the introduction after it had been edited. In June, someone asked whether a claim about temperature monitoring had ever been checked. Nobody knew. The writing was never the problem. Nobody had agreed what the piece was for, who could change it or in what order the checks should happen. This post sets out that route for articles and guides, from brief to later updates. For planning regular social posts, see our post on a social media plan a small team can keep running.

Start every article with a one-page brief

The brief is the cheapest place to settle a disagreement. Changing a line in a brief takes a minute. Changing the direction of a finished draft takes days. Use the same fields every time.

• The reader, named as a role, such as a plant manager comparing third-party warehouses.
• The question the piece answers, written in the reader's words.
• The one action you want the reader to take next, such as booking a site visit.
• The sources: which internal expert, which documents and what the team is allowed to quote.
• What the piece must not do, such as name customers, promise transit times or compare prices with a named competitor.
• Whether it needs a legal or compliance check, and the target publish week.

The approver signs off the brief, not only the writer. A person with final say who never agreed the purpose will usually rewrite the piece at the end.

Most rewrites at the approval stage are disagreements about the brief that nobody had at the start.

Sign off the outline, then write the draft

An outline is the headings in order, with two or three notes under each showing what the section will say. The subject expert can read it in ten minutes. This is where they catch the wrong emphasis, a missing step or a point the business does not agree with.

Ask one question at this stage: is anything here wrong or missing? Do not ask for comments on wording yet. Once the outline is signed off, the writer drafts to it. Any later change to the structure needs a reason, and the owner notes it in the tracker.

Name the owner, the expert and the approver, with a deadline for each

Long-form content rarely stalls while it is being written. It stalls in someone's inbox. Give every piece three named roles before drafting starts.

• Owner: moves the piece through each stage, chases reviews and decides when two comments conflict.
• Subject expert: checks technical accuracy. For a guide to export documentation, that is the person who prepares the documents, not necessarily the most senior person.
• Approver: one person with final say on whether it goes live. Two approvers usually means two sets of edits that contradict each other.

Agree turnaround times in working days, for example two days to sign off a brief or outline, three for expert review, two for the edit and three for a compliance check. Write them in the tracker. If a reviewer misses the window, the owner sends one reminder, then takes it to the approver rather than waiting. Keep all comments in one shared document with tracked changes, so nobody edits an old version sent by email.

Check the facts first, then the style, then the compliance

The order matters. If an editor polishes sentences before the expert has checked them, that work is lost when a paragraph turns out to be wrong.

• Subject-matter review: the expert checks every process step, specification, regulation and figure. They mark what is wrong and say what is right, but they do not rewrite the voice.
• Edit: with the facts settled, the editor checks the draft against the brief, cuts repetition, tightens headings and applies the house style.
• Legal or compliance check, where needed: claims about safety, certifications, delivery commitments, pricing, personal data or a named third party go to whoever signs off contracts or regulatory matters. Many pieces will not need this, so the brief decides in advance.
• Final approval: the approver reads the finished piece against the brief. It is a yes or no with specific corrections. New ideas go into the next update.

Set an update date on the day it goes live

Before the piece is published, the owner runs a short check: title and meta description written, headings in order, images compressed and described with alt text, every link working and the call to action pointing where the brief said. Add links to the new piece from two or three older pages on related topics. Our post on an internal linking plan explains how to choose them.

Then set the date of its first review, based on how quickly the subject changes.

• Pieces that mention regulations, fees, deadlines or platform settings: review every six months, and whenever the rule changes.
• Process guides and buyer checklists: review once a year.
• Explainers and opinion pieces: review after two years, then update, merge or retire them.

An update follows a shorter version of the same route. The owner lists what has changed, the expert confirms it, and a compliance check happens again only if a checked claim has changed. Show the last review date in the tracker, so anyone in sales can see which guides are safe to send to a buyer.

---

Written by Fibvo — Bengaluru and Erode, India — working with clients in other time zones. Questions, or think we have it wrong? Tell us.