A client asks for a round of revisions, you deliver, and then... silence. No approval, no rejection, no reply. Weeks later they say "I never signed off on that" — even though you sent it, waited, and heard nothing back.
A "deemed approved" clause (sometimes called "automatic approval" or "silence is consent") closes that gap. It says, in writing, that if a client does not respond within a set number of days, the deliverable counts as approved. This article gives you the exact wording to add to your contract, how to introduce it without sounding harsh, and the messages to send once the clock is running.
Why this clause matters
Most freelance disputes about scope and payment are not about bad work. They are about missing proof. Without a deemed-approved clause, an unresponsive client can stall a project indefinitely, refuse to pay the final invoice, or come back months later disputing something they never actually rejected.
With the clause in place, you have three things working for you: 1. A deadline the client agreed to in writing. 2. A default outcome (approval) if they miss it. 3. A paper trail of reminders, which is what actually matters if a dispute ever goes further.
The clause: core wording
Use this as a starting point. Adjust the number of days and the deliverable language to match your contract.
Approval and Deemed Acceptance. Client will review each deliverable and provide written approval or specific, written revision requests within [5] business days of delivery ("Review Period"). If Client does not respond within the Review Period, the deliverable will be considered approved ("Deemed Approved") and Freelancer may proceed to the next project phase, issue the related invoice, or consider the project complete, as applicable. A reminder sent by Freelancer during the Review Period does not extend the Review Period unless both parties agree in writing.
A shorter version for simple contracts
If your contract is a one-page agreement rather than a full legal document, this shorter version covers the same ground:
Client has [5] business days from delivery to request changes in writing. If no response is received in that time, the work is considered approved and the project moves forward / the invoice is due.
A version tied to milestone payments
If you invoice per milestone rather than at the end, pair the clause with payment terms directly:
Each milestone has a [5]-business-day review period starting from the delivery date. Deemed-approved milestones are invoiced immediately and payment is due under the standard payment terms in Section [X]. Deemed approval does not waive Client's right to request paid revisions after delivery; it only confirms that the milestone as delivered met the agreed scope.
How to pick the number of days
- 3 business days — fast-turnaround work: social content, single-page copy, small design tweaks.
- 5 business days — the most common choice. Enough time for a client to actually look at the work, not so long that it stalls the project.
- 7–10 business days — larger deliverables (a full website, a brand package) where the client genuinely needs more time to review internally or route it to stakeholders.
Match the number to how long a careful review realistically takes. A number that is too short feels like a trap; a number that is too long defeats the point of the clause.
How to add it without the conversation feeling confrontational
Clients rarely object to this clause when it is framed as mutual protection rather than pressure. A short note when you send the contract works well:
One thing I added to this version of the agreement: a short review window (5 business days) after each delivery. If I don't hear from you in that time, it's treated as approved so the project keeps moving — but you're always welcome to flag changes before then, and reminders don't start a new clock. It just keeps both of us from losing track of where we are.
Using the clause once the clock is running
The clause only works if you actually send reminders — it is not meant to let a reminder-free silence count against the client. A simple reminder sequence:
Day 3 of 5 (gentle nudge): > Hi [Name], just checking in on [deliverable] sent on [date]. No rush, just flagging that the review window closes [date] — let me know if you'd like any changes before then.
Day 5 (window closing today): > Hi [Name], today is the last day of the review window on [deliverable]. If I don't hear back by end of day, I'll treat it as approved per our agreement and move ahead to [next step / invoice].
After the window closes (confirming deemed approval): > Hi [Name], the review window for [deliverable] closed on [date] with no changes requested, so per our agreement it's now approved. I've logged it and I'm moving on to [next step]. Happy to revisit anything specific if it comes up later, just flag it and we'll scope it as a separate update.
That last message is the one worth keeping a copy of. It is the written record that turns "deemed approved" from a contract clause into an actual fact you can point to later.
Keeping the record, not just the clause
A clause is only as useful as the log behind it. If a client ever disputes a deemed-approved item, what settles it is being able to show the delivery date, the reminders, and the date the window closed — in one place, not scattered across email threads.
That is exactly what the Client Approval Log is built for: an Excel sheet that tracks every delivery, approval status, and revision round with dates, plus 50 ready-to-paste messages for approvals, scope creep, and exactly this kind of follow-up when a client goes quiet.
Client Approval Log + 50 Client Messages
Keep a written record of every approval, and ask for it politely. $5.
Get it on Gumroad