Client Content Approval: A Workflow That Doesn't Hold Up Publishing
Paul Boards ·
A content approval workflow that doesn't hold up publishing has four elements: the client sees the post exactly as it will go out, approves it in one place, has a deadline to respond and knows what happens if they don't. When approval depends on a PDF by email and an “OK” on WhatsApp, the post sits waiting for someone to find the latest version.
Below is a workflow template that agencies and marketing teams can copy, with deadlines, statuses and agreements, and how it works in the Scrumboards content calendar, which has post previews and per-client approval.
Where approval usually gets stuck
- Wrong version. The client approves Tuesday's file, but the team had already sent Wednesday's.
- Scattered feedback. Half the edits come by email, the other half by voice message.
- Unclear approver. The marketing manager approves, the business owner sees it in the feed and asks for it to be taken down.
- No deadline. The holiday post arrives for approval the day before.
- Batches that are too big. Thirty posts at once make the client put everything off.
The five-step workflow
1. Content plan approved before production
At the start of the month, approve the topics, dates and formats. Tweaking a line in the plan takes minutes. Redoing finished artwork takes hours. In Scrumboards, the plan goes into the client's content calendar and each post becomes a task with a due date.
2. Internal review with a checklist
Before it goes to the client, someone on the team checks spelling, branding applied per the Brand Kit, the right size for the network, links and hashtags. A checklist in the task template keeps the client from becoming the proofreader.
3. Send in small batches, with previews
Send for approval in weekly batches. Clients approve better when they see the post as it will appear, with image and caption together. The Scrumboards calendar shows a preview of each post per client, so the client can look at the whole week at once.
4. Response recorded on the post itself
Approvals and change requests are recorded on the post, along with the version they refer to. When the task goes back from “With client” to “Changes,” the status history keeps track of it. At the end of the month, the revisions report shows how many posts needed more than one round.
5. A rule for silence
Agree in the contract on what happens when the client doesn't respond by the deadline. The most common options:
- The post is rescheduled for the next open date.
- The post goes out as is, if it's routine content already approved in the plan.
- Campaign posts or posts with pricing never go out without explicit approval.
Build next month's calendar with previews from the start. Add the client, upload the Brand Kit and put the plan on the calendar. Create your client's approval calendar on the Free plan.
Deadlines that work in practice
| Step | Suggested deadline | Who |
|---|---|---|
| Monthly content plan approval | By the 25th of the previous month | Client |
| Weekly batch sent | Monday of the week before publishing | Agency |
| Client response | 2 business days | Client |
| Edits | 1 business day per round | Agency |
| Rounds included | Set in the contract, for example two | Both |
These deadlines are a starting point. Adjust them to the client's pace and put them in the contract, because a deadline agreed only verbally turns into an argument at the first delay.
Statuses that make the calendar readable
With clear statuses, anyone can look at the calendar and understand where each post stands:
- Planned
- In production
- Internal review
- With client
- Changes
- Approved
- Scheduled or published
In Scrumboards, statuses are customizable, so you can use the names your team already uses.
Who approves on the client side
Many revisions come from the wrong approver. The marketing analyst approves, the director sees the published post and asks for it to be taken down. To avoid this, define at the start of the contract:
- A primary approver, responsible for routine content.
- A campaign approver, for anything involving pricing, promotions or sensitive topics.
- A backup for vacations and travel, with the same decision-making authority.
Record these names in the client profile in Scrumboards, along with the Brand Kit and brand voice. That way, anyone joining the team knows who to send each batch to.
How to write feedback that's actually useful
A comment like “I don't like it” leads to a whole round of guesswork. In the first month, it's worth coaching the client to point out three things in every change request: what to change, where the problem is in the post and an example of what they expect. On the agency side, whoever receives the change request summarizes it on the task in one sentence before starting. If the summary is wrong, the client corrects it right there, before anyone spends an hour redoing the artwork.
One simple rule also helps: a new change that comes up after approval counts as a new round. This needs to be in the contract, and the status history shows when each approval happened.
How AI helps without bypassing approval
BrainPilot agents speed up production, but people still make the decisions. ORION writes first drafts of captions based on the brand voice saved in the client profile. PIXEL creates artwork with editable layers. POLARIS builds the monthly report with what was published. Internal review and client approval stay in the workflow just the same.
A month with this workflow
An agency serves a restaurant with 12 posts a month. On the 22nd, it sends the plan: four dish posts, two behind-the-scenes, two event posts and four promotions. The restaurant cuts one event and approves on the 24th.
Every Monday, the agency sends the following week's three posts for approval on the calendar. The owner checks the preview on his phone and approves two. For the third, he asks for a different photo. The task moves to “Changes,” comes back the next day and gets approved.
At the end of the month, the restaurant's monthly report, sent through a link that opens without a login, shows 11 posts published, one rescheduled due to no response and two revisions. The renewal conversation starts from those numbers.
Frequently asked questions
How many revision rounds should the contract include?
Two is a common number. What matters is writing down the limit and what happens after it.
Does the client need to approve post by post?
It works better in weekly batches, with previews of all the week's posts together.
What should I do when the client goes silent?
Follow the agreed rule: reschedule, publish routine content already approved in the plan, or hold anything involving pricing or campaigns.
Can I see how many revisions each client requests?
Yes. In Scrumboards, the status history feeds the revisions report by client.
Does the preview show the post as it looks in the feed?
The content calendar shows a preview of each post with image and caption, separated by client.
Start with next month
Don't try to change the current month midway. Use the workflow for next month's plan, with one or two clients. See how the content calendar and reports work, compare the available plans and explore everything Scrumboards offers.