The client-approval queue: finished work waiting on a client's yes
The client-approval queue is finished work waiting on a client's yes. It builds when work goes out without a clear question or due date, so nobody owns the chase. Send each piece with one clear question and a date. When the date passes, the account lead gets a drafted reminder, and a change is approved or logged against scope.
The work is done. The campaign creative went over on Tuesday, the new homepage is built, and next month's content calendar is ready to schedule. Then nothing comes back from the client. A week later the account lead sends a nudge, the client answers a different question, and the launch date moves. Finished work sits with a client for days before anyone hears back, and from inside the agency it looks like nobody's fault.
Why finished work waits on the client
Nothing on the client's side tracks your work. It arrives in their email between their own deadlines, and it usually ends with something like "let us know what you think". That asks for an opinion with no shape and no date, so it loses to everything on their desk that has one.
On the agency side, nobody owns the wait. The account lead assumes the client is reviewing, the designer has moved on to the next job, and the date the work needs an answer by lives in someone's head. When the answer does come back, it's often vague, or it carries a new request inside it, and that starts another round.
So the queue forms in the gap between sent and approved, and nobody on either side is watching that gap. An approval is a decision. A decision gets made when someone has a clear question in front of them and a date it's needed by.
What the wait costs the agency
The first cost is the schedule. A late yes moves the launch, and whatever you bill on delivery gets billed late with it. The people booked for the next stage either sit waiting or get moved onto something else, and then the approved work comes back all at once and lands on a week that's already full.
The second cost is margin. Work that waits goes cold, so the team reopens files and rebuilds the context before they can act on the feedback. Changes that arrive with a late approval tend to get done without anyone asking whether they were in the agreement. That's how scope creep gets in, one small request at a time, each too small to raise.
The third cost lands at renewal. The client remembers that the campaign launched late. They rarely remember that it waited a week on their own desk, and the account lead is left defending a delay they didn't cause.
The coordination cost calculator takes the projects you have running and the hours of coordination each one needs a month, chasing approvals included, and shows what that time costs across a year.
What the system looks like
I'd build it around one rule. Every piece of work goes to the client with one clear question and a due date. When the date passes, a reminder is drafted for the account lead, who sends it as it is or edits it first. When the client asks for a change, the change is either approved as part of the work or logged against scope, so extra work shows up before anyone does it.
The question does most of the work. "Can the homepage go live on Thursday as it is, or do you want changes to the headline first?" gets an answer in a line. The due date is the date the schedule needs the answer by, written in the message where the client sees it, and it's tied to something they care about, like the launch.
- Work ready for the client
- Sent with one clear question and a due date
- Reminder drafted when the date passes
- Account lead sends or edits itHUMAN
- Approved, or the change logged against scope
| Work waiting on the client | The question it goes out with | What the reminder says | Where a new request goes |
|---|---|---|---|
| This month's campaign creative | Approve these as they are, or mark the ones to change? | Which pieces are still waiting, and the launch date they hold up | Edits inside the agreed rounds are approved work. A new concept is logged against scope |
| Next month's content calendar | Can these go out on the dates shown? | The first post date now at risk, and what moves if it slips | An extra post or a new channel is logged as extra |
| A page of the new site | Can it go live as it is, or do you want changes to the copy first? | The go-live date, and which pages are waiting behind this one | A new page or section is logged against scope |
| The monthly report | Anything to correct before we walk through it on the call? | The call date, and that the report goes as it is unless they flag something | A new measure they want tracked is logged for next month's plan |
| Final files at the end of a project | Can we hand these over and close the project? | What's in the handover, and the date the project closes | New work after sign-off starts as a new request |
What stays with the account lead
The relationship stays with the account lead. The draft saves them writing the chase, and they decide whether it goes. They know when a client is away for a week, when a project is tense, or when the answer already came on a call. Sometimes the right move is to pick up the phone, and that call is theirs to make.
They also decide what counts as extra. The log puts a requested change next to the agreement, and the account lead judges whether it's a fair edit inside the round or new work, then raises it with the client in their own words. Giving something away can be the right call for the relationship, and with the log it's a choice someone made on purpose.
As the owner, you get one view of what's waiting on clients across every account, and of what was logged against scope. When an account's margin looks wrong, that's the first place to look.
Questions
How do I get clients to approve work faster?
Make the answer easy and the date visible. Send each piece with one clear question they can answer in a line, and a due date tied to something they care about, like the launch. When the date passes, follow up the same day with a reminder that says what's waiting and what it holds up.
Should the reminder go out on its own?
I'd keep a person on it. The account lead knows when a client is away, upset, or already said yes on a call, and a reminder that ignores that does more harm than the wait. The draft saves them writing it, and they decide whether it goes.
What if the client still doesn't answer?
Agree in the contract, before work starts, what a late approval does to the schedule. Then the reminder can say it plainly: the launch moves by as long as the answer takes. The delay stays on the client's timeline, and your people can be moved to other work in the meantime.
How do I tell a requested change from scope creep?
Check it against the agreement. Edits inside the rounds you agreed are part of the work. A new piece, a new page, or a round beyond the ones agreed is extra. Logging each one keeps both visible, so the account lead can decide whether to give it, charge for it or move it to next month.
Will clients use an approval tool?
Many won't, and the request still has to reach them. The question and the due date go by email, where the client already reads, and they can answer in a line. Nobody asks them to log in to anything new.
Related
- The owner-approval bottleneck: when every yes waits for youReplies, proposals and discounts all wait for the owner's yes. Written rules send the routine to a named person and bring the owner only the exceptions.
- The agency client lifecycle, stage by stageThe six stages of an agency client, inquiry to renewal: who owns each, the handoff out of it, and where work stalls once the client has signed.
- Scope creepScope creep is work a client gets that was never agreed, added one small request at a time. How the invisible kind eats agency margin and how to see it.
- The reporting bottleneck: writing what changed, every monthSomeone still writes what changed and why, every month. Draft it from the report's own numbers, mark the guesses, and let the account lead sign off.
- From signed deal to running projectClient onboarding automation I built. One form with the signed proposal sets up the Drive folder, ClickUp tasks, Slack channel and welcome email.
- What does coordination cost your business each year?Turn your leads, proposals and active projects into the hours your people spend coordinating each month, and what that time costs you in a year.