How to set up a client approval workflow for social media

Client approvals are where social media work stalls. Drafts go out as screenshots, feedback arrives in three places, and nobody is sure which version the client signed off on. A clear workflow fixes most of this before any tool is involved. The steps below work with any scheduler, spreadsheet, or shared folder.

1. Decide who approves what

Write down three roles for each client account:

• Drafter: writes or edits the post.
• Account lead: checks the post against the brief and the brand’s rules before the client sees it.
• Client approver: the one person on the client side who signs off. Name them. “The team” is not an approver.

Also decide which posts need client sign-off. Some agencies send everything. Others send only new campaigns, offers, and anything that states a price or a date. Either choice works, as long as the rule is written down and the client knows it.

2. Batch posts per client, per week

Send one batch per client each week instead of one post at a time. A batch gives the client a single decision point and gives your team a predictable rhythm. Pick a fixed day for sending, such as Tuesday, and a fixed day for approvals to close, such as Thursday. That way the schedule is not set by whoever sends the next message.

Keep each batch small enough to read in one sitting. If a client needs twenty posts a week, split them by campaign or by network.

3. Keep one place for drafts

Every draft should live in one place: one board, one folder, or one review queue. Feedback that arrives by email, text, and comment threads has to be copied back by hand, and copies go wrong. Choose one home, and say during onboarding that nothing counts unless it is there.

Each draft in that place should show the network, the planned date, the copy, the image or video, and the brand it belongs to.

4. Send one review link per batch, not screenshots

A screenshot shows one post, has no version history, and invites feedback in the wrong place. A single review link for the whole batch lets the client open every post, see the exact text you will publish, and respond to each one on its own.

Whatever tool you use, the rule is the same: the client reviews the text and media that will go live. If a post changes after the client has seen it, send it again.

5. Write one rule for requesting changes

Clients will ask for changes in whatever way is easiest for them. Set one rule and repeat it in your onboarding notes:

• To approve, use the approve action.
• To ask for changes, leave a comment on that post saying what to change.
• Do not reply by email with a new draft. Ask for the comment instead.

Ask the client to say what is wrong, not how to rewrite it. “This price is out of date” is useful feedback. A rewritten paragraph is a draft, and your team should write the drafts.

6. Set deadlines and a silence policy

Every batch needs a date by which approvals close. Put it in the message that sends the batch, for example: “We will schedule everything approved by Thursday at noon. Posts still open then move to next week’s batch.”

Decide in advance what happens when a client is silent. Options include:

• Hold the post, remind the client once, and move it to the next batch.
• Escalate to the named client approver after a stated cut-off.
• Drop the post from the schedule and tell the client which posts were dropped.

Pick one, write it into your contract or onboarding document, and apply it every time. Do not schedule a post the client has not approved. Silence is not approval.

7. Keep a record of decisions

Record who approved each post, when, and which version they saw. Record each change request with its comment attached. This matters when a client disputes a line, when a post needs to be pulled, or when a new team member needs to understand why a brand says what it says.

A spreadsheet is enough. The point is that decisions are written down somewhere other than someone’s memory.

8. Turn repeated feedback into rules

If a client asks you to remove the same kind of phrase three times, that is not a preference. It is a rule. Write it down in the brand’s voice notes: which words to avoid, which claims need a source, and which tone fits which kind of post.

Review change requests once a month and look for patterns. Update the brand notes when you find one. Over time, fewer posts should need changes, and the approval step gets shorter.

How this works in Solvgent

Solvgent builds several of these steps into the product.

• Review queue. Every plan has a review queue. Your team can approve, request changes, or reject each draft. Roles decide who can approve.
• Client review links. On Agency Pro and Enterprise, and during the 14-day trial, you can send a client a review link. Clients can approve a post, approve everything that is left, or request changes with a comment. They do not need a login.
• Expiry and revocation. Every link expires, and you choose how long it stays open when you create it. You can revoke a link at any time.
• Nothing publishes without approval. A draft waits in the queue until someone approves it.
• Lessons from edits. When you edit a draft, or reject it with a reason, Solvgent tries to turn that change into a lesson for the brand. Lessons wait in Brand Brain for you to review; only the preferences you add there guide future drafts. Keep reading drafts closely.

For the full queue and review link details, see approvals. To see how the workflow fits an agency team, see Solvgent for agencies.