Why I Put a Revision Limit in Every Contract
Every contract I write includes a specific, defined limit on how many rounds of revisions are included in the project fee. It's a small clause, easy to overlook when reviewing a contract, but it prevents one of the more common sources of quiet, unpaid scope expansion in creative work.
Explaining why this matters, and how I structure it fairly, tends to reassure rather than concern most clients once they understand the reasoning. If you want the fuller contract framework I use on every project, it's part of a bigger system in The Adventure Travel Photographer's Playbook.
Why Unlimited Revisions Sound Generous But Rarely Work Well
Offering unlimited revisions might seem like a generous, client-friendly gesture, but in practice it creates real problems for both sides. Without a defined limit, there's no natural endpoint to the editing process, and subjective creative feedback can continue indefinitely without ever reaching genuine resolution.
This isn't usually because clients are being unreasonable. Creative feedback is inherently subjective, and without a structural boundary, it's easy for a project to drift into an open-ended cycle of small adjustments that never quite feels finished, consuming far more time than either side originally anticipated.
A defined revision limit creates helpful structure around this naturally open-ended process, giving both sides a clear, shared understanding of when the editing phase is expected to conclude.
How I Typically Structure a Revision Limit
My standard contract typically includes a set number of revision rounds, often two, within the base project fee. Each round covers a defined set of feedback, consolidated and delivered together, rather than an open-ended stream of individual change requests arriving over an extended period.
Additional rounds beyond the included limit are available, but at an additional cost, reflecting the real time involved in continued revision work. This structure keeps the process fair; clients get meaningful opportunity for creative feedback, while additional rounds beyond that are compensated appropriately.
I explain this structure clearly during contract review, so clients understand exactly what's included and what would trigger additional cost before the editing phase actually begins, removing any surprise later in the process.
Why Consolidated Feedback Rounds Work Better Than Open-Ended Requests
I ask clients to consolidate feedback into defined rounds rather than sending individual change requests as they occur to them over several days or weeks. This structure produces meaningfully better results for both sides than a scattered, ongoing stream of piecemeal feedback.
Consolidated feedback tends to be more thoughtful and complete, since it requires the client to actually review the full set of work before responding, rather than reacting to individual images in isolation as they happen to notice them throughout a busy week.
This structure also makes my own editing process more efficient, since I can address a complete, coherent set of feedback in one focused pass rather than repeatedly returning to already-completed work for scattered, incremental adjustments spread across an extended period.
What Happens When a Client Wants More Rounds Than Included
When a client wants revision rounds beyond what's included in the base agreement, I treat this as a straightforward, expected add-on rather than a conflict, similar to how I handle other forms of scope expansion beyond the original project agreement.
I quote additional rounds at a clear, predictable rate established in advance, so there's no ambiguity or renegotiation required in the moment. This predictability makes the conversation easy for both sides, since the terms were already established before the need for additional rounds ever arose.
Most clients, once they understand this structure exists specifically to keep the base project fee reasonable while still accommodating genuine additional need, accept additional-round pricing without significant friction or pushback.
How This Clause Protects Against Indefinite Feedback Loops
Without a defined revision limit, I've seen projects drift into a pattern where minor subjective adjustments continue indefinitely, small color tweaks, slight crop adjustments, minor sequencing changes, each individually reasonable but collectively consuming far more time than any project fee was ever meant to cover.
A defined limit creates a natural, structural endpoint to this process. Once included rounds are used, both sides have a clear, previously agreed framework for how to proceed, either finalizing the current work or explicitly agreeing to additional compensated rounds.
This structure has saved me from open-ended, unpaid editing cycles more times than I can count, while also, somewhat counterintuitively, tending to produce better final results, since it encourages more thoughtful, consolidated feedback rather than endless minor tweaking.
Why Clients Generally Respond Well to This Clause
Most clients, once the reasoning is explained, actually appreciate having a clear revision structure rather than an ambiguous, open-ended process. It gives them a concrete framework for organizing their own feedback process internally, which many find genuinely useful beyond just protecting my own time.
Clients working in industries where similar structures already exist, agency retainers, consulting engagements, tend to find this concept entirely familiar and unremarkable, since defined scope with clearly priced additions beyond that scope is a common structure well outside photography specifically.
I've found that clients who initially seem surprised by the concept generally come around quickly once they understand it protects the quality and focus of the revision process itself, not just the photographer's time and compensation.
What I Do When Feedback Rounds Reveal a Deeper Misalignment
Occasionally, extensive revision requests signal something deeper than simple preference adjustment, a genuine misalignment between what the client actually wanted and what was originally briefed or delivered. In these situations, I address the underlying misalignment directly rather than simply cycling through additional paid revision rounds.
This kind of direct conversation, acknowledging that something beyond normal revision seems to be happening, often surfaces the real issue faster and more constructively than continuing to iterate on individual images without addressing the actual root cause of the ongoing dissatisfaction.
Recognizing the difference between normal revision and a deeper misalignment requiring a different conversation entirely is a judgment skill that's developed considerably over years of managing this exact dynamic across many different client relationships.
How I Adjust Revision Limits for Different Project Types
Not every project warrants an identical revision structure. A large, complex brand campaign with many stakeholders and approval layers might reasonably include more included revision rounds than a simpler, single-decision-maker project, reflecting the genuinely different feedback complexity involved.
I adjust this proportionally when scoping a project, rather than applying an identical revision limit regardless of project complexity or the number of people likely to be providing feedback throughout the process.
This tailored approach keeps the revision clause feeling genuinely fair and appropriate to each specific project, rather than a rigid, one-size-fits-all rule applied without regard to real differences in project complexity and stakeholder involvement.
How I Handle Revisions When Multiple Stakeholders Are Involved
Projects with multiple client-side stakeholders introduce a particular challenge to revision management, since different individuals sometimes provide conflicting feedback within the same round, leaving me to reconcile genuinely contradictory direction before I can actually proceed with meaningful revision work.
I've learned to ask, upfront during contract discussion, who the final decision-maker actually is for revision feedback, so that if conflicting input does arise, there's already a clear, previously agreed process for resolving it rather than leaving me to guess whose feedback should ultimately take priority.
This upfront clarity has prevented considerable wasted revision effort on projects where, without it, I might otherwise have made changes based on one stakeholder's feedback only to have another stakeholder request the exact opposite change in a subsequent round, effectively wasting an entire revision cycle on contradictory direction.
Why I Communicate Revision Status Clearly Throughout the Process
I keep clients informed of exactly which revision round we're currently in and how many remain within their included allotment, rather than leaving this tracking implicit or assuming a client is keeping careful count themselves throughout an active project with potentially many other priorities competing for their attention.
This transparency prevents the uncomfortable situation of a client being surprised to learn they've exhausted their included revisions, which can otherwise feel like an unwelcome ambush rather than the natural, previously agreed conclusion of a clearly structured process both sides understood from the outset.
A simple, brief note at the start of each revision round, confirming which round this represents and how many remain, has proven a small but genuinely valuable habit for keeping this entire process transparent and free of the kind of end-of-process friction that ambiguity tends to produce.
How I Distinguish a Revision From a Genuine Error Correction
Not everything a client flags after delivery counts against their included revision rounds. A genuine error, a technical mistake, a misapplied edit that doesn't match what was actually briefed, gets corrected at no cost and outside the formal revision structure, since that's a quality issue on my end, not a subjective creative preference.
I make this distinction clear to clients upfront, so they understand that flagging an actual mistake is always welcome and never counts against their revision allotment, while requesting a different creative direction or subjective adjustment does count as a genuine revision within the structured process.
This distinction occasionally requires judgment calls, and I try to err on the side of generosity when something sits genuinely close to the line between error and preference, since maintaining goodwill and trust matters more in these borderline cases than rigidly enforcing every technical boundary of the revision structure.
What Happens When a Project Has No Revisions Used at All
Occasionally a client approves delivered work without requesting any revisions at all, and I've sometimes wondered whether unused revision rounds should translate into any kind of credit or discount, given they represent time I'd budgeted for but ultimately didn't need to spend.
In practice, I don't offer a refund or credit for unused rounds, since the fee structure accounts for the availability of that time and flexibility, not a guarantee that it will actually be used. This is similar to how many service-based pricing models work, where included capacity has value whether or not it's fully utilized.
I do sometimes mention, informally, that no revisions were needed, since I think it's worth acknowledging directly to a client when a project came together cleanly on the first pass, even without any formal credit or discount attached to that acknowledgment.
Why I Set a Clear Deadline for Requesting Revisions
Beyond limiting the number of revision rounds, I also set a clear deadline for when revision requests must actually be submitted after delivery, typically a defined window of days or weeks, rather than leaving the request period open indefinitely with no natural endpoint.
This deadline prevents a project from technically remaining open for revisions months after delivery, when priorities, available source material, and even my own memory of specific creative decisions have naturally faded, making late revision requests considerably harder to execute thoughtfully and accurately.
I communicate this deadline clearly at delivery, and most clients, once aware of it, review and respond to delivered work reasonably promptly, which has the added benefit of keeping projects genuinely closed out rather than lingering indefinitely in a technically unfinished state.
What I'd Tell a Photographer Currently Offering Unlimited Revisions
If you're currently offering unlimited revisions and feeling the strain of that open-ended commitment, my honest advice is that adding a defined limit, even on existing ongoing client relationships, is a reasonable and professional adjustment that most genuinely reasonable clients will understand and accept.
I'd introduce the change clearly and directly, explaining the reasoning rather than quietly changing practice without explanation, since transparency about why the structure is changing tends to produce far less friction than an unexplained, seemingly arbitrary new limitation on existing terms clients may have grown accustomed to over time.
This transition can feel uncomfortable initially, but the resulting clarity and boundary consistently proves worth the short-term discomfort, both for the immediate relief of a defined endpoint and for protecting against the kind of quiet resentment that unlimited, unstructured revision cycles tend to build up over time.
Why a Defined Revision Structure Actually Improves Client Trust
Counterintuitively, I've found that a clearly defined revision structure tends to increase rather than decrease client trust over time. It signals a photographer who has thought carefully about how projects actually run, rather than one operating without any clear process for handling the inherently subjective nature of creative feedback.
Clients who have worked with photographers lacking any revision structure often specifically comment on how much smoother a well-structured process feels, since it removes the ambiguity and uncertainty that an undefined, open-ended revision approach otherwise tends to create for everyone involved in a project.
This has genuinely surprised me over the years, since I initially expected a defined limit to feel restrictive to clients rather than reassuring, and the consistently positive reaction has reinforced how much clients actually value clear structure over seemingly generous but genuinely ambiguous flexibility.
How I Introduce This Structure to First-Time Clients
For clients working with me for the first time, I explain the revision structure as simply one part of a broader, considered process rather than isolating it as a standalone rule, framing it within the context of how the entire project will actually unfold from brief to final delivery.
This contextual framing helps first-time clients understand the revision limit isn't an arbitrary restriction but a genuinely considered piece of a professional process designed to produce strong results efficiently, which consistently lands better than presenting the limit in isolation without that broader context.
I've found that clients who understand the full reasoning behind this structure, rather than encountering it as an isolated clause buried in contract language, engage with the revision process itself more thoughtfully and constructively from the very first round onward, submitting more considered, consolidated feedback rather than scattered, reactive requests spread haphazardly across an extended period, which ultimately benefits the quality of the finished work itself far more than either side initially expects going into a brand new working relationship together from the very first day the agreement is actually signed and real work formally begins in earnest.
Building This Into a Coherent, Professional Contract
A revision limit works best as part of a broader, coherent contract structure, paired with clear scope, defined usage rights, and clear payment terms, rather than existing as an isolated clause disconnected from the rest of the agreement.
Building this kind of comprehensive, thoughtful contract practice into every project is part of the bigger business framework I cover in The Adventure Travel Photographer's Playbook.
Reflection Questions
- Does your current contract specify a clear limit on included revision rounds?
- How do you currently handle a client requesting revisions beyond what feels reasonable?
- What would change if you asked clients to consolidate feedback into defined rounds?
Dalton Johnson is a professional adventure and editorial photographer with over a decade of experience shooting on all seven continents. His client work includes Patagonia, GoPro, Arc'teryx, Four Seasons, Nike, Rivian, Big Agnes, Ford Bronco, and 160+ other brands. He runs Dalton Johnson Media as a full-service studio, from pre-production through post and distribution.