Free tool
Turn silence into an approval.
Generate a feedback-deadline clause for your next proposal or contract — if nobody responds in time, the current version counts as approved and the project moves on.
The mechanism
A deadline needs a default.
Without one, an unanswered round doesn't fail — it just doesn't end.
Most review rounds don't stall because someone said no. They stall because nobody said anything, and there is no rule for what happens next — so the work sits until somebody remembers to chase it.
A feedback deadline fixes that by giving silence a meaning. State the window, and say plainly that no response inside it counts as approval. The round ends either way — with a yes, or with the clock deciding for you.
That only works if the deadline is actually tracked and the decision it produces is recorded somewhere, which a clause on its own cannot do. yeses sends the reminders and marks the decision, whichever way it lands.
What this isn't
A clause, not a contract.
This is wording to start from. Whether it holds depends on where it sits and whether you actually follow it.
It isn't a substitute for whatever your agreements are actually structured around. Read it against your own contract or proposal template before it goes anywhere near a client.
It also isn't automatic. The clause only does what it says if a stalled round is actually allowed to move forward instead of getting chased for another week anyway — the wording sets the rule, you still have to use it.
If it's the rounds themselves that are expensive rather than the waiting, the revision cost calculator puts a number on that instead. Not sure which one applies? The approval health check is six questions that name the gaps, in the order they cost you.
Questions
About this clause.
Is this legal advice?
No. It's wording to start from — check it against how your own contracts or proposals are actually structured, or with someone who reviews them for you.
What counts as 'delivery', so the clock starts?
Whichever moment you already use to send work for feedback — an email, a shared file, a review link. The clause doesn't define it, because your process already does.
What if a client asks for more time on one round?
Grant it case by case. The clause sets a default, not a rule you can never bend — the point is that silence has a meaning, not that every deadline is rigid.
Does silence-as-approval actually hold up if it's never enforced?
No better than any clause nobody applies. It only works if a stalled round is actually allowed to move forward instead of getting chased for another week anyway.
Is my input stored anywhere?
No. The clause lives in the page and in the link you copy. Nothing is sent to a server, and there is no account to make.
The deadline is the easy part. Tracking it is the rest.
Every reminder sent automatically, every decision recorded against a name and a version, whichever way the clock lands.