Imagine one product-claim graphic feeding twelve ads: three languages, two aspect ratios and two durations. A designer changes the price in the Affinity source file and presses save. The editor does not re-import anything, yet the corresponding elements in the DaVinci Resolve timelines update.
That can remove twelve manual replacements. It can also distribute one unapproved price to twelve deliverables.
For a campaign that needs both rapid revisions and a fixed release, use live links while the work is changing, then preserve an approved snapshot for delivery. Put three decisions in the brief: which edits a source can update, who approves the result, and how to restore the last approved version. This matters especially when a brand, a China-based production company and regional post teams share responsibility for the same assets.
The capability is real; universal adoption is not
Blackmagic Design’s DaVinci
Resolve 21 New Features Guide, dated April 2026, says Resolve
can decode Affinity .af files natively in the timeline. An
imported file is flattened by default, or its layers can be split in
place across tracks. When the source is saved in Affinity, the content
updates automatically in Resolve.
The same guide states an important limitation: major changes to layer grouping or hierarchy may not appear correctly and can require the modified file to be re-imported. Live linking removes some repetitive replacement work. It does not remove structural change management, approval or regression review.
On September 16, 2026, Canva announced
the Canva ProSuite, connecting Affinity, Cavalry, Flourish and
Leonardo across a broader creative workflow. Canva’s Create
2026 launch page also describes building a Brand System in Affinity
and publishing it into a Canva Brand Kit. Affinity’s own integrations page
describes native .af handoff and automatic refresh in
Resolve.
These sources document the integrations; they do not establish that a supplier's setup supports the same workflow. Before relying on live updates, ask the supplier to test the actual application versions, source files and layer structure planned for the project. The approval and release controls below are workflow recommendations, not guarantees provided by the software.
One save action creates four supply-chain questions
A traditional handoff treats an exported graphic as a static snapshot. The designer exports it, the editor imports it, and any later change requires another transfer and replacement. It is inefficient but legible.
A live link turns that boundary into four operating questions:
- Who may modify the source of truth? The brand designer, production company or regional localization partner?
- What can a save action change? One working edit, or every language, ratio and channel version?
- Who checks the propagated result? Typography, masks, transparency, animation timing and safe areas may all need review.
- When does updating stop? Once a claim is legally approved, a master is delivered or a vendor exits, continued linking can be riskier than freezing.
Without explicit answers, live linking only exchanges “wrong file” risk for “wrong change at scale” risk.
The ONCE Live Dependency Handoff Sheet
ONCE recommends adding a six-field Live Dependency Handoff Sheet to the production brief, estimate and acceptance checklist.
| Field | What the buyer must specify |
|---|---|
| Source of truth | The authoritative .af file, design system or asset library, its location and version identifier, plus who has write access |
| Propagation scope | Every project, timeline, language, ratio and channel version affected by a save |
| State | Whether the asset is live, frozen or released; who may change that state; and how the released copy is protected from later source edits |
| Approval | Which changes require brand, legal, marketing or platform approval, and whether approval happens before or after propagation |
| Regression checklist | Copy, price, type, transparency, masks, timing, safe areas and audio sync to verify after an update |
| Rollback package | The last approved source snapshot, rendered fallback, version manifest and recovery instructions |
These fields turn “latest” into a testable production state. The goal is not to add bureaucracy to a small edit. It is to prevent a hidden dependency from moving across companies and markets without an owner. ONCE’s guide to reusable assets in multi-version commercial video delivery covers version trees, working files and release packages; the additional issue here is what happens while a source can still propagate changes automatically.
Choose among three delivery modes
Static snapshot for final or high-compliance work
Use a static snapshot when the project has few deliverables, or when assets contain approved pricing, legal copy, regulated claims, broadcast masters or a vendor closeout. Freeze the source and supply rendered fallbacks. The workflow gives up some speed to make responsibility clear.
Live link during development and repeated variation
Use live linking when one design element will feed many markets and placements, and the source, edit rights and approval owner are unambiguous. It is most valuable during development, when iteration is expected—not as an unattended publishing mechanism.
Hybrid as the default
Use a hybrid when the campaign needs repeated revisions followed by a fixed release. Keep links active in the working project. At approval, archive the source version and a release project that uses that snapshot or rendered fallbacks, with a manifest identifying the files and application versions. Confirm that editing the working source no longer changes the release project. Start later revisions from a separate working copy.
In short: live is a collaboration mode, freeze is an accountability boundary, and rollback is an exit capability. A robust handoff needs all three.
Measure approved propagation, not saved exports
Compare the live-linked and manual workflows over the same campaign scope and review period. Use a consistent unit: one updated deliverable that has passed approval.
Cost per approved deliverable update = (setup + source edits + integration and replacement work + review + rework + recovery and archiving) ÷ approved deliverable updates
In the opening example, one price change approved across twelve ads counts as twelve deliverable updates. Failed refreshes and repeat exports add cost but do not add approved updates. Include setup costs in both options, convert staff time to cost on the same basis, and record any manually rebuilt versions. Assign each cost once, even when a live-linked workflow also needs manual replacements. If no updates pass approval, report the cost incurred and the failure instead of calculating a unit cost.
The model can produce opposite answers. In an always-on program with many languages, ratios and repeated updates, integration cost may be spread across many approved changes. In a one-off campaign with one or two edits, a complex approval chain or frequent layer restructuring, governance and regression work can cost more than manual replacement.
Ask suppliers to separate setup, routine updates, review and recovery work in their estimates. A cheaper update rate may still require more setup or leave the brand paying for checks elsewhere. Compare the total work needed to deliver the same approved outputs, including the handover package.
Run a disconnection test before acceptance
Run these checks on a duplicate project with isolated copies of its assets, leaving the working and released files untouched. Before testing, confirm that every source path in the duplicate project points to an isolated test copy:
- Make the test source unavailable. Identify what goes offline and demonstrate which archived source or rendered fallback restores it. A timeline opening without an error is not enough; check that the expected picture is present.
- Restore the approved version. Use the handover package to reopen the release and compare the affected frames, copy and timing with the approved reference export. Record any missing assets or manual fixes.
- Test the handover. Have another editor follow the manifest. List required application versions, plugins, licenses and access permissions, and resolve anything that depends on the original supplier's personal account.
Agree the required recovery steps and acceptable exceptions before acceptance. If the replacement editor cannot reproduce the approved result from the supplied package, the handover still needs work.
The next production brief can start with one sentence: Every source asset that can propagate automatically must identify its source of truth, scope, state, approval owner, regression checks and rollback package.
For the twelve-ad price change, that means one source correction, a review of each affected language and format, and a release package that preserves the approved result. The next source edit should change the working campaign without changing what the brand has already signed off.
