Approval processes have a bad reputation, and mostly they earned it. The typical version is a chat thread where someone pastes a draft, three people say "looks good" without reading it, and the post goes out a day later than it needed to. Nobody was protected; everybody was delayed.

That is not an argument against approvals. It is an argument against approvals applied everywhere by default. Used selectively, a sign-off step is the cheapest insurance a social team can buy — the cost of one wrong post is a legal letter, a corrections cycle or a client conversation, and none of those cost less than thirty seconds of review. This guide covers when the step is justified, what it should actually contain, and how it runs inside PostHub without becoming a bottleneck.

When you actually need approval

Ask one question: what is the realistic worst case of a post going out unreviewed, and what does it cost? If the answer is "someone mildly disagrees", you do not need an approval step — you need a clearer brief. If the answer involves any of the following, you do.

Regulated claims. Pricing, health, financial, legal or performance claims. A number that is wrong by a decimal place is a correction; a number that is wrong in a regulated category is a liability.

Client or stakeholder work. When someone else's name is on the account, "they approved it" is the difference between a normal week and a difficult conversation. External stakeholders do not need edit access; they need a visible yes or no.

New or junior authors. Not because juniors write badly, but because nobody has yet seen what they write when nobody is watching. Three reviewed posts establish a pattern; thirty unreviewed ones establish a habit.

News, incidents and anything time-sensitive. The posts most likely to need review are the ones with the least time for it, which is exactly why the process has to exist before the incident rather than during it.

Shared accounts with multiple publishers. Once more than one person can press publish, a review step is the only thing that makes "who sent this?" answerable.

If none of those apply, skip it. A one-person account with a clear voice brief is faster and no less safe without a review queue.

How many steps, and who signs off

One. That is almost always the correct number. Two-step approval — editor, then manager, then director — is the version that turns a thirty-second review into a two-day delay, and it usually exists because nobody was willing to decide who owns the final call.

Decide that explicitly instead: one named approver per group of accounts, with a named backup for when they are away. If a post genuinely needs two perspectives, they should be looking at the same review, not queued one after the other.

Roles make this enforceable rather than cultural. In PostHub the workspace has five of them, and the approver role is deliberately narrow:

• Owner — everything, including billing and deletion.
• Admin — members, settings and all content.
• Editor — create, edit and schedule posts.
• Approver — review and approve posts, no editing.
• Viewer — read-only access to the calendar and posts.

The approver role is the interesting one: someone can hold sign-off without being able to rewrite the post. That separation is what makes review honest — the reviewer is judging the work, not quietly replacing it. Invitations, role changes and removals all happen in the organisation members screen, so the person who leaves the company loses their sign-off the same day their access is removed.

What the review should contain

A review is a decision, not a discussion. Four questions, in this order, take about thirty seconds and catch almost everything:

• Is it true? Every claim, number, name and link. This is the one that actually causes incidents.
• Is it on-brand? Voice, terminology, what the brand does and does not say. Read the first line aloud; if it sounds like a different account wrote it, send it back.
• Is it right for this destination? First line, length, crop, CTA and link placement for the specific platform, not the generic version.
• Is it safe? Media rights, people's faces, confidential information in a screenshot, anything that should not be public yet.

Anything that fails goes back with a specific instruction — "the 40% figure needs a source, otherwise cut the sentence" — not "can you reword this?". Vague feedback is what makes review rounds multiply, and the team approval workflow guide covers writing feedback that shortens the next round.

What the queue looks like in practice

Inside PostHub the flow is deliberately plain. A draft or scheduled post that needs sign-off lands in the approvals screen as a review queue. Pick an item and a proof sheet opens beside it — the post as it will actually render, with its author, status and destination accounts. The action bar carries three decisions: approve, reject, or request changes.

Two details matter more than they look:

