# A Client Approval Workflow That Doesn't Stall Your Content Calendar

_2026-09-30 · How agencies build client approvals that work: what needs sign-off, clear deadlines, approval links instead of email threads, and rules for silent clients._

Every agency knows the moment. The calendar is built, the videos are cut, the captions are written, and everything waits on "the approver" on the client side. A day passes, then another, and finally a message arrives at 10 p.m. with three changes, one of which contradicts what was agreed last week.

Client approval is a legitimate and necessary part of the work. The problem isn't approval itself. It's a process nobody defined. This article lays out an approval workflow that protects the client and their brand without holding the agency hostage.

## Why approvals stall

Usually it's not reluctance. Approvals stall because:

1. **It's unclear what needs approving.** The client gets a spreadsheet with forty posts and doesn't know where to start.
2. **Feedback is scattered across channels.** Some in email, some in chat, some on a call. Nobody knows which version is current.
3. **There's no deadline.** "Approve when you can" means "not now."
4. **There are too many approvers.** Everyone adds a comment, nobody decides.
5. **The client can't see the post as it will appear.** Copy in a doc and an image in a folder don't feel like a post, so it's hard to commit.

Each of these is a process problem, not a willpower problem.

## What the client should approve, and what they shouldn't

This is the most important question and the one least often asked. When an agency publishes to dozens of accounts, approving every post individually doesn't scale. Decide the level of approval up front.

### Three common approval levels

| Level | What gets approved | Best for |
|---|---|---|
| Campaign | Message, offer, CTA, core creative | Clients with many similar accounts |
| Weekly calendar | All posts for the week in one view | Mid-volume clients |
| Post by post | Every post individually | Sensitive or regulated industries |

For most lead-gen agency work, campaign-level approval is right: the client signs off on message and creative, and the agency owns the variations and per-account adaptation. Put this in writing at the start of the engagement.

### What always needs explicit sign-off

1. Prices, discounts and offer terms
2. Claims about results, quality or competitors
3. Images of real people, staff or customers
4. Content in regulated categories such as health, finance or real estate

## One approval link instead of a message thread

The single biggest improvement is getting approvals out of email and chat. A dedicated approval link, where the client sees posts as they'll actually appear, with the image or video, the caption and the scheduled date, changes the dynamic.

What it needs:

1. **A real preview** of the post, not copy separated from the media
2. **Approve and "needs changes" buttons**, with comments attached to the specific post
3. **No sign-up or password** for the client. Every extra step lowers the response rate
4. **An audit trail**: who approved, when, and which version

All feedback lives in one place, attached to the post it refers to, and there's no argument later about "but I told you."

## Deadlines that hold

An approval deadline isn't rude. It's the only way a content calendar survives contact with reality.

### A practical rule of thumb

1. **Send for approval**: at least three business days before the first post in the batch
2. **Approval cutoff**: one business day before publishing, at a set time
3. **Revision rounds**: one included; a second round moves the schedule accordingly

Every agency should tune these numbers. What matters is that they're written down, agreed and visible on every approval request.

## What happens when the client goes quiet

This is where most processes collapse. Decide in advance, and agree with the client, what happens when the cutoff passes.

Common options:

1. **The post doesn't go out.** Safest, but leaves accounts silent and hurts the campaign.
2. **The post goes out as is.** Only appropriate when the campaign was approved and the posts are variations of it.
3. **Pre-approved fallback content goes out instead.** "Evergreen" posts with no prices or claims that the client approved once for use as backup.

Option three is usually the best compromise. The calendar never goes empty, and the client is never surprised by content they haven't seen.

## One approver, not a committee

When five people on the client side comment on the same post, the agency ends up mediating between opinions. Ask the client to name one approver per account or account group, responsible for collecting internal feedback and returning one answer.

Other stakeholders can get the approval link to view, but the final call stays with one person.

## Checklist for setting up approvals

1. Approval level agreed in writing per client
2. Content types that always need explicit sign-off are defined
3. One approver per client or account group
4. Approval happens through a preview link, not in messages
5. Every approval request carries a clear deadline
6. A defined rule for what happens after the deadline
7. A bank of pre-approved fallback content
8. A record of who approved each version

## Wrapping up

A good approval process doesn't slow the work; it speeds it up. When it's clear what gets approved, where, by when and what happens without an answer, the client feels in control of their brand and the agency can plan weeks ahead. Most of the friction disappears once approvals leave the message thread.

With Shager you can send the client an approval link where they see posts as they'll appear and approve or request changes on each one, with no account needed. Posts wait for approval before going out to any account, and you keep a record of who approved what and when.

---
Source: https://shager.ai/en/blog/client-approval-workflow-for-agencies