Tomorrow’s post is ready on Monday. On Tuesday the client sends a WhatsApp voice note: “looks fine, just fix the price”. On Wednesday the head of sales writes in the group chat that the price is different, while the designer is already building the image on the old copy. On Thursday the post goes out with the third version of the price and a wrong date, and everyone honestly believes it was approved.
This is not a discipline problem. It is the absence of a process: no single place where the current version lives, no one person whose “ok” is final, and no deadline after which silence means something. With twenty posts across three networks, approval eats more time than writing.
Below is a working approval scheme: statuses, roles, reply deadlines, what to check before saying “ok”, where to run it by team size, and when approval should be switched off rather than improved.
Why approval breaks
Four causes that show up in almost every team:
- No single source of truth. Copy in Google Docs, edits in Slack, the image in email, the final version in the account manager’s head.
- Too many approvers. When three people must say “ok”, the post waits for the busiest one and the edits contradict each other.
- No reply deadline. A draft sits for a week, then goes out in a rush because “it was due yesterday”.
- Taste edits instead of substance edits. “Make it a bit livelier” is not an edit, it is a new task with no criteria.
Statuses: the path from idea to report
At any moment a post sits in exactly one status, and each status has a condition for moving to the next.
| Status | What it means | Who moves it on |
|---|---|---|
| Draft | Copy and visual ready, links in place | Author submits for review |
| Review | Editor or manager checks facts, tone, typos | Editor: “to approval” or “send back” |
| Approval | Client or business owner gives the final ok | Approver: “approved” or “send back” |
| Scheduled | Sits in the calendar at a date and time; no changes without a new round | System or publisher |
Two rules hold the scheme together:
- Sending back only with a concrete list of edits. “Send back” without a comment is not allowed. One comment with all edits at once, not five messages spread over the day.
- After “approved” the copy does not change. If an edit is needed, the post goes back to Draft and runs the loop again. Otherwise approval loses its meaning: one thing was approved, another went out.
Roles: one author, one editor, one approver
The core rule: every post has exactly one person with the right to the final ok. Not “the marketing team”, not “management”, a named person.
- The author writes, gathers the visual, checks the links and moves the post to Review. No “we’ll add the price later”.
- The editor checks facts, tone and errors and sends the post back with edits instead of rewriting it. One editor per team, otherwise taste edits multiply.
- The approver checks only what they know best: prices, stock, legal risk, promises to customers. Does not touch style. Agree this with the client up front: if they edit commas, the cycle doubles.
Write it down in one line at kickoff: “Maya writes, Tom reviews, Daniel approves by 6 pm the next day.” Put that line in the onboarding brief next to the brand voice, which alone removes half of all taste edits. How to describe it is in the guide to tone of voice.
Reply deadline and the silence rule
Without a deadline approval does not work. A reasonable standard for social media:
- Editor review: up to 4 working hours.
- Client or manager approval: up to 24 hours on working days.
And the most important part: what happens when there is no answer. Two working options, chosen at the start and written into the contract or team rules:
- Silence means approved. After 24 hours without a reply the post goes out. Works for established relationships and regular series.
- Silence means postponed. The post slides to the next slot and the approver gets a reminder. Safer for new clients and for anything involving prices and promotions.
To avoid waiting on every single post, approve in batches: a week of content in one email or one screen on Thursday, with answers due Friday. The client spends 20 minutes once a week instead of 20 separate threads. This fits naturally with content batching.
The approver’s checklist
Approval takes two minutes per post if you check against a list instead of “reading and thinking”. What the approver looks at:
- Prices and terms. Number, currency and promotion dates match reality.
- Availability and links. The product is in stock, the service slot is open, the link leads to a working page.
- Promises. No “guaranteed”, “the best”, “risk-free” unless provable.
- Legal. Sponsored content is disclosed with #ad or the paid partnership label; no competitor bashing, no third-party photos without rights, no tagging people without consent.
What the approver does NOT check: style, paragraph order, emoji choice, “I don’t like this word”. That was handled at the editor stage. If a client keeps editing style, the problem is an undefined brand voice, not the process.
Where to run it: by team size
| Team | Tool | How it works |
|---|---|---|
| Team of 3–5 | Trello, Notion board or a Kanban in your task tracker | Columns mirror the statuses. Card = post, holding copy, visual and comments. Moving the card = changing status |
| Agency with clients | A scheduling tool with an approval feature | The client gets a link or a Telegram message, sees a preview as it will look in the network, taps Approve or writes edits. Never enters your internal tools |
The sign of a good client-approval tool: the preview looks the way the post will look in the network, with the image and the text cutoff. For agencies that approve through a messenger, a bot works well: the draft lands in the client’s Telegram with a preview and two buttons, and the answer takes 20 seconds from a phone. How such a control panel works is covered in the guide to Telegram bots for business.
Approval message template
The text that goes to the client with a batch of posts:
Posts for October 20–26, six in total, in the calendar at the link. Please check the prices in posts 2 and 5 and the promo date in post 4. The rest follows the approved series. Edits by Friday 6 pm, otherwise they go out as scheduled.
The client does not need to read six posts in full, only verify three facts by a known deadline.
The green zone: what never needs approval
Approving every post kills speed exactly where it matters most: replies to comments, behind-the-scenes Stories, reacting to a news hook on the day. Agree on a green zone where the author publishes without a round:
- series whose format was approved once: “question of the week”, before-and-after, review roundups;
- reposts, replies to mentions, Stories with no prices or promises;
- templated posts with data filled in: schedules, a price list pulled from an approved source.
The red zone, where approval is always mandatory: prices and promotions, legal topics, crisis responses, anything touching health or money.
When an approval process is NOT needed
- You are solo and posting for yourself. Statuses exist for handoffs between people. One person needs a calendar and a checklist.
- The approver does not want to own decisions. If the client says “you’re the professionals, just do it”, insisting on an Approve button is pointless. Get it in writing and work from the green zone with a weekly report.
Once statuses, roles and the reply deadline are fixed, the tool stops mattering and edits stop getting lost. In Repost21 the approval loop is built into the calendar: the draft goes to the approver in the Telegram bot with a preview, Approve or Send back is tapped from a phone, and the approved post moves to its best slot. Post approvals come with the PRO plan; everything else here works on any plan, including the free one. Try it on next week’s content and count how many chat messages disappeared.