- A project stalled because the client stops responding can drag on for months and throw your agency’s whole schedule into disarray.
- The fix combines prevention (review deadlines in the contract and a single point of contact) with an escalation protocol that moves from friendly to firm.
- Logging every attempt to reach the client protects you and puts gentle pressure on them without being aggressive.
We’d been waiting 3 weeks for feedback. Revisions ready. Staging environment up and running. Team available. Client gone.
No reply to emails, no answer on the phone. When they did pick up, they promised an answer “by tomorrow,” a tomorrow that never came.
Meanwhile, the project was taking up headspace for 3 people on the team. Every day it sat idle was money not coming in. And we didn’t dare take on new work, because the client could come back “any minute now.”
If you run an agency, you know this story. After seeing it play out again and again, we put a protocol together. It won’t stop clients from disappearing (nothing will), but it limits the damage and gets you out faster.
Why clients go silent (and it’s not always bad faith)
Before you act, figure out what’s going on at their end. Clients who stop responding usually fall into 3 groups:
Overloaded. This is the most common one. Your contact has other priorities or is waiting for sign-off from a boss who never finds the time. It’s not that they don’t want to move forward, they just can’t.
Undecided. The silence hides doubts. They don’t love the revisions but don’t know how to say so. Or they worry that saying “no” will trigger changes they don’t have the budget for.
In crisis. Staff changes, a restructuring, a serious problem in the business. Suddenly the website project isn’t a priority anymore.
Knowing the cause shapes your strategy. Pushing an overloaded client can backfire, and ignoring an undecided client’s fears keeps them stuck indefinitely. A direct, non-judgmental question (“is there anything in the proposal that isn’t quite working for you?”) often unblocks more than 10 reminders.
Prevention: the contract as your first line of defense
The best way to unstick a project is to keep it from getting stuck in the first place. And that starts with the contract.
Clear review deadlines. For example: “The client has 5 business days to review each deliverable. If no comments are received within that period, the deliverable will be deemed accepted.” This is a deemed acceptance clause: for it to carry any weight, it needs to be well drafted and every delivery needs to be documented.
Planned pauses. Define how many days without progress trigger a formal pause, how the project gets rescheduled and whether restarting it carries a fee. You free up resources and make it clear that inactivity has consequences.
A single point of contact. Specify who reviews and approves on the client’s behalf. It heads off the endless “I’m still waiting to hear back from my boss.”
These clauses don’t guarantee the client will comply, but they set expectations from day one: people who know they have 5 days to review tend to respond sooner. If you want to check what else your contract should cover, take a look at the technical clauses your development contract should include.
Make it easy for the client
Some of the blockages come from the way we ask for feedback. A link with a “what do you think?” forces the client to review everything and decide where to start.
- Small deliverables. Reviewing one section today is easier than reviewing a whole website a month from now.
- Specific questions. Instead of “what do you think?”, ask “does the homepage copy describe your services well?” or “shall we approve this menu structure?”.
- A short video walking through the deliverable. A screen recording of 3 or 4 minutes saves a lot of back and forth over email.
- Reviews booked on the calendar. From kickoff, schedule each review date with the client, just as you would a meeting.
The escalation protocol: from gentle to firm
When a project stalls, we follow a sequence, counting from the day we sent the deliverable. Skipping steps usually backfires: jumping straight to an ultimatum burns the relationship, and sticking with friendly reminders drags the stall out.
Days 1 to 3: friendly reminder
A short, collaborative email with no pressure. Sometimes the client has simply lost track.
“Hi [name], just a quick reminder that we’re waiting for your review of [deliverable]. Whenever you get a chance, your input would be a big help. Thanks!”
Days 5 to 7: direct phone call
An email is easy to ignore without a second thought. A phone call forces a decision: answer or decline. And 5 minutes of conversation brings out what an email keeps hidden.
“Is there anything keeping you from reviewing it? Would it help to go through it together on a quick video call?”
Days 10 to 14: formal email with consequences
We raise the tone. We explain what the delay means, without making threats.
“We’ve gone 2 weeks without being able to move forward because we haven’t heard back. This affects our planning and, under the terms of our contract, may result in [consequence]. Can we talk about how to proceed?”
Days 15 to 21: constructive ultimatum
We offer concrete options with a deadline. The client doesn’t have to write anything, just choose.
“We need a decision by [date]. Options: A) you send us your comments this week and we pick things back up; B) we formally pause the project until [date]; C) we set up a 30-minute meeting to get it unstuck. If we don’t hear back, we’ll pause the project.”
After day 21: formal pause or close-out
We do what we said we would. Pausing isn’t abandoning the project: it protects profitability and the team’s schedule. We confirm the pause in writing, explain how the project will restart and reassign the team.
If your agency works with a technology partner, let them know as soon as the project hits this stage: the end client’s silence blocks them too. Your white-label agreement should account for these pauses.
Documentation: your liability insurance
Every contact gets logged. Not out of distrust, but because memory fails and long projects take a lot of twists and turns.
A simple log is enough, in a spreadsheet or your project management tool: date, channel, message sent and response (or “no response”).
It has saved us more than once. Months later, someone says “you never told us,” and there’s the log with every email and every call.
It helps internally too: if 3 people contact the client without coordinating, the agency looks disorganized. With a central log, each contact builds on the last one. It’s the same principle we apply to documenting technical decisions: what isn’t written down ends up getting lost.
What to do when the project restarts
The goal isn’t just to get the project moving again, it’s for it to finish well.
When the client comes back:
Realignment meeting. Don’t pick up exactly where you left off. Review the current status, confirm the goals and adjust the scope if needed: the client’s situation may have changed a lot.
Revised dates. The original dates no longer hold: better to renegotiate a realistic schedule than to promise the impossible. If you have to justify the new timeline, here are some ideas on how to explain to your client why the project took longer than planned.
New ground rules. If the problem was a lack of feedback, set up a more structured rhythm: for example, a short weekly meeting instead of waiting for the client to get in touch.
The extreme case: when it’s time to walk away
Not every project is worth saving. Sometimes the professional thing to do is close it out.
These are the signs that make us consider it:
- The client hasn’t responded in more than 2 months.
- The project has been paused 3 or more times for the same reason.
- The client’s situation has changed radically and the project no longer makes sense as originally planned.
- The team is burned out and it’s already affecting other work.
In these cases we propose an orderly close-out: we hand over what’s done, invoice what’s been completed and leave the door open to pick it up again in the future. Raising this clearly and without blame is easier than it sounds; we cover it in how to say “no” to a project.
Sometimes losing a project means gaining your sanity.
Frequently asked questions
Should I charge for the time the project is on hold?
It depends on what the contract says. We don’t charge for the time a project is paused, but we pause it and reassign resources. We do revisit the budget if restarting means redoing work, for example, because the content has changed.
What do I do if my contact at the client has left the company?
Write to management or to the person who signed the contract. A summary of the project status and the contact history lets them get up to speed in minutes.
Can I use the work already done if the project is canceled?
It depends on what the contract says about intellectual property and the assignment of rights, so put it in writing from the start. Typically the client gets the rights to what they’ve paid for and the agency keeps what hasn’t been invoiced, but don’t take it for granted: check your contract before reusing anything.
Conclusion
Stalled projects happen. They don’t have to turn into a disaster.
A clear protocol, proactive communication and thorough documentation turn a frustrating situation into something manageable. And the best time to deal with it is before it happens, when you draft the contract.
If you have projects stuck in limbo or want to review your contracts and review process so this doesn’t happen again, get in touch and we’ll take a look. Sometimes one well-placed clause saves months of stress.