Notes / Approvals / 4 min read

Revision rounds on a social post

WhizSuite · 2026-10-21

Rounds only work if everyone can tell when a round starts and when it is spent.

Count rounds on the batch, not the mood

A round is a set of notes on a named version, answered with a new named version. It is not every ping that arrives while you are in the file. If you count pings, the client will feel metered and you will still do free work.

Say the number in the proposal. Two rounds on the monthly batch is understandable. "We'll tweak until it feels right" is how Thursday disappears.

What belongs in round one

Round one should catch the claim, the crop, the offer, and anything that would embarrass the brand. It should not be the moment the client sees the idea for the first time if you can help it. A short brief approval before design saves a round you would rather spend on polish.

Bundle notes. A client who sends six separate messages is still on one round if those notes are about the same version. Reply once, with one new export.

The round after the last round

Extra rounds are a change order or a more expensive retainer. They should not be a surprise in week three. Say that before you are tired, not after the fourth "small" change.

A legal correction is not a taste change. Leave room for a safety fix without pretending that a new concept is a safety fix. If the idea changes, the round count resets because the work changed.

Show the count where the work sits

If the round count lives in a slide from onboarding, nobody will check it. Put it next to the post. Version two of four is a calmer sentence than a debate about whether this note "really" counts.

When the count is visible, account managers stop apologizing for the contract. They point at it. That is a better use of the relationship.

Join the waitlist