Short Drama Editor Handoff Guide: What Leaves Set and What the Edit Receives

The moment between wrap and the first edit session is where most micro-drama productions leak value — not in big ways, in small forgetting: the continuity note that stayed in someone's head, the slate log that never left the camera bag, the pickup list that was "obvious" on set and is a riddle three days later. The editor handoff is the transfer of everything the set knew into something the edit can read without a phone call. On a two-person crew where the shooter and the editor may be the same person on different days, the handoff is a note to your future self — and future self has the memory of a stranger. This guide covers the handoff packet's contents, the fifteen minutes it takes to assemble, and the mistakes that turn a two-day edit into a five-day archaeology dig. It runs on rails already laid by the editing workflow, the slate naming convention, and the dailies review, which produces most of the packet's contents as a byproduct of running properly. This is an independent channel-docking resource. It is not affiliated with or endorsed by ReelShort.

The packet: six documents, one folder

The handoff is not a conversation; it is a folder the edit opens before it opens any footage:

| Document | Source | What the edit does with it |

|----------|--------|---------------------------|

| Selects list | Dailies review | First assembly order; shot, take, in-point |

| Gaps list | Dailies review | Explains why coverage is missing; feeds pickups |

| Continuity flags | Continuity photos | Which jumps are real and which are safe |

| Slate log | Slate naming convention | Clip index; the edit's map of the footage |

| Card manifest | Media management | Which folders hold which days; verification trail |

| Release status | Release forms | Confirmations that everything in the cut is cleared |

The selects list is the packet's centerpiece, and it exists only if the dailies review ran — which is the quiet argument for the twenty-minute habit: the review is where tomorrow's edit gets its head start. A handoff without selects is a hard drive with hope.

The fifteen-minute assembly

The packet assembles at wrap, in one sitting, while the day is still fresh. The dailies review has already produced the selects, gaps, and continuity notes; the handoff step is packaging, not authoring: copy the review's output into the project folder alongside the slate log and card manifest, add one paragraph on anything the documents cannot say — the performance nuance the editor should protect, the shot the director loved, the take the slate does not explain — and name the folder with the same project code and date the media system uses. One paragraph of prose is the difference between a packet and a pile: it carries the intent the documents cannot. The call sheet from the shoot day completes the picture — what was planned tells the edit what a missing setup means.

What the edit does in its first hour

A good handoff gets verified, not trusted. The edit's first hour: confirm the card manifest against the folders on disk (the copy-verify trail makes this a glance, not an audit), spot-check three slates against the log, skim the selects list against the footage's runtime, and read the prose paragraph. Ten minutes of verification catches the transfer corruption, the missing card, and the stale selects list while the person who can fix them is still reachable. Skipping verification does not skip the cost — it moves the discovery to day three of the edit, when every hour is more expensive and the fix may require a call instead of a re-copy.

The recurring handoff, refined

Each wrap's packet improves on the last one, and the mechanism is the wrap comparison: what the edit actually asked about is what the next packet should have included. Every "which take was this?" that reaches the editor is a line the selects list should have carried; every "where is the sound for scene six?" is a slate-log gap. The call sheet plan-versus-actual comparison feeds the same loop from the scheduling side. Three cycles in, the packet stabilizes into the production's own house format — shorter than any template, because it contains exactly what this team's edit asks for and nothing else.

Common Handoff Mistakes

• Verbal handoffs — "I'll explain the footage tomorrow" is a plan to forget; the folder is the contract.
• Selects without in-points — "the good kitchen take" sends the edit hunting; timecodes turn notes into navigation.
• No prose paragraph — documents carry facts, not intent; the one paragraph of context is what protects a performance nuance from a blunt trim.
• Unverified transfers — trusting the copy instead of checking the manifest moves discovery to the most expensive possible day.
• Never updating the packet format — the edit's questions are free feedback; ignoring them means rebuilding the same gaps every cycle.

FAQ

What if the shooter and editor are the same person? The handoff still happens — a note to future self written the same evening, because the memory of what "the good take" meant decays faster than the project takes to reach the edit.

How long should the whole packet take to assemble? Fifteen minutes at wrap: the dailies review already produced most of it, so the assembly is copying, one paragraph of prose, and folder naming.

Does the handoff replace talking to the editor? No — it replaces re-explaining; a call that starts from a shared packet answers questions instead of transmitting basics.

What is the first thing the edit should verify? The card manifest against disk, then three random slates — transfer integrity and index accuracy are the two failures that cost the most when discovered late.

Related resources

The consistency viewers see across episodes on the ReelShort site is what a clean set-to-edit pipeline produces at scale — the handoff is the seam that keeps it unbroken.

Email partner@shortdramapartner.com for channel-docking consultation and help applying for your ReelShort invitation code through official channels.