Content Approval Workflow: Stop Chasing Client Sign-Off

Published
November 5, 2026
Reading
19 min read
Share
In This Piece
  1. Five Rules Most Agencies Already Have
  2. Why Client Sign-Off Stalls
  3. Send a Request They Can Finish
  4. When the Client Goes Quiet
  5. What a No-Reply Clause Can and Can't Do
  6. Ask for Changes Against the Line
  7. Record Who Said Yes, and When
  8. One Page per Client, Agreed at Kickoff
  9. Where GoMimic Fits
  10. The Short Version
  11. Questions People Ask

A content approval workflow is the path a piece of content takes from finished draft to the client's yes: who reviews it, in what order, by when, and what counts as approved.

It's tempting to spend all the effort setting those steps up. But the drafts are often ready on time. What runs late is the yes. So most of this guide is about the client's side of the handoff, with messages you can copy for each step, and what a contract can and can't do when the client says nothing.

Six steps: draft, internal review, and send to the client are done. The client's review is marked as where sign-off stalls. Approved and scheduled wait behind it.
The steps on the agency's side usually run on time.

Five Rules Most Agencies Already Have

Read a few articles on this and you'll find the same list. It's a good list:

  • One person makes the final call for each client.
  • The brief is agreed before anyone writes.
  • Feedback lives in one place, not across email, Slack, and doc comments.
  • Every review has a deadline.
  • Revision rounds have a limit.

If you're still working out where approval sits among everything else that happens to a post, this distribution process walks through the steps around it, and the content creation process covers the stages before it.

If you have all five and posts still sit for a week, the problem is on the client's side. That's the part worth fixing, and it's the part the usual advice skips.

Why Client Sign-Off Stalls

From the agency's side, a late approval looks like a client who doesn't care. From the client's side, it usually looks like one of the following.

The Person You Email Isn't the One Who Decides

Your contact is often a marketing manager whose job includes getting a yes from someone else. That might be a founder, a partner, or someone in compliance.

Your email lands, they forward it, and now your deadline depends on a person who has never heard of it.

The agency emails its contact at the client, a marketing manager, who forwards the request to a founder, a partner, and a compliance lead. The agency's deadline now depends on people who never saw it.
Ask at kickoff who really signs off.

Ask at kickoff who really signs off. Then ask whether your contact can approve routine posts on their own. Some can, once someone says so.

They Don't Know What You Want Them to Check

"Please review" is an open invitation. A client who isn't sure what they're checking for will either reread every line or wait until they have time to. Both are slow, and the line-by-line read tends to produce edits to sentences that were fine.

The Ask Arrives in a Hard Format

An attachment to download, a tool that wants a login, a doc with forty comments already in the margin. Approval requests often get opened on a phone between meetings. If a request can't be answered there, it waits for a laptop, and the laptop session is already booked.

There's Too Much at Once

A month of posts in one send feels like a project, and clients postpone projects. A few pieces tied to one post feel like a quick decision.

Nothing Says by When

"When you get a chance" has no deadline. So it goes behind everything that does.

Dates are easier to set from a calendar a client can see and approve.

Send a Request They Can Finish

Most of those stalls come down to how the request is framed. The fixes are small.

Send One Set per Post

If you repurpose client blog posts, the facts in the LinkedIn post, the newsletter section, and the thread already appear in a post the client approved. Send those pieces together, as one set tied to the post they came from.

One decision with context is easier than a dozen without it. It also means the client can see how the pieces fit together, which answers half their questions before they ask them. Our content repurposing examples show what a set can hold.

On the left, six separate please review messages, one per piece, with no context. On the right, one review link holding the published post and the three pieces made from it.
The facts in each piece come from a post the client already approved.

Tell Them What to Check, and What to Leave Alone

Give the client a short list of what you need from them:

  • Names, job titles, and quotes.
  • Numbers, prices, and dates.
  • Offers, discounts, and anything with legal weight.
  • Where each piece sends the reader.

Then say what they can leave to you: the format and length for each channel, and the tone you agreed at kickoff. If the voice itself feels wrong, raise that on its own. Fixing it one post at a time won't stick.

