CHAPTER SEVENTEEN

The Advance

The pre-show information exchange that prevents the night’s disasters.

There’s a piece of business between booking a show and playing it that has no glamour at all and saves more nights than almost anything else in this book: the advance. To “advance” a show is to confirm all the operational details shortly before the date — the load-in time, the sound situation, the payment, the schedule, who to ask for when you pull up — so that everyone involved arrives working from the same plan. It’s the least exciting part of the whole process, a phone call or an email nobody brags about. It’s also the difference between a night that runs smoothly and one that comes apart in a dozen small, avoidable ways before you ever play a note.

The advance is not the same thing as the agreement, and it’s worth being clear about the difference. The agreement, from the last chapter, is the deal — the terms, settled at booking and ideally written down: the date, the money, the broad shape of who provides what. The advance comes later, close to the show, and it’s about turning that agreed deal into an executable plan. The agreement says you’re playing this room on this date for this money. The advance works out the hundred practical details the agreement didn’t: what time the door’s unlocked, where the band parks, whether the room’s PA covers your needs, who’s running sound, how you actually get handed the money at the end. The agreement is what; the advance is exactly how, when, and where.

And here’s the thing about the night’s disasters: almost all of them are avoidable, and almost all of them come from the same source — somebody not knowing something they needed to know. The band shows up at the wrong time to a locked door. The room expected a stage plot that never arrived. The act assumed sound the room doesn’t provide. The owner planned for three people and seven walked in. None of that is bad faith; it’s just information that never got exchanged. The advance is the exchange that prevents it, and the most important thing to understand about it is that it runs in both directions — which is where we’ll start, after a closer look at what’s actually at stake.

17.1 The Anatomy of a Preventable Disaster

To understand why the advance matters, look at what happens without it. A band books a room, settles the deal, and then — nothing, until the day of the show, when both sides discover all the things they’d quietly assumed differently. The band arrives at six expecting to load in, but the room doesn’t open until eight and nobody’s there. The PA turns out to be smaller than the band counted on, with no engineer, on a night the band left its own gear at home expecting one. The sound person, who never received an input list, has to build a mix from scratch while the clock runs toward doors. Each of these is small on its own. Together they turn a night that should have been about music into a scramble of problem-solving, and they sour everyone’s mood before the first song.

And the cost of these avoidable messes is bigger than the inconvenience of the night itself, because of what they do to the relationship. A night that comes apart in preventable ways leaves both sides frustrated and quietly blaming each other, even when nobody was really at fault — the band thinks the room was disorganized, the room thinks the band was unprepared, and a relationship that took real work to build takes a hit over information that a five-minute conversation would have exchanged. Worse, a band that walks into chaos plays a worse show, and a worse show is bad for everyone’s draw and reputation. The disasters the advance prevents aren’t just annoying; they cost money, goodwill, and the quality of the very thing people came for. There’s also a quieter cost, harder to see but just as real: every preventable problem the advance would have caught eats time and attention that should have gone into the show. The hour a band spends untangling a load-in mix-up is an hour it doesn’t spend warming up, dialing in its sound, or settling its nerves. Chaos doesn’t just feel bad; it actively steals from the performance, and the crowd, who knows none of it, still somehow feels the difference.

This circuit needs the advance more than most, precisely because of the informal, handshake culture we just spent a chapter praising. When deals are done warmly and casually, it’s easy to assume the details will sort themselves out, and easy to feel that nailing them down is fussy or distrustful. But informality is exactly what lets details slip through the cracks — the more relaxed the booking, the more got assumed rather than confirmed. The advance is how you keep the warmth of a handshake world without paying for it in chaos. It doesn’t make the relationship more formal; it just makes sure the easygoing trust you’re operating on is backed by everyone actually knowing the plan. Done right, the advance is the most professional thing a casual booking has going for it.

17.2 The Two-Way Document

The single most important thing to understand about the advance is that it is a two-way exchange, not a one-way interrogation. It’s tempting for a band to think of advancing as a list of questions to fire at the room — what time, where do we park, what’s the PA — as if the goal were to extract information from a reluctant venue. And it’s just as tempting for a room to think of it as a list of instructions to issue to the band. Both of those are half the picture, and a half-done advance causes its own disasters. The truth is that each side holds information the other genuinely needs, and the advance only works when it flows in both directions: the band telling the room what the room needs to know, and the room telling the band what the band needs to know.

