The room is the only honest feedback a DJ gets, and it disappears by Thursday. Here is the ten-minute log that turns a night into something you can plan from.
The set ends, you load out, and you get home at four in the morning. By Thursday you can remember two tracks, one mistake, and the general feeling that it went well.
That's the problem. A DJ improves by comparing what was planned with what actually happened, and the second half of that comparison is gone within a week. The room is the only honest feedback you'll ever get, and it's the only feedback that leaves no record.
This is the third piece in the Journal. The first covered how to plan a set and the second covered moving between keys. Both produce a plan. This one is about what happens after the plan meets the floor.
The Takeaway
- The room is your only real feedback, and it is unrecoverable after a few days. Write it down the same night.
- Seven fields and ten minutes is enough. A log is a record, not an essay.
- Field two matters most: where you planned the peak against where the night actually peaked.
- After a season of logs, your recurring mistakes become visible as numbers instead of feelings.
Why the night is gone by Thursday
Memory does not work like a recording. It rebuilds an event each time you recall it, and the rebuild drifts toward what you already believe about yourself as a DJ.
Two things follow from that. The detail decays quickly without something to reinforce it, which is the effect Ebbinghaus described for retention over time (Forgetting curve, Wikipedia, retrieved 2026-09-24). And what survives is shaped by expectation. A DJ who believes they always lose the room late will remember losing it, whether or not it happened (Recall (memory), Wikipedia, retrieved 2026-09-24).
That second effect is the dangerous one. A log written an hour after the gig is a measurement. A memory recalled a month later is a story — and the story is told by the DJ who wants to look consistent.
What to write down
A gig log is a record of one night, written the same evening, in seven fields. It isn't a review of your performance and it's not a tracklist. It is the other half of a plan.
Seven fields — and none of them ask for prose.
- Venue and slot. Where, and how late in the night. The same set behaves differently at eleven and at two.
- Planned peak against actual peak. Where you intended the high point, and where the floor actually gave you one.
- The track that carried the room. Name it, so you can find it again in six months.
- The transitions that worked. Pairs, not single tracks, because a transition is a relationship.
- The transitions that failed. And what they cost you, which is usually a few minutes of floor.
- What the room did. Emptied, held, filled. Raw observation only.
- One change for next time. The whole point of the exercise.
Most of a log is a sentence or less per field. If you're writing paragraphs, you're writing a diary.
The ten-minute rule
The ten-minute rule is this: the log is written before you sleep on the night of the gig.
So why write it then, rather than the next morning? Because the useful details are still attached to each other.
An hour after the gig you can still say which transition emptied the floor. A week later you can only say that something did. The link between cause and effect is the first thing to go, and it is the only part worth keeping.
Two honest exceptions. If the gig ran until dawn, log it before you sleep rather than after. And if you're on a run of nights, log the one you just finished on the drive home, in voice notes, and tidy it the next morning.
Field two is the one that changes everything
Here is where a log stops being a habit and starts being a tool.
Almost every DJ knows roughly how a night felt. Very few know where the peak actually landed, as a share of the set. That number is what turns a feeling into a fact.
Once you have that gap across ten gigs, it usually says something specific. For example, a peak that consistently arrives twenty minutes early is not a mixing problem and not a music problem. It's a peak timing problem, and peak timing is the first field in the next Set Brief.
That's the loop the Journal keeps coming back to. The gig teaches the brief, and the brief shapes the next gig.
What a season of logs looks like
Single logs are stories. Twenty logs are a dataset, and a dataset has no interest in your self-image.
Three patterns show up quickly in most logs:
- A systematic timing error. The peak lands early or late, and it lands the same way every time.
- A recurring weak window. A stretch of the night that sags on almost every date, usually two-thirds in.
- A handful of skipped tracks. Music that fits your sets on paper and never gets played. For example, a track that needs a long blend will be skipped all night if your route never offers one.
None of those are visible in a single night. All three are obvious across twenty.
Forgotten Gems: the tracks you keep skipping
Field note: Watching our own logs, the skip pattern was the most surprising find. The tracks being ignored were rarely the weak ones. They were the ones that never had an obvious slot.
The third pattern deserves its own page. Most DJs have a shelf of tracks that suit their sound, survive every transition check, and never make it into the booth.
That's not a taste problem. It's a routing problem. A track gets skipped because it never quite fits the position you are in when you think of it. Without a record, you never notice the skipping is happening at all.
Forgotten Gems is the list of tracks your own logs show you skipped — music that fits your sets on paper and never reaches the booth. It's part of Pro, alongside Gig Log, because both read from the same record.
| What the gap shows | What it usually means | What to change in the plan |
|---|---|---|
| Peak lands early, every time | The build is shorter than the brief assumes | Move the peak later and add one step to the build |
| Peak lands late, every time | Too much time spent holding the middle | Trim the middle section by two tracks |
| The last twenty minutes sag | The resolution was never planned | Give the ending an intention before the night |
| The same transition fails twice | A genuine incompatibility | Re-route it, or separate those two tracks for good |
| The room holds but never lifts | Energy is flat across the set | Raise the peak and lower the opening |
Why this beats buying more music
A bigger library feels like progress — it's measurable, and it's pleasant. It's also motion without direction.
A log gives you the other half of the loop. You already know what you intended, because you wrote a brief. So what did the room actually do with it? The log is the only place that answer exists. Between those two documents, improvement stops being a matter of taste and becomes a matter of arithmetic.
Start the loop
You do not need a new workflow. You need ten minutes on the night, every time.
SPIRAL DJ is free to start. The free plan covers up to 500 tracks, with local analysis of BPM, key and energy, plus Genre DNA classification and Crate Digger with reasons. It includes the Set Plan, Set Canvas and Set Architect, Auto Flow, Routes, Set Check and a JSON backup. Gig Log and Forgotten Gems sit in Pro, together with the professional exports, the printable booth sheet and an unlimited library.
No card is required, and your music never leaves your machine. The privacy page explains how local analysis works, and the terms cover everything else.
Start free with SPIRAL DJ — 500 tracks, no card, everything local.
Frequently asked questions
How long should a gig log be?
Ten minutes is plenty. Seven fields, a sentence each, and one sentence about the change you would make. If it takes longer than that, you are writing an essay rather than a record.
Do I need to log every gig?
No, but the patterns only appear if you log most of them. Start with the sets that mattered, then add the ordinary ones, because the ordinary nights are where a systematic habit hides.
What if the night went badly?
Log it anyway, and especially then. A bad night recorded is the most useful document you own, because it tells you which field of the brief was wrong. A bad night remembered only becomes a mood.
Is the Gig Log part of the free plan?
No. Gig Log and Forgotten Gems are part of Pro, alongside the professional exports and the printable booth sheet. The free plan keeps a JSON backup of everything you build, so the plan itself is never lost.
What to do after your next set
Before you sleep, write seven lines. Where you played. Where the peak landed against where you planned it. The track that carried the room. The transitions that worked and failed. What the room did. And one change.
Do that for a season and you will know more about your own sets than any amount of new music can teach you. The room told you the answer. The log is how you hear it again.
Editorial note: This guide is written and maintained by the SPIRAL DJ team, the same people who build the app. For corrections or questions, contact
info@spiraldj.com. More about us, and everything else in the Journal, is at the Spiral Journal.
Test setup: this workflow mirrors how the app behaves. The free plan covers up to 500 tracks and every stage through Set Check. The professional exports, the printable booth sheet, Gig Log and Forgotten Gems sit in Pro.