• Approve publishes. Pressing approve is not a status update — it runs the same path as Post now, so the decision and the publish are one action rather than a decision followed by somebody remembering to schedule it.
• Every decision is recorded. Approve, reject and request-changes are written to the workspace's approval history, so they survive a redeploy and are shared with teammates. "Did anyone sign this off?" becomes a lookup rather than a memory test.

The workspace settings decide how much ceremony surrounds that queue. You can send approval requests by default so nothing publishes unreviewed, allow guests to approve — useful when the person who must sign off is a client rather than a teammate — lock posts after approval so an approved post cannot be quietly edited before it ships, and allow self-approval for the cases where one person wears both hats. Each group of accounts can override those settings, which is how a regulated client's accounts run strict review while your own brand account runs without it.

Where approvals break

The failure modes are predictable, and every one of them is a design choice rather than a personality problem.

• The approver becomes a bottleneck. One person, no backup, and everything waits for their Thursday. Fix: name a backup approver and set an expectation — reviewed within one working day, or the post moves to the backup.
• Approval happens after scheduling. The post is already in a slot, so review becomes a panic. Fix: send to review when the draft is finished, before a slot is assigned.
• Everything is approved. When all posts need sign-off, review becomes a rubber stamp within two weeks. Fix: restrict approval to the accounts where the downside is real, using per-group settings.
• Review becomes an editing session. Endless rewrites in the proof sheet mean the brief was wrong, not the draft. Fix: send substantive changes back as instructions and let the author make them.
• Nobody knows who is waiting on whom. Fix: the queue and the history are the answer — if it is not in one of those two lists, it is not waiting on anybody.

Where PostHub fits, and where it does not

PostHub provides the mechanics: a review queue, a true preview of each destination, three explicit decisions, a durable history, and workspace settings that control default requests, guest approval, post-locking and self-approval — all overridable per group. Roles enforce who may decide, and the approver role allows sign-off without edit rights.

What it does not do is the judgement. It cannot tell you that a pricing claim needs checking against the current price list, that the client prefers British spelling, or that the person in the photograph has not consented to being in a campaign post. It also does not chase a reviewer who has been offline for three days — the queue shows what is pending, but escalating it is still your process. Approvals work when the four review questions are written down somewhere the team can find them; the queue is only the delivery mechanism.

Getting started without over-engineering

Start narrower than you think. Pick the single account where a bad post would hurt most, turn on default approval requests for that group only, and run it for two weeks. Read the history: if every post sailed through with no changes, either the brief is working or nobody is actually reviewing — the two look identical from outside, so ask.

Then extend to the next account only if the first one produced at least one real catch. An approval step that has never caught anything is a delay with a nice name, and it should be removed or its scope narrowed until it is doing work.

Key takeaways

• Approvals justify themselves when the downside is regulated claims, client work, junior authors, incidents or shared accounts — not when someone merely disagrees.
• One named approver plus one backup. More steps than that turn a thirty-second decision into a delay.
• Review answers four questions: is it true, on-brand, right for this destination, safe.
• Approve should publish, and every decision should be recorded where the whole team can see it.
• Scope approval to the accounts where the risk is real; universal approval becomes a rubber stamp.

FAQ

Does an approval step slow publishing down?

It adds one handoff when it is designed well — a single approver with a one-working-day expectation. It removes far more time than it costs by preventing the correction cycle that follows a bad post, which takes days rather than minutes.

Can a client approve without getting access to everything?

Yes. Guest approval lets an external stakeholder make the decision without a full seat or edit rights, and per-group settings mean their accounts can require sign-off while the rest of your calendar publishes normally.

What happens to an approved post if someone edits it afterwards?

That is what locking after approval is for. Turn it on and an approved post cannot be quietly changed before it ships, so the thing that was reviewed is the thing that publishes. If your process allows late edits, expect review to mean less over time.

How does this connect to scheduling and roles?

Approval sits before the slot, not after it: draft, review, then schedule. The first post guide walks the whole sequence, and roles are managed alongside the rest of the workspace in the account access guide.