Think about where the necessary information actually lives. Only the room knows the real load-in time, the parking situation, what the PA actually is, who’s running sound, how the payment gets handed over, and what the house rules are. The band can’t find any of that out by guessing — it has to come from the room. And only the band knows how many inputs it needs, what it’s bringing versus what it needs provided, how many people are in the party, when it’ll really arrive, and what it needs in order to play well. The room can’t prepare for any of that without being told. Neither side can plan the night alone, because neither side holds all the pieces. The advance is simply the two sides putting their pieces on the same table. This is also why an advance led by only one side tends to leave gaps. A band that fires off its questions but never volunteers its own information gets a room ready to receive a mystery; a room that issues its instructions but never asks gets a band it can’t actually accommodate. The completeness comes from both parties treating it as their job to give as much as to get — to hand over their own pieces, not just collect the other side’s.

In bigger operations this two-way exchange is captured in an actual document — an advance sheet, increasingly a shared file, that lays out both sides’ information in one place. On most of this circuit it’s less formal than that: a phone call, an email thread, a few texts in the days before the show. The form doesn’t matter; the completeness and the two-directionality do. What matters is that by the time the band pulls up, both sides have answered the other’s questions and nobody’s working from an assumption. And when the advance does turn up a problem — a mismatch in what each side remembers the deal to be, or a thing the room promised that it turns out it can’t actually provide — that discovery is the advance doing its job, not a crisis. A remembered-deal dispute is exactly what the written agreement from the last chapter is for. A can’t-provide problem is a calm conversation to have right then, days out, while there’s still time to solve it, rather than a fight at the loading dock with the clock running. Approached in the right spirit, the advance isn’t an interrogation or a set of orders — it’s two professionals comparing notes to make sure they’re about to put on the same show. The next two sections lay out the two directions in turn: what the room owes the band, and what the band owes the room.

17.3 What the Room Owes the Artist

Start with what the room must tell the artist, because the band literally cannot plan its day without it. First, the schedule, in real detail: not just “the show’s Friday,” but the actual load-in time, when soundcheck happens, when doors open, when the band goes on, how long it plays, and when the night has to end. Second, access and logistics: where to load in, where the band can park, which door to come to and whether it’ll be unlocked, and — the single most useful piece of information a room can give — the name and cell number of the person who’ll actually be there when the band arrives. A band that knows who to call when it pulls up to a dark building has been spared the most common load-in disaster there is.

Next, and critically, the sound situation, because this is where the biggest day-of surprises happen. The room needs to tell the band exactly what it provides: is there a full PA, and monitors? Is there a sound engineer, or is the band running sound itself? Is there any backline — a drum kit, amps — or is the band bringing everything? Vague answers here are how a band ends up with the wrong gear or no way to be heard, so the room owes the band specifics, not “we’ve got sound, you’re fine.” This information lets the band show up with exactly what’s needed and nothing missing, and it sets up the soundcheck — which gets its own chapter in the night ahead — to go smoothly instead of becoming a frantic guessing game. The same goes for power and stage size, easy to forget until they bite: how many outlets there are and where, how big the playing area is, whether there’s room for the whole band and its gear. A five-piece that arrives to a stage built for a solo act, or a setup that trips the room’s breakers mid-song, is living proof that the dull questions are the ones most worth asking.

Finally, the room owes the band clarity on two more things. The payment logistics: confirming the agreed money, yes, but also how it’ll be paid — cash or check — who physically hands it over, and at what point in the night, so there’s no awkward hunting for the owner at the end. We’ll get to the settle itself later; the advance is where its mechanics get set so it runs smooth. And the house information: where the green room is if there is one, where to set up merch and whether the room takes a cut, what the hospitality is — its own subject in the very next chapter — and any house rules the band should know. A room that volunteers all of this proactively marks itself as professional and easy to play, and spares itself a night of answering the same questions in a panic at load-in.

17.4 What the Artist Owes the Room

Now the direction bands most often neglect, because they think of the advance as being about what they get rather than what they owe: the information the room needs from them. First and most important, the technical needs — the stage plot and the input list. The stage plot is a simple diagram of where everyone stands and what they need; the input list tells the sound person how many channels the band uses and what plugs into each. Sent ahead of time, these let the engineer set up before the band even arrives, which is the whole difference between a fast, easy soundcheck and a long, stressful one. A band that emails its input list a few days out marks itself instantly as professional, and a band that shows up with its tech needs a mystery makes an enemy of the one person who controls how it sounds.

