MOOIEV BLOG
A video-editor handoff checklist you can actually test
Prepare a small-production edit with an original media manifest, a clear review brief and a recipient-side opening test before calling the handoff complete.
In this article 10 sections
Make the first edit possible without a rescue call
A delivery link is a location, not a complete handoff. An editor still needs to know which material is current, which decisions are approved, what remains unresolved and who can answer the next question. A neatly named folder can be missing all four.
This checklist ends with a test: the receiving editor opens the package in the agreed editing application, identifies the current brief, locates representative picture and sound, and reports the exceptions. This is an original suggested workflow for small productions, not a promise that one folder structure fits every post-production team.
Agree on the assignment before collecting files
Write a short edit brief before uploading media. Separate the first review from final delivery: a review export with temporary music is not a finished master, and a proxy-only editing package does not establish that the finishing team has the originals.
The following example is fictional. Night Bus is a small, staged transport film with invented files and roles. Its specifications are illustrative choices, not recommended defaults for every platform or client.
| Decision | Fictional handoff agreement | Who confirms it |
|---|---|---|
| Deliverables | One 30-second landscape film and one 15-second vertical cut; separate sequences and framing review. | Producer and editor |
| Working setup | Record the exact application/version used, sequence frame rate and resolution in README; agree changes before upgrading. | Sending and receiving editor |
| First review | A clearly marked review export; unresolved material stays labelled temporary. | Editor |
| Approval | One producer returns consolidated notes; the editor flags conflicting instructions before revising. | Producer |
| Finishing | Identify who holds camera originals and who approves the final picture, sound and delivery exports. | Producer and finishing editor |
Keep camera originals, proxies and references distinguishable
Adobe describes proxies as smaller-resolution copies used for editing. Its proxy attachment workflow links proxy files with full-resolution clips using matching information such as filenames and timecode. That supports a practical distinction in your manifest: identify what a file is, rather than relying on a folder called FINAL.
Preserve the recorded filename and camera-card context in the log. A human-friendly shot label such as 03B / take 2 belongs beside that identity. Two cards can contain similarly named files; the card or source-folder reference helps the receiving editor distinguish them. Check the pairing on a representative clip instead of assuming that similar names prove it.
Do not rename or reorganize an already linked media package casually. Agree the transfer approach with the editor and verify the copied project. If only proxies are being delivered now, say so explicitly and document the location and availability of the originals for the later stage.
Worked example: a manifest that exposes the missing insert
Use one row per relevant asset or asset set, with the actual inventory becoming as detailed as the job requires. The abbreviated fictional manifest below is a planning example, not a list of real downloadable media. Its last column tells the editor what can proceed and what needs a decision.
The missing ticket insert is a production fact within this invented example, not something the editor should silently invent to satisfy the shot plan. The first review can proceed if the producer agrees to the visible placeholder; final delivery waits for an explicit decision. A planned shot and a recorded clip are different records.
| Asset / reference | Identity and purpose | Status / next action |
|---|---|---|
| 03B / take 2 | Card A001: A001C014.mov; proxy A001C014_Proxy.mov. Candidate doorway reaction. | Picture pair checked on receipt; selection remains an editorial decision. |
| 03B / sound | Recorder card R002: R002_018.WAV. Separate production sound associated in the log. | Receiving editor verifies sync against the picture; do not assume the naming proves sync. |
| 03C / ticket insert | Listed in the shot plan; no corresponding recorded file in this package. | Not supplied. Producer confirms whether to omit, replace or arrange a pickup. |
| Review brief v03 | NightBus_EditBrief_v03.pdf; one current reference, with the previous version in the archive. | Producer confirms this is the version to follow. |
| Music candidate | TEMP_music_01.wav with source and clearance status recorded separately. | Reference only; do not treat it as cleared for final delivery. |
Give each folder a job and each document a version
An example top-level package is NightBus_Handoff_v01. Use the editor’s agreed organization if one already exists. The names below are suggestions; keeping the contents and README consistent matters more than adopting these exact words.
- 00_README: current assignment, package version, application/version, contact role, file map and known exceptions.
- 01_PROJECT: the intended editing project or agreed interchange files, labelled with their version and purpose.
- 02_MEDIA: camera originals when included; preserve the agreed card and source-folder structure.
- 03_PROXIES: clearly identified editing proxies, with their relationship to the originals recorded.
- 04_AUDIO: production sound and other audio, with references back to the media log.
- 05_BRIEF_AND_REFERENCES: approved brief, script or AV script, selected boards and any relevant shot notes.
- 06_REVIEW: review exports named by version; clearly distinguish review files from approved masters.
- 07_STATUS: asset manifest, questions, decisions and the receiving editor’s opening-test result.
Choose the collection method with the editor
For a Premiere project, Adobe documents File > Project Manager and the Collect Files and Copy to New Location option. It gathers footage used in the selected sequences and creates a project linked to the selected media. Review the collection choices deliberately: excluding unused clips can remove alternatives that the receiving editor still needs.
That command is one collection method, not your acceptance test. State which sequences and media were included, then open the copy from its delivered location. If the assignment includes new editing from unselected takes, the package must cover that assignment rather than only the media used in an existing cut.
Ask the recipient to perform the opening test
Run this on the receiving setup and from the delivered package or agreed shared location. A project that opens on the sender’s machine can still depend on files that the receiver cannot access. An upload-complete indicator alone does not answer that question.
- Open README and identify the approved brief, deliverables and first-review scope without asking the sender.
- Open the intended project or import the agreed material; record missing media, unsupported dependencies and application/version warnings.
- Locate a representative picture clip and its sound. Check the intended proxy/original relationship where that workflow is used.
- Check a sample across the beginning, middle and end for picture/sound alignment; record any discrepancy rather than silently correcting the log.
- Locate references and temporary assets. Confirm the editor can distinguish them from approved deliverables.
- Return one acceptance note: package version received, what opened, what is missing and who owns each next action.
Record what the acceptance actually covers
For the fictional Night Bus package, a useful result is: “v01 opens; 03B picture and sound checked; 03C not supplied; temporary music remains reference-only. Ready for first review with the agreed placeholder; not ready for final delivery.” That is more useful than a blanket “all good” because it defines the limit of the acceptance.
Keep the handoff log separate from the revision log
The handoff log answers whether the editor has the material and context to begin. A revision log answers what must change in an existing cut. Keep them linked by package and review versions, but do not bury a missing source clip among creative preferences such as making the opening feel faster.
Keep the relevant script, shot references and planning decisions accessible alongside this record. Editing media, transferring files and producing the final master belong in the tools and storage workflow agreed with the post-production team; this article does not claim that Mooiev is a footage editor or a media-transfer service.
Editorial notes and sources
Written by Mooiev with AI assistance and reviewed for this publication on 23 October 2026. The Night Bus scenario, asset names, folder map, manifest and acceptance note are original fictional examples. They do not describe a customer project or guarantee an editing outcome.
Adobe documentation was checked on the same date for the limited proxy and project-collection descriptions linked above. The remaining checklist is Mooiev’s suggested workflow. No third-party images, real client files, private crew information or licensed music are reproduced.