How We'd Write Revision Rounds Into Your SOW

Round three shows up as a forwarded email with eleven comments, four of them from someone who wasn't on the kickoff call. The SOW says "two rounds of revisions." The client says they're still on round two, because the first batch "was just initial thoughts." Design has already opened the files.

So how many rounds of revisions should you include? For most creative deliverables, two is a reasonable default. But the number was never what failed here. The SOW said "two" and never said what a round is, so nobody could count them, and they couldn't run out. Here's how we'd write revision rounds into an SOW, in the order we'd do it: pick the number, define the round, draft the six lines, then propose them and hold the line when someone tests it.

The clause below is sample wording, not legal advice. Have your own contract reviewed before you use it.

Step 1: pick how many rounds of revisions to include

Our starting points, from common agency and in-⁠house practice rather than any industry standard. Adjust for budget, risk and the number of approvers.

Two rounds hold up when each one is real. Five rounds fall apart when none of them are. The definition decides which you get, so that's the next step.

Step 2: define what a round means

A round only runs out if everyone agrees what one looks like. Four parts make it countable:

• One consolidated batch. All feedback on a version arrives together, in one document.
• One named approver. Someone with authority sends the batch and confirms it's complete. Other reviewers feed into it rather than sending their own. If you haven't settled who that is, an approval matrix sorts approvers from commenters.
• A named version. The feedback is on "Hero_v3," not on "the latest."
• A feedback window. The batch arrives within agreed business days, or later dates move.

Most revision fights are really about the first two. For the longer version of why a number alone won't hold, see why "two rounds" needs a definition behind it.

Step 3: write the six lines into the SOW

This is the clause we'd use (sample wording). Paste it into your SOW and fill in the brackets. Every line answers an argument you'd otherwise have in round three.

Why each line is there:

• 1 keeps concepting, where exploring is the job, out of the count.
• 2 is the definition. Without it, the number in line 1 can't be counted.
• 3 handles "these are just a few more thoughts."
• 4 separates a revision (inside the brief) from a change (a new brief, approver or deliverable).
• 5 makes round three a price and a date rather than an argument.
• 6 stops late notes from quietly squeezing production.

In-⁠house, with no SOW? Put the same six lines in the brief or the kickoff deck as "revision terms," and replace "billed at" with "re-⁠prioritized against the team's other work, confirmed by [creative lead]." The logic holds without a contract.

Step 4: propose it before anyone signs

Most round-⁠three arguments are cheaper to have before signature. We'd frame the revisions section as protecting the client's date. Here's what to say where it usually stalls.

1. Sending the SOW for signature

They say: nothing yet. The SOW is ready to send.

Don't send: a bare attachment with "Let us know if you have questions."

Send: "One section worth reading before you sign: Revisions. It defines a round as one consolidated set of feedback from [Client Approver] within three business days. That's what lets us hold your launch date. If [Client Approver] isn't the right person to send that batch, tell us now and we'll change the name."

Why it works: it frames the clause as date protection and invites the one edit that matters: the approver's name.

2. "Can we just say unlimited?"

They say: "Can we just say unlimited? That's what we had before."

Don't send: "Sure, we'll be flexible."

Send: "We can include more rounds. We can't include an undefined number and still commit to a delivery date, because the date depends on knowing when feedback ends. Would three rounds, each defined the same way, cover what you need?"

Why it works: it trades a bigger number for keeping the definition, which is the part that protects both sides.

3. Procurement asks to strike line 5

They say: "Please remove the additional-⁠rounds pricing. We don't pre-⁠approve extra spend."

Don't send: "Done, I've removed it."

Send: "Understood. We can change it so additional rounds need a written change order before any work starts. No pre-⁠approved spend, and nothing billed without your sign-⁠off. We need some path for a third round, or the only option left is to say no."

Why it works: procurement's worry is surprise spend. A change-⁠order trigger removes it.

Step 5: hold the line when round three arrives

A clause nobody points to is decoration. These are the lines for when the round count gets tested. Line numbers refer to the clause in Step 3.

1. "Round one was just initial thoughts"

They say: "Round one was just initial thoughts. This is our real feedback."

Don't send: "No problem, we'll treat this as round one."

