What do you do when a client keeps delaying the project?

Client delays are the single biggest cause of blown timelines, and the fix has nothing to do with confrontation. Track when work is waiting on the client, make that wait visible, and agree upfront what a delay does to the timeline and scope. Once the pause is on the record, the reset conversation gets easy.

Client delays are frustrating mostly because they create confusion before they create conflict. A review takes longer than expected, the person who needs to sign off goes quiet for a week, or a late request lands right before a deadline. Then the project starts slipping and both sides feel the pressure.

Picking a fight is not the answer. The better move is to make the delay visible, set expectations early, and handle the reset calmly once the facts are clear.

What client-caused delay really looks like

Unreasonable delay usually comes down to a few things: communication breaks down, a late change request lands, or expectations quietly stop matching the original plan.

Sometimes the delay is a hard stop, like missing feedback or approval. Sometimes it is softer, like a late request that changes what the team is being asked to do. Either way, the project starts waiting on the client side instead of moving through planned work.

That is the key thing to name. The issue is not that the client is being difficult. The issue is that the Job is no longer moving under the original assumptions.

Make waiting on the client visible

This is where many small firms weaken their own position. They feel the delay, but they never mark it clearly anywhere. The project just looks late.

A better habit is to show when work is blocked because something is still sitting with the client. That creates a real record of what the team is waiting on, and since when. Once that waiting time is visible, the conversation changes from vague frustration to plain operating reality.

That visibility also protects the team. It makes clear that the drift is not some random internal failure. The work is paused because a needed input has not arrived yet.

Set delay expectations before the project gets tense

Timeline conversations go much better when expectations were set early, right at the start of the Job.

Make sure the client understands upfront what inputs, reviews, and approvals the plan depends on. Be clear about what happens if those dates move, not in a threatening way, just a practical one. If feedback arrives late, the timeline resets. If a request changes the work, the scope needs to be revisited.

That is much easier to accept when it is established upfront than when it first surfaces in the middle of a stressful week.

Keep the conversation patient, but concrete

Patience and empathy still matter here. Clients are often delayed because they are busy, stuck internally, or reacting to their own pressure.

That does not mean you absorb the consequences silently. It means you handle the discussion without turning it personal. Name what the team is waiting on. Show the current pause. Explain what it changes in the timeline. Then ask for the decision or input needed to restart the work cleanly.

Calm clarity usually beats irritation.

Make the reset conversation easy

When the delay is documented, the reset is straightforward.

You do not need to argue about who is responsible for what. You can simply say: this item was waiting on approval, here is when the pause started, here is what has shifted, and here is the revised path forward. If the late request changes the work itself, that is also the moment to talk about scope instead of letting the team quietly absorb it.

That is why a visible wait state matters so much. It takes the emotional charge out of the conversation, because the conversation is attached to the record instead of someone’s memory.

A light way to support this structurally

The structural point is simple: when blocked work, ownership, and status live close to the Job, it becomes much easier to show what is waiting on the client and what that pause is doing to the timeline. In workflow management software like Net Net, that kind of record stays attached to the work instead of disappearing into scattered messages.

The bottom line

Client delays happen. The goal is not to eliminate every pause. The goal is to handle them in a way that protects the timeline and keeps the conversation clean.

Make client-caused waiting visible. Agree upfront what delays do to timing and scope. Then, when the project pauses, use the record to reset expectations calmly. That is how you protect the Job without turning the relationship into a fight.

FAQ

How do I handle a client who won’t give feedback?

Make the blocked state visible and ask for the specific input needed to move forward. Keep the tone calm, but be clear that the timeline depends on that response. If the pause stretches, reset the plan based on when feedback actually arrives instead of pretending the original timeline still holds.

Can I charge for client-caused delays?

That depends on your agreement, but the important operating move is defining the effect of delays upfront. If late approvals or late changes affect timeline or scope, say so clearly before the project gets tense. Then the later conversation is about applying the agreed structure, not inventing terms midstream.

How do I protect my timeline from slow approvals?

Spell out review windows, approval responsibilities, and what happens if those dates slip. Then track when work is waiting on the client side so the pause stays visible. When the record is clean, revising the timeline without drama gets a lot easier.

What is the biggest mistake firms make with client delays?

Usually it is letting the delay stay informal. The team feels blocked, but nobody marks the wait clearly or resets expectations soon enough. Then the work looks late for no obvious reason, which makes the later conversation harder than it needed to be.