Handing an edit to another person involves more than providing files. The new editor needs to understand the film’s current state, the decisions already made and the questions still open. Write a brief that lets them begin without inheriting every conversation the previous team remembers.
Agree first on the technical handover requirements with the receiving editor. Follow the relevant software and storage guidance for the actual project. This article concerns the working brief that accompanies that transfer, not a substitute for checking media, project compatibility or access.
Describe the cut that exists
Identify the current project and matching review export clearly. State what stage the cut has reached and which elements remain temporary. Keep this factual: scenes missing, sound incomplete, titles provisional. Avoid a defensive account of why every rough edge is still present.
Include a short synopsis if the editor is new to the project, but do not bury the working information beneath a long creative statement. The person needs enough context to understand the film and enough precision to locate the current work.
Explain any version that should remain available as a reference. A previous opening may contain an approach the team still wants to consider. Label why it matters so the new editor does not mistake it for the active cut.
Separate decisions from suggestions
Create two short groups: decisions to preserve for now and questions to investigate. Name who made a decision and what it covers where that distinction matters. A preference expressed during an informal screening should not silently become a fixed requirement.
For an open question, describe the problem before proposing a repair. “The journey between these scenes feels unclear” gives the editor room to work. “Add the street shot” may be a useful idea, but it should remain attached to the problem it is meant to solve.
Keep conflicting notes visible rather than blending them into a false consensus. If collaborators disagree about the ending, say who will resolve that question and how. The new editor should not have to discover the disagreement by completing the wrong version.
Make the first task achievable
Choose an initial task with a clear boundary. It might be reviewing the current cut and identifying questions, or trying an alternative order for a particular sequence. Avoid asking for a complete solution before the editor has confirmed that the project opens and the materials are usable.
Agree on the form of the first response and the person who will collect notes. A single point for consolidated feedback can reduce conflicting instructions, provided the team knows how its views reach that person.
Include the practical contact route for missing information. Identify who can answer story, production and technical questions without publishing unnecessary personal details in widely shared documents.
After the editor receives the project, allow time for a brief confirmation conversation. Ask what is missing from the handover rather than assuming silence means everything is clear.
Update the brief when a decision changes during the transition. Keep the earlier record where it helps explain the work, but make the current direction easy to identify. A thoughtful handover gives the next editor both context and room to contribute, instead of a folder full of unexplained certainty.