Rounds multiply for three reasons: client feedback arrives in sequence instead of in parallel, it comes from people who were never named as reviewers, and it lands in four places at once. Fix those three and one round becomes realistic. Give every reviewer role the same feedback window, collect all comments against one version in one place, which is what client proofing software is built to do, and require the client to resolve internal disagreement before it reaches the agency.
Round 2 happens on good campaigns. Round 4 is not a picky client. It is a process that lets the reviewer list grow after production starts.
Why does round 4 exist?
Tuesday, 10 a.m. Version 1 of the Black Friday email goes to Javier Peña, marketing manager on the client side. Wednesday he replies with six comments: subject line too long, swap the second product block, fix the discount copy. Thursday you send v2.
Friday at 4 p.m., Nadia Ortiz in the client's legal team sees the email for the first time. The offer needs a terms line and the exclusions have to be visible without scrolling. Monday you send v3. Tuesday, the CEO's cousin, who runs the brand's Instagram account, is added to the thread and says the hero image feels cold. Round 4 arrives eight days after v1, four days before the send date.
None of it was unreasonable on its own. The problem is structural, and it has three parts.
The reviewer list is open. Nobody wrote down who at the client reviews this email, so the set grows every time the file gets forwarded. Each round advertises the campaign to a few more people, and a share of them will have an opinion. Naming reviewers by role at kickoff is one of the eight fields we argue for in how to write an email campaign brief, and it is the field agencies skip most often.
Feedback is sequential. Javier reviewed alone, then legal reviewed alone. Because each reviewer only sees the version that survived the previous one, they comment on decisions the earlier reviewer already made. Reviewer three undoes what reviewer one asked for, and the agency becomes the arbiter of a client-side disagreement it was not part of.
Every round costs the same regardless of size. Rebuild, re-export, re-proof, re-send, write the note explaining what changed, wait. Call it 90 minutes of production and most of a working day of calendar time. Round 4 cost what round 1 cost, and it changed an image.
What is a role-based feedback window?
You collect feedback by role, not by person, and all roles review the same version at the same time inside one fixed window.
For a promotional email, the roles on the client side are usually four: the brand and copy owner, legal or compliance if the offer carries terms, the person who owns targeting and data, and the decision-maker who can say yes. Each role gets one named reviewer and one named backup. All of them receive v1 in the same hour with the same deadline. Forty-eight hours for a single email, seventy-two when legal is in the set.
Most agencies review in sequence for a defensible reason: they want to shield the client from a version with rough edges, or they want the main approver's take first. It feels efficient and it costs a full round every time a later reviewer objects to something an earlier one accepted. Sending to Javier first because he catches the big things is how Nadia's terms line becomes round 3 instead of a line item in round 1.
Parallel review only works if you scope it. Tell each reviewer what they own and, more importantly, what they do not: "Nadia, you are reviewing the terms line, the exclusions, and the unsubscribe copy. The hero image and the subject line are not in your scope." Without that, you get four opinions on the subject line and no one checks the legal note.
Then decide what happens when the window closes and someone has not answered. This is where the proofing window hands over to a decision deadline, and they are two different clocks: silence is not feedback, and it is certainly not approval. A late reviewer does not reopen a closed round by default. Both rules belong in a written approval SLA with your client, agreed before the first campaign rather than invented during it.
What is the one-voice rule?
The client sends one consolidated response per round.
Internal disagreement on their side gets resolved on their side, before it reaches the agency.
In practice that means one named feedback owner per campaign at the client. Javier collects what Marta Ruiz in CRM wants, what the country manager wants, and what legal requires, removes duplicates, resolves the contradictions, and sends one list. If Marta wants the price bigger and the country manager wants the lifestyle image bigger, both at the top of the email, that is Javier's call. It is not the agency's, and it should not cost two rounds to discover.
Give the feedback owner a format so consolidation is cheap. Four columns are enough:
Consolidated feedback format
- Which asset
- Where in it
- What to change
- Who asked
That last column matters more than it looks. It gives you a name to go back to when a request is technically impossible, and it makes visible when most of the comments come from one person who was never a reviewer.
The rule needs one written consequence, and this is the sentence that saves round 3: feedback arriving outside the consolidated response is a change request, not round feedback.
Be honest about the trade. The rule moves work onto the client, so it will not sell as a process improvement for the agency. It sells as date protection: every extra round pushes the send, and the send date is theirs. It also needs one obvious place to leave comments. When feedback lives in a Slack thread, two email replies, and a PDF with markup on page 3, the account manager is the consolidator no matter what the rule says, which is why the rule only holds if you also keep campaign feedback attached to the correct version.
What do you do when late feedback arrives anyway?
It will arrive. The move is neither to refuse it nor to quietly absorb it. Classify it, in writing, before you open the file.
Two questions do the sorting. Does it change what was already approved? Does it change the send date? Every late request lands in one of three buckets.
A factual error or a typo gets fixed, immediately, with no new round. "Ends 30 November" when the offer ends the 29th is not feedback, it is a defect.
A change of substance inside the agreed concept becomes a costed change request, priced in dates rather than hours: "We can add the second CTA. It moves the send from Thursday to Monday, and I need your confirmation before I start." Then you wait for the answer.
A change of direction after the client has approved is a new version and a new round, with the previous approval explicitly invalidated. If the client wants a different hero concept two days before the send, the honest answer is that the approved version stands or the date moves. Absorbing it silently teaches everyone that the window and the sign-off were both decorative. The mechanics of the first two buckets, where you handle changes after sign-off without restarting every review, come down to which approval scope the change actually lands in.
All three depend on knowing which version each comment was left on, and which version the client last agreed to. Agencies that run this in email lose that record inside a week, which is why "you approved it" becomes an argument nobody wins. This is the part LaunchSign is built around: reviewers assigned by role to each asset, one open round per version with comments anchored to the element in question, and a client who reviews and requests changes through a link without creating an account. When the round closes, approval is a separate action with its own record. It sits between the brief and the platform the client already uses to build and send campaigns, so the trail does not live in a mailbox.
Rounds start in the brief. If the reviewer roles, the window, and the feedback owner are not written down before v1 goes out, you are relying on goodwill to keep round 4 from happening.
FAQ
Is one review round realistic for a large multichannel campaign?
One round per asset, per production phase. A campaign with an email, a landing page, and an SMS has three assets and, if design and build are separate phases, up to six rounds. The goal is that no single asset needs a second and third pass to collect opinions that could have arrived together. Going from four rounds to one means consolidating reviewers, not reviewing less.
What if the client refuses to name one feedback owner?
Name one yourself and confirm it in writing: "We will treat Javier's consolidated email as the round response and read anything else as a change request." Most clients accept that once they see the alternative priced in send dates. If nobody on their side can resolve internal disagreement, you want to know before quoting the next campaign, because it will show up as unbillable rounds.
How long should a feedback window be?
Two business days for a single asset, three when legal or compliance is in the reviewer set, counted in the reviewer's business hours rather than yours. Shorter than a day produces skimmed reviews and late objections. Longer than a week lets priorities change underneath the campaign.
Does closing the proofing round mean the campaign is approved?
No. Closing the round means nothing is unresolved. Approval is a separate action on a named version by a named person, and a client who has run out of comments has not authorized anything yet. Keeping the two apart is what makes the round countable and the sign-off defensible.
