A content workflow for a small team is a fixed sequence of stages, a named owner for each decision, and a template the next piece starts from. The same sequence covers a content development workflow, a content review workflow, and a content marketing workflow. Which stage you are stuck in is the part that changes.
This page is the general version. It does not assume an AI tool. If you want the points where a model may draft and a person still has to decide, use the AI content workflow. If you want software that can hold the stages, use the content workflow platforms roundup.
The stages
Six stages are enough. Add a stage only when a real handoff is getting lost. A team of one still walks all six. The same person changes hats, and the point of the sequence is that approval is not the last sentence of the draft.
| Stage | What you produce | Done when |
|---|---|---|
| Brief | Audience, the one claim, the offer, the sources, the channels, and the date | The angle is accepted before a full draft exists |
| Draft | One core version, plus channel versions only after the core is stable | The draft follows the brief, and anything not in the sources is marked |
| Review | Comments on facts, the offer, voice, and the channel versions | Every comment is resolved or explicitly dropped |
| Approve | A yes on one named version | The approver has seen the version that will go live, not an earlier file |
| Publish | The live post, page, or email | The link sits with the approved version |
| Read | A short note on what happened | You record one thing to repeat or one thing to stop |
Brief
The brief is the content development workflow. Write it before the draft, in a few lines:
- Who it is for.
- The single claim.
- The offer or next step, and the date it expires if it has one.
- The sources, each with an owner and the day you checked it.
- Claims you will not make.
- Channels, and what has to change per channel.
- Who accepts the angle, and by when.
If the angle is wrong, every later stage gets more expensive. Accept or reject the brief before anyone writes the full piece. On a team of one, accept the brief the next morning, in a sitting of its own.
Draft
The draft follows the brief. It does not invent a new audience or a new offer halfway down. If a fact is not in the sources, mark it in the draft so review has something to check. Do not hide the gap inside a smooth paragraph.
Channel versions come after the core version is stable. A LinkedIn post, an email, and a short script that were written as three separate assignments will drift, even when the same person writes all three. Start them from the approved claim. Repurposing from one message is the longer version of that rule.
Review
Review is where the work is checked, not where it is re-strategized. A content review workflow needs a list, or every reviewer invents a new one.
Check these, and only these, unless the brief asked for something else:
- The claim matches a source, and the source is still current.
- The offer, price, and date match what you can actually do.
- The voice matches the last piece you were willing to publish. If the same correction shows up on every draft, put it in the brand notes instead of the comment thread. Keeping voice consistent across channels is that job.
- Links, names, and the call to action are the ones in the brief.
- Channel versions still say the same thing.
A review names the line and the fix. "The second sentence claims a result we have not published. Cut it or cite the source." "Make it pop" leaves the writer guessing.
Approve
Approval is a yes or no on one named version. Keep it separate from the review comments. The approver looks at the file that will go out, including the image and the first comment if those ship with the post. If the draft changes after that yes, the yes is void and the new version goes back.
A small team often has one approver. Name a backup for when that person is out, and name the deadline. Work that waits with no deadline becomes a pile. Speeding up approvals without skipping the person covers the deadline and the backup in more detail.
Publish
Publish from the approved version. Copying from an older doc, or from a chat that kept going after approval, is how the unapproved sentence ships. Store the live link next to the version that was approved, so the next person can see what actually went out.
Read
A week after it is live, write three lines: what you expected, what the numbers were, and one change for the next piece of the same type. Do not turn this into a dashboard project. The note is there so the next brief starts from evidence. The campaign reporting workflow is the longer version when a whole campaign has to be read.
The roles
Five decisions. On a small team, two people can hold all of them, and one person can hold all of them if the review and the approval happen in a later sitting than the draft. An unnamed decision is what fails.
| Role | The decision they own | On a team of one or two |
|---|---|---|
| Requester | What this piece is for, who it is for, and when it is due | You, in the brief, before the draft |
| Maker | The draft that follows that brief | You, or the person who writes |
| Reviewer | Facts, the offer, and voice, against the brief | A second pass, or the other person. Not the same minute you finished writing |
| Approver | Whether this version can go out | One named person. The maker does not approve their own unchecked draft |
| Publisher | The channel, the time, and saving the live link | Whoever has the login, from the approved version only |
If a client or a founder has to say yes, they are the approver for that piece, and they need the version, the deadline, and a single question: can this go out as shown? Do not also ask them to rewrite the middle. That is the reviewer's job, and it should be finished first.
Write the names into the template below. Put a person's name in the approver line. If the approver is also the maker, say so, and keep the two sittings on the page so the second one actually happens.
The template
Copy this into the doc, ticket, or brief for the next piece. Fill the top before drafting. Fill the bottom as the piece moves. Delete a line only when you have decided you do not need that check, not because the box was annoying.
CONTENT PIECE
Title or working name:
Type: post / page / email / other
Requester:
Due:
BRIEF
Audience:
One claim:
Offer and expiry, if any:
Channels:
Must change per channel:
Sources, owner, date checked:
Claims we will not make:
Angle accepted by: date:
DRAFT
Maker:
Core version link:
Channel version links:
Lines not backed by a source:
REVIEW
Reviewer:
Facts and offer checked against the sources:
Voice checked against the last approved piece:
Comments still open:
APPROVAL
Approver:
Version approved, link:
Approved on:
Changes after this point send it back: yes
PUBLISH
Publisher:
Live links:
Scheduled time:
READ, ABOUT A WEEK LATER
What we expected:
What happened:
One change for the next piece of this type:
Run this twice on the same kind of piece, a weekly post or a monthly page, before you add stages or buy a tool. The second run shows which lines you skip. Those lines are either busywork or the step where mistakes ship. You will know which after two pieces. You will not know from a blank template.
Where this sits next to the calendar, the AI guide, and a tool
The calendar says when something goes out. This workflow says how a piece gets from a claim to a live link with the approved version still attached.
The AI content workflow is the page that decides where a model may draft and where a person still decides. A model can sit inside Draft, and sometimes inside the brief. Approve stays with a person. This page stays the checklist of stages and names.
A shared doc and a folder of final files can run the checklist for a team of two. When the brief, the draft, the yes, and the live link live in four apps, look at platforms that hold plan, create, approve, and publish, or turn one approved brief into the channel versions with one campaign brief, several channels.
Start with the next piece you were going to write anyway. Fill the template. If a line has no answer, that is the gap, and it was already there.