Check what you need before you send anything
A client’s silence can feel personal, especially when you are waiting to finish a piece of work. It may simply mean your message was buried, the decision needs another person’s input, or the project has slipped down their list. You do not need to guess which explanation is right. Your first job is to identify the specific response that would let the project move forward.
Look back at the last exchange. Did you ask a clear question, or did you send an update that sounded as though no reply was needed? Note what is outstanding: feedback on a draft, approval to proceed, access to files, or a decision between options. Also check any agreed milestones and communication preferences. This gives you a factual basis for following up rather than sending a vague “just checking in” message.
Make the first follow-up easy to answer
Keep your first message short, friendly, and tied to the work. State what you are waiting for, explain what happens once you receive it, and offer a simple next step. If there are several questions, separate the essential decision from the details that can wait. A client who is short on time is more likely to answer one clear question than reopen a long discussion.
For example: “Hi Sam, I’m following up on the homepage draft I sent over. Could you let me know whether the overall direction is approved, or whether you’d like changes before I develop the remaining pages? Once I have your answer, I can plan the next stage. If it’s easier, a brief reply with ‘approved’ or your main concern is enough.” Adapt the wording to the relationship and the decision at hand; the useful part is the clear request, not the exact phrasing.
Avoid adding pressure through a string of messages across email, chat, and social platforms. Use the channel you agreed on or the one the client has been using. Give them a reasonable chance to respond before trying another route.
Explain the effect on the schedule
If the first follow-up gets no answer, your next message can be more direct without becoming accusatory. Describe the practical consequence of the missing input. You might be unable to complete a design, book the next review, or hold the original delivery window. Focus on what you can control rather than suggesting the client has done something wrong.
A useful message might say: “Hi Sam, I still need your approval on the homepage direction before I can continue with the remaining pages. If I hear back by Thursday, I can confirm an updated schedule. If not, I’ll pause this stage and propose new dates when you’re ready to resume.” Choose a date that makes sense for your workload and any existing agreement; do not present it as an ultimatum unless it genuinely reflects how you manage your availability.
Be precise about the difference between a paused task and an abandoned project. If you can work on an independent part of the brief, say so. If proceeding would risk wasted effort or unapproved changes, explain why you are waiting. This helps the client understand that the follow-up is about making a sound decision, not demanding attention.
Pause cleanly if the silence continues
Repeated reminders rarely improve an unclear situation. After a small number of well-spaced attempts, send a concise status note. Record what has been completed, what input is still needed, and what will happen to the schedule while the project is paused. Keep a copy of the relevant messages and working files so you can restart without reconstructing every decision.
You could write: “I haven’t received the approval needed for the next stage, so I’m pausing work on this project for now. The homepage draft is ready for review, and the remaining pages have not yet started. When you’re ready to continue, please send your feedback and I’ll confirm my availability and a revised timeline.” If your agreement sets out a process for pauses, deadlines, or payment, refer to it accurately rather than inventing new terms in a follow-up.
Make future projects easier to restart
Client silence is easier to handle when expectations are set before it happens. At the start of a project, agree on where feedback should go, who can approve work, and which decisions block progress. Put review points in the schedule and explain that delivery dates may need to shift if key input arrives late. A brief written recap after a meeting can also prevent uncertainty about who owes the next response.
When a quiet client returns, welcome the reply and reassess the project before promising an immediate restart. Confirm whether the brief, decision-makers, and priorities are still the same, then offer dates that fit your current workload. The goal is not to win an argument about the gap in communication. It is to give both sides a clear, workable path forward.
