How to Set Up a Client Approval Process That Doesn't Stall When Clients Go Quiet

The work is done, the preview link is sent, and then nothing. A week later you're writing "Just bumping this" to a client who hasn't opened the email, and the next phase can't start until they reply.

A client approval process that works has three parts: named approvers, a stated deadline, and a default outcome when nobody answers. Most stalls come from missing one of those three.

What a client approval process actually is

A client approval process is the set of steps that takes finished work from "we think it's done" to "the client has accepted it." According to awork's glossary entry on client approval, client approval is the formal confirmation from a client that a delivered result, such as a design, has been accepted.

That definition matters because it separates approval from feedback. A client saying "looks nice, but can we tweak the footer?" is feedback. Approval is a clear yes that you can point to later.

Without that clear yes, three things go wrong:

• Work sits "in review" while the next phase waits.

• Feedback arrives in four places and contradicts itself.

• Months later, someone says "I never signed off on that."

I've lived all three. On one early project, I treated a thumbs-up emoji in Slack as approval. Two weeks later, a different person at the client asked why the homepage looked "so different from what we discussed." The emoji came from someone who wasn't the decision maker. That was my mistake, not theirs.

Why approvals stall

Quiet clients are rarely ignoring you on purpose. They're busy, they aren't sure whose call it is, or they don't know what you need from them.

The usual causes are simple:

• Nobody knows who has to say yes.

• The request doesn't say what a yes looks like.

• There's no date, so nothing is late.

• Nothing happens if the client stays silent.

Every one of those is fixable with process, not nagging.

My stance: stop chasing, start defaulting

Don't build an approval process around reminders. Build it around a default outcome. A reminder asks the client to do something. A default tells everyone what happens if they don't.

Here's the practical position in three sentences. Every piece of work gets one named approver and a deadline. If the deadline passes, you send one nudge. If the nudge goes unanswered, the work approves itself after a window you both agreed to up front.

The trade-off is real. Auto-approval can feel aggressive to some clients, and it doesn't suit every kind of work. A legal disclaimer or a pricing page probably needs an explicit yes. A third round of small color tweaks on a blog graphic probably doesn't.

So agree on it in the kickoff, put it in writing, and apply it by work type. Clients rarely object when the rule is stated early. They object when it's a surprise.

Step 1: Name your approvers

The first step is to decide who can say yes, who should be consulted, and who just needs to know. Adobe's guide to getting design approval notes that a well-defined approval process begins with clarity on who is responsible for what, and suggests a RACI matrix (responsible, accountable, consulted, informed) to map that out.

You don't need a full matrix for a five-page website. You need to answer four questions per client:

1. Who is the one person who can approve this work?

2. Who must be consulted before they answer (legal, a founder, a brand lead)?

3. Who just needs to see it?

4. Who covers when the approver is out?

The key word is one. Two approvers means two opinions, and the one who answers last often undoes the first. If a client insists on two, ask which of them breaks a tie.

Write it down at kickoff

Put the approver names in the client's record, not in your head. A short note works: "Priya approves copy and design. Marcus is consulted on anything with pricing. Both are cc'd on previews."

If you run client work through a portal, this is where you set it up once. In Dora's client portal, each client has a private space for requests, files, and approvals, so the right people see the right work in one place.

Step 2: Define what "done" means before you send it

A clear approval request says what you're asking, what's included, and what's out of scope for this round. Vague requests get vague answers, or none.

Compare two hand-offs.

Before: "Here's the new landing page. Let us know what you think."

After: "Here's the landing page we briefed on March 4. It includes the hero, three feature blocks, and the pricing table. Please approve or request changes by Thursday at 5 pm. Footer and blog templates come in the next round."

The second version tells the client what to look at, what to ignore, and when to answer. It also gives you a record of what they approved.

This ties back to the brief. If the original request was fuzzy, approval will be too. Dora, the AI account manager, helps here by asking for what's missing at intake, such as the page, the goal, and the deadline, and by writing a clear brief that you can point back to at sign-off.

Keep one thread per piece of work

Feedback scattered across email, Slack, PDF comments, and calls is the fastest way to stall a review. Pull it into one place per request.

