Content approval process flowchart (brief to publish and refresh)
Content approval process flowchart template: brief, draft, editor check, brand, SEO, subject-matter and legal reviews, final approval, scheduled publishing and a refresh or retire review after launch.
What the content approval process flowchart (brief to publish and refresh) process is
Most content approval goes wrong in the middle. A draft is sent to everyone at once, each person comments on whatever catches their eye, and the writer gets five contradictory sets of edits. This chart gives each reviewer a written scope and puts one person, the editor, between the reviewers and the writer. It starts when a request is accepted onto the calendar and ends when the piece is closed, because a published page that nobody reviews again is still your content a year later.
The distinguishing structure is the group of specialist reviews. After the editor's 'Does the draft meet the brief?' check, the editor sends the draft to brand and voice, SEO and metadata, and subject-matter accuracy at the same time, and once the accuracy check is done asks 'Does it make claims that need legal review?' to bring in legal and compliance only when the piece needs it. Everything funnels into one consolidated list, and 'Are changes required?' sends the writer round the loop with a single set of edits. The content owner then answers 'Is the piece approved for release?', with approve, rework or reject, and a rejection is logged rather than silently dropped. For single-document sign-off with one approver, see /templates/document-approval-workflow; for the social post variant, see /templates/social-media-approval-process.
After publishing, the chart does something most approval flows skip. The publisher schedules the approved version, publishes it with a refresh date set, and the process waits for that date before asking 'Is it still accurate and performing?'. Keep resets the clock, Update sends a new version back to the editor, and Retire redirects or unpublishes the page. Any legal triggers, review windows and refresh intervals in the chart are placeholders to replace with your own policy, and legal wording should be checked with your counsel.
What this flowchart covers
In this template
- Five swimlanes (Content owner, Writer, Editor, Specialist reviewers and Publisher) across five phases: plan, draft and edit, specialist review, approve and schedule, publish and maintain
- An editor gate, "Does the draft meet the brief?", that sends a weak draft back to the writer before specialist time is spent
- Brand and voice, SEO and metadata, and subject-matter accuracy reviews that start together, plus a conditional legal path behind "Does it make claims that need legal review?"
- A consolidation step and the decision "Are changes required?", which loops the writer back to the reviewers with one list instead of many
- Final approval with three outcomes under "Is the piece approved for release?", including an exception path, "Park or retire the piece and log the reason"
- A scheduled publish with a refresh date set, a "Wait for the refresh review date" step, and "Is it still accurate and performing?" with keep, update and retire outcomes
When to use this template
- Your reviewers comment on everything, contradict each other, and the writer cannot tell which edit wins
- Legal or compliance sees every piece, including those that make no claims, and the queue is slow as a result
- Published pages go out of date because nobody owns a review after launch
- You need to show an auditor, agency or executive how a piece moved from brief to live and who approved it
- You want one process for blog posts, landing pages and lifecycle emails with the reviewer lanes adjusted for each
How it works
Rename the lanes to your team
Replace Content owner, Writer, Editor, Specialist reviewers and Publisher with your roles. If one person is editor and publisher, keep both lanes so the handover is still visible, or merge them deliberately.
Write the brief format
Decide what goes in the brief: audience, goal, keyword, sources and any claims the piece will make. The claims line decides who reviews, so make it required.
Set each reviewer's scope
Write one sentence for brand and voice, SEO and metadata, and subject-matter accuracy saying what they may and may not change. Add a due time so the three run together.
Define the legal triggers
List what sends a piece to legal and compliance, for example testimonials, comparisons, pricing or regulated topics. Agree the list with counsel; the chart uses a yes or no question so the rule is visible.
Cap the change loop
Decide how many rounds of changes the editor allows before the content owner decides. State who settles a disagreement between reviewers.
Lock the approved text
Say what happens to the approved version when it is scheduled. Changes after approval should go through the loop again, not straight to the CMS.
Set the refresh interval
Choose a review date by content type, for example a shorter interval for pricing or product pages and a longer one for evergreen guides. Treat the numbers as placeholders and adjust to your own data.
Frequently asked questions
What is a content approval process?
It is the set of steps that takes a piece of content from request to published and then to maintenance. This one starts with a brief, a draft checked against it, and specialist reviews for brand, SEO, accuracy and, where needed, legal. It continues with a consolidated list of changes, a final approval by the content owner, a scheduled publish and a later decision to keep, update or retire the piece.
How is this different from a document approval workflow?
A document approval workflow, see /templates/document-approval-workflow, usually has one approver deciding on one document. Content has several reviewers with different scopes, a scheduled publish and a life after launch. This chart models those three differences: parallel specialist reviews, a scheduled publication step and a refresh review.
Does every piece need legal review?
The chart assumes not. It asks 'Does it make claims that need legal review?' and sends only those pieces to legal and compliance. What counts as a trigger is a decision for your organisation and counsel, and the examples in the chart are placeholders. Check your jurisdiction and counsel before relying on any rule.
How often should published content be reviewed?
There is no correct number. The chart sets a refresh date when the piece is published and asks 'Is it still accurate and performing?' on that date. Pick intervals by how fast the subject changes and by how much risk an out-of-date page carries, then adjust after a few cycles.
Where this process fits
In most operations this process hands off to Campaign launch process flowchart (brief to post-campaign review).
Comes after
- Campaign launch process flowchart (brief to post-campaign review) — Marketing campaign launch flowchart template: brief and sign-off, parallel creative and channel builds, pre-launch QA, go/no-go gate, first-week monitoring and a review that feeds the next brief.