Get Clients to Approve Posts on Time (Without Nagging)
What to put in the agreement, how to word the approval message, and when silence should not count as approval. With three copy-ready messages.
Clients approve on time when the request is small, has a date and says what happens if they do not answer. Most stalled approvals come from the opposite: a big batch, no deadline and a message that asks "thoughts?".
This post is for freelancers and small agencies who run Instagram and Facebook for local businesses. It gives you a diagnosis of why approvals stall, three messages to copy, and a table that separates what can be approved by silence from what never can. The advice is editorial, drawn from common practice, not measured results. It is not legal advice.
Short answer
- Agree the rules before the first post: who approves, how long they have, and what happens at the deadline.
- Send a small batch (one week, or one page of posts) in one message with one date.
- Ask a yes-or-no question and offer a fast way to answer.
- Use "silence means go" only for low-risk posts, and only if the client agreed in writing.
- Never let silence approve prices, offers, health or result claims, reviews or anything with a person's face in it.
- Keep a record of what exact version was approved, by whom and when.
Why approvals stall
A local business owner is usually serving customers when your message arrives. The post is not their job. These are the patterns behind most late approvals:
| What you see | What is probably happening | Fix |
|---|---|---|
| Reads the message, never replies | The reply feels like work: they have to open a file, judge it and write feedback | Ask one question that can be answered with one word, and put the post in the message or a link they can open in one tap |
| Replies days late | No deadline, or a vague one ("when you can") | Give a date and time, and say what you will do after it |
| Approves, then asks for changes after it posts | They approved without really reading | Show the caption in full, flag the one thing to check (price, date, name) and restate it in the message |
| Sends a long list of edits | The batch was too big, or the post missed their voice | Batch by week, cap revision rounds, and fix the cause in a voice or facts note |
| Different people answer differently | No single approver | Name one approver and one backup in the agreement |
| Always "fine", then complains later | They are approving what they do not understand | Say in plain words what the post claims, and ask them to confirm those facts |
None of this is about a lazy client. It is about making the easy answer the default.
Agree the rules up front
Put these six points in your agreement or onboarding document. Have the client reply "agreed" in writing. If you want contract wording, ask a lawyer: whether a silence clause holds up depends on your country and your contract.
Approval terms to agree in writing
- Approver: one named person, plus one backup, with the channel they will answer on (email, text, link).
- Batch and day: you send a week (or a month) of posts on a fixed day, for example every Thursday for the following week.
- Deadline: a date and time, in the client's time zone, at least two working days before the first post goes out.
- Silence rule: what happens at the deadline. Options: the post is skipped, a backup post runs, or low-risk posts publish as drafted. See the table below.
- Revision rounds: how many rounds are included. Two rounds per batch is a common practitioner suggestion, not a standard. Say what extra rounds cost.
- Late changes: a change after approval needs a new approval. A change after publishing is a new request.
A message that gets answered: three to copy
Short, specific and dated. Replace the brackets. Send them on the channel the client already answers.
1. First request (send on batch day)
One batch, one question, one date.
- Message
- Hi [name], next week's posts are ready: [number] posts for Instagram and Facebook. Here they are: [link or attached]. Could you reply "approved" or tell me what to change? I need your answer by [day, time] so everything goes out as planned. Please check two things: [the price / the date / the name that appears]. Thank you.
2. Reminder (one day before the deadline)
Make the cost of waiting concrete, without blame.
- Message
- Hi [name], a quick reminder: I'm still waiting on [number] posts for next week. If I have your answer by [day, time], they run on the days we planned. If I don't, [the first post will be skipped / the backup post will run]. A one-word reply works: "approved".
3. Deadline notice (at the deadline)
State what you are doing, exactly as agreed. Do not apply a silence rule you did not agree.
- Message
- Hi [name], the deadline passed at [time]. As we agreed, [post A, a low-risk post, will go out as drafted / posts with prices and offers will not go out until you approve them]. The backup post [description] will run in their place. Tell me any time and I will update the rest of the week.
Three habits improve all three messages. Name the post's job in five words ("Saturday opening hours post") so the client knows what they are judging. Put anything that must be exact, such as a price or a date, in the message text rather than only inside an image. Do not apologise for asking.
Fast lane and batch
You can split work into two lanes so the client's time goes where it matters.
- Fast lane: routine posts that repeat a pattern the client has already approved, such as "new week, same opening hours", a team spotlight with a photo they supplied, or a product photo with a caption that restates a price from a fact sheet. These can be approved in a single tap, or by silence if the client agreed in writing.
- Careful lane: anything new: an offer, a price change, a claim about results or health, an event, a post that shows customers or staff. These go to the client one at a time or at the top of the batch with a note on what to check.
Batching by week keeps the ask small. A monthly batch looks efficient to you, but it is a larger decision for the client, and facts such as prices go stale before the last posts run. If a client prefers monthly, send it as four weekly pieces with one approval link.
A no-login approval link can also remove one source of delay, because the client does not have to create or remember an account. We have not measured how much faster this is, so treat it as a design principle, not a promise. KeepsPosted's approval links work this way: the client opens a link, sees the post as it will appear and approves or comments.
Silence is not approval for some content
A deemed-approval clause ("no reply by the deadline means approved") is common in agency contract templates. It is a convenience for you, and it is also a risk. A client who did not read a post can still be the business that is responsible for what it says. Regulators look at the business and the content, not at who failed to reply.
| Content | Silence can approve? | Why |
|---|---|---|
| Opening hours post that matches the fact sheet | Yes, if agreed | Low risk, repeats approved facts |
| Team or venue photo the client supplied | Yes, if agreed, and people shown have consented | Low risk once consent is on file |
| Recipe, how-to or general tip you wrote | Usually yes | Check it contains no health or result claims |
| Price, offer, discount or deadline | No | A wrong price or an offer the business cannot honour becomes the client's problem |
| Health, wellness, weight-loss or treatment claims | No | Often regulated. Ask the client's regulator or adviser, not you |
| Customer review or testimonial | No | Reposting a review turns it into a testimonial under the US FTC rule. The client must confirm it is real and has permission |
| Photos of customers, children or staff | No | Consent must be confirmed per person |
| Claims such as "best in town", "award-winning", "guaranteed" | No | Needs evidence only the client has |
| Posts about a sensitive event (closure, incident, apology) | No | Tone and facts need the owner |
On testimonials, the US Federal Trade Commission's Q&A on its Consumer Reviews and Testimonials Rule says that when reviews are featured in advertising or marketing they become testimonials (FTC Q&A, read 10 November 2026). It also says incentives for reviews are allowed only if nothing expresses or implies that the review must be of a particular sentiment. Rules differ by country and by profession.
Revision rounds
Without a limit, clients assume revisions are unlimited. Practitioners often cap them at two or three rounds per batch. That is a common practice, not a rule. What matters is that the number is written down and that you say what a round is.
- A round is one set of consolidated feedback from the approver on one batch. Three separate emails in one day are one round.
- Ask for edits in a list tied to each post, not a general comment. "Post 3: change Saturday hours to 9 to 4" is clear. "Make it more fun" is not.
- Fix the cause as well as the post. If three captions are "not us", the issue is the voice note, not the captions. Update the client's voice and facts document.
- A change of fact (a new price, a new opening time) is not a revision. It is a correction, and you make it straight away.
- After the cap, extra rounds are billed or wait for the next batch. Say so kindly and early, not as a surprise.
What a record should show
If a client says "I never approved that", you want the answer in one place. A useful record shows, for each post:
- The exact text and media that were approved (a copy or a version label, not "the caption we discussed").
- Who approved, by name.
- The date and time of approval.
- The channel and the account it was published to.
- Any change after approval, and the new approval.
- For silence-approved posts, a copy of the message that stated the deadline and the rule.
A spreadsheet works. So does the history inside a tool that publishes for you. A record is evidence of what happened, not proof that a post was lawful, and it does not replace a lawyer's advice. For a longer approval process inside one business, see our approval workflow guide.
Common questions
How long should I give a client to approve posts?
Long enough to read, short enough to protect your schedule. Many agencies use two working days, and ask for approval at least two days before the first post. Pick a number, write it down and use it every week.
Can I publish posts if the client does not answer?
Only if you agreed a silence rule in writing, and only for low-risk posts. Keep prices, offers, health or result claims, reviews and photos of people out of that rule.
Should the approver be the owner or a manager?
Whoever can answer for the facts: prices, hours, claims. Name one approver and a backup so a post never waits on an absent person.
Sources
- FTC: Consumer Reviews and Testimonials Rule, questions and answers (checked 10 Nov 2026)
Written by the KeepsPosted editorial team, with AI assistance for drafting and a person reviewing every claim. The workflow advice is editorial, based on common practice for agencies and freelancers, and has not been measured. Contract and regulatory points are general information, not legal advice.
Keep reading
A Simple Social Media Approval Workflow for Small Teams
Who checks what before a post goes live: roles, deadlines, revision limits and a one-page rule set for owners, managers and staff who share an account.
Onboarding a Local Business Client for Social Media
Access, voice, facts, consent and approvals: the checklist for the first week with a new local client, including a Meta access set-up that never uses passwords.
Managing Client Accounts Without Posting to the Wrong One
Access, separate fact sheets, approval status and a weekly check for freelancers and small agencies who run several local brands on Instagram and Facebook.