A client going unresponsive mid-project is one of the most frustrating situations in freelance work: you’re blocked through no fault of your own, and waiting costs you time you can’t bill for. Not after delivery, mid-project, when you need feedback, approval, or information to continue. The work is in progress and you’re stuck.
Why It Happens
The most common reason is priority shift. The project mattered last month when it was new. Now the client has seven other things happening, and your request for feedback is sitting under all of them. This is not great client behavior, but it’s usually not malicious, it’s the way internal priorities work, and freelancers are often the last item on the list when everything else is urgent.
A second pattern: the client is stuck and doesn’t know it. You’ve sent a question or a deliverable for review, and they haven’t responded because they’re genuinely unsure about the answer. Rather than saying “I don’t know yet,” some clients go quiet and hope the question resolves itself. It doesn’t. The project just stalls while they avoid a decision they haven’t made.
Less commonly: something has changed internally that they haven’t told you about. The budget got cut, the team changed, the strategy shifted, the project is under review. Clients sometimes go quiet because the situation on their side has changed in a way they’re not ready to communicate. You’ll find out eventually, but until you ask directly, you’re working with incomplete information.
The Mid-Project Block Is Different from Post-Delivery Ghosting
When a client disappears after delivery, the work is done and the main issue is payment. When a client disappears mid-project, you have a live engagement with no forward motion, and time is passing. Your calendar may be partially committed to this project. You may be turning down other work while you wait. The cost accumulates in real time.
This is why mid-project silence requires a faster response than post-delivery silence. Waiting three weeks to escalate after delivery is standard. Waiting three weeks while a project sits blocked is a different situation, by then you’ve lost time, momentum, and potentially other opportunities. The follow-up sequence is shorter and more direct here.
How to Follow Up When a Client Is Unresponsive Mid-Project
The first follow-up should assume the best. Something like: “Hi [Name], just checking in on [specific question/deliverable]. Want to make sure I’m not missing anything from you. Happy to jump on a quick call if that’s easier than email.” Short, non-accusatory, and gives them an easy way to re-engage.
Wait five to seven business days. Not two. Not one. If you follow up every other day, you create pressure that produces resistance, not response. Give the client enough time that a reply would be reasonable and comfortable.
If that doesn’t land, the second message is more specific: “Hi [Name], I haven’t heard back and I wanted to flag that [project phase/deliverable] is on hold until I hear from you. I’m [available / scheduled to work on this] [timeframe], if the timeline has shifted, let me know.” This message does two things: it makes the consequence explicit (the project is paused, not in progress) and it opens the door to a conversation about whether the situation has changed.
The third message, if you need it, is the direct one: “Hi [Name], I’ve reached out a few times and haven’t been able to move forward. I need to hear from you by [date] or I’ll have to [reschedule this project / reassign the time / treat the engagement as on hold]. Let me know what’s happening.” This isn’t a threat, it’s an honest statement of your situation. You have limited capacity and you can’t hold a slot indefinitely for a project that isn’t moving.
How to Keep the Project Moving Without the Client
Some mid-project blocks can be partially worked around. If you’re waiting on feedback on section A, can you work on section B in the meantime? If you’re waiting on assets they said they’d provide, can you proceed with placeholders and flag the dependency clearly? This isn’t a substitute for their response, but it keeps the project from freezing entirely while you wait.
Document what you’ve done and what you’re waiting on. A brief note in your project log or a message in the project thread, “I’ve completed X and Y. Awaiting your feedback on Z before proceeding”, creates a clear record of where the block originated. That record matters if a timeline dispute happens later.
Don’t use a client’s silence as an opportunity to reinterpret the brief or proceed past your mandate. If you’re stuck at a decision point, the decision is theirs to make. Moving forward without it usually means rework.
When the Silence Is About the Project, Not the Response
Sometimes mid-project silence isn’t communication avoidance, it’s a signal that something is wrong with the engagement. The client may have looked at the draft and realized it’s not what they wanted. They may have shown it internally and received pushback. They may have changed their mind about the direction without knowing how to say so.
If your follow-up prompts a response that reveals one of these situations, “actually, we’ve been rethinking the approach”, that’s the conversation you needed. A brief change or scope revision costs something, and how that’s handled depends on your contract. The relevant piece is whether your agreement covers scope changes and who pays for rework when the brief shifts after work has started.
This is distinct from the client who keeps changing the brief as a habit. That’s a different pattern with a different response. Mid-project silence that resolves into a direction change is usually a one-time event tied to a specific decision the client was struggling with.
When a Client Is Unresponsive Mid-Project: When to Stop Waiting
At some point, holding a project slot for a non-responsive client starts costing you more than the project is worth. That point is different for every engagement, but the calculation is: what is the opportunity cost of keeping this project open, and is it greater than the value of the engagement itself?
If you’ve sent three messages over three weeks and heard nothing, you have a few options. You can formally put the project on hold: “Hi [Name], given the lack of response, I’m treating this project as paused. When you’re ready to continue, let me know and we’ll schedule accordingly.” This closes the loop on your end without terminating the engagement. You’re not firing them; you’re naming the reality.
If the project is paused long enough that your timeline or rate no longer makes sense when it resumes, that’s a legitimate reason to renegotiate terms when they come back. A project that stalls for six weeks and then restarts is not the same project it was, your availability has changed, other commitments have shifted, and the rate that made sense in a continuous engagement may not make sense for a restart.
If the silence has gone on long enough and payment for completed portions is outstanding, that becomes a payment issue that runs on its own track. The steps for following up when a client ghosts after delivery apply to the payment portion of a mid-project stall.
The Contract Clause That Helps Here
A project pause or abandonment clause in your contract tells you exactly when you can formally put a project on hold, what happens to the timeline if it restarts, and whether re-engagement requires a new agreement. Without it, you’re negotiating these questions in real time with a client who may not be responding.
The clause doesn’t need to be complicated: something along the lines of “if the client fails to respond within [X] business days of a request for feedback or information, the project is considered paused and the timeline extends accordingly” is enough to give you a written basis for pausing without it becoming a dispute. The contract clauses that protect you covers this and similar provisions in more detail.
Mid-project silence is common enough that having this clause is more about expectation-setting than enforcement. A client who knows the project formally pauses after 10 business days of non-response tends to respond within 10 business days. If an unresponsive client pattern keeps repeating, it may be worth reviewing the red flags that predict difficult client behavior to catch these situations earlier in future engagements.
