The morning after a good show, all most venues have is a feeling: that one felt busy. But "felt busy" doesn't rebook the act, doesn't help you hold the line on a bar minimum, and doesn't tell you what to program next month. Three weeks later the details are gone, and you're making your next booking on a vibe you half-remember.
A recap fixes that, but only if it's built to be used — not a diary of the night, a tool for the next one. This is a post-show recap template for live music venues that captures the handful of things that actually make your following show better, plus the one section most rooms never fill in.
The short version
- A recap is a booking and programming tool, not a scrapbook. Only capture what changes a future decision.
- Six things matter: turnout, spend, participation and demand, revenue moments, what worked operationally, and the one call it changes.
- The demand data is the part you're probably missing — what the room asked for, including what never got played. It's what makes your next booking smart instead of hopeful.
- Write it the same night. A template you fill in beats a blank page you keep meaning to start.
The six sections that earn their place
Everything else is optional. These six are the ones that pay you back the next time you book, price, or program. Here's what goes in each and why it's worth the two minutes.
| Section | What to record | Why it matters |
|---|---|---|
| The basics | Act, date, room, doors-to-close, headcount | Anchors every other number to a specific night |
| Spend | Bar/food total, per-head average, comps | Tells you if a busy room was actually a profitable one |
| Participation & demand | How many took part, unique people, what they requested | The clearest read on what your crowd came for |
| Revenue moments | Cover, boosts, merch cut, sponsorship | Separates nights that drew from nights that earned |
| Ops notes | What ran smooth, what jammed, staffing read | So the same problem doesn't repeat next month |
| The one decision | Rebook? Reprice? Reprogram? One line. | A recap with no decision is just a receipt |
The trap is treating all six as equally easy to fill. Five of them you can reconstruct from the register and your memory. The third one — participation and demand — is the one venues skip, because there's usually no way to capture it. That's a shame, because it's the most useful section on the page.
The template you can copy tonight
Paste this into your notes app or a shared doc and fill it in before you leave. Keep it short. A recap you'll actually finish beats a thorough one you won't.
SHOW RECAP — [Act] — [Date]
BASICS
- Room / capacity:
- Doors → close:
- Headcount (est.):
SPEND
- Bar + food total:
- Per-head average:
- Comps / promo:
PARTICIPATION & DEMAND
- People who took part:
- Unique participants:
- Top requests (played):
- Top requests (NOT played — the gap):
- Off-catalog asks worth noting:
REVENUE MOMENTS
- Cover / tickets:
- Boosts / add-ons:
- Merch / sponsorship:
OPS NOTES
- Ran smooth:
- Jammed / fix next time:
- Staffing read:
THE ONE DECISION
- Rebook / reprice / reprogram? One line:That "top requests NOT played" line is the sleeper. It's the room telling you, in its own words, what it wanted that it didn't get — the single best input you have for what to book, program, or add next time.
The section that's hard to fill — and how it fills itself
Five sections you can do from memory and the register. The participation-and-demand section is the one with no obvious source, which is exactly why most venues leave it blank and keep booking on instinct.
It's also the section a fan request moment fills automatically. When fans request songs through a setup your staff controls, the system captures all of it — and the morning-after recap hands you that section done: total requests, unique people, what got surfaced versus held, and demand for songs that were never even in the set.
This is where CueTonight turns a show into data you can book against. Two real recaps show what a filled-in participation section looks like. At a Slick Rick show at The House of Independents in New Jersey, the recap logged 588 requests from 412 unique people in a twelve-minute window, with a clear split between what the team surfaced and what it held for pacing — the difference between raw demand and the approved reveal, on the page. And a Juneteenth Eve night at Elsewhere in Brooklyn fills the revenue line too: roughly 2.5K requests, and on the venue side about $2.2K in boosts across some 320 paid boosts that night — one example of what the "revenue moments" section can hold when the room earns from the moment.
Fill those sections show after show and the recap stops being a receipt. It becomes a pattern: which acts, which nights, which sounds actually move your crowd — and what they keep asking for that you haven't given them yet.
FAQ
What should a live music venue include in a post-show recap?
Six things: the basics (act, date, headcount), spend (bar total and per-head), participation and demand (how many took part and what they wanted), revenue moments (cover, boosts, merch), ops notes (what ran smooth or jammed), and the one decision the night points to. Skip anything that doesn't change a future booking, pricing, or programming call.
How do you measure whether a show was successful?
By the numbers that predict the next one, not the size of the crowd. A packed room that barely spent isn't a win; a smaller room with high per-head spend and strong participation might be. Track headcount against bar spend, participation, and revenue moments together — a busy night and a profitable night are not the same thing.
How often should a venue write show recaps?
Every show, same night, while it's fresh — that's why a fill-in template matters more than a detailed one. The value is in the pattern across nights, not any single recap. Two minutes per show compounds into a real read on your calendar; a recap you write "when you get to it" never gets written.
What's the one number most venues forget to track?
Demand for the songs the room wanted but didn't get. Turnout and spend are easy; what the crowd was actually hungry for is the input almost nobody captures — and it's the one that tells you what to book and program next. If your recap has a "requested but not played" line, you're already ahead of most rooms.
The bottom line
The difference between a venue that guesses and one that programs on purpose is a two-minute habit: capture the six things that matter, same night, in a template you'll actually finish. Most of it you can pull from the register and your memory. The demand section — what the room asked for and what it didn't get — is the one worth setting up to capture automatically, because it's the one that makes every future booking smarter.
If you want that section to fill itself — participation, surfaced-versus-held, and demand data handed to you the morning after — see how CueTonight runs for a venue.