The Engineer's Workpad

How to know when a song is actually finished

Every producer stalls on the same question. The answer is not a feeling — it's a definition you set before you got tired of the track.

You know the loop. The track sounds good on Tuesday. On Thursday the kick feels weak, so you swap it, which unbalances the low end, so you remix the bass, and now the drop feels empty, so you add a layer, and by Sunday you're back to a version that sounds suspiciously like Tuesday's. Three months later the project folder has final_v9_FINAL_actualfinal.flp in it and the song still isn't out.

The problem is almost never skill. It's that "finished" was never defined. When "done" is a feeling, every listen re-opens every earlier decision — and a track with open decisions in four areas at once can never converge. The fix is boring and it works: define done per stage, in advance, as checkable steps. Then finishing stops being a mood and becomes an audit.

The four stages, and what "done" means in each

1. Songwriting — done when the song survives naked

Before production tricks, the song itself has to be finished as a piece of writing. Play it with one instrument and the melody (or a rough vocal). If it holds attention like that, production will amplify it; if it doesn't, production will camouflage it for a while and then you'll be back here in week three wondering why the drop "doesn't hit".

2. Production — done when adding hurts more than it helps

Production finishes at the point of diminishing returns, and that point arrives earlier than it feels. A reliable signal: you add a layer, and to make it fit you have to turn three other things down. That's the arrangement telling you it's full.

3. Mix — done when it translates, not when it's perfect

Mixes die of a thousand tiny moves nobody can hear. The professional definition of a finished mix is not "nothing could be better" — it's translation: the mix does its job on every system that matters.

That last item is the honest one. A named defect ("the snare disappears in the car") is work. An unnamed unease after the fortieth listen is fatigue, and fatigue is not information about the mix.

4. Master — done when it's loud enough, and no louder

The rule that makes the checklists work

Stages close in order, and a closed stage stays closed unless you can name the concrete defect that reopens it. This is the whole trick. The endless-tweaking loop is powered by free reopening: any stray feeling on any listen is allowed to drag you back into songwriting while you're supposed to be mixing. When reopening costs a named reason, ninety percent of the reopenings never happen — because they never had one.

Producers who release consistently aren't more talented at finishing. They've just moved the decision of what "done" means to the start of the project, when they were still objective — and then they trust the checklist over the 3 a.m. feeling. Fatboy Slim reportedly finishes about one track in ten; the point of a definition of done isn't that every track ships, it's that every track either ships or gets killed on purpose, instead of rotting in the folder as version nine.

Do it on paper, or do it in the Workpad

Everything above works with a pen. Write your steps per stage, tape them to the wall, check them off, and don't reopen closed stages without naming a defect.

The Engineer's Workpad is that method as a tool: the four stages with every step accounted for, per project — with a progress log so decisions stay decided, notes for the step you're stuck on, and reference EQ and pan charts where you actually need them. It runs in the browser, on your phone too, no app store required.

Stop asking "is it finished?" — start answering it.

One active project free · $4.99 one-time unlocks full features · plans for 10+ projects. No card to start.

Open The Engineer's Workpad