Before The Show Begins

Chapter 1. The Venue and the Rider: Where an Idea First Meets Reality

The most useful thing an empty venue does is strip away our illusions. On a render, everything is usually beautiful: lines are clean, the screen hangs perfectly, fixtures point exactly where they should, and for some reason nobody is ever standing in an aisle. In real life, the first things you find are a door ten centimeters narrower than the case, a ceiling beam in precisely the wrong place, and a venue representative who calmly says, 'You can't rig from that.' That is where the real profession begins.

I stopped thinking of this as a fight against circumstances a long time ago. A venue does not owe our presentation anything. It existed before us and will exist after us. Our job is to finish the conversation between the idea and reality so that, by evening, nobody can see how many compromises were required in the morning. Sometimes it feels like architecture. Sometimes diplomacy. Sometimes a multimillion-dollar game of Tetris. An empty room is one of the most honest spaces in the entertainment business. There is no applause yet, no expectation, no status attached to the artist, no magic of light. None of the social energy that will later make an ordinary black riser feel like the center of the world. There are only architecture, physics, and constraints.

A first site walk very quickly becomes a conversation about specifics: ceiling height and point loads, power, evacuation routes, truck access, door widths, stage access, noise restrictions, and curfews. Then your eye moves to the FOH position, whether delay lines are possible, which seats may have to be killed, where the LED can go, and where the fire lanes run. And near the end, almost inevitably, you discover that the only suitable room for the technical racks is locked and the key belongs to someone nobody has seen all morning. This is where the presentation ends and production begins.

In a visualization, a stage can float in mid-air. In a real building, it has to be supported by something. In a promo film, a lighting fixture can be placed anywhere. At the venue, that exact point may contain a sprinkler, ductwork, a ladder, a VIP route, or a structure you are forbidden to rig from. Good production begins with respect for reality. That sounds obvious until you see how many projects are built in the opposite order: first someone invents the effect, then the team tries to negotiate with the laws of physics. Professional logic works the other way. It does not kill creativity; it gives creativity a form it can survive in. Almost anything can be done if you understand early enough what needs to be done, why it matters, and what it will cost.

A site visit is not a walk through the future venue. It is the moment when the idea first meets infrastructure. An experienced person reads a room differently from an audience member. The audience sees a stage. The engineer sees signal paths. The rigger sees load. The lighting designer sees angles. The video engineer sees sightlines and viewing distances. The production manager sees time. Security sees human flow. The promoter sees sellable seats. The venue manager sees what must not be damaged. And all of them are right at the same time. That is the first difficulty of concert production: there is no single reality. There are several systems laid on top of one another.

The creative system says, 'We need a bigger screen.' The building says the weight cannot be flown here. Finance reminds everyone that a ground-support structure is not in the budget. Operations needs load-in completed by four. Safety quietly closes an access route that somebody has already used in a beautiful render. The job of a strong production team is not to choose a winner. It is to build a solution in which every system remains functional. Professionalism rarely looks like heroism.

When I was starting out, I thought the strongest specialist was the one who could rescue a problem faster than anyone else once it had already happened. Over the years, my view has almost reversed. The most expensive professional luxury is arranging things so that nobody needs rescuing. Heroism looks excellent in a story and rather poor in a production schedule. Heroics begin where the plan has already failed. Real mastery often looks boring: arrive early, measure, ask, check the paperwork, get the load table, verify power, photograph access, open old drawings, call someone who has worked in the building before, and discover the problem three weeks before the event. None of that is spectacular. It is also exactly how shows are saved.

The Stage as a Temporary State

During a large event, a venue develops something close to its own form of government. There is territory. There are access zones. Department heads. Hierarchy. A language. Temporary rules for movement, safety, and decision-making. Some people can enter a certain door and others cannot. Some objects cannot be moved without permission. Hundreds of actions answer to one schedule. For one day, a temporary state appears and exists until the last case leaves the building. And the larger the event, the less important the equipment becomes compared with the structure of authority - who is allowed to make which decision. You can buy the best systems in the world and still lose because nobody knows who approves a change. You can have a merely adequate equipment package and deliver an extraordinarily difficult show if responsibility is clear.

An empty room makes this especially visible. Before anyone comes in, the truth is obvious: a show is not a collection of things. It is a set of relationships between people, space, time, and technology. At night, the audience sees the picture. In the morning, production sees the system.

A Rider Is Not a Shopping List

Technical riders are often read too literally. If the document names a console, find that console. If it specifies a microphone, order that microphone. If it asks for eight monitor mixes, provide eight. If it includes a stage plot, reproduce the plot. That approach works until the first situation that does not fit the template. A good rider is not an inventory list. It describes the conditions under which the artist's team believes the show can be reproduced predictably. The distinction matters.

