1. Decide whether a client needs approval at all
Approval costs time on both sides. It is worth it when the brand is regulated (health, finance, alcohol), when posts mention prices, offers or people, when the client relationship is new, or when a past post caused trouble. For an established client posting evergreen content, a lighter rule may be enough: approve campaigns and offers, let routine posts through.
Write the rule into the contract or onboarding notes, so nobody is surprised when posts wait.
2. Name one approver and one backup
“The client” is not an approver; a person is. Agree on one named approver and one backup for holidays. More approvers sounds safer but usually means slower, contradictory feedback. If legal or a product team must see some posts, route only those posts to them.
3. Agree what reviewers check
Give approvers a short list so their feedback is about the things only they know:
- Facts: prices, dates, opening hours, product names, availability
- Claims: anything that promises a result, compares with a competitor or mentions health or money
- People and partners: tags, names, permission to use photos
- Brand: tone, words to avoid, required disclosures for paid partnerships
- Accessibility: alt text on images, captions on video, readable text in graphics
Our approval checklist puts this on one printable page.
4. Set a turnaround time
Agree a response time, for example two working days, and a default: posts not reviewed by the deadline move to the next slot rather than going out unapproved. Batch reviews help: one review session a week for the following week’s posts is easier for a busy client than daily requests.
5. Make feedback specific
“Not quite right” is hard to act on. Ask approvers to say what to change and why, in a note attached to the post. When feedback lives on the post rather than in e-mail, the writer sees it at the moment they edit, and there is a record of what was approved.
6. Keep a record
You should be able to answer “who approved this, and when?” months later. Keep approvals inside the tool you schedule with, not in chat screenshots.
How this looks in PostRoost
On the Team plan and above, tick Posts need admin approval before publishing for a client and add the approver as a client owner or admin. They review under Approvals, and approve, request changes with a note, or reject. Anything sent back appears in the writer’s Actions list with the note. See approval workflows.