Preparing Source Files: Mistakes That Cost Editors Hours
Most trouble in a voiceover edit starts before the first cut. These are the preparation mistakes we see most often with recordings and scripts, and the simple habits that prevent them.
Daniel Okafor · · 6 minutes to read
Starting to edit before the files are checked
The commonest mistake is also the most understandable: a folder of recordings arrives, the deadline is close, and the editor opens the first file and starts cutting. Twenty minutes later a take turns out to be a duplicate, another is missing its second half, and a third was recorded at a different sample rate from the rest. None of this is visible until you look for it, and each problem is much cheaper to find before any edit exists than after.
We ask learners to spend the first part of any job listening, not editing. Play each file through at least once with headphones, note its length, and confirm that it opens, plays to the end and matches the format you were told to expect. Check that the channel layout is what you assumed, because a mono voice delivered as a stereo file with one silent side is easy to miss on laptop speakers.
A simple checking pass takes a few minutes for a short explainer and perhaps half an hour for a long interview film. It is the cheapest time you will spend on the whole job.
- Open and play every file to its end
- Confirm sample rate, bit depth and channel layout
- Note duplicates and obviously incomplete takes
- Record anything odd in a short written list
Working without an approved script
A voiceover is edited against words, and those words need an owner. When the script on your desk is an early draft, a version someone retyped, or a file with tracked changes still visible, you will match takes to text that the client no longer wants. The mismatch usually surfaces at the review stage, when a sentence you carefully assembled is the wrong sentence.
Ask for the approved script in writing, and ask which version it is. Put the version or date in the file name so it cannot be confused with an earlier copy. If the narrator changed a line on the day, make sure that change was agreed and is written down, not simply spoken in the booth and remembered by one person.
Where a recording departs from the script, mark the departure beside the line instead of quietly choosing one. That small note gives the producer a clear decision to make, and it keeps you out of an argument about who changed what.
- Request the approved script and its version in writing
- Name the script file with a version or date
- Mark every spoken departure from the text
Muddled naming and labelling
Files called final, final2 and final_real are a warning that nobody has agreed a naming rule. They also guarantee that someone, at some point, edits the wrong one. A consistent name should tell you the project, the speaker or section, the take and the date without opening the file.
Choose a pattern before the first file is imported and apply it to everything, including the script and any notes. Keep it short, avoid spaces and unusual characters that some systems dislike, and use leading zeros so that take 2 sorts ahead of take 10. If a colleague opens the folder cold, they should understand it within a minute.
Labelling also covers what a recording is. A clean studio read, a phone interview and a location report need different treatment later, so say which is which at the start. The label costs seconds now and saves you guessing when you reach cleanup.
- Agree one naming pattern before importing anything
- Use leading zeros so takes sort in order
- Label the type of recording, not only its name
Skipping the question of permission
Learners sometimes treat rights as someone else's concern. Yet an edit built on a recording you were never cleared to use is wasted work, and in some cases it creates a problem for the producer. Before you touch a file, confirm that the recording is authorised for this project and that you know who gave that authorisation.
This does not need to be a legal exercise. A line in an email from the producer, saved with the project, is usually enough to show that the material is cleared for editing and delivery. Keep it where you can find it again.
The same care applies to anything you did not expect to receive, such as a stray music bed or an extra interview left in the folder. If you are unsure whether it belongs in the job, ask before it reaches your timeline. Asking takes a moment, and not asking can undo a day's work.
- Confirm who authorised each recording
- Keep the written permission with the project files
Overwriting the originals
The mistake that cannot be fixed afterwards is working on the only copy. A destructive edit, a wrong export over the source, or a drive that fails mid-session can remove a recording that cannot be made again, particularly with an interview.
Copy the delivered files into a read-only folder at the start and never edit from it. Work from a second set, and keep that second set separate from your exports. If the narrator is unavailable for a re-record, the untouched originals are the only way back to a clean starting point.
Make a note of where the originals live and tell anyone who shares the project. A short habit like this protects the producer's material as much as your own time, and it costs only a few seconds of copying.
- Copy originals to a read-only folder first
- Edit only from a working copy
- Keep exports in a separate place
Leaving the handover note unwritten
Even careful preparation loses its value if the next person cannot see what you did. A short handover note, kept beside the files, records the checks you made, the script version you used, any problems found and any questions still open.
It need not run past a page. List the files received, the files you consider usable, and anything missing or doubtful. If a take was dropped, say why. If the narrator stumbled on a name, flag it so the producer can decide whether to correct it.
Written notes also protect you when a client remembers a conversation differently. They show what you were given and when, and they turn a vague recollection into something you can both read. Learners who adopt this habit early find that revisions stay smaller, because the starting point was clear to everyone.
- List files received and files judged usable
- Record dropped takes and the reason
- Flag open questions for the producer
Preparation mistakes rarely look serious on the day, which is why they repeat. Check the files, confirm the script, name things clearly, secure permission, protect the originals and write a short note. None of it is difficult, and together it makes every later stage of the edit calmer. Learners who build these habits find the cleaning, balancing and delivery work that follows goes noticeably more smoothly and with fewer surprises.
Daniel Okafor
Instructor, Sync and ReviewDaniel works with picture editors on synchronisation and review workflows. He guides learners through feedback rounds and revision scope.