Guides

Client approval workflow for social media: five steps

Get client approval by agreeing the rules first, then sending each reviewer one link with a deadline. Show every post as it will publish, collect feedback in one place and record each decision. A weekly rhythm works for most clients: you draft Monday, the client reviews Tuesday and Wednesday, and you publish from Thursday.

Mirza Pašić

Key takeaways

  • Agree who approves, how fast and what happens on silence before you send the first post.
  • Show each post as it will publish, per network, with the date and time.
  • Ask for a decision per post: approve or request changes with a note.
  • Keep feedback in one channel so you never merge comments from email, chat and calls.
  • Treat any edit after approval as a new version that needs a new yes.

To get client approval on social posts, agree the rules before the work starts, then send each reviewer one link with a deadline. Show every post the way it will publish, ask for approve or request changes on each one, and record the answer. A client approval workflow for social media fails most often at the rules, so start there.

The rest of this guide gives you the steps, a weekly turnaround policy and message templates. They work with a shared document, a spreadsheet or a scheduling tool.

Approval in five steps

  1. Set the rules. Name the approver, the turnaround and the escalation path in writing.
  2. Draft the week. Write every post for the week in one batch, with media, network and publish time.
  3. Send one review request. Send each approver one link or file and one deadline.
  4. Collect decisions per post. Each post gets approve or changes requested, with a note.
  5. Revise, confirm and schedule. Send changed posts back for a second yes, then schedule only approved posts.

If you manage several brands, run the same five steps per client. Our guide on managing multiple social media accounts covers how to keep the calendars apart.

Set the rules with the client

Settle three things in the kickoff call and confirm them by email. Clients rarely object to rules they agreed to in week one.

Roles

Name one approver per client. A second person can comment, but only one person says yes. If the client insists on two approvers, agree whose answer wins when they disagree.

Turnaround

A weekly rhythm keeps both sides predictable:

  • Monday: you: Draft next week's posts and send the review request by end of day
  • Tuesday: you: Answer questions; client: Reviews and decides
  • Wednesday: you: Revise change requests by noon; client: Confirms revised posts by end of day
  • Thursday: you: Schedule approved posts
  • Following week: you: Posts publish

The client gets two working days and you get a buffer day before anything goes live. For time-sensitive posts, agree a same-day path, such as a phone call with a named backup approver.

Escalation

Write down what happens when the client goes quiet. One rule that works: a reminder on Wednesday morning, a final notice on Thursday at noon, and after that you hold the posts. Holding is safer than publishing on silence. Some agencies agree "no reply means yes" for routine posts, but put that in the contract if you use it, and never apply it to offers, prices or anything legal.

A ready-made version of these rules is in the social media approval process template.

Send posts so clients can decide

Clients approve faster when they see the post as their audience will see it. A paragraph in an email leaves them guessing about crops, line breaks and links.

For each post, show:

  • the network and account it will publish to
  • the full text for that network, including hashtags and links
  • the image or video as it will appear, with the crop
  • the publish date and time, with the time zone
  • anything that changes per network, such as a shorter caption for X

Group the posts by week, in publish order. One review request per week beats five separate messages, because the client sees the plan as a whole and can spot two posts that repeat each other.

Review request template

Hi [name], next week's [number] posts for [brand] are ready for review: [link]. Please approve or request changes on each post by Wednesday at 5 pm. Anything without a decision by Thursday noon stays unscheduled.

Keep it that short. The link and the deadline are what the client needs.

Handle change requests

Ask clients to write feedback on the post itself, not in a reply email. When feedback arrives in email, chat and a call, you end up merging three versions and something gets lost.

When a change request comes in:

  1. Reply within your agreed window, even if only to confirm you have it.
  2. Make the change, or explain in one sentence why you suggest another option.
  3. Send the revised post back for a new yes. An approval covers the version the client saw, not the next one.

Change made template

Hi [name], I've updated the [day] post as you asked: [one-line summary of the change]. Please confirm here: [link].

Pushback template

Hi [name], on the [day] post, the offer sits at the end of a long caption, and many readers stop before it. I suggest moving it to the first sentence. Here's the revised version: [link]. Happy to go with your original if you prefer.

Reminder template

Hi [name], [number] posts for next week are still waiting for your decision: [link]. I'll hold anything without a decision after Thursday at noon.

Keep a record of each decision with the date and the version. When a client asks why a post went out, you can show who approved it and when.

Do it in Weekbird

Weekbird handles the sending and recording part of this workflow on the Team and Agency plans. You send each reviewer a personal link. The client opens it without creating an account, sees the posts, and approves or requests changes with a note on each one. Links last 30 days and you can revoke one at any time.

A post that is waiting for approval does not publish, even if it has a scheduled time. If you edit a post after the client approved it, the post needs a new approval, which matches step 5 above. The rules and turnaround policy are still yours to agree with the client.

You can read how the link works on the approvals feature page, and how agencies set up client work on the agencies page.

Questions

How long should client approval take?

Two working days is a workable default for a weekly batch: the client reviews on Tuesday and Wednesday and you schedule on Thursday. Agree a faster path for time-sensitive posts, with a named backup approver.

What if the client does not respond?

Follow the escalation rule you agreed at the start: a reminder, a final notice with a time, then hold the posts. Publish on silence only if the contract says so, and only for routine posts.

Do clients need to log in?

That depends on the tool. With a shared document they need access to it. In Weekbird, a reviewer opens a personal approval link and needs no account. Freelancers who work with one or two clients can find more on the freelancers page.