A Quiet Review Round Does Not Tell You the Site Is Approved
An empty inbox leaves several possibilities open. Give the client a simple way to say which one applies and update the plan from that answer.

The review deadline passes without a reply. There are no new comments on the website. That tells you that no response has reached the agreed channel; it does not establish whether the client opened the page, finished reviewing it or accepted the version you sent.
Give the uncertainty a name
In this fictional example, a freelancer has asked a clinic manager to check two service descriptions before a planned launch. The manager has not replied by Wednesday. The freelancer is tempted to label the copy approved so the schedule can continue. A more useful status is “review response not received”, followed by a concrete next action.
This article offers a collaboration process, not an interpretation of contractual silence. Do not invent a legal meaning for non-response. If the project has agreed acceptance provisions or an unresolved contractual question, use the applicable agreement and appropriate advice. The practical record should still distinguish the evidence you have from what you hope the client meant.
Check the invitation before sending another reminder
Confirm that you sent the intended version through the agreed route, to the right review contact, with a clear assignment. Was the client asked to check service facts or the whole website? Could they access the pages? Did you give a return date that had actually been agreed? A reminder cannot repair an undefined review task merely by sounding more urgent.
Check for a response in the agreed channel and any known alternative that you offered. Do not demand that the client resend feedback you already received by telephone but failed to record. If someone else is coordinating the client’s contributors, ask that coordinator about progress rather than starting competing reminders to everyone.
Send a reminder that permits an honest answer
Use a message with three response choices, written as ordinary language rather than a forced approval button. The recipient should be able to say they have not started without disguising that as rejection or acceptance. Keep the version and required decision visible.
A possible message reads: “Hi Alex, I have not received the factual review of Services A and B, version C sent on Monday. Could you tell me which applies: you have not reviewed them yet; you have reviewed them and have corrections; or you have reviewed this version and confirm that these two service descriptions are accurate? If access is the obstacle, let me know and we will use another route. Please suggest a realistic return time if Thursday is no longer workable.”
Record the answer at its actual scope
“I looked and it seems fine” may still require one short clarification. Ask whether the person is confirming the assigned factual descriptions in the named version. Do not silently expand that answer to form behaviour, specialist checks, every page or permission to launch. If their role is limited, preserve that limit.
If the client says they have not reviewed, record that answer and agree the next review point. If they send corrections, process them as corrections. If they confirm the requested material, record who confirmed what and which version it concerns. A later material edit may require a fresh decision on the affected content; the old answer should not automatically cover it.
Make the scheduling consequence explicit
When a response remains outstanding, explain the dependency in practical terms: “We need the service facts confirmed before publishing those descriptions. If the review arrives Friday, we will reassess the launch window after the resulting changes and checks are known.” Avoid presenting an unchanged launch date as certain while its prerequisite is unresolved.
You may be able to offer a narrower release or a short guided review. Describe the actual boundary and ask the authorised person to choose. Do not remove important content or publish unconfirmed claims simply to avoid another conversation. A useful alternative states what can proceed, what remains excluded and which decision is still needed.
Close the loop without rewriting history
When the response arrives, keep the earlier waiting period visible enough to explain the revised plan. The aim is a reliable sequence, not a case against the client. One clear reminder, a precise answer and an updated dependency are more useful than a thread of escalating “just checking” messages.
Make it easy for the client to distinguish “I have not reviewed it” from “I have reviewed this version.” Your feedback process should preserve that distinction instead of inferring approval from silence.
Continue with Ask a Busy Client to Review Three Pages, Not “the Website” and “Resolved” Is Not the Same as “Ready to Launch”.




Discussion 0
What did this article make you think about?