Manage music projects — from first session to finished release

What a music project needs to track

Before choosing a system, it helps to list what a music project actually needs to manage. Most people underestimate the scope.

Files. Source recordings, stems, production files, mix exports, masters, references, artwork. Multiple versions of most of these. Files need to be versioned, accessible to collaborators, and organised so the right file is findable when needed.

Tasks. What needs to happen, by when, and who is responsible. Recording session, mix delivery, feedback turnaround, mastering, metadata completion, distributor submission. Tasks accumulate quickly and informal management means things get missed.

Collaborators. Who is involved, what access they have, and what they have been sent. A producer, mix engineer, mastering engineer, and featured artist may all have different levels of access to the project and different deliverables.

Decisions. What was approved, what was changed, and when. The mix that was approved on a specific date. The split that was agreed before release. The version that was submitted to the distributor. Decisions that are not documented are reconstructed from memory when they become important — which is always the wrong time.

Deadlines. Release date, distributor submission window, promo campaign start, DJ promo send. Missing a deadline at any stage has downstream consequences for the whole release.

The three project management failure points in music

Files without structure. When files for a project live in multiple locations without a clear hierarchy — some on a hard drive, some in a shared Dropbox folder, some in email attachments — the project has no single source of truth. Finding the right file requires knowing where it was last put.

Tasks without assignment. "We need to sort the artwork" is a note, not a task. A task has an owner, a due date, and a status. Without these three attributes, tasks remain as vague intentions rather than trackable commitments.

Decisions without records. The mix engineer says the master sounds great in a WhatsApp voice note. The collaborator agrees to a 30% split in a DM. These decisions are real, but they are not recorded in a way that is findable, timestamped, or evidential if they become important.

Managing a music project in TYFRA Vault

Create the Project at the start, not retrospectively

The single most important habit in music project management is creating the project infrastructure before the work starts rather than after. A Project created at the beginning of a session becomes the natural home for every file, decision, and task that follows. A project folder created retrospectively is a reconstruction job.

In Vault, create a Project when you start a new track or session. Name it clearly — artist, track title, session date if relevant. Add collaborators immediately with appropriate permissions. The project is now the container for everything that follows.

Task management — making implicit work explicit

Vault's task management turns the mental to-do list of a project into an explicit, tracked record. Create tasks for each next action with a due date, a priority, and an assignee. Tasks can be templated — a standard release checklist means the same ten pre-release steps are created automatically for every new release rather than being remembered (or forgotten) each time.

Tasks connect to the project they belong to. When you open a project, you see the outstanding tasks alongside the files they relate to — not in a separate app, not in a text document, in the same place as the work.

Version tracking — knowing which file is current

The version question is the most common source of wasted time in music project management. Track Revisions (v1/v2/v3 for production iterations) and Track Versions (Instrumental, Radio Edit, Extended for functional variants) mean the current file is always identifiable. Notes on each revision provide the context: "v3 — low end revised after mastering feedback, approved by label 14 March." The project record shows not just which version is current but why it changed from the one before.

Collaborator management — clear access, clear expectations

Each collaborator added to a project has a defined role and permission level. They see what they need to see and not what they do not. When you send a mix engineer a share link for the stems, the link points to a specific revision and tracks whether they accessed it. You know when they downloaded the files. You know when the project's feedback comments were left. The communication is visible in the project rather than reconstructed from email threads.

Split documentation — part of the project, not separate from it

Publishing and mechanical splits are created and agreed within the same Vault Project as the files they relate to — see managing music splits for the full workflow. The producer's split percentage, the featured artist's mechanical interest, the co-writer's publishing stake — all proposed, accepted, and logged with timestamps in the project record. When the track generates income, the split record is there. When a question arises later, the original document is in the project alongside the mix it was agreed on.

The release stage — from Project to Product

When a track is approved and ready for release, the work moves from Project to Product. A Product in Vault is a release container — the finished track with artwork, complete metadata, track ordering (for EPs and albums), and a distributor-ready export. The metadata carried through the Project populates the Product automatically.

The Product then connects to the rest of the TYFRA platform. The track is available in Promo for DJ campaigns without re-uploading. Revenue from the release is tracked in Finance. Any formal collaboration agreements live in Contracts, referenced from the same track record.

Building the project management habit

The value of good music project management is cumulative. A single well-managed project produces a clean record that answers questions months or years later. Fifty well-managed projects produce a catalog with complete metadata, version histories, and split documentation across every release.

The habit is built one project at a time. Create the project first. Add files and collaborators as they come in. Create tasks when work is agreed. Document decisions when they are made. The time investment is small — minutes per session — but the benefit compounds across the life of the catalog.

Related on TYFRA