HOS
All articles
Projects & operations

What to do when a client goes quiet mid-project

A client stops replying and the project stalls. Use a simple escalation timeline, a pause clause and a restart fee so silence stops costing you time and money.

Cover graphic titled Client silence: what to do when a client goes quiet mid-project, showing three steps

A client has not answered in two weeks. Your team is waiting on feedback, the next stage cannot start, and the time you set aside is going unused. Silence is not a decision, but it costs you as if it were. This post gives you an escalation timeline, a pause clause for your agreement, and a worked example of what idle time costs.

Find out why they went quiet

Before you escalate, think about the likely reasons. The client may be busy, waiting on someone internal, unhappy and avoiding the conversation, or out of budget. Each calls for a slightly different message.

You usually cannot know which one it is. So write your first messages to work for all of them: short, friendly and easy to answer. A message that asks for one thing gets answered more often than a message that asks for five.

If the silence follows a disagreement, deal with that directly. See handling feedback rounds without endless revisions for how to keep a disagreement from stalling the work.

The cost of waiting

Silence has a price, even when you are not billing for it. You reserved time for this project and turned down other work to make room.

Say you set aside 15 hours a week for three weeks. That is 15 x 3 = 45 hours. At an internal rate of $100 an hour, that is 45 x 100 = $4,500 of capacity reserved for the project. If the client goes quiet and those hours go unused, you cannot easily get them back.

Seeing the number makes it easier to justify a firm policy. It is not a penalty. It is the cost of holding space.

Escalate in steps

Use a set timeline so you are never deciding what to do while annoyed. This example uses business days:

  1. Day 3: a short check-in. One question only, such as "Can you confirm the homepage layout so we can start the build?"
  2. Day 7: a second message with a date. Restate the question and add what happens next: "If we hear back by Friday we keep the current schedule. After that we will need to move your slot."
  3. Day 10: a pause notice. Tell the client the project is paused and what it takes to restart.
  4. Day 30: a close-out notice. If there is still no reply, state that the project will be treated as closed under the terms of your agreement.

Change the numbers to fit your work. What matters is that the client knows the timeline before it starts, and that you follow it each time.

Try a different channel

If email gets no answer, change the channel once before you pause. A short phone call or a message to a second contact at the client often works. Keep a record of each attempt and its date.

Do this at day 7 or day 10, not as a replacement for the timeline. Trying another route shows you made a reasonable effort, which helps if you need to rely on the pause clause later.

Put a pause clause in the agreement

None of this works unless the client agreed to it in advance. Add a short clause to your agreement with four parts:

  • The trigger. For example, no response to a request for 10 business days.
  • What pausing means. Work stops and the schedule is released.
  • The restart terms. The client must give notice, and work resumes when you have capacity, not at once.
  • The end point. After 30 days of no contact, the project closes and any kill fee terms apply.

Place it near your scope statement so both documents answer the same question about what was agreed.

Charge a restart fee

Starting again is not free. Your team must reread the brief, recover context and fit the project back into the schedule.

Say you estimate 4 hours to get back up to speed. At $100 an hour, a restart fee is 4 x 100 = $400. State it in the agreement and mention it in the pause notice, so it is not a surprise.

Keep the fee tied to real cost. A fee that looks like a penalty invites an argument. A fee that matches your actual restart time is easy to explain.

Protect the invoice side

If the project is paused with work done but not yet invoiced, send an invoice for completed work at the pause. Do not wait for the client to return. Use your normal late fee rules for anything unpaid.

A deposit helps here as well, because you are never fully unpaid when a project stalls. For how much to ask, see deposits and upfront payments.

When the client comes back

Stay calm and stick to the terms. Confirm the restart fee, offer the next available slot and update the schedule in writing. If the pause was short, you may choose to waive the fee as a goodwill gesture, but make it clear that you chose to.

This post is general information, not legal advice. Pause and termination terms differ by place and contract, so have a qualified person review your clause.

Next step

Open your standard agreement and check whether it says what happens when a client stops responding. If it does not, write a pause clause with your own number of days and a restart fee based on your real restart time. Then set the day 3, day 7 and day 10 messages as saved templates so you can send them without hesitation.

Free plan available

Ready to run it all in one place?

Projects, clients, time tracking and invoicing in one platform.