A social media approval workflow is the set of steps a post goes through between draft and publishing: who writes it, who reviews it internally, who signs it off on the client side, by when, and what happens if something changes after approval. For agencies, the workflow that works is short and explicit: one draft per post, one named approver per client, a fixed deadline before publishing, and a rule that approved posts are only changed with a new approval. Everything else is tooling.
This guide lays out the stages, how to set approval levels per client, the deadlines and rules to agree in your contract, how AI drafts fit in, and how to run it in a scheduler.
Key takeaways
- Most approval delays come from unclear ownership, not from slow clients. Name one approver per client.
- Not every client needs to approve every post. Set an approval level per client: every post, campaigns only, or none.
- Agree an approval deadline (for example 48 hours before publishing) and what happens when it passes.
- Keep a single, visible status per post: draft, pending approval, scheduled, published.
- If you use AI to draft, AI-created posts should always land in pending approval, never straight on the calendar.
Why agencies need a formal approval process
With one client, approvals happen informally: a message, a thumbs up, done. With ten clients and several posts a day each, informal approval breaks. The symptoms are familiar:
- Feedback in five places (email, WhatsApp, Slack, comments on a doc, a call).
- Two versions of the same post, and nobody knows which one was approved.
- Posts going live late because the approver was on holiday.
- A post published that the client never saw, and an awkward call afterwards.
A written workflow fixes this by making three things explicit: the stages, the people and the deadlines.
The six stages of an agency approval workflow
| Stage | Who | Output | Status in the calendar |
|---|---|---|---|
| 1. Plan | Account lead + client | Monthly themes, key dates, campaigns | None yet |
| 2. Create | Copywriter, designer (or AI + editor) | Draft post with copy and media | Draft |
| 3. Internal review | Account lead or editor | Checked for facts, tone, limits, brand rules | Draft |
| 4. Client approval | Named client approver | Approved or change requests | Pending approval |
| 5. Schedule | Account lead | Post set for date and time | Scheduled |
| 6. Publish and monitor | Community manager | Live post, replies handled | Published |
Internal review before the client sees anything is the stage agencies skip most, and it is the one that protects the relationship. Clients should review content, not typos.
Set an approval level per client
Treating every client the same wastes time on both sides. Agree one of three levels at onboarding and write it in the contract:
| Level | What the client approves | Best for |
|---|---|---|
| Full approval | Every post | Regulated industries, new clients, sensitive brands |
| Campaign approval | Monthly plan and campaign posts; evergreen posts go out after internal review | Established clients with a clear brand guide |
| Plan approval only | The monthly plan; the agency publishes within it | Long-term clients with high trust |
Move clients between levels as trust grows. A new client might start at full approval and move to campaign approval after two or three months without issues.
Agree deadlines and rules in writing
The workflow needs a few rules both sides sign off on:
- Approval deadline. For example: posts are sent for approval at least five working days before publishing, and the client replies at least 48 hours before.
- Silence rule. What happens if the client does not reply by the deadline: the post is postponed, or it goes out as planned. Both are valid; ambiguity is not.
- Rounds of changes. How many revision rounds are included per post (one or two is common).
- Change after approval. An approved post is only edited with a new approval, except for typos.
- Urgent posts. Who can approve same-day posts and through which channel.
- Single channel for feedback. All feedback in one place, so there is one source of truth.
How to run the workflow in a scheduler
The calendar should be the single source of truth for status. Here is how it maps in Postika.
One project per client
Each client gets a project with its own channels, calendar and time zone. Dates in a project are in its local time, so a post at 9:00 for a client in New York goes out at 9:00 in New York, whichever office scheduled it. Every Postika plan includes unlimited projects, and pricing is by connected channels, not by seats (Standard €29/month for 5 channels up to Ultimate €99/month for 100; see pricing).
Statuses as the workflow
Posts move through draft, pending approval, scheduled and published. Pending approval is the gate: nothing in that state is published until someone approves it in the app. In the weekly or monthly calendar you see at a glance which posts are still waiting.
Preview and limits before the client sees it
Each post is previewed per network with its own format and limit, and Postika checks those limits before scheduling: X at 280 characters, LinkedIn at 3,000, Instagram at 2,200 with media required, and so on. That removes a whole category of internal review comments.
Getting the client's sign-off
Be clear about one thing: Postika does not have client approval links or client portals. The approval in Postika happens in your team's account. For client sign-off, agencies typically use one of these:
- Weekly review call or message: share the week's previews from the calendar (screenshots or a short screen recording) and collect approvals in one thread. Then approve the posts in Postika.
- Approval document: a shared doc per month with each post's copy, media and date; the client marks each one as approved or with changes.
- Plan-level approval: for trusted clients, approve the monthly plan and let internal review handle individual posts.
Whatever you choose, record the approval (date and who) in the same place every time.
Where AI fits in an agency workflow
AI can take most of stage 2 (create) off your team. With an AI assistant connected to Postika through MCP, a copywriter or account lead can ask:
In the Client-Acme project, draft next week's posts following the plan: LinkedIn Monday to Friday, Instagram Tuesday and Thursday. Leave everything pending approval at 10:00.
The AI checks what is already scheduled, writes the posts and puts them in the calendar. By default, Postika's MCP server tells the AI to prefer approval, so AI drafts land as pending approval and cannot go live on their own. Since photos and videos cannot be sent over MCP, Instagram and TikTok posts wait for your designer to attach media in the app.
Two rules make AI safe in an agency:
- AI drafts always go through internal review. The AI is a writer, not an approver.
- One project per client. The AI works inside the project you name, so channels and calendars do not mix.
You can connect Claude, ChatGPT, Claude Code, Cursor, Gemini CLI or VS Code; setup steps are on the AI integrations page. For the full method, read how to manage social media with AI.
A weekly rhythm for an agency team
| Day | Task |
|---|---|
| Monday | Draft next week for all clients (team or AI); internal review |
| Tuesday | Send previews to clients for approval |
| Wednesday-Thursday | Collect feedback, one revision round |
| Thursday | Approve in the calendar; posts become scheduled |
| Friday | Check every client's next week is scheduled; chase late approvals |
| Daily | Publish, monitor and reply in each network |
Plan the monthly calendar in the last week of the previous month, so campaign posts and key dates are approved at plan level before weekly production starts. Our guide to building a social media content calendar covers the planning side.
What to send the client for approval
What you send changes how fast and how well the client approves. A bare list of captions in an email invites vague feedback; a clear package gets a yes or a precise change. For each post, include:
- The network and the date and time, in the client's time zone.
- The final copy, exactly as it will appear, not a summary.
- The media, or a clear placeholder if the photo or video is still in production.
- The preview for that network, so the client sees where the caption is cut and how the image is cropped.
- The link, if any, with the destination page.
- One question, if you need a decision. "Shall we mention the discount code or keep it for the newsletter?" is easier to answer than "Any thoughts?"
Group posts by week, not by network. Clients think in campaigns and dates, and a week view makes it easy to spot two similar posts on the same day. Ask for approval per post (approved or changes) rather than a general "looks good", so there is no ambiguity about what was signed off.
Common approval problems and fixes
| Problem | Fix |
|---|---|
| Client approves late | Written deadline plus a silence rule |
| Feedback in many channels | One feedback channel per client, written in the contract |
| Too many revision rounds | Include one or two rounds; extra rounds are billable |
| Posts changed after approval | "New edit, new approval" rule; keep one version per post |
| Several people on the client side give contradicting feedback | One named approver who consolidates feedback |
| Internal team skips review | Make pending approval mandatory for every new post |
Approval workflow checklist for new clients
- Approval level agreed (full, campaign, plan only).
- One named approver and a backup.
- Approval deadline and silence rule in the contract.
- Number of revision rounds included.
- One channel for feedback.
- Brand guide and banned topics shared with the team (and in your AI brief).
- Client project created with its channels and time zone.
- First month at full approval, then review the level.
If you are choosing tools for an agency, see Postika for agencies and the glossary entry on approval workflows.
FAQ
What is a social media approval workflow?
It is the sequence of steps a post follows from draft to publishing, including who reviews it, who approves it and by when. For agencies it usually includes internal review and client approval before scheduling. A clear workflow prevents unapproved posts going live and reduces back-and-forth.
How do agencies get client approval for social media posts?
The most common methods are approval features inside a social media tool, a shared approval document or a weekly review message with previews. Whatever the method, the key is one named approver, a deadline and a single place for feedback. In Postika, approval happens in the agency's account, so client sign-off is collected outside the app and then the posts are approved in the calendar.
Should clients approve every social media post?
Not always. Regulated or new clients often approve every post, while established clients can approve the monthly plan and campaigns only. Setting an approval level per client saves time for both sides and can be revisited as trust grows.
Can AI-generated posts skip approval?
They should not. AI drafts need the same internal review as any other post, and client approval where the client's level requires it. In Postika, posts created by an AI through MCP wait as pending approval by default, so nothing publishes until a person approves it.