Please check names, job titles, and quotes. Numbers, prices, and dates. Offers, discounts, and anything with legal weight. Where each piece sends the reader. Leave to us: the format and length for each channel, and the tone agreed at kickoff.
A short list the client can actually finish.

A client who knows the job is four checks will finish it. A client facing "any feedback?" might never feel done.

Offer a Third Answer: Not Approved

Most review requests offer two choices: approve, or request changes. Add a third: not approved.

Sometimes a client doesn't want a post to run at all. Maybe the offer changed or the timing is wrong. With only two buttons, they'll either approve it and tell you separately, or type "don't run this" into a change request. The second one looks like a revision brief, and someone rewrites a post that was already dead.

Approve: the post is scheduled. Request changes: it is revised and sent back. Not approved: it is dropped with no rewrite, and a short conversation follows.
A plain no is a valid answer, and it saves a rewrite.

A plain "no" doesn't need a reason attached. Your next step is a short conversation.

Put a Time and a Time Zone on It

"By Thursday at 5 p.m. ET, so it can go out Monday" works better than "this week." It gives the client a reason, and it tells you exactly when to follow up. How long a window to give depends on the content, and counting back from the go-live date sets it.

For a request that puts all of this together, with subject lines and versions for Slack and WhatsApp, see how to ask a client to review.

When the Client Goes Quiet

Here most guides go quiet too, and it's where approval needs the most thought.

Why "No Reply Means Approved" Is a Bad Rule

One tempting fix is to write it into the contract: if the client doesn't answer within a set time, the work counts as approved. It's also the rule most likely to damage the relationship it's meant to protect. The same goes for auto-approve in a tool, which is the same rule running by itself.

The same goes for the rest of the job: here's what to automate and what to keep with a person.

Content goes out under the client's name. If they didn't answer because they were on vacation, out sick, or waiting on legal, the first time they see the post is when their customers do. A wrong price or a quote from someone who has left the company is now public. "You didn't reply" is a weak position to argue from.

The costs aren't even close. Holding a post for three more days costs some timing. Publishing something the client would have stopped can cost the account.

GoMimic learned this the direct way. It used to offer automatic approval after a set number of days, and removed it after finding it had approved posts whose clients hadn't been able to open the review link. Now a link that runs out simply expires. It never counts as a yes.

A timeline: sent Monday, reminder Wednesday, deadline Thursday at 5 p.m. ET. With no reply, the link expires and the posts are held. Counting the silence as approval is crossed out.
Holding a post costs some timing. Publishing without a yes can cost the account.

Set Your Follow-Ups When You Send

Decide when you'll follow up at the moment you send, not when you notice the silence. For a Thursday deadline, a reasonable schedule is a nudge the day before, then a short note on the day.

Send with a deadline, a reminder the day before, a short note on the day, then the backup approver, then hold the posts and tell the client.
Each step should make answering easier than the last.

Hi [name], a quick reminder that the three pieces from the spring pricing post need your yes by tomorrow at 5 p.m. ET. They're short, and it's one answer for all three.

Hi [name], today's the day we need these to keep Monday. If Monday no longer works, just say so and we'll move them.

Keep each follow-up shorter than the last, and make answering easier each time rather than making the silence feel worse.

Go to the Backup Approver

If the deadline passes, go to the backup you named at kickoff. Frame it as protecting their schedule. Nobody wants to be the reason a colleague got chased. If two people always need to see the work, make the second an approver rather than a backup. If you got the answer by phone or in a chat, write down who said it, how, and when.

