Every VFX project has scope changes. The director changes a director’s note. The agency comes back from internal review with five new comments. The picture cut shifts. A new shot enters the breakdown three weeks in. These aren’t failures of planning; they’re how creative projects actually work, and any vendor who pretends otherwise is going to be the one absorbing the cost (or padding the bid, which means you’re absorbing it before it happens).
The question isn’t whether scope will change. The question is whether the change is documented, priced, and approved before the work happens — or after. Producers who run smoothly are the ones who built a change order discipline before they needed it. Producers who run rough are the ones who treated change orders as a contractual fight whenever scope shifted, and burned the relationship in the process.
This post is about treating change orders as a normal piece of production paperwork, not as a battleground.
Why Change Orders Exist
The original VFX bid is built against the original breakdown. Those two documents together form the scope of work. When something changes — a new shot, a different methodology, an extended turnaround, additional revision rounds beyond what was bid — the scope of work has shifted, and the bid is no longer accurate.
A change order is the formal acknowledgment that scope shifted. It documents what changed, what the impact is on timeline and budget, and gets sign-off before the new work starts. It’s the mechanism that keeps the original bid honest.
What happens without change orders: the vendor either absorbs the cost (which means they’re losing money on the project, and you’ll feel the consequences in the form of less attention or lower quality on the back half), or pads the original bid for safety (which means you paid for hypothetical changes that may not have happened). Neither outcome is good. The change order is the alternative — pay for what actually changed, when it actually changed, with a paper trail that prevents disputes later.
What a Change Order Should Contain
A real change order has four sections. Anything less is a verbal agreement waiting to be misremembered.
1. Description of the change. What is being added, removed, or modified, in plain language. “Add 3 new shots to the campaign — V247, V248, V249, all shot at 4K, all complexity rating 3, all with set extension and beauty work.” Not “more shots.” Specific.
2. Schedule impact. What does the change do to the delivery timeline? Either the existing schedule absorbs the change, or it doesn’t. If it doesn’t, the new delivery date should be in the change order. “Original delivery: April 22. New delivery: April 29 to accommodate added shots.”
3. Budget impact. What does the change cost? Per-shot rate × shot count, or hourly rate × estimated hours, or a flat fee for the additional work. The number should be transparent, with the calculation visible. “3 shots × $X per shot = $Y, payable on existing schedule.”
4. Sign-off. A line for the producer (or whoever has authority to approve) to indicate written acceptance. Date, signature, and ideally a reference to the original engagement contract.
That’s it. Four sections. A change order doesn’t need to be a multi-page legal document — it needs to be specific enough that there’s no ambiguity later about what was approved.
The 48–72 Hour Standard
The industry-standard turnaround on a change order is 48–72 hours from the moment the request is documented. The vendor receives the change request, drafts the change order, and sends it back to the producer within that window.
Why 48–72 hours: change orders that take longer create their own problems. The director or agency is waiting for an answer about whether the change is feasible. The schedule is hanging in the air. The vendor’s main work is paused on the affected shots. A slow change order workflow creates the appearance that the vendor is dragging their feet on a request, which damages the relationship even when it shouldn’t.
Vendors who can turn change orders around in 24–48 hours generally have mature production discipline. Vendors who take a week or more usually don’t have a defined process for it yet, which is fine on small engagements but becomes painful when scope shifts are happening every few weeks.
The producer’s side of the discipline is equally important. Once the change order is back, sign it (or push back, with specifics) within a similar window. The vendor can’t proceed until the sign-off is in. A change order that sits unsigned for two weeks is two weeks of production momentum lost.
The Definition of “Submitted” Matters
One of the most common change order disputes is about when the clock started. The producer thinks the request was submitted on Tuesday. The vendor thinks it was submitted on Friday, when the formal request came through the official channel. Three days of disagreement on a 7-day deliverable is significant.
The clean fix: define “submitted” upfront — in the engagement contract if there is one, or in the kickoff email chain that’s serving as the working agreement. Submitted means a formal written request through a specified channel — typically an email to a named contact, or a ticket in a tracking system that both sides can see. Casual mentions in calls or DMs aren’t submitted requests until they’ve been written up.
This sounds bureaucratic. It is bureaucratic. It’s also what prevents misunderstandings about timelines from becoming arguments about who said what when. The discipline is small; the protection it provides is large.
What Doesn’t Need a Change Order
Not every scope shift is a change order. Two common scenarios that should not generate change orders, even though they technically change the work:
1. Revisions within the agreed revision count. If the contract specifies two rounds of revisions and you’re on round one, that’s not a change order — that’s the work continuing as scoped. Revisions become change orders only when they exceed the agreed count.
2. Vendor-side errors. If the vendor’s delivery has technical errors — wrong color space, wrong handles, wrong naming — fixing them is part of the original scope, not a change order. The vendor doesn’t get to charge for fixing their own mistakes.
The reverse is also true. Things that should generate change orders but sometimes don’t:
- New shots added to the breakdown
- Methodology changes (a 2D approach changing to a 3D approach)
- Schedule compression (delivery date moved forward)
- Additional revision rounds beyond the agreed count
- Format changes (delivering in 4K instead of 2K, or in additional aspect ratios)
If any of these happen and there’s no change order, somebody is going to absorb the cost. Usually the vendor, until they push back. The push-back is the moment the relationship gets stressed, and it’s exactly the moment that the change order discipline would have prevented.
How to Run a Change Order Conversation
When a change is needed, the producer’s first move is the request: “We need to add three shots — V247, V248, V249 — same complexity as the existing batch. Can you turn around a change order with timeline and budget impact?”
The vendor’s first move is the change order, drafted within 48–72 hours: timeline impact, budget impact, sign-off line. Sent back as a clear document, not an email paragraph.
The producer’s second move is sign-off, push-back, or negotiation. If the change order looks right, sign and return. If something’s off — the timeline impact seems too aggressive, the per-shot rate is higher than the existing batch — push back with specifics. The vendor can revise and re-send.
Once signed, the work proceeds. The change order goes into the engagement file and gets referenced in any future scope discussions. The conversation is complete.
What this entire flow has in common: nothing personal, nothing emotional, nothing requiring trust between humans who don’t know each other yet. The discipline does the work that personal trust would do otherwise. That’s why it’s reliable across vendor relationships even when individual people change.
How FXiation Digitals Handles Scope Changes
In practice, our engagements run on an email chain — kickoff through delivery — where scope, deliverables, and timelines are documented and dated. When something shifts mid-project (new shots, methodology change, format expansion, timeline compression), the conversation gets a fresh thread: what changed, what the impact is on schedule and budget, sent across, held for written confirmation before any new work starts. Same principle as a formal change order template, with less paperwork.
The principles that matter, regardless of format:
- No revision-count caps. We don’t bill against a “two rounds included” stipulation. We trust our work to clear review in 2–3 rounds (often the first), and we’d rather get there with the right shot than meter out review cycles.
- Errors on our side are fixed at no charge. They’re part of original scope, not a change order.
- New scope gets documented before it’s executed. Additional shots, methodology changes, format expansions, timeline compression — all written down with impact on schedule and budget before any new work begins. Nothing is invoiced that wasn’t agreed in writing first.
- Client-side contracts and templates are honored. When you bring your own engagement contract or change order workflow, we work to its terms.
The producers we’ve worked with consistently say this is the discipline they wish more vendors had — not the paperwork itself, the principle behind it. The paperwork can be heavy or light; what matters is that scope changes don’t become memory tests three weeks later.
If you’re scoping a project and want to see how we handle scope before you commit, reach out. We’d rather walk you through it upfront than have it come up as a surprise three weeks in.
Common Questions