Guide
A content approval process that a small team will follow
An approval process exists to catch the wrong price, the wrong date and the sentence nobody should have published, before readers do. It only works if it is short enough to be followed every time.
Free plan, no card needed.
Why bother approving
Deleting a post does not unpublish it. Somebody has already read it, forwarded it or taken a screenshot. A second pair of eyes before publishing is cheaper than any apology after it, and a small team is exactly where there is no one else to catch a mistake.
The shortest process that works
- Draft. Somebody writes the post.
- Check. Somebody else reads it against the facts.
- Approve. That person approves the exact text, the channel and the time.
- Publish. Only the approved version goes out.
Four steps, two people. If your process has more steps than this, each extra one needs a reason.
Decide who does what
Write down who may write and who may approve, by name. In a team of two, each approves the other's posts. A sole owner can still approve their own, but should do it at a different time from the writing: the next morning catches what the evening missed.
For an agency, the client approves. Agree at the start who at the client that is, and what happens when they do not answer.
Approve the version, not the idea
The most common failure is approving a draft and then changing it. The approver said yes to one text, and a different text went out. Make the rule simple: an approval belongs to one exact version, and any edit afterwards needs a new approval, however small the edit.
What the approver checks
An approver is not there to rewrite. They check, in this order:
- Facts: the price, the date, the address, the offer and its end.
- Claims: anything about results, quality, health or what others say about you.
- Links: each one opens, and opens the right page.
- Pictures: you have the right to use them, and they show what the text says.
- Voice: it sounds like the business.
- Channel and time: it is going to the right place at a sensible hour.
Keep it fast
A process that takes days is abandoned in a week. Agree how quickly an approval is given, who approves when that person is away, and which few kinds of post, if any, may go out without one. Then hold to it.
Keep a record
Know who approved what and when. Not to assign blame, but because the day something goes wrong, the first question is how it got out, and you want an answer that takes a minute.
Where Studio fits
Onflow Studio builds this process in. Every draft is a numbered version. An approval names one version, one channel and one time, and an edit after approval takes the approval away and stops the scheduled post. Claims that are not in your confirmed facts are marked, and the approver ticks that they checked them. On plans with seats, an editor can write but not approve, and a client can approve but not edit. Everything is written to the workspace's activity log.
Questions people ask
Is an approval step worth it for a business of one?
Yes, as a pause. Approving your own post at a different time from writing it catches most mistakes, and it costs a minute.
Who should approve a post?
Somebody who knows the facts in it and was not the one who wrote it. In an agency that is the client, or whoever the client has named.
What happens if a post is edited after it was approved?
It should need a new approval, however small the change. Otherwise the approval means only that somebody once agreed to a different text.
How do I stop approvals slowing everything down?
Agree a time limit, name a second approver for absences, and keep the checklist short. Speed comes from everyone knowing the rule, not from skipping it.
Keep reading
Try it on your own brand
Studio drafts and schedules. You approve. What a post achieves is measured afterwards, never promised.