A social media approval workflow for client posts

A good social media approval workflow moves every post through the same stages, from idea to draft to approved to scheduled, with one named person who approves and a deadline for doing it. If the client does not answer by the deadline, the post does not go out. Every approval, revision and rejection is written down, so the same feedback never has to be given twice.

Here is how to set that up for client work, and how to handle the parts that usually go wrong.

The stages a post moves through

Fewer stages are easier to run. Each one should have a clear owner and a clear exit.

1. Idea. A one-line description of the post and the theme it belongs to. Cheap to reject, so reject freely.
2. Draft. The full text. This is where most revisions happen.
3. Image. The visual, if the post has one, checked against the text.
4. Scheduled. Approved and waiting for its slot. Nothing enters this stage without approval.
5. Posted. Live on the feed, with the link recorded.

A board with one column per stage makes the whole pipeline visible at a glance. You can see what is waiting on you, what is waiting on the client, and how many days of approved posts are left in the queue.

Who approves

One person per client. When two people at the client can approve, each assumes the other did, or they approve different versions. Name the approver in the contract and in your tool.

For a founder or executive posting on their own profile, the approver should be that person. Their name is on the post. An assistant or marketing lead can collect feedback, but the final yes belongs to the person whose feed it lands on.

Set deadlines for approval

Without a deadline, approval drifts toward the morning of the post, and then past it. Agree a rhythm at the start and keep it the same every week.

• Drafts reach the client a fixed number of days before they go out, for example one week.
• The client approves by a fixed day, for example Thursday for the following week.
• Batch the requests. One message a week with five drafts gets answered. Five separate messages get ignored.
• Keep a queue of approved posts a few days deep, so one slow week does not leave a gap.

What to do when a client goes silent

It will happen. The client is travelling, closing a round or on holiday. The temptation is to publish the drafts anyway, because the cadence is what they are paying for. Do not do it.

A post goes out under the client's name. An unapproved post with a number they did not want public, or a view they no longer hold, costs more trust than a missed week ever will. Agree the rule in the contract: unapproved posts do not publish.

1. Send one reminder the day before the deadline, with the drafts attached or linked.
2. If the deadline passes, the scheduled approved posts keep going out as planned. Unapproved ones wait.
3. If the queue runs dry, send a short note saying the feed will go quiet from a given date until drafts are approved.
4. When the client is back, offer a single short session to clear the backlog.

Some agencies ask clients to approve a small reserve of evergreen posts in advance, for exactly these weeks. It keeps the cadence without breaking the rule.

Capture feedback so it is not repeated

The most frustrating thing for a client is giving the same note twice. 'I never say synergy.' 'Do not mention that customer by name.' 'Shorter opening.' If the second draft of the month repeats a mistake from the first, the client starts to wonder what they are paying for.

• Keep one short document per client with their rules: voice, format, topics to avoid, numbers that are off limits.
• After every revision, ask whether the note applies to this post only or to every post. If every post, add it to the rules.
• Read the rules before drafting, every time. It takes a minute.
• Share the rules with the client once a quarter so they can correct anything that has drifted.

Keep an approval log

An approval log is a plain record of who decided what, and when. Each entry has the post, the action (approved, revised or rejected), the person, the date, and any comment.

It settles disagreements. When a client asks why a post went out, you can show that they approved it on a given day. When they ask why the feed was quiet, you can show that drafts were sent and not answered. It also shows you patterns: a client who rejects most ideas from one theme is telling you the theme is wrong.

Never overwrite the log. If a post was revised three times, keep all three entries. The history is the point.

How GoodSocials handles this

Every client profile has a board with five columns, Idea, Draft, Image, Scheduled and Posted, and every card has three actions: Approve, Revise and Reject. Nothing reaches Scheduled without an approval, and the publish loop only posts what is scheduled, so an unapproved card waits however long the client is away.

Each action is written to an append-only log with the person and the comment. A revise comment rewrites the card and updates the matching brand principle for that client, voice, visual or format, so the note carries into every later post without anyone keeping the rules document by hand.