Can you update your brand film next year? Settle rights and handover before production
Your team approves a film built around a product interface. Next year, the interface changes. You have the finished master, but does your agreement permit a revised version—and can anyone access what they need to replace the screen?
Permission and practical ability are separate. A licence may allow continued use without requiring the vendor to supply editable materials. Project files, if supplied, do not establish that music, voice performances, stock footage, fonts or contributed artwork are cleared for a new version or territory. Plan for both before production, rather than treating delivery of the master as the end of the decision.
Separate launch requirements from future options
Give bidders the same account of what to lock in the production brief and how it might change. Mark firm requirements separately from options worth pricing; you do not need to buy every possible right now.
Put this matrix in the production brief alongside the changes you can foresee. Ask each bidder which permissions are included, which would need further clearance, who would obtain it and who would pay. A narrower initial scope may reduce today’s quote, but an expansion could take time when a campaign date is fixed.
Design the likely update—and choose who will make it
In the hypothetical film, replacing a separate end card is a different job from rebuilding an interface that appears across several animated shots. If the interface is accompanied by a voiced feature claim, the change may also affect sound and captions. Flag that risk at script, treatment and animatic stage: information that is likely to change can sometimes sit in a defined, replaceable element rather than being woven through the sequence.
The handover request should follow the intended update route:
Localisation needs the same test. Permission to translate does not remove text embedded in artwork or create room in a tightly timed sequence. If other-language versions are plausible, ask whether a textless picture, separated dialogue and music, and a transcript would help the team making them—and agree those items as deliverables if needed. Check separately whether the voice, music and other elements are cleared for the intended versions and markets. For AI-assisted, traditional or hybrid work, ask the vendor to explain the actual revision route; not every shot will have a conventional, reproducibly editable project file.
Compare the responsibility behind each bid
A promise to supply “source files” says little about whether the likely update can be made. compare production bids on responsibility and risk and ask each bidder to specify:
One bidder may price a broad handover while another assumes you will return for every revision. Those are different allocations of work and risk, even if the proposed films look alike. For more on that distinction, see how production bids assign responsibility. Have legal or procurement review the proposed rights and clearance terms rather than relying on a production estimate to settle them.
Sign off a usable update path
At delivery, check the package against the agreed schedule—not a generic promise of “all files.” Verify the required exports and versions, the named working materials, documented permissions and any restrictions or outstanding approvals. Then confirm who can make the anticipated change and how a new version would be requested.
The final test is: Where can we run it, for how long, who clears every ingredient, what exactly arrives, and what happens if we need a new version? If the last answer depends on materials or permissions nobody has agreed to provide, the update path is not yet settled.
