The contract conversation in most VFX engagements lasts about ten minutes. The producer’s legal team sends a template, the vendor’s legal team marks it up, a few exchanges happen on standard clauses, and the engagement gets signed. The conversation focuses almost entirely on the money — total bid, payment milestones, late penalty structure. The clauses that actually matter when something goes wrong barely get discussed.
This is fine on the projects where nothing goes wrong. On the ones where it does — and over a long enough timeline, every producer encounters a few — the contract clauses no one paid attention to become the entire conversation. By that point, it’s too late to negotiate them. They are what they are.
This post is about the clauses that matter beyond the money. Scope of work, exclusivity, key personnel, force majeure, IP transfer, security, and jurisdiction. What each one is doing, what to look for, and what’s worth raising with your legal counsel before signing.
A note before reading: This post is operational background, not legal advice. Every contract has context — your project, your jurisdiction, your studio’s standard practice — that an attorney needs to weigh. Use this as a checklist of what to discuss with your legal team, not as a substitute for that conversation.
Scope of Work
The scope of work clause references the breakdown and any methodology documents attached to the engagement. It defines what the vendor has agreed to deliver and what falls outside.
Worth discussing with counsel: the scope of work clause should reference the specific breakdown document by version number, with the breakdown attached as an exhibit. “Vendor shall deliver the work described in Breakdown V3, dated [date], attached as Exhibit A.” Without the version reference, “the breakdown” is ambiguous if the breakdown gets revised mid-engagement, and ambiguity is what change orders are supposed to resolve.
The scope of work clause should also explicitly state what’s included in the per-shot rate (revisions count, post-delivery support window, file formats) and what’s not (additional shots, methodology changes, format expansions, extended turnaround).
A vague scope of work is the most common reason VFX engagements get into contractual disputes. A specific one is the cheapest insurance available.
Exclusivity
The exclusivity clause defines whether the vendor can take other work during the engagement. There are three common arrangements:
Non-exclusive. The vendor can take other work freely. This is the default and the most common arrangement. The vendor commits to the agreed timeline and capacity for your project; they’re not committing to only work on your project.
Capacity-exclusive. The vendor can take other work, but a defined number of artists or a defined percentage of capacity is reserved for your project. This is reasonable for large engagements where the production needs visibility into resourcing.
Project-exclusive. The vendor doesn’t take other work during the engagement. This is rare and almost always overpriced relative to the value it provides. Don’t insist on it unless the project genuinely requires it (some major studio engagements with unique security requirements, for example).
What to look for: clarity. The clause should state the arrangement explicitly. “Non-exclusive” or “capacity-exclusive with X artists or Y% of vendor’s resources reserved.” Vague language like “vendor will prioritize this engagement” doesn’t mean anything contractually.
Key Personnel
The key personnel clause names specific people on the vendor’s side who are committed to the engagement. The lead compositor, the lead matchmover, the project manager. If those people leave the engagement during the project, the producer has the right to know and (in some clauses) to renegotiate.
This clause matters more than it sounds. On a long engagement, the relationship between the production team and the vendor’s team is built around specific people — not the vendor as an abstraction. When the lead compositor you’ve been working with for six months gets reassigned to another project halfway through, the productivity hit is real, and a key personnel clause gives you a contractual basis to ask about it.
Worth discussing with counsel: the names of the leads in each affected discipline (or, if the vendor isn’t willing to commit to specific people, language requiring 30 days’ notice before any lead is reassigned). On smaller engagements this might be excessive; on engagements over six months or several hundred shots, it’s worth having.
Force Majeure
Force majeure clauses describe what happens when something outside both parties’ control disrupts the engagement. Natural disasters, war, pandemic-level disruption, government action that prevents the work from proceeding.
These clauses got a lot more attention after 2020. Many older VFX contracts had force majeure language that was vague enough to be litigated either way during the pandemic, and a lot of vendor-producer relationships ended up in disputes over whether the disruption qualified.
Worth discussing with counsel: specific force majeure events listed (not just “acts of God” or “extraordinary circumstances”), and a defined process for how the engagement responds. Typical structure: notification within X days, attempt to mitigate by [reasonable means], renegotiation of timeline if mitigation isn’t possible, mutual termination right if the disruption extends beyond Y days.
The clause that matters most is the termination right. If the disruption goes on indefinitely, both sides should be able to walk away cleanly without litigation.
Intellectual Property Transfer
The IP transfer clause defines when ownership of the delivered work moves from the vendor to the producer. The standard arrangement is “upon final payment” — the vendor delivers, the producer pays, the IP transfers. This protects the vendor against non-payment and ensures the producer ends up with clean ownership of the final work.
What to look for: language that addresses both finished deliveries and works in progress. If the engagement gets terminated mid-project (for any reason — non-payment, force majeure, mutual decision), what happens to the work that’s been delivered but not paid for? What about work in progress that hasn’t been delivered? The clause should specify both.
Worth discussing with counsel: explicit language that the producer’s payment for delivered work conveys the IP for that delivered work, even if the engagement ends before completion. This prevents a vendor from holding partial deliveries hostage in a payment dispute. The reverse — vendor IP retention until full payment — is also reasonable, but it should be explicit.
Security and NDA
Security clauses define what the vendor will do to protect the production’s confidential material. NDAs (non-disclosure agreements) define what can be discussed externally.
For projects with major studios, streaming platforms, or pre-release commercial campaigns, the security clause is often the longest in the contract. It might require TPN certification (Trusted Partner Network — an industry-standard security certification), specific data handling protocols, watermarking on review copies, restricted access lists, audit rights, and notification requirements for any security incident.
Worth discussing with counsel: TPN certification (or equivalent) for any vendor handling pre-release content. The certification is industry-standard for a reason — it provides a baseline of security infrastructure that’s been audited by a third party, rather than relying on the vendor’s claims.
Beyond TPN, the specific security requirements depend on the project. A major studio engagement will dictate most of the language; the producer’s job is to make sure the language matches what the studio actually requires (and that the vendor can comply).
Jurisdiction and Governing Law
Jurisdiction clauses define where disputes get resolved if the engagement ends up in litigation or arbitration. Governing law clauses define which country’s or state’s laws apply.
For domestic engagements, this clause is usually formality. For international engagements — including engagements with overseas vendors — it matters significantly. The cost of pursuing a dispute in a foreign jurisdiction can be high enough to make any dispute uneconomic, which means the clause effectively determines who has leverage if things go wrong.
What to look for: jurisdiction in a country with a reliable legal system and reasonable enforcement of contracts. For US-based producers working with international vendors, common arrangements include English law (London arbitration), New York law (with arbitration in New York), or Singapore law (with arbitration in Singapore) — all of which have well-developed commercial dispute infrastructure.
What’s worth raising with counsel: any jurisdiction where contract enforcement is unpredictable or where the producer would have no practical ability to pursue a dispute. This is one of the clauses where legal advice is most worth paying for.
Termination Rights
The termination clause defines when and how either party can end the engagement. Common termination rights:
Termination for convenience. Either party can end the engagement with notice (typically 30 days), with the producer paying for completed and in-progress work up to the termination date. This protects the producer against being locked into an engagement that’s not working.
Termination for cause. Either party can end the engagement immediately if the other party materially breaches the contract (non-payment, missed delivery deadlines beyond a defined tolerance, security violations).
Termination for non-performance. A specific subset of termination for cause, triggered when the vendor fails to deliver agreed milestones within an agreed window. Worth having explicitly when the engagement is large enough that a non-performing vendor would be expensive to replace mid-project.
Worth discussing with counsel: termination for convenience with reasonable notice, plus termination for cause with a clear definition of “material breach.” Without these, the contract is one-directional, and one-directional contracts create stress when the relationship gets tested.
What This Adds Up To
A VFX contract that handles all of the above clauses well is a contract that protects both parties from the unusual scenarios. Most of the time, none of these clauses get invoked — the engagement runs smoothly, the work delivers on schedule, payment happens cleanly, and the contract sits in a folder.
When something goes wrong, the contract is the document that determines whether the situation gets resolved cleanly or gets messy. Producers who’ve been through the messy version once tend to insist on stronger contracts the second time around.
How FXiation Digitals Approaches Contracts
We’re the receiving end of a lot of contracts, so we’ve seen the language that works and the language that doesn’t. Our standard engagement contract has clear scope referencing a specific breakdown, non-exclusive arrangement with named key personnel, defined force majeure with mutual termination right, IP transfer on payment with explicit handling of partial deliveries, TPN-certified security, jurisdiction in a venue both sides can work with, and termination for convenience and cause both available.
We negotiate. We push back on language that’s overly one-sided. We’re not trying to win the contract — we’re trying to make sure both sides have something they can rely on if the engagement gets stressed. Producers who’ve worked with us through one of those stress moments will tell you the contract did its job.
If you’re scoping a project and want to look at our standard engagement contract before any work begins, send us the brief. We’ll share the document and walk you through the clauses that producers most often have questions about. Either you’ll know what you’re signing before you sign it, or we’ll learn something from your pushback that improves the next contract we write.
Common Questions