Lesson 4 of 88 min read
Approvals clients actually do
Get sign-off without email chains, using one batch, one deadline, one place to approve and a written rule for clients who go silent.
In this lesson you will
- Design an approval step with one batch, one approver and one deadline
- Choose between in-tool client approval and written client sign-off
- Agree on a rule for silence before the first silent week happens
Approvals are where agency calendars go to wait. You send a batch of posts on Monday. On Wednesday the client replies to one of them. On Friday someone else on their side replies to the original email with a different opinion. The next Tuesday, three posts that were meant to go out have not, and the client asks why the account has been quiet.
Approvals stall for predictable reasons: there are too many of them, they arrive at random times, nobody knows who has the final word, the client has to open five attachments to see what a post will look like, and nothing happens when they do not answer. Each of those has a fix. None of them is "chase harder".
Why approvals stall
Here are the five causes we see most, with the fix for each:
| Cause | Fix |
|---|---|
| Posts sent one at a time | One batch per week (or per month for smaller clients) |
| No clear final approver | One named approver per client, written down at onboarding |
| Client cannot see what the post will look like | Send the post as it will render, per network, not as text in an email |
| No deadline | A fixed reply window, the same every week |
| Nothing happens when they are silent | A silence rule agreed in advance |
Fix the first two and most of the problem goes away. A client who receives one batch every Thursday, knows they are the one who decides, and knows the answer is due Monday at noon, behaves very differently from one who gets a trickle of "quick question" messages.
One batch, one approver, one deadline
The rhythm that works for most clients:
- Send on the same day every week. Thursday is good: it gives the client Friday and Monday to review, and you still have time before the following week starts.
- One approver. Others on the client's side may comment, but one person says yes. If two people genuinely both must approve (often marketing and legal), make it sequential and give each their own window.
- One deadline, stated in every batch. "Please approve or comment by Monday 12:00. Posts start going out Tuesday."
- Three possible answers per post. Approve, approve with a small edit (they write the change), or send back with a reason. Do not invite open-ended discussion inside the approval round; if a post needs a rethink, it comes out of this batch and into the next plan.
The batch itself should make approval easy. For each post: the date and time, the networks, the text exactly as it will appear on each one, and the image or video. If you send a link to a tool, check that the client can open it without a login they do not have.
Two ways to get client sign-off
There are two honest ways to run client approval, and the right one depends on how much access you are comfortable giving a client.
Option A: the client approves inside your tool. The client has their own login, sees the posts waiting for them, and approves or sends back each one. The record of who approved what lives next to the post. This is the cleanest flow when the tool's approver role gives the client only what they need. Check exactly what that role can do in your tool before you invite anyone outside your company; in some tools the role that can approve can also manage other settings.
Option B: your team approves inside the tool, the client signs off in writing. Your account lead is the in-tool approver. Every post a writer schedules is held until the lead approves it. The client reviews the batch (as a viewer with read-only access, or as a preview you send) and replies "approved" in writing. Only then does your lead release the posts. You keep the written sign-off with the batch.
Option B is more work for you, but it suits clients with many stakeholders, clients who do not want another login, and agencies that prefer not to give outsiders any write access. Whichever option you pick, write it into the onboarding page from lesson 1 so the client knows how sign-off works before the first batch arrives. Changing the approval method halfway through a contract confuses everyone, so choose once and review it only at renewal.
Whichever you choose, keep an internal review step too. Your own account lead reading every post before a client sees it catches most problems before they become client feedback.
What a useful review looks like
Clients are rarely taught how to review social posts, so their feedback is often vague ("can it be punchier?") or about the wrong level (rewording a sentence when the real objection is the topic). Help them with a short note at the top of the first few batches:
- Check facts first. Names, dates, prices, product details and links. These are the things only the client can verify.
- Then tone. Does it sound like us? If not, point to the line, not the whole post.
- Then topic. If the post should not exist at all, say so and say why; it comes out of the batch.
- Skip personal taste on small words unless it is in the voice guide. If it should be, tell us and we will add it.
When feedback comes back, answer every comment in the same place it was made, even if only with "done". A client who sees that every comment was handled stops writing long emails to make sure they were heard.
Multiple stakeholders need extra structure. If marketing and legal both review, legal sees only the posts that touch claims, prices or regulated topics, flagged by you. Everyone else's view is advisory, collected by the approver. One person still gives the final yes.
When the client goes silent
At some point a client will not answer by the deadline. Decide now, in writing, what happens then. There are three reasonable rules; pick one per client at onboarding:
- Hold. Nothing goes out without explicit approval. Safest, but the account goes quiet. Use this for regulated industries or anything legal-sensitive.
- Evergreen only. Posts labelled evergreen (lesson 2) go out as planned; anything time-sensitive, promotional or about people waits. A good default for most clients.
- Silence means yes. Everything goes out as planned after the deadline. Only with clients who have explicitly agreed to it in writing, and never for launches, prices or apologies.
Whatever the rule, send one reminder halfway through the window and one at the deadline, then follow the rule without arguing about it. If silence becomes a pattern (three weeks out of four), it is a conversation about scope, not about approvals: maybe the client needs a monthly batch instead of a weekly one.
Worked example: our own brand's approval flow
If we hired an agency, here is the approval setup we would ask for, based on how we work ourselves: nothing publishes without an explicit approval step.
Rhythm. One batch every Thursday covering the next week, deadline Monday 12:00, posts from Tuesday.
Approver. One person on our team approves; nobody else's comment counts as approval.
Silence rule. Evergreen only. Posts about our free tools and how-tos can go out; anything about a new feature or our pricing page waits for explicit approval, because a release post about something that has not shipped is worse than no post.
What the batch message looks like:
Batch for next week, 6 posts, approve by Monday 12:00.
1. Tue 09:00 - X, Bluesky - GIF support in the composer (thread)
2. Tue 14:00 - LinkedIn - same release, single post
3. Wed 10:00 - Instagram, Threads - free line breaker how-to
4. Thu 09:00 - Discord - weekly changelog note
5. Thu 15:00 - X - question to developers about posting from scripts
6. Fri 10:00 - LinkedIn - tag every link before you post
For each post: approve, approve with an edit, or send back
with a reason. Silence rule for this account: evergreen only
(3, 5 and 6 go out as planned; 1, 2 and 4 wait).
When the approver replies, the account lead confirms in one line which posts are released, which are edited and which moved to the next batch. That reply is the record. If anyone later asks why a post went out, the answer is a dated message, not someone's memory of a conversation.
The message tells the approver exactly what is being asked, by when, and what happens if they do not answer. That is the whole job of an approval message.
Recap
- Approvals stall because of random timing, unclear ownership, unrendered previews, no deadline and no silence rule.
- Send one batch on a fixed day, to one approver, with one deadline and three possible answers.
- Choose between client approval in the tool and written client sign-off after internal approval; check what the approver role can do first.
- Agree a silence rule per client at onboarding: hold, evergreen only, or silence means yes.
- Keep an internal review step either way.
Exercise
Write your approval packet
- Pick one client and write their approval terms in five lines: send day, approver, deadline, the three possible answers, and the silence rule.
- Take three posts from your next week's plan. For each, build a preview using the free Instagram post preview or the matching network's post formatter, such as the LinkedIn post formatter, so the client sees the post as it will appear.
- Write the batch message using the structure in the worked example, including which posts the silence rule would release.
- Send it to yourself first and check that a busy person could approve it from a phone in two minutes.
- Done looks like: a five-line approval terms note and a ready-to-send batch message with previews.
Go further
Require approval
In FoPost, turn on Require Approval in a brand's settings (open them from the brand switcher): posts scheduled by Members are then held until an Owner or Admin approves them, while posts scheduled by Owners and Admins are not held. Approvers review held posts in the Approvals tab of Posts, and a post sent back returns to drafts with the reviewer's reason; read the role descriptions in Team before deciding who approves. The agencies page shows how this fits with one brand per client.
Check yourself
1What are the two fixes that solve most stalled approvals?Show answer
One batch on a fixed day instead of a trickle of posts, and one named approver who has the final word.
2When does written client sign-off make more sense than in-tool client approval?Show answer
When the client has many stakeholders, does not want another login, or when the role that can approve in your tool would give them more access than you want.
3Which silence rule is a sensible default for most clients?Show answer
Evergreen only: timeless posts go out as planned, while anything time-sensitive, promotional or about people waits for explicit approval.
Keep reading, free
Tell us a little about you and the rest of this lesson, and every lesson in every course, opens on this device. No account and no card.