A social media approval workflow clients actually follow

Most approval problems are not about the client being difficult. They come from a process that was never designed: a PDF of next week's posts sent by email, a "looks good" on WhatsApp, a voice note asking to change "the second one", and a forwarded thread where the marketing manager and the owner disagree about the same caption. By Thursday you are publishing from memory and hoping.

A workflow fixes that. Here is one that works for freelancers and small agencies, with a timeline, a message you can copy and a clause for your contract.

Why email and WhatsApp approval chains fail

Chat and email are fine for conversations. They are poor at decisions, for four reasons.

Versions drift. The client approves post-3-final.jpg, you fix a typo, and now there is post-3-final-v2.jpg. Which one did they approve? Nobody can say for certain, and the thread does not help.

Feedback scatters. One comment arrives by email, one in a voice note, one during a call. Every round, you rebuild the full picture by hand, and the comment you miss is the one the client remembers.

"OK" is ambiguous. "Looks good" sent at 22:40 under a batch of twelve posts could mean all twelve, the last one they opened, or "I haven't really looked but I trust you". You only find out which after something goes live.

There is no deadline, so silence wins. Without a date on the request, the batch sits in an inbox until the day before publishing, when the client finally opens it and asks for a new photo shoot.

There is a fifth, quieter problem: clients often approve a caption pasted into a document, not the post as it will appear. They never see the crop, the first line that shows before "more", or the shorter version you wrote for X.

What a good approval workflow looks like

One link per batch, not one message per post

Send the week (or the month) as a single batch the client can open in one place, ideally showing each post as it will be published: media, caption, network, date and time. One link means one place to look, one place to comment and one record of what was decided.

A decision per post

Ask for a clear decision on every post: approved, or changes requested with a comment. "Approve all" is convenient but encourages skimming. A per-post decision makes the client look at each one, and gives you an unambiguous record later.

A deadline on every round

Put the deadline in the request itself, not in your head. A weekly rhythm that works for most small clients:

For monthly batches, send by the 20th with a deadline five working days later. Leave at least one full working day between the deadline and the first publish date, so a late "small change" never becomes a weekend job.

One person with final say

Ask at onboarding: who approves? Get a name, not a department. Other people at the client can comment, but one person decides, and if two stakeholders disagree, that person settles it before the deadline. This single rule removes a lot of contradictory feedback.

Some clients do not get to choose. A US broker-dealer, for example, generally needs a qualified registered principal to approve each retail communication before it is used, and the exceptions (such as posts in interactive online forums) must still be supervised and reviewed, under FINRA Rule 2210. With regulated clients (finance, health, legal), ask early who has to sign off and how long it usually takes, then build that time into your calendar.

Two revision rounds, then a call

Agree on a number of revision rounds per batch (two is common) and write it into your proposal. A third round on the same post is usually a sign that the brief is unclear, not that the caption is wrong. Pick up the phone, fix the brief, and save both of you a week of comments.

A client points at a post preview on a tablet while their social media manager notes the change, the kind of feedback that belongs in one place.

If you work in Julexis, this is what its review link does: the client opens a private link with a password you set, without needing a Julexis account, and approves each post or requests changes on it. You get one summary notification when they finish their round, not an alert for every click. The review link is on the SMM and Agency plans; see the features.

What "approved" means, and what silence means

Write down what approval covers. A useful definition: the client confirms the copy, the visuals, the networks and the publishing date of that post. After that, any change is a new request you will handle if time allows. Approval does not cover how the post performs or what a platform decides to do with it.

Silence is the harder part. In most legal systems, not answering is not the same as saying yes. The UNIDROIT Principles of International Commercial Contracts, a reference text for cross-border contracts, put it in one sentence: "Silence or inactivity does not in itself amount to acceptance" (Article 2.1.6). So if you want "no reply by the deadline" to mean "go ahead", agree on that in writing before the work starts, not in the reminder email.

You have two sensible options, and many agencies use both:

• Deemed approval for routine content: evergreen tips, behind-the-scenes posts, reposts of approved material. No answer by the deadline means you publish as planned.
• Hold for sensitive content: prices, promotions, legal or health claims, anything that names or shows a person, and anything tied to news. No answer means it does not go out, and you tell the client which slot it missed.

Whichever you choose, keep the record: who approved what, and when. If a post is ever questioned, that record is your answer.

A message to send with each batch

Keep it short and specific. Something like:

Hi Marta,

Next week's posts are ready for your review: 9 posts across Instagram, Facebook and LinkedIn, Monday 2 to Sunday 8 November.

Link: [review link]

For each post, please choose Approve or Request changes and leave a comment if something needs fixing. Feedback by Wednesday at 17:00, please, so we can schedule everything on Friday.

As agreed, routine posts without feedback by the deadline will go out as planned. The two promotional posts (Thursday and Saturday) will only go out once you approve them.

Thanks, Luca

It names the deadline, the scope, what silence means and which posts need an explicit yes. The client does not have to reread your contract to know what happens next.

A sample approval clause for your contract

Adapt this with a lawyer in your country; it is a starting point, not legal advice.

Content approval. The Agency will send scheduled content to the Client for review in batches, at least five (5) working days before the first publishing date in each batch. The Client's designated approver is [name, role]. The Client will approve each item or request changes within three (3) working days of receiving the batch. Each batch includes up to two (2) rounds of revisions; further rounds are billed at the hourly rate in Schedule A.

Items marked as routine that receive no response within the review period are deemed approved and may be published as scheduled. Items marked as requiring explicit approval (including promotions, prices and claims about products or services) will not be published without the Client's written approval.

Approval confirms the text, media, channels and publishing date of each item. Changes requested after approval are treated as new requests and handled subject to availability. The Agency is not responsible for the timing or outcome of content held because of a late response.

The awkward cases

The change after approval. It will happen. Treat it kindly but as a new request: "Happy to update it. It's scheduled for 9:00 tomorrow, so I'll move it to Thursday to make sure it's right."

Reactive posts. News, a viral moment, a local event. Agree in advance on a fast lane: a short list of post types that can be approved within two hours by message, with the same approver.

Too many cooks. If feedback arrives from three people, reply to all with one line: "Thanks, I'll wait for Marta's final decision on these." Then wait.

The client who never answers. Look at the pattern after a month. If deemed approval covers most posts, it is working. If everything ends up on hold, schedule a fixed 15-minute review call each week instead: some people decide better live.

If you run several clients on this rhythm, stagger their deadlines so you are not chasing everyone on the same Wednesday. We cover the weekly planning side in how to manage social media for multiple clients.

Key takeaways

• Send one link per batch, showing each post as it will be published, and ask for a decision on every post.
• Put a deadline in every request and keep one full working day between the deadline and the first publish date.
• Name one approver, agree on two revision rounds, and switch to a call when a third round starts.
• Silence is not approval by default: if you want deemed approval for routine posts, write it into the contract first.
• Keep a record of who approved what and when; it settles most disputes before they start.

Cover image generated with AI.