Treat client silence during review as a workflow state, not as a personality mystery.
This page is for the narrow question of what to do when work has been sent, a decision is still needed, and the client has gone quiet. It is not a full communication guide. Its job is to help you respond without turning silence into hidden delay, accidental approval, or emotional guessing.
What this page is not for
Do not use this FAQ to define the whole review process, fix a weak approval path from scratch, or replace the broader delivery or proposal-review workflows.
Start upstream first if…
- the review stage itself is still undefined,
- you still do not know who can approve the work,
- multiple stakeholders are involved and no routing rule exists yet.
In those cases, go first to Proposal Revision and Approval Workflow for Freelancers and Solo Service Businesses, Milestone Delivery Workflow for Solo Service Businesses, or Approval and Feedback Routing Worksheet for Multi-Stakeholder Review.
What to do first
Confirm four things before you send another message:
- what decision you are actually waiting for,
- who the Next Action Owner is,
- what work or billing that silence is blocking,
- what date should trigger the next follow-up.
If those are not clear, the real problem is not silence. The real problem is that the review state was never defined tightly enough.
If several stakeholders are involved and the comments are not even reaching one clear approval path yet, define the routing rule first with Approval and Feedback Routing Worksheet for Multi-Stakeholder Review.
If the review has stayed blocked long enough that you need to choose pause, escalation, or closeout instead of sending another ordinary follow-up, use Escalation and Pause-State Worksheet for Solo Operators.
If the blocked review has already damaged the original plan itself and now needs a revised baseline, move next to Scope Reset and Recovery Worksheet for Solo Operators.
How long should you wait before following up?
Use the expected review window you already set. If none exists, use a short bounded follow-up rather than waiting indefinitely.
The important point is not the exact number of days. It is that review should have a visible boundary. A review state with no follow-up trigger is just parked work with nicer language.
What should the follow-up actually say?
Keep the message operational:
- restate what was sent,
- restate the decision needed,
- state what happens next once they reply,
- give one clear reply path.
Example structure:
“Checking in on the review package sent Tuesday. The open decision is whether this milestone is approved as-is or needs revisions. Once I have that answer, I can either close the milestone or schedule the next revision step.”
This works better than “just following up” because it names the workflow state directly.
When does silence become a workflow problem?
It becomes a workflow problem when:
- a milestone cannot close,
- the next invoice cannot trigger cleanly,
- closeout timing is now unclear,
- the same reminder is being rewritten without changing the state.
At that point, stop treating the issue as a one-off communication lapse. Name it in the system as blocked review or pending client decision.
Should silence count as approval?
Only if your agreement and review rules explicitly support that. Otherwise, no.
Operationally, silence is not the same thing as acceptance. If you need approval, ask for approval. If you can proceed after a bounded review window under agreed terms, document that rule in advance instead of inventing it during tension.
What if silence is delaying invoice closure or offboarding?
Separate the layers:
- review silence is one state,
- billing closure is another,
- final offboarding is a later stage.
If review silence is blocking invoice or closeout, keep that dependency visible rather than acting as if the project is already finished. Use Milestone Delivery Workflow for Solo Service Businesses for the review state, then Client Offboarding Workflow for Freelancers and Solo Service Businesses once true closeout is possible.
Where to go next
- If your updates are too vague to support clean follow-up, go to Client Status Update Workflow for Freelancers and Consultants.
- If the silence is happening during proposal review before signature, go to Proposal Revision and Approval Workflow for Freelancers and Solo Service Businesses.
- If the silence is happening at a milestone approval point, go to Milestone Delivery Workflow for Solo Service Businesses.
- If the project is near the finish line and review silence is blocking closeout, go to Client Offboarding Workflow for Freelancers and Solo Service Businesses.