Send: "Thanks for the full notes. Under the revisions section, the first batch on v2 was round one, so this is round two, the last included round. If anything here is new direction rather than revision, I'll flag it separately so you can decide whether it's worth a change request."

Why it works: you count the round without arguing about intent.

2. A new stakeholder appears after approval

They say: "Our VP saw it and has a few notes." The work was approved two days ago.

Don't send: "Of course, we'll fold them in."

Send: "Happy to look at the VP's notes. [Item] was approved in writing on [date], so changes to it fall under line 4 of the revisions section, which means a change request with a cost and a date. Should I scope that, or would [Client Approver] like to confirm the approval stands?"

Why it works: you name the approval and its date, then hand the decision back to the person who owns it.

3. "It's a tiny change, not a whole round"

They say: "It's just the headline. Five minutes."

Don't send: "Okay, just this once."

Send: "If it's quick, the cost will be small. It's still the third round, so I'll send a one-⁠line change order with the cost and the date impact. If you want it inside round two instead, send it with the rest of round two's notes."

Why it works: a small round gets a small price, not a free pass.

4. Round three arrives anyway

They say: a third set of feedback, after the included rounds are used.

Don't send: "On it," with the cost raised after the work is done.

Send: "We've used the two included rounds on [deliverable]. A third round is [cost] and moves delivery from [date] to [date]. Reply ‘approved’ to go ahead, or tell me which notes matter most and we'll see what fits inside the date."

Why it works: it gives a price, a date and two clear choices before anyone opens a file.

5. Late feedback, same delivery date

They say: feedback two days after the window, plus "we still need it on the 14th."

Don't send: "We'll make it work."

Send: "Got it. The notes came in two days after the window, so under line 6 of the revisions section the delivery date moves to [date]. If the 14th can't move, here's what we'd cut to hold it: [option]. Which do you prefer?"

Why it works: late feedback gets a visible cost, and the client picks date or scope.

6. The account lead wants to absorb it quietly

They say: "Let's just eat this round. They're a good client."

Don't send: silence, while the team quietly absorbs it.

Send: "We can choose to absorb it. Let's say so in writing: ‘Round three included at no charge as a one-⁠time courtesy.’ Otherwise the next project starts with three rounds as the expectation."

Why it works: goodwill stays a decision you made, instead of a precedent you didn't notice setting.

If the ask is really new scope, like a new deliverable, format or market, it's a change request. What to say when creative scope changes has the scripts for that. For why it keeps happening, see scope creep on creative projects.

If you'd like the whole system behind this, from revision rounds and change requests to stakeholder management for creative work, that's the core of the CPMA Level I certification ($147, self-⁠paced).

Revision rounds FAQ

Is two rounds of revisions standard?

Two is a common default for design and copy, and it's the number most clients expect, but there's no formal industry standard. The definition matters more than the count: two defined rounds tend to finish, and two undefined ones tend to multiply. Match the number to the deliverable, the budget and the number of approvers.

What's the difference between a revision and a change?

A revision adjusts the work inside the approved brief and concept: wording, layout, color, pacing. A change alters the brief itself, such as a new deliverable, format, audience, market, approver or an approved concept. Revisions use up included rounds. Changes go through a change request with their own cost and date.

What if feedback says "approved with comments"?

Treat it as a round until the comments are resolved, unless the approver confirms in writing that the comments are optional. Ask which it is: "approved as is, with these as suggestions," or "approved once these are done." See approved with comments for the scripts.

Define the round, then count it

The number in your SOW only protects you when the round behind it is defined. Write down what a round is, who sends it and when it's due, then point to that line every time someone tests it.

For the full foundation behind this (planning, revision rounds, change requests and stakeholder management for creative work), start with CPMA Level I: Training + Certification. It's $147, one-⁠time. Eight self-⁠paced modules, typically 10 to 15 hours. Pass the exam with 70%, with unlimited retakes. Your Certificate of Completion is emailed when you finish, and it never expires. If it's not the right fit, there's a 5-⁠day full refund. Start with Level I.

Want the whole path? The Bundle is $297 and includes Level I, Level II, the Creative PM AI Kit and the PM Resume Kit. Bought separately they're $498, so you save $201. Get the Bundle.

CPMA was developed with veterans from Disney, Google, Snap Inc., Red Bull, Sony Pictures, Accenture, and Paramount Pictures.