Releasing music has a habit of becoming messy very quickly. Even modest independent releases involve a long list of moving parts: masters, artwork, metadata, distribution, press assets, social posts, mailing lists, and deadlines that don’t always line up neatly.
Over time, I found that the problem wasn’t knowing what needed doing, but keeping everything organised and consistent from one release to the next. Things would get scattered across notes apps, folders, spreadsheets, and half-remembered plans, which added unnecessary stress to a process that’s already time-sensitive.
This post outlines how I’m beginning to structure an upcoming release, and how I’m using TrackOffice, a tool I built myself, to manage that process.
Why I built TrackOffice
TrackOffice exists to solve a very specific problem: keeping music releases organised without relying on memory, improvised checklists, or one-off documents that never quite get reused.
I wanted a system that could:
- structure a release into clear stages
- break the workload into manageable tasks
- surface what needs doing now versus later
- keep assets, links, and press material in one place
- provide stable, outward-facing pages for press and promotion
Most general productivity tools are flexible but abstract. TrackOffice is deliberately opinionated around the realities of releasing music. It treats a release as a structured project with repeatable steps and standard outputs.
How I’m structuring this release
At an early stage, I’m working with a simple framework rather than a rigid schedule. The aim is to reduce decision fatigue and avoid last-minute scrambles.
Defining the release
The first step is locking down the basic shape of the release:
- format (single, EP, album)
- physical and digital formats involved
- whether there are lead singles
- any anchor events (gigs, announcements, launch windows)
This information becomes the reference point for everything that follows.
Locking core assets early
I’m trying to get the essentials in place sooner than I have in the past:
- final masters and backups
- artwork and format variants
- track titles, credits, and metadata
- short and long descriptions that can be reused
Having this material settled early makes it easier to build press assets and avoid rewriting the same text repeatedly.
Building the press kit as I go
One change in approach is creating the EPK early, rather than treating it as a final-week task.
TrackOffice allows me to build a permanent press page that holds:
- release details
- cover artwork
- press text
- links to audio and platforms
Because it’s a stable page, it can be shared with promoters, blogs, or radio without needing to assemble a new pack each time.
Turning the plan into tasks
Once the release shape is clear, I translate it into structured tasks inside TrackOffice. This is where most of the stress reduction happens.
Instead of holding the whole process in my head, I can see:
- what’s outstanding
- what’s coming up soon
- what can wait
Over time, these task structures will become templates that can be reused and refined across releases.
TrackOffice: where it’s at right now
TrackOffice is very much a working tool rather than a finished product, but it’s already supporting real release planning.
Current features
- Release records with structured metadata
- Task planning tied directly to releases
- Public press (EPK) pages
- Public artist pages acting as stable hubs
- Centralised handling of artwork, text, and links
The emphasis is on reducing fragmentation and keeping everything connected to the release itself.
In development
- Improved task templates for different release types
- Clearer timeline views across a release cycle
- Refinements to public vs private page behaviour
- Better asset tracking and version clarity
- Presentation improvements for press pages
The goal isn’t to add features for the sake of it, but to remove friction from the parts of the process that consistently cause problems.
An unfinished system by design
TrackOffice isn’t being built in isolation. It’s being developed alongside real releases, using live projects as test cases.
Each release highlights:
- what works
- what’s missing
- what adds clarity
- what creates unnecessary complexity
Rather than aiming for a “complete” tool upfront, the plan is to sharpen it through repeated use, documenting changes and decisions as I go.
This approach keeps the system grounded in practical needs rather than abstract planning.
The aim: consistency without burnout
Ultimately, TrackOffice is about making releases repeatable and sustainable.
If it’s working properly, each release should feel less like a one-off emergency and more like a familiar process with:
- clear stages
- known tasks
- reusable assets
- stable public pages
That consistency frees up time and mental space for the creative work itself, rather than administrative overhead.
What’s next
The current focus is on:
- finalising the release structure
- building the EPK early
- refining the task flow inside TrackOffice
- documenting the process as it happens
Future posts will dig into specific parts of the workflow in more detail, using real releases as examples rather than theoretical guides.
