MFDI9313 Chap.1 How an Edit Moves from Plan to Master
How an Edit Moves from Plan to Master
Editing begins before the timeline. This chapter links pre-production, production and post-production to the sequence of assembly, rough cut, fine cut, picture lock, sound, colour, effects, titles and mastering. It shows how naming versions, logging material and testing handoffs protects both the concept and the project. The practical focus is choosing the next useful action and explaining why it belongs at that stage.
Pre-production leaves a concept, source plan, permissions questions and schedule. Production leaves gathered material and logs. Post-production leaves named sequences, screening notes and verified outputs. Those traces allow a collaborator to understand the state of the work without relying on the editor's memory.
The chapter also separates creative milestones from backups: a milestone records a meaningful editorial decision, while a backup protects the files. Students practise both by packaging a small project, reopening it away from the original folder and testing whether another person can identify the approved cut. That recovery exercise exposes missing labels, broken links and undocumented assumptions before the stakes are high.
The underlying lesson is that project management is not outside the artwork. Reliable architecture creates space for experimentation because every risky revision can be compared, explained and reversed.
What this chapter covers
- 01
Pre-production, production and post-production
- 02
Assembly, rough cut, fine cut and picture lock
- 03
The editor as collaborator and problem solver
- 04
Version control and recoverable handoffs
- 05
Feedback as evidence for a controlled revision
- 06
Mastering and delivery verification
Worked example · free
Recovering a stalled short documentary
- +1Duplicate and date the current project before changing anything.
- +1Organise and log the material by type, action and story value.
- +1Build a new assembly around one controlling question.
- +1Screen a rough cut and reach picture lock before detailed finishing.
- +1Test the handoff and preserve the previous version.
Key terms
- Assembly edit
- An early sequence that gathers required material into a workable order.
- Rough cut
- A developing version used to test story, duration and broad rhythm.
- Picture lock
- The point at which image order and duration become stable for finishing.
- Mastering
- Preparing and verifying the final deliverable after the edit and finish are approved.
How an Edit Moves from Plan to Master FAQ
Why does editing start in pre-production?
The concept, script or treatment, permissions, schedule and source plan determine what material will exist and what the editor can reasonably build. Clear planning reduces gaps that no software command can repair later. It also creates evidence for later choices: the editor can compare the proposed experience with the material captured and explain why the final structure changed.
When should I declare picture lock?
Declare it only after structure, shot order, timing and essential feedback are settled. Sound, colour, effects and titles depend on stable image duration, so an early lock creates avoidable rework. Record who approved the lock and which sequence it names.
How should feedback change a cut?
Treat feedback as evidence about a viewer experience. Diagnose the cause, preserve the old version, change one relevant variable and compare the result rather than obeying a vague instruction literally.
Assessment move
Rebuild the workflow from memory and attach one concrete risk to every stage. Practise identifying whether a problem belongs to concept, capture, organisation, structure, continuity, sound, colour or delivery. Keep dated versions during your own work and add a one-sentence change note. For each screening comment, write what the viewer experienced, your diagnosis and the smallest revision that could test it.
Before moving into finishing, explain why the cut is ready for picture lock. Finish the exercise by opening the handed-off project and watching the export on another device. Start a fresh practice folder and write a short concept before collecting material. List the evidence that pre-production should leave behind: a synopsis, source plan, schedule, rights questions and a naming convention.
Gather a deliberately small set of clips, then log action, quality and story value rather than relying on thumbnails. Build an assembly whose only purpose is to expose coverage and order. Duplicate it for the rough cut, and keep a note of every structural decision. Ask a viewer where attention dropped, where geography became unclear and what they expected next.
Translate each observation into a hypothesis instead of an automatic command. Make one change in a new version and screen the relevant section again. When structure and duration settle, state the reason for picture lock in plain language. Prepare a test handoff that includes the current sequence, required assets and a short status note. Open it away from the original working folder.
If media relinks and the intended sequence is obvious, the architecture is doing its job. Repeat the check after sound, colour, titles and mastering, because finishing can introduce new dependencies. The final review should compare the verified master with the locked sequence and change log.
This routine develops the habit the unit values: technical actions become evidence-backed editorial decisions, and project management becomes part of creative control rather than an administrative layer added at the end.