I used to read riders almost like a procurement sheet: there is a line item, so that line item must be closed. Eventually I realized that the more important question is what problem that line is trying to prevent. Once you understand that, the negotiation stops being an argument over brands and becomes a conversation about outcome. Sometimes, admittedly, you learn this lesson standing next to an open road case and a very unhappy member of the touring crew - an excellent, if expensive, form of education. If you understand the purpose behind a requirement, you can discuss an equivalent professionally. If all you see is the model name, every deviation becomes an argument.

Suppose a touring engineer asks for a particular console family. The reason may have nothing to do with that model sounding objectively superior. They may have a show file, scenes, plug-ins, a familiar automation workflow, and a short soundcheck. Replacing it with a 'console of equivalent class' may look reasonable on paper while creating a production risk: the engineer now has to rebuild a workflow on show day. Or the artist may request a specific wireless system. That may be about the capsule, familiarity, coordination parameters, or compatibility with a touring rack. You cannot know until you ask the right question. A strong advance starts with a simple question: 'What is this requirement actually protecting?' Not because every line should become a negotiation. Because you need to understand the architecture of risk.

Hard Requirements and Preferences

Most riders contain requirements of very different kinds. Some are genuinely hard requirements: safety, input count, required power, physical stage dimensions, frequency compatibility, protocols, timecode, specific playback elements, or show-control components. Others are preferences. Some are historical residue: a document copied from tour to tour long after the show itself changed. Some are insurance. Some are simply a way of making sure the local provider does not arrive with an underpowered system. An experienced technical manager should be able to tell the difference - but not unilaterally. The key principle is approval.

If the exact requested item is not available, the question is not, 'Can we give you something similar?' It is: 'We propose this equivalent. Here are the specifications. Here is how it covers your requirement. Please confirm.' A large part of professional culture fits inside that short procedure. Bad production hides a substitution and hopes nobody notices. Average production asks permission without understanding what it is proposing. Good production proposes a solution and explains why it is equivalent in the context of that particular show.

The Rider as a Test of Understanding: The Brown M&M's Story

Some stories in the concert business are so good that the retelling gradually strips away their original meaning. Van Halen's brown M&M's are one of them. For decades, the clause was repeated as proof of rock-star excess: as if stages, amplifiers, and limousines were not enough, the band demanded that someone sort candy by hand.

The truth is more useful than the joke. David Lee Roth, and later Alex Van Halen, explained that the odd request served as a quick indicator of how carefully the promoter had read the rider. The document contained serious technical and safety requirements. If the promoter missed a bright, easy-to-check detail about candy, the touring team had reason to wonder whether the same person had skimmed the sections on power, staging, or load limits.90

The lesson, obviously, is not that every artist now needs a color-coded confectionery audit. I would almost argue the opposite: if you have to hide a trap in the rider to test a partner, trust is already imperfect. But I understand the logic. A document does not matter because it exists. What matters is whether the process can detect that the document was not understood.

I have heard the phrase 'We received the rider' more times than I can count, and it is usually true. The file did arrive by email. Sometimes somebody even downloaded it. But between received and understood, between understood and confirmed, between confirmed and delivered, there is an entire profession. It becomes especially funny when ten people at the venue confidently say, 'Yes, yes, that was in the rider,' and every one of them means a different file. Moments like that teach you that a PDF is not a management system. It is simply a very calm witness to the fact that, at some point, somebody wrote something down.

A rider is not an English-language exam and not a competition in page count. It is an agreement about the future reality of the show. If the artist's manager, the promoter, the venue, and the supplier can read the same line four different ways, the problem already exists. It simply has not been plugged into power yet.90

The Rider as a Negotiation of Trust

There is another function of the rider that is rarely stated directly. It tests how much the touring team can trust the local side. When a touring party sends a document, they do not know who will be standing in a venue in another country. The paperwork becomes a proxy for experience. The less trust there is, the more detailed the language tends to become. A good advance changes the relationship before the artist even arrives. Replies are fast. Deviations are declared honestly. Drawings make sense. The patch is confirmed. An RF plan exists. The contact sheet is current. If something is unavailable, everyone knows in advance. By the time the touring team arrives, they already know that the people on the other side of the email read more than equipment model numbers. In live events, trust is usually built before people meet in person. And it can be destroyed before then too.

One email saying 'everything will be fine' instead of answering a concrete question can tell you more about a production company than ten pages of corporate presentation.