Why Revision Rounds Belong in the Contract

What a revision round actually is, why undefined revisions damage both sides, and how to structure feedback so the included rounds are enough.

The revision clause is the part of a video contract that decides whether a project ends well. Almost every dispute between a studio and a client traces back to it, and almost every one of those disputes was avoidable through a paragraph that took ten minutes to write. The problem is rarely bad faith on either side. It is that the two parties held different definitions of a word neither of them defined.

A revision round should mean one consolidated set of feedback, from one named approver, delivered at one time, after the client has completed their internal consultation. Under that definition three rounds is generous and most projects finish within two. Under the other common interpretation, where every individual comment from every stakeholder as it occurs to them counts as part of the same round, three rounds is unlimited work, and the studio will either absorb an unbudgeted loss or raise the issue awkwardly halfway through.

The reason drip fed feedback is so damaging is that it produces contradictory instructions. One stakeholder asks for a section to be shortened, a second asks for detail to be added to the same section three days later, and the editor implements both, sequentially, at full cost. Consolidation is not an administrative preference, it is the mechanism by which a client resolves their own disagreements before paying someone to enact them.

The contract should also define what a revision is not. Changing the script after picture lock, adding a new deliverable format, changing the music after the mix, or introducing a new stakeholder with different opinions in week five are not revisions, they are changes of scope. Naming them as such in advance, with rates attached, turns a difficult conversation into an administrative one. Mirzaei et al. (2025) argue that project methodologies should be customised to the specific project rather than applied uniformly, and the revision structure is one of the places where that customisation is most valuable: a project with four stakeholders needs a different arrangement from one with a single decision maker.

Stage gating is what makes a small number of rounds sufficient, and it is the studio's responsibility to enforce. Approval should be sought and recorded at the script, the storyboard, and the offline edit, before the film is finished. A client who has approved the script and the board has already made most of the decisions, and their feedback on the finished film is correspondingly narrow. A client shown nothing until the final cut will have every reaction at once, and no revision allowance survives that.

The economics are worth stating plainly because clients often read the revision limit as meanness. Post production is where a substantial portion of the cost sits, and open ended revisions can double it. A studio offering unlimited revisions has either priced for the worst case, which makes them expensive, or has priced for the best case and intends to resist changes when they arrive, which makes them difficult. A defined limit is the more honest arrangement in both directions.

For the client, the practical protection is to run their internal process before sending anything. That means circulating the cut internally with a deadline, collecting all comments into one document, resolving contradictions between stakeholders internally rather than passing them to the studio, and sending timecoded, specific feedback from one person. Feedback that says the middle feels slow is a conversation. Feedback that says cut the section from twenty two to thirty one seconds is an instruction.

Timecodes matter more than clients realise. Vague feedback requires the studio to interpret, interpretation is frequently wrong, and a wrong interpretation consumes a round without improving the film. Two minutes spent noting the exact moment of each comment saves an entire cycle, and it is the single most useful habit a client can adopt.

The clause should also cover what happens when the included rounds are exhausted, because that situation is normal rather than exceptional on complex projects. An hourly or per round rate agreed at the outset removes the awkwardness entirely: the client can choose to buy another round knowing the cost, and the studio does not have to decide between working free and raising an uncomfortable subject mid project. Sarasvuo et al. (2023) found that buyer perceptions of fit shape how B2B services are evaluated, and a supplier who has anticipated this situation reads as professional rather than restrictive.

The summary a buyer should take into any negotiation is short. Ask how many rounds are included, ask what constitutes a round, ask what counts as scope change rather than revision, ask the rate for additional rounds, and confirm the approval gates at script, storyboard and offline. A studio that has clear answers has run enough projects to have needed them. A studio that says do not worry about it is describing a conversation you will have later under worse conditions.

References

Mirzaei, M., Mabin, V. J., & Zwikael, O. (2025). Customising hybrid project management methodologies. Production Planning & Control, 36(9), 1188–1205. https://doi.org/10.1080/09537287.2024.2349231

Sarasvuo, S., Liljander, V., & Haahtela, K. (2023). Buyer perceptions of corporate brand extension attractiveness and fit in B2B services. Industrial Marketing Management, 115, 69–85. https://doi.org/10.1016/j.indmarman.2023.09.006