Why social posts stall in approval, and seven fixes that work
Posts rarely stall because a client is difficult. They stall because nobody owns the decision, feedback is vague or reviews arrive one at a time. Seven practical fixes.
Every agency knows the feeling: the month is planned, the captions are written, the images are ready, and twelve posts are sitting in “waiting for approval” with the first one due tomorrow. It is tempting to blame a slow client. In practice, approval stalls almost always come from the process around the client rather than the client themselves. This post looks at the usual causes and seven fixes that make sign-off predictable.
The usual reasons posts stall
Before changing anything, work out which of these is happening. Most stalls have more than one cause.
- Nobody owns the decision. Posts go to “the marketing team” or a shared inbox, and everyone assumes someone else will reply.
- Too many approvers. Three people review, each changes something, and their changes contradict each other.
- Reviews arrive one post at a time. A busy client gets a request every day and starts ignoring them.
- No deadline. Without a date, review is always something for later.
- Vague feedback. “Not quite right” sends the post back, but nobody knows what to change, so it comes back for the same reason.
- Feedback in the wrong place. Comments arrive by e-mail, chat and phone, the writer misses one, and the post goes round again.
- The approver is reviewing the wrong things. They rewrite captions for style when the agency needed them to check a price.
Fix 1: name one approver and one backup
Agree a single named person who approves for the client, and one backup for holidays and sick days. Write both names into your onboarding notes. If other people (legal, a product team, a franchise owner) must see certain posts, agree which posts and route only those to them. One clear owner is faster than three cautious ones.
Fix 2: batch reviews into a weekly review day
Daily approval requests compete with everything else in the client’s day. A single weekly review session for the following week’s posts is easier to protect. Pick a day and time with the client, put it in both calendars, and send the batch the day before. Many clients find thirty minutes once a week much easier to give than five minutes every day.
Fix 3: set a deadline with a default
A deadline only works if everyone knows what happens when it passes. Agree a turnaround (for example two working days before the scheduled date) and a default. The safest default for most clients is that unreviewed posts move to the next free slot rather than going out unapproved. Write it down, so moving a post is an agreed rule rather than a judgement call.
Avoid defaults that publish unapproved posts automatically. They save time once and cost trust the first time a post goes out with a wrong price.
Fix 4: tell approvers what to check
Give approvers a short list of what only they can confirm:
- Facts: prices, dates, opening hours, product names and availability
- Claims: anything that promises a result, compares with a competitor, or mentions health or money
- People and permissions: tags, names, photos of customers or staff
- Brand: tone and words to avoid, and required disclosures for partnerships
- Accessibility: alt text on images, captions on video
When approvers know their job is to confirm facts and spot risks, they spend less time rewording sentences. Our printable approval checklist puts this on one page.
Fix 5: make “request changes” specific
Ask approvers to say what to change and why, in one or two sentences. “Change ‘from Friday’ to ‘from Saturday 12 October’, we open a day later” can be fixed in a minute. “Doesn’t feel right” can take three rounds.
You can help by making the request easy to answer. When you send a batch, flag any post where you need a decision (“Do you want the price in this post?”) rather than leaving the approver to spot the question.
Fix 6: keep feedback on the post
Feedback that lives on the post itself, rather than in e-mail threads, does two things. The writer sees it at the moment they edit the post, so nothing is missed. And there is a record of who approved what, and when, which matters months later when someone asks why a post went out. Screenshots in a chat are not a record.
Fix 7: separate routine posts from sensitive ones
Not every post needs the same scrutiny. A lighter rule for routine, evergreen posts (opening hours, recurring features) and full review for campaigns, offers and anything mentioning people can halve the number of posts waiting. Agree the categories with the client and review them after a quarter. Some clients start with approval for everything and relax it once they trust the process.
Measure where the time goes
If approvals still slow you down after these changes, look at the numbers you have. Which posts waited longest? Were they a particular type, or for a particular approver? How many went back for changes, and why? A quarterly look at this, shared with the client, usually points to one specific change rather than a general complaint.
Doing this in PostRoost
In PostRoost, approval is switched on per client: tick Posts need admin approval before publishing in the client’s settings. Writers press Submit for approval, without needing a date yet. Approvers (agency owners and admins, and the client’s own owner and admins) review under Approvals, where each post shows its image, caption, author and networks, and they approve, request changes with a note, or reject.
Anything sent back lands in the writer’s Actions list with the reviewer’s note, so feedback stays on the post. Approvers see the number of posts waiting next to Approvals in the sidebar when they sign in; there are no approval reminder e-mails, which is one more reason to agree a weekly review day. Client approvers sign in as client users and only ever see their own brand.
Approvals are included from the Team plan and on every agency plan. The full workflow is described on the approval workflows page, and our guide to setting up a client approval workflow covers turnaround times and roles in more depth.
A one-page summary for your next client call
- One named approver and one backup
- A weekly review day, with the batch sent the day before
- A turnaround, and a default that never publishes unapproved posts
- A short list of what approvers check
- Specific feedback, attached to the post
- Routine posts on a lighter rule, sensitive posts on full review
- A quarterly look at what waited and why
None of these fixes need new software or a difficult conversation. They need a short agreement, written down, that both sides can point to when the month gets busy.
