A finished render is only one part of a reusable handoff. The next person needs to know which source belongs on each display, what should stay consistent and which file is meant for which placement.
Try it in SynthMock
Start with a Duo scene.
Use a reusable template as your starting point, then apply the choices in this article.
A paid plan is required to use templates and export.
Start with the creative decision
Write a short note naming the campaign's audience, selected task and visual direction. For example: a screen-led planning-app launch, one Star White Duo, a quiet sage setting, and the same itinerary across cover and inner views. This tells the next creator what they are preserving when they make changes.
Include an approved reference image and distinguish it from rough alternatives. Without that distinction, a later collaborator may treat an abandoned camera angle as the current direction. Use names that describe purpose rather than a pile of final-final filenames.
A practical handoff inventory
The following inventory is a proposed collaboration checklist. Store only source material you are entitled to share, and make access expectations clear to the recipient.
| Item | What to record |
|---|---|
| Screen sources | Large inner and small outer files, task state and permissions |
| Scene reference | Relevant project/template link, finish, background and light intent |
| Deliverables | Actual dimensions, format and intended placement for each file |
| Motion notes | Shot purpose, important reading moments and approved endpoints |
| Review status | Approved choices, unresolved issues and concept labels |
Test what the recipient can actually open
A private project link and a public template link have different purposes. Use the appropriate sharing flow and explain whether the recipient needs an account and paid access to create or export their own version. A link that works in the owner's session is not sufficient evidence of a useful external handoff.
Finish by opening the delivery files themselves. Check the poster, first and last frames, screen assignments and any visible private content. When a source is a concept, say so in the package rather than expecting that context to travel with a conversation. The handoff should let someone continue the work while understanding both the creative intent and the limits of the assets they received.
Final pass
Before you call it finished
- Name screen files by role and include their approved state.
- Record actual output dimensions and placement.
- Verify the intended recipient's link and access expectations.
Make the next version yours.
Explore Duo templates ↗