Whether it is an album, a podcast season or a set of videos, recording projects fail for the same reasons: an undefined finish line and a schedule with no slack.
Define the outcome first
Write one paragraph describing what exists when the project is finished: how many pieces, how long, in what format, published where, by when. Every later decision is measured against that paragraph.
Map the stages
Most projects follow the same shape: preparation, recording, editing, finishing, delivery and publication. Write what must be true before each stage starts. Recording cannot start until material is finished and people are booked. Editing cannot start until files are delivered and backed up.
Book in the right order
Book the scarcest resource first. That is usually a specific person or a particular room, not the equipment. Confirm dates in writing with a deposit where appropriate. Hold a contingency date at the same time; rescheduling later is far harder.
Build the schedule backwards
Start from the publication date and work back through delivery, finishing, editing and recording, including approval time for everyone who must sign off. Approval is the stage most often forgotten, and the one most likely to take a week.
Add contingency deliberately
Add time at the end of each stage rather than one block at the end. Something always needs re-recording. Something always arrives late. A schedule with no slack is not a plan; it is a hope.
Assign decisions, not just tasks
Name who decides when a take is good, when a mix is finished and when a piece is ready to publish. Projects stall on unowned decisions more often than on unfinished work.
Track the boring things
- Files: where they live, who has copies, what they are named.
- Money: deposits, invoices, what is agreed in writing.
- Rights: releases, licences, credit, ownership.
- Contacts: everyone involved, with a role next to the name.
Review at the end
Spend thirty minutes writing what took longer than expected and why. The second project always runs better than the first if that document exists, and worse if it does not.