Pastel's guide to approvals describes the value of letting clients, teammates, and stakeholders review work, request changes, and give sign-off in one place. That's the point of the exercise: one thread, one status, one answer.

Step 3: Set deadlines and a nudge schedule

Every approval request needs a date. Without one, nothing is ever late, so nobody feels any pressure to answer.

Pick a review window that fits the work, and keep it consistent. For example, a small agency might use:

• Social posts and small edits: 2 business days

• Design rounds and page drafts: 3 to 5 business days

• Large deliverables with several stakeholders: 7 business days

These are examples, not benchmarks. Adjust them to how your clients actually work, then watch your own data for a month and tune.

Send one nudge, not five

A single, specific nudge beats a drip of "just checking in" emails. Send it at the midpoint or one day before the deadline, and make it easy to answer.

A good nudge reads like this: "Quick reminder: the homepage draft is waiting on your OK by Thursday. One click approves it, or you can ask for changes right in the thread."

It names the work, the date, and the next action. It doesn't apologize and it doesn't scold. In Dora, this nudge can go out for you, so your team isn't writing it by hand. See how the AI account manager handles nudges and answers clients in the thread.

Step 4: Add an auto-approval window

An auto-approval window means that if the client doesn't respond within the agreed days, the work counts as approved and moves on. It's the piece that actually stops the stall.

Picture a four-person web studio. Before, a typical page sat in review for about two weeks, and the team spent part of every Monday writing follow-ups. After agreeing on a 7-day window at kickoff, the studio's rule became: one nudge on day four, auto-approval on day seven. The outcome they'd expect is fewer open reviews and fewer status emails, measured over the first month.

That's an illustrative example, not a customer result. But the mechanism is simple, and you can test it yourself.

With Dora's approvals, you hand work over with a note and a preview link. Clients approve or ask for changes in one click, and if nobody replies, the work approves itself after the days you choose.

When not to use auto-approval

Be honest about the limits. Skip the default for:

• Anything with legal or regulatory exposure

• Pricing, claims, or contract-like language

• First-ever deliverables for a brand-new client, until you've built trust

• Work where a wrong approval is expensive to undo

For those, set a longer deadline, name a backup approver, and escalate by phone if you must. The goal isn't to remove the client from the decision. It's to make sure silence doesn't freeze your calendar.

The four-part approval setup you can reuse

Here's a simple model you can say in one line: named approver, clear ask, firm date, default outcome. I'm not branding it. It's just the four things every request needs.

Use this numbered checklist the next time you hand over work:

1. Name the approver. One person says yes. Others are consulted or informed.

2. Make the ask specific. State what's included, what's not, and what a yes means.

3. Set the date. Pick a review window based on the type of work.

4. Choose the default. Decide what happens if nobody answers: nudge, then auto-approve, or escalate.

5. Keep it in one thread. Previews, comments, and the final yes live together.

6. Record the result. Save who approved, when, and which version.

The last step matters more than people expect. Frame.io's 10-step guide walks through staged approvals and getting approval in writing. A written, dated yes is what saves you when someone asks later who approved what.

A realistic example: a five-person studio fixes its review queue

Picture a five-person design studio with eight active retainer clients. Their old process was email. Previews went out as links, feedback came back in replies, Slack DMs, and the occasional voicemail.

Baseline. Several pieces of work sat "in review" at any time, and the project lead spent part of each week asking "Any update on this?" in the other direction. Two clients regularly sent contradicting notes from different stakeholders.

Intervention. Over two weeks, the studio did five things:

1. Asked each client to name one approver and one backup.

2. Moved all reviews to a single thread per request.

3. Added a standard review window by work type.

4. Sent one nudge at the midpoint of each window.

5. Introduced a 7-day auto-approval window for routine work, with written agreement from each client.

Expected outcome. Fewer items stuck in review, fewer status emails, and no more arguments about who signed off on what. The studio would measure it over 30 days.

How to measure it yourself

Since this example has no published numbers, here's a measurement plan you can run:

• Baseline metric: Average days from "sent for review" to "approved" over the last 20 requests.

