A social media approval workflow is one rule with software behind it: nothing publishes until someone other than the author signs it off. Everything else, the roles, the queues, the notifications, exists to make that rule survive a busy Friday afternoon.
Most teams discover they need one the expensive way. A typo goes out on the brand account. A scheduled post lands during a news event it should not have. A contractor publishes a client's campaign a week early. The instinct afterwards is to write a policy document, which nobody reads, instead of changing the mechanism, which everybody has to use.
This is how to build the mechanism, what it genuinely costs, and the three ways these workflows quietly fall apart.
Running this across many clients changes the process; our social media workflow for agencies maps it.
Our post approval workflow feature page covers how ours is built.
What an approval workflow actually is
Strip away the vendor language and there are only four states a post can be in: draft, awaiting review, approved and scheduled, and rejected with notes. A workflow is the set of rules that move a post between those states and the permissions that stop anyone skipping a step.
The important word is stop. A process where an editor is supposed to check posts but can be bypassed by anyone in a hurry is not a workflow, it is a habit. Real workflows are enforced by permissions: the author literally cannot publish, only submit.
That distinction decides which tool you need. Plenty of management platforms we have reviewed offer a shared calendar and call it collaboration. Far fewer make publishing a permission you can withhold.
The four roles every workflow needs
You can run an approval process with two people, but you need four roles defined even if one person wears several hats.
The creator drafts the post and submits it. They should not hold publishing rights on the accounts they write for. This is the whole point.
The reviewer checks the thing that matters most for your organisation. For a consumer brand that is tone and timing. For a clinic or a law firm it is factual accuracy and whether the claim is defensible. Reviewers need to reject with a reason, not just reject.
The approver holds publishing rights and takes final responsibility. In small teams the reviewer and approver are the same person. In regulated firms they must not be.
The admin manages who holds which role and which accounts each role covers. Getting this wrong is the most common cause of a workflow that "does not work": someone was quietly left with publishing rights and kept using them.
Assigning these roles per account rather than globally is what separates a workable setup from a frustrating one. A social lead might publish freely to the brand's own channels while still needing sign-off on a client's. Team workspaces exist to keep those permission sets apart.
How to set one up, step by step
1. Decide what actually needs approving. Approving everything is how workflows die. Most teams land on: all paid promotion, anything making a claim about the product, anything on a client account, and anything published during a live incident. Routine replies and evergreen reposts usually do not need a queue.
2. Separate the accounts. Connect each brand or client into its own workspace before you assign anyone. Retrofitting isolation after ten accounts share one space is painful. Our multi-account management guide covers the structure.
3. Remove publishing rights from creators. This is the step people skip because it feels like distrust. It is not: it is the only part of the setup that does any work. Every other step is bookkeeping.
4. Set the review window. Decide how long a reviewer has before a post is considered stale. Sprout, for instance, automatically rejects a message that is not approved before its scheduled send time, which is sensible but surprises teams the first time it happens.
5. Write the rejection convention. "Rejected" with no note is the fastest way to make creators resent the process. Agree that every rejection carries one line explaining what to change.
6. Test it with a real post. Submit, reject, revise, approve, publish. Ten minutes of rehearsal catches the permission mistakes that would otherwise surface during a campaign.
Want approvals without agency pricing? PostEverywhere's team workspaces give every plan from Starter up role-based permissions, so a reviewer can hold sign-off without the enterprise contract. See plans.
What it costs: the seat maths nobody mentions
Here is the part vendors bury, and it is the single biggest reason small teams give up on approvals.
An approval workflow needs at least two seats. One person cannot approve their own post. So the real question is not "does this tool have approvals" but "what is the cheapest plan that includes two users and the approval feature". Those are frequently different plans.
Hootsuite's content approval is not available across the board: it sits on Advanced with multiple users, Business and Enterprise plans, and Super Admins can configure up to three layers of sign-off. Sprout Social puts Message Approval Workflows on Professional and Advanced, and reserves external approvers, up to three of them, for Advanced only. Per-seat pricing then multiplies: a three-person team on a per-user plan pays three times over for a feature only two of them use.
For comparison, PostEverywhere bundles seats into the plan rather than charging per person. Lite at $9/month is a single seat, so it cannot run an approval loop by definition. Starter at $19/month includes 2 seats, which is the genuine floor for approvals. Growth at $29/month gives 3 seats and 10 connected accounts, and Scale at $39/month gives 5 seats, 20 accounts and 5 workspaces. Roles and permissions are available on every plan from Starter upward. Every plan includes a 7-day free trial, a card is required to start it, and there is no permanent free plan.
The point is not the price. It is that you should work out your seat requirement first, then compare plans, because the feature tier and the seat tier rarely line up.
Approval in regulated industries
If you work in finance, healthcare or law, an approval workflow is not a nicety, it is the control that evidences supervision.
FINRA's rules are the clearest published example. Under Rule 2210, retail communications generally require a registered principal's approval before use, and FINRA draws a sharp line between static content, which a principal must review in the form it will be launched, and interactive content, which does not require pre-approval provided it is supervised like correspondence. Regulatory Notice 17-18 sets out how that supervision must work in practice: training, surveillance to test compliance, defined actions when problems are found, and documentation of findings and corrective steps.
Two practical consequences follow. First, your tool needs an audit trail, not just a button: who submitted, who approved, when, and what changed between versions. Second, the approver must be a different person with the appropriate authority, so "the marketing manager approves their own drafts" fails the test regardless of what the software allows.
Similar logic applies without the regulator. Clinics reviewing patient-adjacent claims and firms reviewing legal commentary are solving the same problem, which is why our guides for advisers and financial firms, clinics and legal teams all start from the review step rather than the content calendar.
Where approval workflows go wrong
The bottleneck of one. A single approver who also has a day job becomes the reason nothing ships. Name a deputy from the start and give them the same rights. Most teams add this only after missing a launch.
Approving everything. If routine posts sit in a queue behind campaign work, people start scheduling around the system. Scope the workflow to what carries risk and let the rest flow.
Silent rejection. A rejection with no explanation costs the creator a guess and a resubmission. It is the fastest route to a process everyone resents.
Approval theatre. The worst failure, because it looks like success: approvers click through without reading because the queue is long and the deadline is close. If your approval rate is effectively 100%, the control is decorative. Shrink the queue until reviewing is genuinely possible.
Running client accounts? Keeping each client in an isolated workspace with its own reviewers is the difference between an agency workflow and a shared inbox. See PostEverywhere for agencies or compare what agencies actually use.
How the major tools compare
The differences that matter are fewer than the feature lists suggest: how many approval layers, whether external clients can approve without a paid seat, whether permissions are per account, and what it costs to get two people in the room.
Hootsuite supports up to three approval layers and mobile approvals, but gates the feature to its higher tiers. Sprout Social offers multi-step workflows with external approvers on Advanced. Planable and Kontentino are built around client sign-off specifically, which suits agencies whose clients want to approve in a familiar interface. Loomly and HeyOrca sit in similar territory with per-calendar or per-user pricing that scales with client count.
If you are moving off an enterprise tool primarily because of cost, our side-by-side on the enterprise incumbents covers where approvals land on each option. For the full side by side, see the best social media approval workflow tools.
Frequently asked questions
What is a social media approval workflow?
It is a process where posts must be reviewed and approved by someone other than the author before publishing. Permissions enforce it, so creators can submit but not publish.
How many people do you need for an approval workflow?
At least two, because nobody can approve their own post. That means any plan with a single user seat cannot run approvals, whatever its feature list claims.
Does Hootsuite have approval workflows?
Yes. Hootsuite supports up to three layers of approval, but the feature is limited to Advanced plans with multiple users, Business and Enterprise, rather than being available on every tier.
Can clients approve posts without paying for a seat?
It depends on the tool. Sprout Social allows up to three external approvers on its Advanced plan. Several agency-focused tools include client review by design, which is usually cheaper than buying client seats.
What happens if a post is not approved in time?
That varies by tool and is worth checking. Sprout automatically rejects messages not approved before their scheduled send time, so the post does not go out late by surprise.
Do approval workflows slow teams down?
Only when they are scoped badly. Approving everything creates a queue people work around. Approving paid promotion, product claims and client accounts keeps the volume reviewable.
What does an approval workflow cost?
Budget by seats first. Approvals need two or more users, and on per-seat tools the second user often costs as much as the first. Bundled-seat plans start lower: PostEverywhere includes 2 seats at $19/month and 5 at $39/month.
Is an approval workflow required for compliance?
In regulated sectors, supervision is. FINRA requires principal approval for static retail communications and documented supervision for interactive ones, which in practice means you need an audit trail of who approved what and when.
The bottom line
An approval workflow is cheap to describe and easy to get wrong. The parts that matter are the ones teams skip: taking publishing rights away from creators, naming a deputy approver, scoping the queue to what actually carries risk, and insisting that rejections come with a reason.
Work out your seat count before you compare feature tables, because that is where the real cost sits. And if your approval rate never drops below 100%, you do not have a control, you have a formality.
Ready to put a reviewer between draft and publish? Start a 7-day free trial with role-based team workspaces included from Starter up. A card is required to start, and you can cancel any time before the trial ends.
Founder & CEO of PostEverywhere. Writing about social media strategy, publishing workflows, and analytics that help brands grow faster.