The Track List You Actually Bring: Culling a 60-Track Prep Pool Down to a 20-Track Set

Bringing everything is not safer prep. It is worse prep. If you have spent an afternoon dragging fifty or sixty tracks into a prep pool for one gig, the instinct behind it makes sense — more options feels like more control. But every track sitting in that pool is a decision you have deferred, not a decision you have made. And decisions deferred to the booth, under lights, with a room watching, get made worse than the ones you make at your desk the week before.

Mixgraph's DJ set planning guide covers the sizing math for this — how many tracks a 60, 90, or 120-minute set actually needs, and why you should prep 25–30% more than that number as a buffer. That guide stops there, at “have extras ready.” This one picks up where it leaves off: how you actually decide which of those extras earn a place in the set you play, and which ones were only ever there to make you feel prepared.

More Tracks in the Bag Means More Gaps You Haven't Checked

Every track you add to a prep pool without a plan for where it goes is a chemistry decision you are pushing to the night itself. Fifty or sixty plausible tracks sounds like flexibility. In practice it is fifty or sixty potential transitions you have not actually worked out — most of which you will never touch, and a handful of which you will reach for mid-set with no real idea whether the key bridges, whether the energy holds, whether the groove survives the blend.

That is decision fatigue, not preparation. Standing at the booth scrolling past forty tracks you “might” play, trying to work out live whether the next one actually connects to what is currently in your headphones, is a worse position than standing there with twenty tracks you have already sequenced and six backups you have already checked. A smaller, tighter pool is not a compromise on ambition. It is what preparation is supposed to produce — a set you have genuinely thought through, not a folder you never finished sorting.

The fix is not simply bringing fewer tracks and hoping for the best. It is being honest about which tracks in that big pool are doing real work in the set, and which ones are only there because you like them.

Split the Pool Into a Main Line and a Backup Line

The single biggest structural mistake in a bloated prep pool is treating it as one pile of maybes. Sixty tracks sitting in one folder, all roughly equally “in contention,” is not a plan — it is a queue with no order and no purpose. The fix is splitting it into two lists that do different jobs.

Your main line is the set you are actually going to play: somewhere around 18 to 20 tracks, sequenced, with a chosen energy shape and a genre thread running through it. This is the set on paper. Every track in it has a specific slot, specific neighbours, and a reason for being there beyond “I like it.”

Your backup line is smaller and does a completely different job — 5 to 8 tracks, each one a real alternate for a specific pivot point in the main line, not a runner-up that almost made the cut. A backup earns its place by solving a named problem: what plays if the room wants harder than you planned at minute 30, what plays if the key you were leaning on for the peak doesn't bridge cleanly on the night, what plays if you need to bring the energy down without losing the room. Two lists, two purposes. Everything else in the original pool gets cut.

The Story Test: Earning Its Spot, Not Just Proving You Own It

Before you can cull anything, you need a standard to cull against. That standard is the shape of the set itself. Mixgraph's Energy Arc Planner names five of these: a Journey (the classic warm-up-build-peak-cooldown arc), a sustained Peak that holds high energy from the first track, a Build that only moves one direction start to finish, a Steady set that holds one energy level and varies through texture instead, or a Cooldown that eases down from someone else's peak. Pick the shape before you touch the pool — naming it gives you something concrete to test every track against, instead of judging tracks on whether you like them.

Once you have the shape, run every track in the pool through the same question: does this track serve the set, or does it just prove you own it? Those are different things, and the gap between them is where most of the fat in a sixty-track pool actually lives. A track can be genuinely good — well produced, a track you are proud to have found — and still be wrong for minute 40 of this particular set. Loving a track is not the same as it earning a slot.

The cut most DJs flinch at is the ego cut: the flashy new promo, the track you just got signed off a label you admire, the one you want people to know you have. If it doesn't connect to the arc you have chosen — if it sits outside the energy block it needs to fill, or drags the genre thread somewhere the rest of the set never goes — it does not go in the main line just because you are proud of it. Save it for a set where it fits.

Three Cutting Passes, in Order

Once you have a shape to test against, cut in passes rather than trying to make every call at once. Each pass asks a different question, and doing them in order stops you from cutting a good track for the wrong reason.

Pass one: kill the weak transitions. This pass is not about whether a track is good — it is about whether its links into its neighbours hold up. Go through the pool in the rough order it would play and check the chemistry into and out of each track: harmonic movement, rhythmic feel, energy direction, groove. A track with one shaky link either side is a track you will be forcing on the night. Cut it, move it, or find it a different neighbour. You are not judging the track. You are judging the join.

