How to run website approval rounds without endless emails.

"Just one more thing" is how projects quietly double in length. Each small request seems reasonable on its own, but together they turn a two-week review into two months of email. The fix is not to be stricter with clients. It is to give reviews a shape they can follow.

What an approval round actually is

A useful round has four parts:

1. You open the round. You share the pages to review, say what the round is about and give a date.
2. The client collects everything. All comments from all reviewers, on all pages in scope, in one place.
3. The client sends it. They tell you the feedback is complete. From now on, the batch is closed.
4. You make the changes and answer each comment. Then you ask for approval, page by page.

The important part is step 3. Without a clear "this is everything", you start working on the first comments while new ones keep arriving, and the round never ends.

How many rounds to include

There is no right number, but there should be a number, and it should be in your proposal. Many studios include two or three rounds of revisions per stage. Choose what fits your price and the size of the project, and write down what happens after that: an hourly rate, a fixed price per extra round, or a new quote.

Saying it up front is far easier than raising it in week six. Most clients are fine with limits they agreed to at the start. What frustrates them are limits they discover later.

Approve page by page, not "the website"

"Is the website approved?" is a big question, and a nervous client will hesitate. "Is the About page approved?" is a small one. Breaking approval down by page has several benefits:

• Progress is visible. Eight of ten pages approved feels like nearly done.
• Approved pages stay approved. If someone wants to reopen one, it is a clear and visible decision, not a casual comment.
• Problems stay contained. A difficult Pricing page does not hold back the Contact page.

Keep a simple list of pages with a status for each: still to review, feedback sent, approved.

Make "approved" mean something

An approval should be written, specific and easy to find later. "Looks good!" in a chat message is friendly, but it is not a decision about a particular page in a particular state. Better options:

• A reply to an email that names the page and says "approved".
• A status on the page itself, set by the client, recorded with their name and the date.
• A signed sign-off form at the end of the project (see the launch sign-off checklist).

What matters is that later, if someone asks "did we agree this?", you can show the answer in seconds.

Set a rhythm

Rounds work best with a fixed rhythm that both sides can plan around. For example:

• You open a round on Monday.
• The client sends all feedback by Thursday.
• You reply and deliver changes by the following Tuesday.
• The client approves or asks again by Friday.

If the client misses a date, the next step moves, and so does the launch. Saying this kindly and early protects your schedule without any drama.

When rounds are not the right fit

Rounds are not always necessary. On a small update, a landing page or a client you have worked with for years, it can be simpler to let notes flow as they are written and deal with them in batches yourself. The point of rounds is control on bigger projects, not ceremony on small ones. Choose per project, and say which way you are working.

Templates you can adapt

Opening a round:

"Hi Ana, round 2 is ready for review: Home, About, Services and Contact. This round is about wording and photos; the layout is agreed. Please collect everything from your team and send it by Thursday. I will reply to each comment and send the changes on Tuesday."

Closing a round:

"Thanks, I have everything. I will not add new comments to this round, so anything else that comes up will go into round 3. You will have the changes on Tuesday."

Asking for approval:

"All comments on the Services page are done. Could you check it and mark it approved if you are happy? If anything is still not right, leave a note on the page and I will pick it up in the next round."

How Tweakpin handles rounds

In Tweakpin, your client leaves notes pinned to the elements on the live page. With rounds on (the default), they collect their notes on a page and press Send feedback when they are done, and the page then shows as feedback sent until you have looked at it. When you have made the changes, the client sees which notes were addressed and approves the page, or asks again. Each page shows its status (still to review, feedback sent or approved) to everyone who opens it.

If a project does not need rounds, you can turn them off for that site: notes then reach you as they are written. Either way, the conversation stays under each note, on the page it is about, instead of spreading across email threads.