How to hand off a script to your video editor (what editors need)

A typical bad handoff looks like this. A creator sends one long Google Doc called “final_v3_FINAL”. The footage is split between a Drive folder, a WeTransfer link that expires in four days, and “the rest is on my phone, I’ll send it tonight”. The only direction is “make it pop”. Two days later a new doc arrives, “final_v4”, with changes nobody marked.

I’ve been on the receiving end of a script handoff to a video editor for 7+ years and over a thousand edited videos, for creators and agency clients. The script is rarely the problem. The handoff is. Here is what your editor actually needs, a checklist you can copy, and how to run feedback without losing a week.

What your editor actually needs

Editors don’t need more words from you. They need fewer guesses. Every item below removes a guess.

A locked script with a version name. “Locked” means you won’t rewrite it while the edit is happening. Name it with a date or number, like “ep14_script_v2_2026-11-08”, and say which version is the one to cut. If something changes later, it becomes v3 and you tell the editor what changed.

Scenes with target lengths. Break the script into scenes and give each one a rough duration. “Intro 0:20, problem 1:00, fix one 2:00” tells me where the weight of the video sits and what to trim when it runs long. If you write in scenes already, this is half done.

Visual notes per line. For each line or scene, write what the viewer sees: talking head, screen recording, stock of a busy street, a graphic with three numbers. Short is fine. A B-roll plan built from the script is the single biggest time saver I get from a creator.

Must-keep vs can-cut. Mark the lines that carry the video and the ones that are nice to have. When the cut runs two minutes over, I know what to lose without asking.

An asset list, and where every file is. One list: every clip, recording, graphic, logo, font and music track, with its location. One folder, not three services and a phone.

Take and file naming. If you recorded the intro four times, tell me which take you liked, or name the files so I can tell (“intro_take3_good”). Camera default names like “C0047.MP4” for 200 files cost hours.

References. One or two links to videos whose pacing, captions or style you want, with a note on what to copy. “The caption style from this one, the pacing from that one” is useful. “Make it like the big channels” is not.

Delivery specs. Aspect ratio (16:9, 9:16, both), target length, captions (burned in, separate file, or none), music source and licence, and where the final export goes.

Deadline and who approves. A date, and the name of the one person whose “yes” means done. If three people can approve, nobody can.

The script handoff checklist

Copy this into your project notes and tick it before you send anything.

[ ] Script is locked and named with a version (e.g. ep14_script_v2)
[ ] Script is split into scenes, each with a target length
[ ] Every scene has a visual note (what’s on screen)
[ ] Must-keep lines and can-cut lines are marked
[ ] Asset list written, with the location of every file
[ ] All footage, audio and graphics are in one shared folder
[ ] Takes are named or the best take is marked
[ ] 1–2 references with a note on what to copy from each
[ ] Aspect ratio and target length stated
[ ] Captions: burned in / separate file / none
[ ] Music source and licence confirmed
[ ] Brand assets included (logo, fonts, colours) if needed
[ ] Deadline for first cut and for final
[ ] One named approver
[ ] Where the final export should be delivered

If you can’t tick an item, say so in the message. “No music yet, use temp” is fine. Silence is what causes rework.

How to export the script for your editor

There are two good ways to export a script for an editor, and one bad one.

A PDF. Good when the script is locked. A PDF can’t change under the editor’s feet, it opens the same everywhere, and I can keep it on a second screen while I cut. Put the version name in the file name.

A shared link to a single document. Good when you expect small changes. The rule is that it’s the only copy. The editor bookmarks one link and that link is always the truth.

The bad way: pasting the script into chat. Formatting breaks, scene breaks disappear, and the next time you paste a “small fix” there are now two scripts in the thread and I have to diff them by eye. Same for screenshots of the script and voice notes with changes.

Whichever you choose, keep one source of truth. If you edit the script after handoff, change it in that one place, bump the version, and list what changed in a single line.

Feedback rounds

Most edits go wrong in feedback, not in the first cut. A few rules keep it short.

Use timecodes. “At 2:14, cut the pause before ‘and that’s why’” can be done in ten seconds. “The middle feels slow” starts a conversation. If you have a vague note, attach a timecode range to it anyway: “1:40 to 3:00 drags, can we lose about 20 seconds?”

Send one consolidated list per round. Watch the whole cut, then send every note at once. Notes that arrive one by one over two days mean I fix the same section three times. If several people review, one person merges their notes and removes the contradictions before it reaches the editor.

Decide who has final say. When the creator wants the joke in and the client wants it out, the editor shouldn’t be the referee. Name the person who decides, and agree on how many rounds are included before the edit starts. Two is a common number.

Separate fixes from new ideas. “The logo is the old one” is a fix. “What if we restructure the second half” is a new direction. Label them, so everyone knows which notes change the timeline and the deadline.

For what the first assembly should look like, see script to rough cut.

Mistakes I see every week

Changing the script after the cut starts, without saying where. Even one rewritten line can shift a whole section.
“Make it pop” as the only direction. Name one reference and one thing to copy from it.
Footage in three places. Every extra location is another chance a file goes missing.
No target length. A 14-minute cut of a “roughly 10-minute” video is not the editor’s fault.
Approval by committee. Five people giving notes with nobody deciding turns two rounds into six.

Most of these disappear when the editing plan starts before recording. Video production planning covers that part.

How I do this in Syntale

This is the handoff I wanted as an editor, so I built it into Syntale. The script is split into scenes, each with its own duration and a visual plan next to the words, so the editor sees what’s on screen for every line. You share the project with your editor or client, they comment and approve in the same place, and there’s one version of the truth. When it’s locked, export a PDF the editor can cut from. Start for free, or grab the free template first.

FAQ

What should I send my video editor?

A locked, versioned script split into scenes with target lengths and visual notes, plus one folder with all assets and a list of what’s where. Add references, delivery specs (aspect ratio, length, captions, music licence), a deadline and the name of the person who approves.

How do I give feedback to a video editor?

Watch the full cut, then send one consolidated list of notes with timecodes. Separate fixes from new ideas, and make sure one person has the final say.

What format should a script be in for an editor?

A PDF once the script is locked, or a single shared document link if small changes are still expected. Either way, keep one source of truth, split it into scenes, and put the version name in the file name. Don’t paste the script into chat.