The strategy document was sent two weeks ago. The client hasn't responded. The creative team is waiting. The project timeline has already shifted by 10 days, and the client doesn't know they caused it.
This happens in every agency, on almost every project, multiple times per engagement. It's the single most common source of delays, margin erosion, and team frustration in agency work — and most agencies don't track it, don't measure it, and don't have a system for managing it.
Client approvals aren't a small administrative detail. They're the mechanism that determines whether agency projects stay on track or quietly fall apart.
Why approvals stall
Understanding why helps, but it doesn't fix the problem. What fixes the problem is having systems that make stalls visible before they become expensive.
The client is busy. Your project isn't their only priority. Your email sits in an inbox with 200 others. The approval request competes with board meetings, hiring decisions, budget reviews, and every other demand on their time. Without a nudge or a visible reminder, it drops.
The client needs internal alignment. Your deliverable needs sign-off from the marketing director, but the marketing director wants the CEO's input, and the CEO is travelling until Thursday. The approval chain inside the client's organisation is invisible to you — and longer than you assumed.
The client doesn't know they're the bottleneck. From the client's perspective, the agency is "working on it." They don't realise that the project has stopped because they haven't responded. There's no visible signal — in their inbox or anywhere else — that their inaction is costing the agency time and money.
The feedback is hard. Sometimes the deliverable needs changes but the client doesn't know how to articulate what's wrong. So they procrastinate. The review sits in their to-do list, getting pushed day after day, while the project clock keeps running.
What slow approvals actually cost
The direct cost is obvious: the project is late. But the indirect costs compound in ways that most agencies don't measure.
Timeline compression
A 2-week approval delay doesn't add 2 weeks to the project. It compresses everything downstream. The creative phase that was planned for 3 weeks now has to fit into 2 because the launch date hasn't moved. The production team works overtime. The QA phase gets shortened. The final deliverable is rushed.
The client caused the delay. The agency absorbs the consequences. And because the downstream work was compressed, the quality is lower and the team is exhausted — both of which affect future work.
Context-switching costs
When a project stalls waiting for approval, the team moves on to other work. When approval finally arrives — 10 days later — the team has to switch back. They need to re-read the brief, re-familiarise themselves with the project, and re-enter the creative headspace they were in two weeks ago.
Research on task-switching consistently shows that context-switching reduces productivity by 20–40%. For a creative team working across multiple clients, approval-driven context switches are the norm, not the exception. The cost is invisible because it looks like "the team is busy" rather than "the team is losing hours to avoidable re-orientation."
Margin erosion
Every hour spent waiting, re-orienting, compressing, or chasing is an hour that wasn't in the estimate. On a single project, this might mean 3–5 extra hours — annoying but manageable. Across 10 clients over a quarter, it's 120–200 hours of unplanned effort. At an average agency blended rate, that's thousands in margin that disappeared into approval delays nobody tracked.
Relationship strain
The irony: slow approvals strain the client relationship in both directions. The agency is frustrated because the client is holding things up. The client is frustrated because the project feels slow — even though the delays are on their side. Without a clear record of when deliverables were sent and when (or whether) they were reviewed, the "who's responsible for the delay" conversation becomes a disagreement rather than a fact-based discussion.
Compounding across the agency
One stalled approval on one project is a nuisance. Stalled approvals across 5 of your 10 active projects simultaneously is an operational crisis. Suddenly half the agency's work is blocked, the team is under-utilised on those projects and over-committed on others, and the founder is firefighting instead of leading.
This is the hidden cost that matters most: approval delays don't happen in isolation. They compound across the agency, creating a persistent drag on delivery, profitability, and team morale that's hard to see because no single delay looks like a big deal.
What most agencies do (and why it doesn't work)
Email follow-ups. The account manager sends a "just checking in" email. It works sometimes. But it's manual, it's time-consuming across multiple clients, it feels like nagging, and it doesn't prevent the next stall — it just addresses the current one.
Slack messages. Faster than email, but even easier to ignore. And the agency's record of "we sent this for review on the 5th and haven't heard back" is buried in a Slack thread nobody will find again.
Status column updates. The PM tool has a task marked "Awaiting Client Approval." Nobody checks. The task sits in that status for two weeks. When the operator finally notices, the damage is done.
Weekly status meetings. "What's blocking you?" "Waiting on the client." "Which client?" "Three of them." "Since when?" "Not sure." Weekly status meetings catch stalls reactively, days after they've started compounding.
None of these approaches give the agency what it actually needs: a single view showing which clients have deliverables waiting for review, how long they've been waiting, and which projects are at risk — across the entire agency, in real time.
What actually works: purpose-built approval tracking
The solution isn't better follow-up discipline. It's structural visibility.
Track the full approval lifecycle. Not just "approved / not approved" — but "sent for review," "viewed by client," "approved," "changes requested," and "waiting." Each status tells the agency something different, and the distinction between "the client hasn't seen it" and "the client saw it and hasn't responded" changes the follow-up approach entirely.
Track it across every project. One project's stalled approval is a minor issue. Five across the agency is a pattern. The operator needs a cross-project view showing every pending approval, every client with outstanding reviews, and every project at risk of timeline slippage.
Make it visible to the client. When the client can see — in their own project view — that three deliverables are "awaiting your review," the agency doesn't have to send a chasing email. The visibility itself is the nudge.
Create a record. When a project runs late and the client says "the agency was slow," the approval record tells a different story: deliverable sent 5 March, viewed 8 March, feedback received 19 March, 14-day client-side delay. That record protects the agency in scope conversations, timeline disputes, and renewal negotiations.
Act early, not late. When the operator can see that 3 clients have pending approvals approaching the 5-day mark, they can intervene before the delays cascade — a quick call, a nudge via the client view, a conversation about priorities. Early intervention is cheaper than late recovery.
How Kavaro handles client approvals
Kavaro tracks client approvals natively — across every project, pitch, and proposal in the agency. The operator sees which deliverables are waiting for review, which clients have viewed them, who's approved, and who's still sitting on something that's blocking the next phase.
Clients see pending approvals in their own project view — a clean, visible reminder of what needs their attention, without the agency having to send a follow-up email.
Approval data feeds into Kavaro's estimates vs actuals tracking, so the agency can see the real cost of approval delays — not just the timeline impact, but the effort impact of context-switching, compression, and re-work.
When a project stalls, the record is clear: when the deliverable was sent, when it was viewed, when it was approved. No ambiguity. No disagreements about who caused the delay.