P2 · Trying to get paid
The Client Went Silent Mid-Project
Handle a silent client with written review windows, precise approval requests, project-pause rules, released calendar capacity, restart terms, and delivery evidence.
Silence is a scope and scheduling problem, not just a communication annoyance. Your contract should identify client dependencies—feedback, approvals, data, access—and explain what happens when they are late. A deemed-approval clause can say that a deliverable is treated as accepted if no written rejection identifying specific defects arrives within a stated review window, but enforceability and fairness depend on the contract and law.
Use a dated reminder ladder so silence has a process
Use a reminder ladder tied to dates: deliverable sent, review due, reminder, pause notice, then restart process. The client should be able to see exactly which dependency is blocking progress.
Release a stalled calendar slot after a documented review window
Silence protocol: Day 0 deliverable sent with review due Friday; Monday reminder identifies the exact decision; Wednesday pause notice says schedule is released after Friday; if no response, project status changes to paused and a new restart date is quoted when the client returns. These are example operating dates, not legal mandates.
Move the schedule when the client misses its review dependency
Do not keep a delivery slot open forever. State that dates move by at least the length of the client delay and may be rescheduled around other committed work.
A restart fee must be agreed before the long pause
A restart fee can compensate for remobilizing after a long pause, but it should be agreed in advance and proportionate to real coordination cost rather than invented after the client disappears.
Tie cash flow to objective stages instead of endless client approval
Protect cash flow by tying milestones to delivery or objective stages rather than an approval the client can postpone indefinitely. Another option is billing reserved capacity on a monthly retainer.
Protect the schedule when approval becomes the bottleneck
Silence is expensive because it consumes schedule capacity while leaving acceptance and payment unresolved. Design a review window into the contract and every delivery email. A deemed-approval clause can state that a deliverable is accepted if no timely written rejection identifies specific deficiencies, but whether that clause is appropriate or enforceable depends on the agreement and law. Even without deemed approval, you can define a project-pause rule so a missed review deadline releases the delivery slot instead of reserving it indefinitely.
Use a dated reminder ladder: deliverable sent, review due, first reminder, pause notice, then project status changed to paused. Preserve the exact deliverable and delivery timestamp. Tie payment milestones to delivery or another objective event when possible so the client cannot postpone cash forever by declining to click 'approve.' If you use a restart fee, agree to it in advance and connect it to real remobilization cost. When the client returns after weeks or months, do not promise the old due date. Reconfirm scope, outstanding invoice status, dependencies, current availability, and a new calendar before work resumes.
Prevent the silent-client problem in the project design. Put feedback windows on the timeline and state what happens when the client misses them: the project pauses, later dates move, and restart depends on capacity. A ‘deemed approval’ clause can be useful in some contracts, but it should be drafted carefully for the service and jurisdiction; it is not a license to treat obviously unfinished work as accepted. A safer operational version is often to make the next phase contingent on written approval and to suspend the schedule after a defined review period. For retainers or reserved capacity, specify whether the reservation continues to be billed while the client is unavailable.
When silence happens, send messages that make the decision easy. First recap what is awaiting review and link directly to the item. Then give two choices and a date: approve the draft, or send consolidated changes by Friday. If there is still no response, cite the project pause rule and explain the schedule consequence. Do not keep producing downstream work that depends on unapproved assumptions. Preserve the messages and current files so the state of the project is clear if payment later becomes disputed. If the client returns after a long pause, reassess availability, stale assumptions, vendor prices, and whether a restart fee or revised schedule is allowed by the agreement. A dormant project should not occupy invisible capacity forever.
Put one owner on each approval. ‘Client team to review’ is an invitation to silence because nobody knows who must decide. The project plan should name the approver and state whether consolidated feedback is required. If multiple stakeholders can comment, ask the client to resolve contradictions before sending revisions. That prevents the freelancer from acting as an unpaid internal referee. When the approver changes, confirm the new person and reset the review date in writing. A surprisingly large share of ‘ghosting’ is not disappearance; it is an undefined internal decision path. Fixing ownership can restart the project without adding pressure or legal language. Track how many calendar days each approval actually takes. After several projects, replace optimistic two-day review assumptions with the client reality. Better schedules reduce the temptation to blame a silent client for a delay the project plan should have anticipated.
Silent-client response timeline
- Review request
Send the deliverable with the exact decision or feedback required, where to respond, and the review date already agreed in the project process. “Any thoughts?” is too vague for a stalled client.
- Reminder
Reference the pending item, explain what downstream work cannot proceed, and restate the date when the schedule assumption changes. Preserve delivery timestamps and follow-ups.
- Pause
Use the contract’s pause, deemed-approval, rescheduling, or nonpayment language only if it actually exists and is enforceable in context. Release capacity when the documented trigger is reached rather than keeping the slot reserved indefinitely.
- Restart
When the client returns, confirm outstanding invoices, current scope, changed assumptions, decision-makers, and a new delivery slot. A months-old calendar promise should not automatically revive after the client’s silence.
Before a stalled project consumes another week
- Put review windows in the contract.
- Name the exact approval or feedback needed.
- Release calendar capacity after the stated pause point.
- Preserve delivery and reminder evidence.
- Re-scope and re-schedule after a long silence.
Client-delay and contract references
Questions to answer when the client disappears
What should I send when a client goes silent?
Ask for one specific decision, restate the review deadline, and explain the schedule consequence already provided in the agreement. A message such as 'approve option B or send consolidated changes by Friday' is easier to act on than a general request for feedback.
Can I treat silence as approval?
Only if the agreement clearly created a valid deemed-approval mechanism and applicable law supports it. A safer operational pattern is often to make the next phase dependent on written approval and to pause or release the schedule after a stated review window.
What happens to the project slot after repeated silence?
Follow the written pause rule. You can release reserved capacity and quote a new restart date when the client returns, rather than keeping the calendar indefinitely blocked. State that consequence before the pause, not as a surprise after weeks of inactivity.
Can I charge a restart fee?
Only if the contract supports it and the amount is lawful and commercially reasonable. A restart can involve re-planning, reloading files, rechecking assumptions, and rebooking scarce capacity, but the fee should not be invented after the delay has already happened.