Script Formatting Choices That Help Your Editor

The short answer

Formatting that helps an editor does one thing well: it answers questions before they are asked. Scene numbers, consistent markers, and clear note types do that work quietly on every page.

An editor should never have to hunt through a paragraph to find what changes on screen. If they are searching, the format is costing them time you already spent.

The format carries as much information as the words once the cut starts, so it deserves the same attention you give the script itself.

Mark what the editor needs

Number scenes so the editor can match script beats to clips. A number is easier to call out in a session than a vague description of where something happens in the story.

Separate spoken lines from production notes visually. The editor reads words in one style and instructions in another, without pausing to sort them on the fly.

Label insert shots and graphics so the editor knows which footage and assets to expect before the timeline is built and the gaps appear.

Reduce back and forth

Every question the editor sends you costs time on both ends. Pre-answer the common ones, such as which take is preferred or where a graphic lands in the scene.

Keep a short notes section at the top for global instructions like music mood or pacing across the whole piece. Global notes do not belong buried in scene twelve.

Update the script when decisions change, so the file never lies about the current plan and the editor trusts what they read.

The best script note is the one the editor never has to ask for.

Format for the cut

Use a table or clear indents so the editor can scan rather than read. Scanning is how they find a beat in a long file while a deadline sits on the other side of the edit.

Separate each scene with a clear break so the timeline maps cleanly to the page in front of them. Clean boundaries make the whole project easier to navigate.

Export a clean text version for the editor and keep the styled version for the rest of the team, so each reader gets the format that suits the job.

Handoff notes for the edit

A short handoff section beats a long conversation at the start of an edit. List the preferred takes, the music direction, and any open question in one place.

Mark which scenes are final and which still need a decision. The editor can then work on the settled parts while the rest waits for an answer.

Update the handoff note as the edit progresses so the script stays a live reference. A document that matches reality saves everyone a status meeting.

The handoff note should fit on one screen. If it runs long, the editor stops reading and starts asking, which is the outcome you wanted to avoid. Trim it to the decisions that change the cut and leave the rest for a conversation. A short note gets read twice, once at the start of the edit and once at the end. That second read is often where a missed detail surfaces before the export. Date the note so a stale instruction never masquerades as a current one, and when a decision changes, strike the old line and add the new one rather than erasing the history. That visible trail turns a tense review into a calm one.

Key takeaways

• Number scenes so script beats match clips.
• Separate spoken lines from production notes.
• Pre-answer common editor questions in the script.
• Update the file when decisions change.
• Give the editor a clean text export.