Building a Setlist That Actually Fits Your Time Slot

A venue gives you a 45-minute slot starting at 8:00 PM. You draft a ten-song setlist, eyeball the song lengths, and it looks close enough. It isn't — and the gap between songs, the few seconds of tuning, count-ins, and stage banter that happen between every pair of tracks, is almost always the part that gets forgotten in the eyeball estimate, precisely because no single gap feels like it should matter on its own. Running the same setlist through this site's Setlist Timer, which sums real per-song durations plus a fixed gap and can project the whole thing onto an actual clock, turns that vague sense of “probably fine” into an exact number.

The math behind a setlist's real length

A setlist's total time is every song's duration, plus a gap for every transition between songs (one fewer gap than the number of songs, since there's no gap after the last one). Given a start time, the same calculation can also produce a running clock time for exactly when each song begins and ends — useful for coordinating with a sound engineer, a stage manager, or a support act waiting to go on next. That's precisely what computeSetlist() does: sum the songs and gaps into a total, and, if you give it a start clock, walk that total forward one song at a time into real start and end times.

A worked ten-song set

Here's an actual band's draft set, run through the tool with a 45-second gap between songs and an 8:00 PM (20:00) start:

Total runtime: 48 minutes 45 seconds, ending at 8:48 PM against an 8:45 PM slot end — three minutes and forty-five seconds over. On paper, adding up just the ten song lengths might have looked close enough to the 45-minute target to wave through; run against nine real 45-second gaps as well, the set is meaningfully over.

Two honest ways to fix it

The obvious fix is cutting a song. Dropping “The Long Way Back” and rerunning the same nine songs at the same 45-second gap brings the total down to 42 minutes 20 seconds, ending at 8:42 — comfortably inside the slot, but now with almost three unused minutes and one fewer song played. The less obvious fix: keep all ten songs and tighten the gap between them instead. Cutting the gap from 45 seconds down to 20 — a genuinely achievable target with practiced between-song transitions — brings the exact same ten-song set in at precisely 45 minutes 0 seconds, ending at 8:45 PM on the dot. Neither fix is automatically correct: cutting a song is simpler and safer if your transitions are genuinely slow, while tightening the gap keeps every song you wanted to play but demands real discipline on stage to actually hit that shorter changeover every time.

Why the gap matters more than it looks like it should

Nine gaps at 45 seconds each add up to 6 minutes 45 seconds of pure transition time inside a 45-minute set — 15% of the entire slot spent not playing music. That's the real reason a setlist that looks fine song-by-song can run so far over: the gaps aren't a rounding error, they're a substantial fraction of the total, and they scale with how many songs are on the list, not with how long the set is supposed to run. A setlist with more, shorter songs pays this tax more heavily than one with fewer, longer songs covering the same total playing time, purely because more songs means more transitions. This is worth factoring in at the setlist-building stage, not discovering after a soundcheck runs long, and it's exactly the kind of hidden cost that a quick manual add-up of song lengths reliably misses, because nobody sits down and separately tallies nine small gaps the way a calculation does automatically.

Sequencing is a separate decision from timing

Fitting a time slot and building a good running order are two different problems that happen to share the same setlist, and it's worth solving them somewhat separately. A common energy shape opens with a strong, immediately engaging song to win the room over quickly, saves the highest-energy or most anticipated material for the back third, and places at least one deliberate change of pace — a slower song, a stripped-down arrangement — somewhere in the middle so the whole set doesn't run at one unbroken intensity. Once you have a running order that makes emotional sense, the timing calculation is what tells you whether that specific order, at those specific song lengths, actually fits — and if it doesn't, you can often solve a timing problem by cutting or swapping a song without disturbing the shape of the set, rather than reshuffling everything from scratch.

Encores need to be planned separately from the slot

An encore is easy to leave out of the timing math entirely, and that's usually the right call — treat the core setlist as the thing that has to fit the contracted slot, and plan any encore as bonus material contingent on the crowd and the schedule actually allowing it, rather than baking it into the same fixed-duration calculation. If a venue's schedule is genuinely tight with another act following immediately, it's worth deciding in advance, before you're on stage in the moment, whether an encore is realistically available at all; nothing strains a tightly-run schedule like a spontaneous encore that wasn't accounted for anywhere in the planning.

Gaps aren't always uniform in real life

The setlist calculation here uses one fixed gap length between every song, which is a reasonable simplification but not always literally true — swapping from acoustic guitar to electric takes longer than nothing at all, and a song requiring a full retune eats more transition time than one that doesn't. In practice, the fixed-gap version of the calculation works best as a planning average: set the gap to whatever your slowest realistic transition actually takes, and any faster transition just becomes a small buffer against the next one running long. If one specific transition is a genuine outlier — a costume change, a full reset of the stage — it's more accurate to fold that specific extra time directly into the preceding song's listed duration for planning purposes, rather than distorting the gap figure for every other transition in the set.

Build in a buffer, don't cut it to the second

Landing a setlist at exactly 45:00 against a 45-minute slot, as the tightened-gap version above does, is a satisfying number but a risky plan in practice — it assumes every single transition goes exactly as fast as planned, with no broken string, no monitor issue, no extra bar of a count-in. A safer target is planning to a total a minute or two under the actual slot, so that ordinary small delays don't push the last song past the hard stop a venue or a following act needs. If the tool's total comes out suspiciously exact, that's usually a sign to either trim slightly further or plan explicitly for which song gets cut first if time runs short, rather than assuming the plan will execute perfectly.

A real clock time is more useful than a total

A bare total duration answers “how long is this set,” but a start-clock projection answers a more useful question for actually playing the show: what time does each specific song start. That's valuable well beyond satisfying curiosity — a sound engineer riding a specific song's levels, a videographer timing a shot list, or a co-headliner who needs to know exactly when to start getting their own gear ready all benefit from knowing real clock times, not just a running total. Feeding a start time into the setlist calculation, rather than only tracking a duration, turns the setlist into a genuine schedule other people on the show can plan around.

Plan your own set against the clock

The Setlist Timer runs this exact calculation for any set of songs, any gap length, and any start time you enter, producing both a total and a full per-song clock schedule. If your set is built around a specific arrangement's bar count rather than a fixed song length, How Long Is a Chorus, Really? covers the tempo-and-bars math that determines how long each individual song actually runs in the first place, and the Song Structure & BPM Reference has common section lengths pre-computed across a range of tempos if you're still drafting the songs themselves.