Pass two: kill redundancy. With the weak joins gone, look for tracks doing identical work in the arc — two tracks at the same energy, similar tempo, similar mood, filling the same block. You do not need both. Keep the one with the stronger transitions either side and cut the other. This is usually the biggest single pass, because a sixty-track pool built up over weeks of prep is full of near-duplicates you added on different days without noticing you already had something doing the same job.

Pass three: kill the wrong-fit tracks. What is left is a pool of tracks that transition well and are not duplicating each other — and some of them will still be wrong for this specific crowd and this specific room. A track that is objectively excellent can still be the wrong call for an early slot in a small room, or too niche for a crowd that has never heard the artist. This pass is about the gig you are actually playing, not the set in the abstract.

What Actually Earns a Spot on the Backup Line

The natural instinct after three cutting passes is to keep the best of what got cut as your backup line. Resist it. Runners-up from the main-line cut are not backups — they are tracks that lost, sitting in a second pile with no more purpose than they had in the first. A real backup line is built forward from the pivots in your set, not backward from the tracks you couldn't bring yourself to delete.

Go through your sequenced main line and name the actual pivot points — the moments where the room could plausibly need something different from what you planned. A different energy direction if the floor is already ahead of you by minute 20. A different key bridge into the peak if the track you were leaning on for that transition doesn't read right on the night. A floor-read escape hatch — something lower energy and higher groove — if you overshot and need to walk it back without losing the room. Each of those is a named, specific problem. A track only belongs on the backup line if it solves one of them.

This is the same structural idea behind the way Flow Builder handles Pro slot alternatives — a backup isn't a separate playlist floating next to your set, it is attached to a specific position in the sequence, with real chemistry to the tracks either side of it. Five or six backups tied to five or six named pivots is a genuinely useful list. Fifteen tracks you liked but couldn't place is just the pile you were supposed to have cut.

Worked Example: 60 Tracks Down to a 90-Minute Peak-Time Set

Say I am playing a 90-minute peak-time slot at a club night I have played before — tech house, mostly, housier in the first 20 minutes and darker through the last third. Three weeks of pulling tracks I like into a prep pool has left me with 60.

Before I cut anything, I check the Set Length Calculator for what a 90-minute set at this pace actually needs, buffer included: roughly 26 tracks total. That is my target — not “whatever survives,” a real number I am cutting toward. Around 20 of those will be the main line, and 6 the backup line.

Pass one goes through the pool in rough play order and checks the joins. Fourteen tracks come out — not because they are bad, but because at least one link either side is shaky: a track at 128 BPM I wanted between two 124s with nothing to smooth the jump, a moody minor-key track with no clean harmonic path out of it, a groove that does not sit right against its neighbours. Pool: 60 down to 46.

Pass two looks for redundancy. Three separate tracks are doing the same job in my mid-set energy block — driving, around 126 BPM, similar mood — and I only need one. Two rolling, groove-led tracks are earmarked for the same slot in the build. Across the pool, sixteen tracks get cut because something else already does their job, with better transitions either side. Pool: 46 down to 30.

Pass three is the fit check. Four survivors are genuinely good but wrong for this room — a bootleg edit that plays better in a smaller, rowdier room than this club's main space, a track leaning deeper and more minimal than this crowd has responded to before, and two peak-time tracks I already have stronger versions of for this exact arc. They come out. Pool: 30 down to 26.

That is exactly the number the calculator said I needed. Twenty tracks get sequenced into the main line — opening, build, peak, cooldown, each one checked against its neighbours. The remaining six become the backup line, each tied to a named pivot: two energy escape hatches if the floor gets there before I do, two alternate key bridges into the peak sequence, one darker option for the last third, and one like-for-like swap for the peak itself in case the room hasn't responded to my first pick by the second track in.

Build the Cull Into Your Prep, Not Into Memory

None of this needs to live in your head, and it definitely should not live in a notes app you will not open again before you walk into the venue. The sequence in this article maps onto three tools in order: size the set with the Set Length Calculator so you know the real number you are cutting toward, pick the shape it has to serve with the Energy Arc Planner so the story test has something concrete to measure against, then do the actual cull inside Flow Builder.

Flow Builder is built around exactly the split this article argues for — a main line of sequenced slots, and up to two real Pro alternatives attached to each slot for the pivots that actually matter, with real chemistry to the tracks either side rather than floating in a separate playlist you will forget you made. Build the main line, name the pivots, attach the backups, and the split holds under lights instead of collapsing back into one pile of maybes the moment the set starts.

The cull happens before the gig. What happens after you walk in and the room tells you something your plan did not account for is a different problem — that is what Live Mode is for, pulling a backup-line pick into the set in real time based on how the floor is actually reading, rather than guessing at the booth. Preparation gets you a tight, trusted set. The room still gets the final word.