• Target metric: Cut that average by a third within 30 days.

• Secondary metric: Count of "Any update?" emails per week, before and after.

• Instrumentation: A simple sheet, or the timestamps in your portal's request history.

If the numbers don't move, look at which of the four parts is missing. It's usually the approver or the default.

Common mistakes that bring the stall back

Most broken approval processes fail in the same few ways. Here are the ones I see most.

Treating any reply as approval. A thumbs-up from someone without authority isn't a sign-off. Check the name against your approver list.

Letting feedback scatter. When notes arrive in five channels, you spend the review reconciling them. Second Wind's piece on the client feedback zone covers how to respond to negative feedback and manage the process more carefully, which starts with having one place to receive it.

Springing auto-approval on clients. If the first time a client hears about it is when work approves itself, you've damaged trust. Agree to it at kickoff and repeat it in each hand-off.

Skipping the revision limit. Unlimited rounds mean unlimited review. State how many rounds each request includes, and treat extra rounds as a change request.

Approving too much at once. A giant deliverable with one approval at the end invites a giant surprise. Break it into stages so problems surface early.

Forgetting the record. If approvals live in a Slack thread nobody can find, they don't exist. Keep the yes where the work is.

Tools: what to look for

You can run this process with email and a spreadsheet, and many small teams start there. It works until volume grows.

When you look at tools, check for the basics. Can clients approve in one click? Can you set deadlines and defaults? Does the history show who approved what? Planable's roundup of approval software notes that approval software helps streamline work and reduce errors by building a review and approval process around a well-defined, documented workflow. That's a vendor's view, so read it as a starting point and compare options yourself.

Some tools focus on content calendars and social posts. CloudCampaign, for example, describes creating a sharable approval link to send to your team or clients for review. That suits social-heavy agencies well. If your work is broader than social, such as sites, brand work, and retainers, you'll want approvals tied to requests, briefs, and files.

Dora is built for that wider case. Clients ask however they like, Dora asks for what's missing and writes the brief, and approvals sit alongside files and status in one portal. Pricing is simple: your first client is free, forever, and each client after that is $10 a month, with unlimited team seats and every feature included. You can see the details on the pricing page.

If you want to keep clients informed without more emails, Dora also sends weekly client summaries, so status questions get answered before they're asked.

FAQ

What are the steps in a client approval process?

The core steps are: name the approver, brief the work, hand it over with a clear ask, set a deadline, nudge once, and record the decision. Larger projects add stages so clients approve direction before polish. The aim is a dated, written yes for each piece of work.

Who should approve work on the client side?

One person with the authority to say yes. Others can be consulted or informed, but a single approver prevents contradicting feedback. Name a backup in case the approver is out.

Is auto-approval safe to use with clients?

It's safe when you agree to it in advance, state the window, and use it only for suitable work. Avoid it for legal, pricing, or high-risk deliverables. Always send at least one nudge before the window closes.

How long should a client have to review work?

There's no universal number. Many teams use two to three business days for small items and up to a week for larger ones. Start with a reasonable window, then adjust based on how long your clients actually take.

How do I get approval in writing without sounding formal?

Ask for a one-click approve inside the request thread, and keep the record there. A dated approval with the version attached is enough. You don't need a contract for routine creative sign-off.

What if a client approves, then asks for changes later?

Point to the approved version and treat new changes as a change request. Be friendly and clear: the approved work matched the brief, and new changes are scoped separately. This is much easier when your records show who approved what and when.

Start with one client this week

You don't need to rebuild everything. Pick one client, name the approver, set a review window, and agree to a default for routine work. Run it for a month and compare your average days in review.

If you'd like to try it in a portal built for this, Dora's first client is free, forever, so you can test the approval flow on real work. What's the one piece of work sitting in review right now that a named approver and a deadline would unstick?

References

1. awork: Client Approval

2. Adobe Business: design approval

3. CloudCampaign: client approval for social media agencies

4. Pastel: approvals

5. Second Wind: client feedback zone

6. Frame.io: 10 steps for client approval

7. Planable: approval software

8. Project Approval Process: 9 Stages of Client Approval