Hi [name], [approver's name] usually approves our posts for your team, and we haven't been able to reach them this week. Could you take a quick look at these three pieces so Monday's posts can go out? If you'd rather wait for them, that's fine too. We'll hold them.

Hold the Posts, and Say So

When nobody answers, don't publish, and don't go silent either. Tell the client the posts are on hold and what it takes to restart them. That turns the silence into a decision they can see.

Hi [name], we've held Monday's three pieces because we didn't get a yes. Nothing will go out until you approve it. If this week got away from you, tell us a day that suits, and we'll send a fresh link.

Offer the easy way out rather than a guilt trip. It's the follow-up people ask us for most.

What a No-Reply Clause Can and Can't Do

Some agencies put the rule in the contract, on the theory that a signed sentence makes silence safe. It settles less than it seems to. What follows is plain general information about US law, read from the sources linked on November 5, 2026. It isn't legal advice, and the rules differ by state.

What These Clauses Say

They tend to have three parts: a clock, a form of answer, and a result. Here's one we made up to show the shape, so don't copy it:

If Client does not approve or reject a deliverable in writing within five business days, it is deemed approved.

You'll also see "deemed accepted", "treated as final", or a line saying the client waives objections after the deadline.

A page of an agency contract with one made-up clause highlighted: if the client does not approve or reject a deliverable in writing within five business days, it is deemed approved. Handwritten notes ask three questions. Approved for what, the invoice or publishing? Who had to see it? And what if the email never arrived?
The clause is made up. The three questions are the ones to ask of your own.

Read your own clause for what it actually decides. In our view, a sentence like this suits work you hand over and bill for, such as a website or a logo, where "accepted" closes a milestone and the invoice can go out. Publishing in the client's name is a different act, and the clause may not say it covers that. Check who has to receive the request, how it has to arrive, and whether a new version restarts the clock.

Silence Usually Isn't Acceptance in US Contract Law

The starting point is that saying nothing doesn't accept anything. California's jury instruction on this, CACI No. 310, tells jurors that a person who doesn't respond to an offer ordinarily hasn't accepted it, unless both sides understood silence to mean acceptance.

The Indiana Supreme Court applied the same idea in Land v. IU Credit Union (2023). A credit union sent members an addendum with their account statements. It would bind them unless they opted out in writing within 30 days. Land never opted out. The court found the notice reasonable, and still held that her "silence and inaction did not amount to acceptance." It said silence counts as acceptance "in only three exceptional circumstances," and that the "mere fact that an offeror states that silence will constitute acceptance" doesn't take away the other side's right to stay silent. It also noted that she'd had to click "Accept" when she opened the account, which it took as a sign that the parties' dealings called for an actual yes. On rehearing in February 2024, the court affirmed in full and left open a different standard for some future case.

That's a consumer bank case under Indiana law, so treat it as a clear statement of the rule, not as a ruling on agency contracts.

A Signed Clause Is a Different Thing

Don't read any of this as "your clause is void." A clause both sides signed isn't one side announcing what silence means. The client agreed to it in advance, and California's instruction allows for silence to count where both sides understood it that way. Neither source settles a signed clause between two businesses. In our reading, the rule bites hardest on the lines nobody really agreed to.

Four places a no-reply line can live, from easiest to hardest to challenge: a line in an email, a notice of new terms with an opt-out, a past habit of running posts after no reply, and a clause both sides signed. Even the signed clause only binds the two who signed it.
This is our general reading, not a rule. Courts and states differ.
  • A line in an email. "If we don't hear back by Friday, we'll assume it's fine" is one side saying so. That's the sentence the Indiana court was talking about.
  • A notice of new terms. Adding the rule partway through a contract, with an opt-out, is close to what happened in Land.
  • A past habit. The California Supreme Court, quoted in the notes to CACI No. 310, says a relationship or a previous course of dealing can make silence read as acceptance. That can help you, but one post that ran without complaint isn't much of a course of dealing. And if your process asks the client to press a button or write back every time, that history may point the other way, as the "Accept" click did in Land.
  • A signed clause. The strongest of the four. Even so, you'd have to show the clock started and the request arrived. GoMimic's own automatic approval failed at exactly that point, on links clients hadn't been able to open.

What a Clause Doesn't Protect You From

A contract binds the people who signed it. Your exposure mostly sits outside it.

Inside a dashed line marked the contract: you and your client. Outside it, and not bound by it: the FTC, a person the post names or quotes, and the client's customers who read the post.
A clause can decide who owes whom. It can't decide for anyone else.

The FTC. Its advertising FAQ says "the advertising agency also may be held legally responsible for misleading claims in ads." It says agencies have "a duty to make an independent check" on the information behind a claim, and that they "may not rely on an advertiser's assurance" that the claim is substantiated. If a client's actual assurance isn't enough, then in our view their silence is worth less. Not every post is an ad, but one that makes a claim about a product, a price, or a result may be, and the FAQ says online ad claims "must be truthful and substantiated." That also means a real yes from the client doesn't end your own fact check.

Other people. Someone quoted with an old job title, or a customer who relied on a wrong price, never signed your contract. An indemnity clause can move the cost between you and the client. It doesn't stop anyone from bringing the complaint to you.

The client. You can win the argument about the clause and still lose the account. Holding a post costs some timing, and that's a far cheaper mistake.

Write the Clause So the Posts Wait

What agencies usually want from a no-reply clause is two things: not to be blamed for a missed date, and to get paid. You can ask for both without publishing anything. Another made-up example, to give your contract person the idea:

If Client has not answered by the review date, the post waits and its publishing date moves. Fees for work delivered stay due on the agreed date.

If a client really doesn't want to review routine posts, ask them to say so in writing. That's the client's decision, made in advance and on the record, which is a different thing from reading a decision into their silence.

Ask for Changes Against the Line

Most revision loops start with feedback that doesn't say what to change. "Make it punchier" produces a second draft that's punchier in the wrong place.

Here's what happens when a client asks for changes in GoMimic, and why any edit sends a post back to Draft.

On the left, an email reply that says in the second one, third paragraph, change the part about pricing. On the right, the same feedback pinned to the highlighted line of the LinkedIn post it is about. The wording is illustrative.
The wording is illustrative.
  • Ask for changes against the specific piece and line, not in a separate email.
  • Collect a full round of feedback before revising. Two people's notes arriving a day apart means two rounds.
  • Agree on a number of rounds at kickoff. A piece that goes past it usually points to a problem with the brief or the voice, and another edit won't fix that.
  • Treat "not approved" as final for that post. Don't rescue it with a rewrite unless the client asks for one.

Record Who Said Yes, and When

Sooner or later someone asks who approved a post. It's usually a colleague of your contact, the day after a post they didn't expect.

We've laid out what an approval record holds, and how to record a yes that came by WhatsApp.

The answer should be easy to find: which post, who approved it, when, and what they said if they asked for changes. If the yes came by phone or in a chat, the record should say that, and say who wrote it down.

A record with one row per post, showing the decision, who made it, and when, with made-up times.A record with one row per post, the decision, who made it, and when. Spring pricing: approved by the client approver. Hiring guide: changes requested by the client approver. Summer menu: not approved, by the second approver. Team update: approved externally, on a call with the client approver, recorded by the editor. The times are made up.
The roles are real. The times are made up.

Email can hold that in theory. In practice it ends up split across inboxes and forwards. Whatever you use, keep each decision attached to the post it's about, with a name and a time on it. It's also one of the questions worth asking any tool before you buy it.

One Page per Client, Agreed at Kickoff

Most of the friction above goes away if you agree on the rules at kickoff, instead of discovering them on the first late post. One page per client covers it:

  • Who approves, and who approves when they're out.
  • Whether the approver can say yes alone, or needs to check with someone.
  • The usual review window, and how much notice you'll give.
  • What they should check, and what they can leave to you.
  • What happens when there's no reply: the posts wait.
  • How many revision rounds are included.

Some clients don't want to review every post at all. That's fine. Agree on it, and write down that they chose it, not that they went quiet.

An approval setup page for one client listing the approver and backup, whether the approver can say yes alone, the usual review window, what they check, what happens with no reply, and the number of revision rounds. The entries are examples.
The entries are examples. Agree on yours at kickoff.

Some agencies also put the review window and the hold rule into the contract or statement of work. That's worth doing, along the lines of the clause above, but have whoever handles your contracts write the wording. Nothing here is legal advice.

Silence Is Not a Yes

When nobody answers, hold the posts and say so.

the part about us

Where GoMimic Fits

Create client content. Get it approved. Deliver it. That's GoMimic, the Connected Content System for Client Work, and we make it, so weigh this accordingly. Here are the steps above as they run inside it:

If you're comparing tools, read our buyer's guide to content approval tools. It also scores them on newsletters and articles, for clients who approve those beside their social posts.

  • Before it goes. Someone on your team signs off each asset, and the post becomes Ready for Client. You tick the posts that are ready and send them as a numbered round.
  • The client's side. The review page opens with no login. The client types their name, answers post by post (Approve, Request Changes, or Not Approved), and presses Send My Review. Approve All approves whatever is left in one go. They can select the exact words they mean and leave a note there.
  • When the window closes. You choose how long a link stays open when you send: 12 hours, 1 day, 3 days, or 1 week. When it closes, the link expires. It never approves anything by itself. If a link went to the wrong person, you can withdraw it.
  • Chasing. On the Agency plan, reminders go out in your business name, one email for the round, and they stop on their own. On Pro, the Approvals page still shows who you're waiting on.
  • More than one person. Pro holds one approver. Agency holds several per client, and you mark who must approve.
  • A yes that came elsewhere. Record an Outside Approval and the post reads Approved externally, naming who recorded it. It never reads as the client's own answer.
  • After the yes. Approved text locks, and Edit Anyway is the only way back in. The approval record is added to and never rewritten, and exports as a PDF or a CSV. An Approval Certificate holds the exact text someone approved, and the client's own progress page shows what's waiting on them.

Clients who don't review content can be set to No Approver. Your team's Ready for Client then counts as the approval, and it's never shown as the client's own. The approved version can be copied, saved to Google Drive or Notion, sent to Slack, sent as a draft to Buffer, Kit, or Mailchimp, or sent by webhook to Zapier and on to the tool you use. GoMimic never posts. It's built for content work for many clients, and how it works has the rest. Before you buy any tool for this, these questions are worth asking.

Where it falls short: the follow-up calls and the conversation about a late yes are still yours. No tool should be having that conversation for you. And a recorded yes doesn't replace your own fact check.

Put real client work to the test.

Start the Taste TestBack by email within 4 working hours

The Short Version

  • Name one approver per client, plus a backup.
  • Send one set of pieces per post, not a message per piece.
  • Tell the client what to check and what to leave to you.
  • Offer three answers: approve, request changes, not approved.
  • Put a date, a time, and a time zone on every request.
  • Decide your follow-ups when you send.
  • When nobody answers, hold the posts and say so. Silence is not a yes, and auto-approve isn't safe for client work.
  • A contract clause that counts no reply as approval settles less than it seems to. It can't bind the FTC or anyone else outside it.
  • Keep each decision attached to the post, with a name and a time.

Questions People Ask

What is a content approval workflow?

The path content takes from finished draft to the client's yes: who reviews it, in what order, by when, and what counts as approved.

Why do clients take so long to approve content?

Usually not because they don't care. The person you email may not be the one who decides, the request doesn't say what to check, it arrives in a hard format, it's too much at once, or it has no deadline.

Is auto-approve safe for client work?

In our view, no. Content goes out under the client's name, and if they were away or waiting on legal, their customers see any mistake first. GoMimic used to offer automatic approval and removed it. Hold the posts and tell the client they're on hold.

Can a contract make no reply count as approval?

It can do more than a line in an email, because both sides agreed to it, though silence usually isn't acceptance in US contract law without something like that. Even a signed clause binds only the two who signed. The FTC says an agency has its own duty to check ad claims. This is general information, not legal advice.

How many times should you follow up?

Decide when you send. For a Thursday deadline, a nudge the day before and a short note on the day, then go to the backup approver you named at kickoff.

What should a client check when approving content?

Names, titles, and quotes; numbers, prices, and dates; offers and anything with legal weight; and where each piece sends the reader. Format, length, and the agreed tone are yours.

How do you stop revision loops?

Ask for changes against the specific piece and line, collect a full round of feedback before revising, agree a number of rounds at kickoff, and treat "not approved" as final for that post.

GoMimic

Written by the GoMimic team

GoMimic helps you create client content, get it approved, and deliver it, in each client’s voice.

Why It Works

Your Client's Yes Should Be This Easy to Find.

Start Free TrialFree for 14 daysNo credit card required

See Why It Works

Approved