Tips & Tricks

Put Feedback Rules in the Contract: Rounds, Deadlines, Sign-Off

A website revision policy belongs in the contract. Sample clauses for revision rounds, feedback deadlines, one feedback channel and sign-off.

A contract with a green seal on the signature line, a calendar and arrows looping around them.
A practical field guide
In this article 6 sections

It is week nine of a six-week project. The client’s e-mail is titled “a few last tweaks” and lists 23 items, four of which undo changes they approved in round two. You open the contract to check what you promised and find one line: “The price includes revisions.”

That line is not a website revision policy. It is an open tab. The fix is not being stricter with clients, it is writing the rules down before anyone is annoyed, so both sides know how many rounds there are, when feedback is due, where it goes and what “done” means. Below are sample clauses you can adapt, and a way to run them day to day. They are a starting point, not legal advice: have your lawyer check them against your contract and local law.

Why “includes revisions” is not a revision policy

Open-ended revisions fail in a predictable way. Without a number, every request is “a small change”. Without a deadline, feedback arrives whenever the client’s boss finally looks. Without one channel, round two lives in an e-mail, a phone call and a WhatsApp message, so nobody can say when it ended. And without a sign-off rule, the project is never quite finished, which also means the final invoice is never quite due.

Most of what gets called scope creep starts here. The client is rarely acting in bad faith. They simply were never told where the edges are.

Five clauses for your website revision policy

Each clause below answers one question the client will otherwise answer for you. Replace the numbers and names with your own.

1. How many rounds, and what a round is.

The fee includes two (2) rounds of revisions at the design stage and two (2) rounds at the development stage. A round is one consolidated set of feedback submitted within the feedback window. Further revisions are billed at [hourly rate] or quoted separately.

The definition matters more than the number. “One consolidated set” stops a round from turning into a drip of messages over three weeks.

2. The feedback window.

The Client will submit feedback within five (5) business days of the Agency announcing that a stage is ready for review. If no feedback is received in that time, the round is closed. Delays in feedback move the delivery date by the same number of days.

The last sentence is the one clients remember. It links their speed to the launch date without anyone having to argue about it.

3. One channel, one contact.

Feedback is submitted by the Client’s designated contact, [name], through the feedback tool on the staging site. Feedback sent through other channels becomes part of a round only once it is added there.

4. Revision, change request or defect.

A revision is a change within the approved brief and scope, such as copy, colour, spacing or layout details. New pages, features, integrations or changes to previously approved designs are change requests, quoted and scheduled separately. Defects, meaning anything that does not work as specified, are fixed at no charge and do not count as a revision round.

Keeping defects out of the rounds is fair to the client, and it makes the rest of the policy easier to accept.

5. Sign-off.

After the final round, the Agency will request written sign-off. Within five (5) business days the Client will either confirm acceptance or list remaining defects. If the Client does neither, or publishes the site, the work is deemed accepted.

Putting the rules to work, step by step

A clause nobody follows is just paper. This is how the policy runs on a real project.

  1. Put the rules in the proposal, not only the contract. The client should see “two rounds per stage, five business days each” when they compare quotes, not discover it at signing.
  2. Walk through them at kickoff. Ten minutes, with the timeline on screen. Show the client how to report something so the channel clause is easy to keep. Our guide on how to get useful feedback from non-technical clients covers what to show them.
  3. Open each round with a date and a link. “Round 1 is open until Friday 5 pm.” With Zorko, the widget on staging stays hidden in the default Only people with the link mode, so you send the client the staging URL with ?zorko=KEY and only they can report. They need no account. Each report arrives with the page URL, browser, device and a pin on the exact spot, so “the button on the right” never needs a follow-up call.
  4. Close each round in writing. When the window ends, send a short summary: how many items came in, how many are done, which ones are defects and which are change requests with a quote. The Zorko dashboard list with statuses and comments is your record of what was reported and when. A review link (valid for 1, 7 or 30 days) lets the client see every report as a pin on the live page, including what is already fixed.
  5. Tie sign-off to your QA pass. Request sign-off only after your own launch QA checklist is clear, so the client is signing off a site you have already checked. Our older post on the approval workflow has an approval e-mail template you can reuse here.

When the client breaks the rules

They will, and that is fine. The policy exists so you can be generous on purpose instead of by accident. A few replies that keep the tone friendly:

  • Late feedback: “Thanks, these are useful. Round 2 closed on Friday, so I will add them to round 3, or we can handle them as a small change request if you would rather not wait.”
  • Feedback by phone: “Got it. Could you drop that as a pin on the page? That way it is in the round and nothing gets lost.”
  • A new feature mid-round: “Good idea. It is outside the current scope, so I will send a short quote today and keep the rest of the round moving.”

Each reply points back to the clause, not to your mood. That keeps the relationship out of the argument.

Count it for yourself

A rough formula for what an unwritten policy costs you:

extra rounds × hours per round × your hourly rate

An illustration: say a project priced at $6,000 was planned with two rounds and ended with four. If each round takes six developer hours and two project manager hours at a blended rate of $60, the two extra rounds cost 16 hours, or $960. That is 16% of the fee, gone without anyone deciding to give it away.

Run the numbers on your last three projects. If the extra rounds add up to more than an afternoon of work, the five clauses above are worth adding to your next contract. And if you want one channel for feedback that makes rounds easy to count, start a free Zorko project on your next staging site.

FAQ

How many revision rounds should a website contract include?

Two rounds per stage is a reasonable starting point for most brochure and small business sites. Larger projects may need more, but the number matters less than a clear definition of what one round is.

What if the client misses the feedback deadline?

The round closes and the delivery date moves by the number of days of the delay, as the clause says. Tell the client in writing when the window closes, so it never feels like a surprise.

Do bug fixes count as a revision round?

They should not. Anything that does not work as specified is a defect, and fixing it is part of delivering the work. Keeping defects out of the rounds makes the rest of the policy fair.

No. They are examples to adapt. Contract law differs between countries, so have a lawyer review the final wording, especially the deemed acceptance clause.

Zorko news in your inbox

Product updates and practical tips for agencies, about once a month. Nothing else.

Put it into practice

Give clients the right way to show what they mean.

Zorko keeps screenshot and desktop video feedback together with the page details your team needs to act.

Start free See how it works

Free includes 1 project and 10 feedbacks a month. No credit card required.