The worst status a deliverable can have isn't "rejected" — it's "in their inbox." You sent the work two weeks ago, the final invoice is queued behind client acceptance, and the client, so responsive back when this was a sale, has gone quiet. You can't bill, you can't close the project, and you can't confidently book the next one into the gap either, because this one isn't actually over.
Six weeks from now they'll resurface, having finally looked at it, carrying a list of thoughts — and because nothing in your paperwork says the project ever ended, that list is indistinguishable from the revision round you already budgeted for. This limbo is what a deemed-acceptance clause exists to prevent. It's one paragraph in the contract and one line in your delivery email, and it converts client silence from an open file into an answer.
What deemed acceptance actually is
A deemed-acceptance clause says a deliverable counts as accepted — formally, with invoicing consequences — if the client doesn't return written objections within a defined window after delivery. That's the whole mechanism. The client keeps a real review period with a real remedy: written deficiency notices, free corrections against the agreed criteria. You get a date on which the deliverable is done whether or not anyone has found time to look at it.
It isn't a gotcha, and it isn't a freelancer invention — professional-services agreements have run on this structure for decades, because both sides benefit. The client's alternative to a review window is not unlimited review time. It's vendors who, burned once, quietly price limbo into every proposal and pad every timeline.
One caveat before the wording, the usual one: this is orientation from an operator, not legal advice. Contract norms vary by state and country, and paperwork carrying real money deserves an hour with a lawyer in your jurisdiction. What follows is the structure you'll pay that lawyer to adjust, not to invent.
Why five business days
The window has to survive two opposing pressures. Short enough that a one-person business isn't financing the client's inattention — every silent week is a week the final invoice doesn't send. Long enough that an honest client with a company to run can genuinely review: convene the stakeholder, open the staging link twice, write down the objections. Five business days is where those pressures balance for most deliverables a solo operator ships.
It also calendars cleanly. Deliver on a Monday and the window closes end of business the following Monday — one working week, no arithmetic about weekends, no argument about holidays. (There is no argument, in this clause: only business days count, so a project delivered Thursday crosses a weekend without burning two of its days.) Scale the number by deliverable size if you like — three business days for a one-page asset, ten for a full site — but put the scaling in the contract, not in a vibe.
What you never do is leave the units fuzzy. "Within five days of delivery" invites a dispute about whether Sunday counted; "within a reasonable time" invites a dispute about everything. Business days, a stated count, and — in the delivery email, where the clause actually comes alive — the named calendar date it closes.
The clause, word for word
Here it is, built to sit in a statement of work or service agreement next to the acceptance criteria it references:
Each deliverable is deemed accepted five (5) business days after delivery unless the Client provides, within that window, written notice of specific deficiencies referencing the acceptance criteria for that deliverable. Deficiency notices must be consolidated into a single written list. Corrections of deficiencies so identified are made at no charge within five (5) business days. Requests first raised after the window closes, or exceeding the agreed criteria, are handled as change orders under the change-control section.
Walk the load-bearing phrases, because each blocks a specific failure. "Written notice" kills the phone-call objection nobody quite recorded. "Specific deficiencies referencing the acceptance criteria" is the fairness hinge: the client can't veto with "we're just not feeling it" — they point at criteria they signed, and you fix what genuinely misses them, free. That obligation is what makes the window defensible on the day you have to stand on it.
"Consolidated into a single written list" is the anti-drip-feed line — no Tuesday email, Thursday addendum, Sunday afterthought; one list, one pass. The last sentence is the boundary that keeps the project finite: anything after the window, or outside the criteria, routes to the same change-order process as all other new work. None of this is harsh. All of it is stated — and stated is what lets it be routine instead of personal.
The delivery email that starts the clock
A clause in a signed PDF starts no clocks by itself. The clock starts when a reasonable person would say delivery happened — so make delivery an event, with a timestamp and a spelled-out end date. The email is a form letter once you've written it once:
Subject: [Deliverable] delivered — review window closes [date] Hi [name] — [Deliverable] is delivered: [link / attachment]. Per our agreement, the review window is five business days, so it closes end of business [weekday], [month] [day]. If anything misses the acceptance criteria, send it to me as one consolidated list by then and corrections are on me. If I don't hear otherwise by that date, the deliverable counts as accepted and I'll send the [milestone / final] invoice.
Two details carry the weight. First, name the actual date — "closes end of business Monday, October 5" — because nobody, including you, wants to reconstruct business-day arithmetic six weeks later, and a named date is what both inboxes will search for. Do the counting for them. Second, say the quiet part plainly: silence means acceptance, the invoice follows. Stated warmly in advance, that's a courtesy. Sprung afterward, the same fact reads as a trap.
And when the window passes in silence, send the invoice that day — not the following week, not after things settle. The clause's value compounds through predictability: clients learn your dates mean something, which is exactly the reputation that makes the next client's window feel routine rather than adversarial.
Day six, when "one more thing" arrives
The clause will be tested, usually within the first few clients, usually politely: day six or seven, an email that opens with an apology and contains a list. How you answer the first one sets the precedent, so answer with structure, not irritation. Sort the list into two piles — misses against the acceptance criteria, and new direction — and respond to each pile on its own terms:
Thanks — good catches. Two of these are on me: [items] miss the criteria we agreed, and corrections come back by [day]. The other three are new direction rather than fixes, so I'll send a change order for those today — priced on their own, and the corrections aren't waiting on it.
Yes, you'll occasionally absorb a marginal call, and yes, that's the cost of the system working — a clause enforced rigidly against a genuine defect loses the only court that matters at this scale, which is the client's sense of whether you're straight. The new-direction pile is where the clause earns its keep. You're no longer refusing an open-ended obligation; a signed document is routing the request to a process they've already used. Most clients, shown the boundary once, work within it happily — the deadline was never the imposition. The ambiguity was.
The edge cases
Client vanishes mid-project: deliver the milestone to the agreed channel anyway, with the same email. The window runs, acceptance happens, the invoice sends. A client who has abandoned a project rarely disputes its paperwork — and if they resurface in three months, the record shows a delivered, accepted milestone rather than your unilateral decision to stop.
Partial or preview deliveries don't start the clock. The clause covers deliverables, so label anything incomplete as a preview — explicitly — or someone will eventually argue the window ran on a draft. Each milestone gets its own window, starting at its own delivery; they don't chain, and they don't overlap.
When a client pushes back at signing — some will, and it's a healthy sign they're reading — concede the length, never the existence. Ten business days costs you almost nothing when everyone knows the date; a contract with no window costs you the ending of every project. The pushback worth real thought is the enterprise client whose procurement boilerplate imposes its own thirty-day review. That's a business decision about deal size and cash timing, taken with open eyes — not a clause problem.
Make silence an answer
Every deliverable you ship either ends on a date or ends when the client gets around to it. There is no third option, and the second one is why so many solo businesses keep a graveyard folder of projects stuck at ninety-five percent. The window takes an afternoon to adopt: one paragraph in the contract, one form email, and the discipline to name the date every single time. The Client-Ready Business Templates ($19) ship the service agreement and statement of work with this language already in place, alongside the change order it routes to; the statement of work piece covers the acceptance criteria this clause points back to. Then send tomorrow's delivery email with a date in it, and let the silence finally mean something.