Beyond the tech, the room needs the practical shape of what’s coming. How many people are in the party — band plus crew — so the room can plan hospitality, space, and the guest list. What the band is bringing versus what it needs from the room, the mirror image of the sound conversation, so nothing’s doubled up or missing. On a multi-act night this part of the advance grows a whole dimension, because the bill shares gear and a stage. Who’s providing the backline everyone uses — the drums, the amps — and what each act brings versus borrows has to be settled ahead of time, along with the order of play and how the changeovers will run, so the night flows instead of stalling between sets. When the band will actually arrive, so somebody’s there to meet it. The guest list — who the band needs admitted, and how many. Any genuine special needs, kept reasonable. None of this is about making demands; it’s about letting the room prepare, so the band’s arrival is something the room is ready for rather than something it has to scramble to absorb. The clearer the band is about its own needs, the better the room can actually meet them.

It’s worth seeing that providing this information isn’t a courtesy the band does for the room — it’s pure self-interest, because everything the band tells the room ahead of time is something that goes right on the night instead of wrong. Tell the room your input list, and soundcheck is smooth. Tell it your party size, and the hospitality and the guest list are sorted. Tell it your arrival time, and someone’s there to let you in. Every piece of information the band volunteers is a problem that doesn’t happen. And the band that advances its own needs clearly earns the most valuable operational reputation there is — easy to host — which is exactly the reputation that gets a band re-booked by rooms that have learned the hard way how rare it is. Telling the room what it needs to know is how you guarantee your own good night. And there’s a trust dividend in it, too. A band that consistently tells the room what it needs, accurately and ahead of time, teaches the room that its word can be relied on — that when this band says it needs four inputs and brings four people, four inputs and four people are exactly what show up. That reliability, built one honest advance at a time, is the foundation that the entire back half of this book rests on.

17.5 Timing, Tone, and the Handoff to the Night

Two practical questions remain: when to advance, and how. Timing first. The advance shouldn’t happen at booking — that’s too early, weeks or months out, when plans are still soft and details will change. And it absolutely shouldn’t happen on the day of the show, when it’s too late to fix anything that’s wrong. The sweet spot is the window before the show — for most gigs, the week or several days ahead — when the plan is firm enough to confirm but there’s still time to solve any problem the advance surfaces. That timing is the whole point: you advance early enough that discovering the PA won’t work, or that the load-in time clashes with something, leaves room to fix it rather than just to panic about it. A good advance is early enough to be useful and late enough to be accurate. It also helps to advance against a short, repeatable checklist rather than from memory, so the same detail doesn’t get forgotten every time. The specifics change from gig to gig, but the categories don’t — schedule, access, sound, payment, party, tech — and running down that same short list every time is how the easy things stop slipping through precisely because they seemed too easy to bother confirming. None of this rules out a quick day-of touch — a one-line “still on for tonight, see you at six” that isn’t a second advance but simply catches the rare last-minute change before it turns into a wasted two-hour drive. The full advance happens days out; the day-of note is just a final glance to confirm nothing moved.

How you advance matters as much as when. Do it warmly and professionally, as a friendly “let’s make sure we’re all set for Friday,” never as an interrogation or a barrage of demands — the same right-sizing logic from the agreement chapter applies here. A big, complex production needs a detailed, thorough advance; a routine local gig with a room you know might need nothing more than a five-minute call to confirm the handful of things that matter. On a handshake circuit, plenty of advancing happens in exactly that form — a quick, easy call between two people who trust each other, just making sure they’re on the same page about Friday. The point isn’t formality. It’s that the conversation happens at all, sized to fit the gig, in a tone that makes it one more easy exchange between partners.

Whoever handles the band’s business — often the same person who books and manages, as we saw a few chapters back — is usually the one who advances, talking to the room’s point person to line everything up. And when it’s done well, something quietly wonderful happens: the band pulls up Friday to an unlocked door, a sound person who already has the input list, parking sorted, the money plan clear, and everyone working from the same plan — so the night gets to be about the music instead of about solving preventable problems. That’s the whole gift of the advance. It’s the last act of the booking and the first act of the night, the unglamorous phone call that clears the way for everything that follows. One of the things the advance confirms is the hospitality — what the room feeds you, where you wait, where you sleep if it’s a travel night — and what’s reasonable to ask and to provide there is a subject all its own. That’s next.