Collaboration and Handoff
Creative work often continues through other people. Someone reviews a shot, changes a material, replaces a source asset or prepares a delivery. They need enough context to act without accidentally discarding an earlier decision.
Collaboration includes successive work on a shared artefact as well as simultaneous editing. Begin with the responsibilities and handoffs observed in Understanding the Work.
Anchor Review to the Work
A comment should identify the asset or object, the relevant frame or range, and the version reviewed. Preserve the anchor when the work changes, or make it clear that the comment refers to an earlier state. A note on frame 48 of version 3 should not silently appear to describe frame 48 of a retimed version 4.
Distinguish a proposed change from an approved decision. Keep the reason where it will help the next person: “retain this timing to match the voice-over” explains more than “locked”. Allow questions and unresolved issues to remain visible without making every annotation a blocking instruction.
Make Responsibility and Edit Scope Clear
Show who owns or is editing an asset, which version is current, and whether a local change has been shared. Before an operation affects other people's work, show its scope. Renaming a shared texture or changing a referenced rig can affect far more than the selected object.
Choose conflict handling to suit the material. Some property changes can be merged; incompatible geometry or timing edits may need an explicit choice. Preserve the competing versions long enough to inspect them. Avoid silently accepting the last save as the correct result.
Prepare a Usable Handoff
Include:
- The editable project, its version and intended next step.
- Required source assets, fonts, plug-ins and other dependencies, with missing items identified.
- Relevant settings, including frame rate, colour interpretation and output requirements.
- Approved decisions, outstanding questions and the person responsible for resolving them.
- A preview or reference output against which the recipient can check the reopened work.
Keep this information attached to the project where practical. A separate message may explain the handoff, but should not be the only place a critical dependency is recorded. See Working Across Applications for transfer losses and Recovery and Versions for approved states.
Practical check: ask a second artist, who has not watched the work being made, to open it and carry out a revision. Watch for missing files, mistaken approvals, stale comments and changes whose consequences they cannot predict. Revise the handoff until they can explain what they received and safely continue it.