How to Manage a Project When a Client Is Slow to Respond

When a client is slow to respond, manage the project by making the dependency visible. Name the exact decision, input, or approval you need; separate blocked work from work that can continue; state when the reply affects the next milestone; and agree on what happens if that date passes. Silence is a status to manage, not automatic approval unless your written terms explicitly make it one.

Start with what is waiting

"The client is slow" describes a feeling, not a project state. The useful question is: what work cannot move until a specific response arrives?

A delayed answer can mean different things. A client may need to choose between options, provide an asset, resolve an open question, or approve a deliverable. Those requests unlock different work. Write the dependency in one sentence: "The next layout is waiting on the client's choice between A and B," or "Production is waiting on the approved copy." That sentence makes the next action easier to see.

Then separate the delay from its cause. You may not know whether the client missed the message, needs another person's input, or has changed priorities. Do not fill that gap with a story. Ask for the response you need and make the project impact clear.

Classify the response before following up

Keep the request narrow. If the client owes a decision, do not ask for general thoughts. If you need a missing file, identify the file and the step it unlocks. If you need approval, point to the exact version under review and use the approval process already agreed for the project.

Separate blocked work from work that can continue

Put the work into three simple groups:

• Blocked: work that depends on the response. Do not present it as in progress.
• Ready: work you can complete without guessing at the client's choice or permission.
• At risk: work that can continue now but may need to change if the answer goes another way.

This prevents two common mistakes: stopping the entire project when one task is waiting, and producing speculative work that may need to be undone. Continue only with tasks that remain useful under the possible answers. If a choice could change the direction, hold the dependent work rather than treating a guess as a decision.

A short action record is enough: the pending item, who owns the response, the date requested, the next milestone affected, and the next review point. The project action-item register can help keep waiting work visible without turning it into a long status list.

Send a decision-ready follow-up

A useful follow-up gives the client something specific to do and shows why the date matters. Include four parts:

1. The item and the version under review.
2. The exact response needed, with a link or a short list of options.
3. A requested date tied to the next milestone or your capacity plan.
4. The next project step if the response arrives later.

For example:

Subject: Decision needed on [deliverable] by [date]

Hi [Name], I'm holding the next layout until we have a direction. Please choose option A or B on the linked page by [date] so I can keep the next review on the current plan. If that timing no longer works, send the date you expect to decide and I'll update the forecast. If the reply comes later, I'll confirm a revised schedule before restarting the blocked work. I'll keep the item pending under our agreed approval process.

Use a date that fits the plan you have made with the client. There is no universal follow-up interval for every project. A same-day production decision and a multi-person review are different dependencies. Your agreement, milestone, and actual capacity should guide the request.

Keep the tone neutral. Describe the work, the needed response, and the schedule effect. Avoid assigning motive, adding pressure that the plan does not support, or sending several versions of the same "checking in" note.

Choose the right status when the date passes

If the requested date passes without a response, update the project record and forecast. Do not quietly keep the old delivery date if a dependent step cannot happen. Send one clear update that says what remains blocked, what can continue, and which date now needs a decision.

• Continue: keep moving on independent, useful work.
• Reforecast: adjust dependent milestones and show which response date the new plan assumes.
• Pause: if the project cannot proceed, confirm the hold and restart conditions in writing, consistent with the agreement.
• Resume: when the response arrives, confirm the decision, remaining scope, and realistic next date before restarting.

Do not treat late feedback as a simple calendar shift if your capacity has changed. The original time may no longer be available. Say when you can resume and confirm the revised sequence. If the client asks for a change as part of the reply, separate the new request from the overdue decision and clarify its effect on scope and timing before treating it as part of the current work.

Set the dependency up before the next project

At kickoff, list the decisions, assets, and approvals the client must provide. Give each one an owner, a requested date, and the work it unlocks. Agree on who can approve, how feedback will arrive, and what the team should do when a response misses its date. Put any pause, restart, or schedule rules in the project's written terms rather than inventing them during a tense moment.

When a delay threatens a larger commitment, use the escalation route the project already defines. Escalation should move a decision to the right owner; it should not simply make the message louder. The signal-to-decision escalation plan is a useful companion when a blocked item has become a material risk.

That structure protects the working relationship as well as the schedule. It gives the client a clear next move and gives you an honest account of what is, and is not, moving.

Keep the work honest

A slow response does not have to become a project-wide stall or a personal conflict. Make the dependency specific, keep safe work moving, set a date tied to the plan, and update the forecast when the facts change. Most of all, keep the status true: waiting work is waiting work, approval is approval, and a new schedule is a decision to confirm.

If you are building a simple workday uniform, the Standard Issue Hoodie uses black heavyweight fleece with the mark embroidered in white thread. See the live product details for the current options.

Explore more from The Self Made Journal.