A sane system for managing revision requests from clients

Start with a number, not a feeling

The healthiest revision process starts before the first draft exists. Tell the client exactly how many rounds are included and what a round looks like in practice. A number on the invoice agreement beats a vague promise to keep going until it feels right.

Open-ended revision language sounds generous and turns into a second unpaid job. Clients do not push past a stated limit when they met it on day one. They push when the limit was never there.

Treat comments as a batch

One collected round beats five scattered ones for both sides. Ask the client to gather feedback from their team and send it in a single document or timestamped list. You answer everything at once and the draft stays coherent.

Scattered comments are where scripts fall apart. A note about the intro arrives, you rewrite it, then a note about the ending contradicts the new intro. Batching removes that loop and saves everyone a week.

A revision round is a batch of comments, not a drip of second thoughts over fifteen days.

Separate preference from correction

Some notes fix a factual error or fix a line that misrepresents the client's product. Those are corrections and they always get handled. Other notes say the tone feels off or the hook could be punchier, which is taste, and taste has no natural stopping point.

When a note is taste, offer one adjustment and describe what you changed. If they still dislike it, that is a new round, not a reopening of the old one. Naming the difference out loud keeps the process fair.

Hold the line without hostility

Enforcing limits does not require a cold voice. A short message works: this round covers the notes you sent, and the next set starts a third round at the quoted rate. Most clients accept that without friction because you warned them early.

The clients who react badly to a stated limit were the ones planning to ignore it. That reaction is useful information about the rest of the project.

Key takeaways

• Quote a fixed number of revision rounds in the original scope
• Require feedback in one collected batch per round
• Handle factual corrections, and treat taste changes as new rounds
• Warn about extra rounds in writing before you start them
• Log which round each comment set belonged to

Use the system you already have

You do not need new software to manage revisions. A spreadsheet with draft versions, comment dates, and round counts covers it. The point is that both you and the client can answer the question how many rounds are left without digging through chat history.

When revision volume starts to eat your week, the data you kept tells you whether to raise prices, tighten the original brief, or drop that client. Managing revision requests is really managing information, and sloppy records hide the truth.