Advancing a Show

Advancing a show means turning the agreement to perform into a shared, current plan that the artist, venue, promoter, production team, and engineers can actually use. The advance should answer five questions before anyone arrives: when does each part of the day happen, who owns each decision, what equipment and space are required, how will people and information move through the venue, and what happens if conditions change?

A strong advance is not a test of whether you know every technical term. It is a reliable handoff. The artist should be able to arrive knowing where to go and what to bring. The venue should know what it must provide and when. The engineer should have usable technical information rather than having to reconstruct the show from memory. The promoter should know which promises need confirmation. Everyone should know who can make a decision when the original plan no longer works.

There is no authoritative universal rule that every act must advance exactly one or two weeks before a show, make a call exactly 10 days out, or arrive exactly two hours early. Timing depends on the show’s complexity, the venue, the contract, travel, local procedures, and the people involved. Treat the timing examples in this article as practical recommendations, not industry mandates.

What an advance is—and what it is not

An advance is the current pre-show information exchange. It may be an email thread, a shared document, a call followed by written confirmation, or a combination of those formats. The important feature is not the format; it is that the relevant people can find the same version of the plan.

A technical rider is one part of that exchange. It is pre-show information supplied to a venue, promoter, stage manager, or sound engineer. Terminology and required contents vary by venue, promoter, event scale, and contract. A rider is therefore not a universal form that automatically covers the entire business or safety plan. The broader advance should connect the rider to the schedule, logistics, contacts, hospitality, settlement, and contingencies. What is a Technical Rider and why do I need one?

The advance also is not a substitute for the contract. If the contract promises a particular production package, hospitality item, payment process, access arrangement, or curfew, the advance should confirm how that promise will work in practice. If the venue procedure or local requirement is different, the responsible organizer and competent safety personnel must resolve the conflict. This article is educational information, not individualized legal, financial, contract, or safety advice.

Start with the show-day route

Begin with the physical and operational route through the day. Write the sequence in plain language, then identify the information needed at each handoff.

A useful route is:

1. Arrival and loading access.
2. Parking and credentials.
3. Load-in and equipment movement.
4. Dressing or green-room access.
5. Setup and line check.
6. Soundcheck or rehearsal, if applicable.
7. Doors and audience entry.
8. Support set, changeover, and headline set, if applicable.
9. Curfew and any encore or overrun decision.
10. Settlement.
11. Strike and departure.

The schedule should contain named activities, responsible people, and dependencies. “Load-in at 5” is less useful than “artist vehicle uses the north loading door; venue production contact meets the driver; stage must be clear before setup begins.” “Soundcheck at 6” should make clear whether the artist is expected to be ready at 6, whether the room is available at 6, and who decides if the preceding task runs late.

The same principle applies to doors, sets, changeovers, curfew, settlement, strike, and departure. A schedule does not need to pretend that every minute is predictable. It does need to show what is expected, what can move, and who communicates a change.

For a straightforward club show, a practical editorial recommendation is to gather the core information early enough that missing answers can still be corrected. For a complex production, festival, outdoor event, multi-act bill, unusual backline, or difficult travel route, start earlier and update the plan when the important variables change. The right question is not “How many days out is the advance?” but “Do the people who need the information have a current, workable plan before the day becomes expensive to change?”

Build the contact and escalation map

A contact list should identify more than names and phone numbers. It should explain responsibility. At minimum, map the artist-side representative, venue representative, promoter, production lead, front-of-house engineer, monitor engineer where applicable, stage manager, and the person responsible for emergency or safety decisions. Not every show has every role, and one person may hold several of them.

For each contact, record:

• Name and role.
• Organization or side of the deal.
• Email and day-of-show phone number.
• What that person can decide.
• Who is the backup if they are unavailable.
• Which issues should be escalated immediately.

A simple escalation route might read: artist representative to promoter for deal or settlement questions; artist representative to production lead for technical changes; production lead to venue manager for access or room conflicts; venue’s designated safety lead or competent person for crowd, weather, emergency, or show-stop decisions. The exact chain is venue- and event-specific. The value of writing it down is that the crew does not have to debate ownership during a time-sensitive problem.

Emergency planning should include clear responsibilities, shared plans, contingencies, communications, and possible show-stop procedures. UK Health and Safety Executive guidance discusses planning for severe weather, fire or structural failure, cancellations, unavailable staff, show stops, and performer briefings, while emphasizing that event-specific arrangements must be planned and communicated. Planning for incidents and emergencies

Do not put emergency responsibility on the artist merely because the artist is the most visible person in the room. The advance should identify who has authority to pause, stop, relocate, or otherwise alter the event under the venue’s procedures and applicable requirements. Performers and crew should know how that decision will reach them: stage communication, radio, phone, runner, public-address announcement, or another agreed method.

Exchange a usable technical package

The technical package should describe the current show, not an old template copied from another date. A practical package can include a stage plan, channel or input list, and equipment or backline list. These are core examples, not mandatory contents for every show. What is a Technical Rider and why do I need one?

The stage plan should communicate performer positions, instruments, microphones, monitors, cables, venue-provided equipment, and artist-provided equipment. It should be legible at a glance. Label the drum position, amplifiers, keyboards, playback, vocal positions, monitor positions, and any space needed for unusual instruments or movement. If a performer needs a particular orientation, sightline, power location, or clear area, show it rather than burying it in a paragraph.

The channel list should map inputs to instruments or equipment. It may include preferred microphones or DIs, positioning notes, stage-box inputs, and stand requirements. The point is to reduce guesswork and expose conflicts early. If the artist’s current setup has changed, update the list. A channel list that names equipment no longer used can create more confusion than no list at all. What is a Technical Rider and why do I need one?

The equipment and backline list should separate artist-provided items from venue-provided items. Identify what travels with the artist, what the venue supplies, what is shared between acts, and what requires confirmation. Include practical details such as left-handed or right-handed configurations, amplifier quantity, keyboard stands, drum hardware, playback connections, and power requirements only when they match the actual show. Avoid presenting a preference as a non-negotiable requirement unless the deal or production plan makes it one.

Ask the venue or production team to confirm capability rather than simply acknowledging receipt. Useful confirmations include console and monitor setup, microphones and DIs, stands, power, stage dimensions, changeover space, house backline, patching, lighting needs, and whether the venue can support the requested configuration. If something cannot be supplied, document the substitute and the person responsible for providing it.

Confirm the non-technical details

Many show-day failures are logistical rather than musical. The advance should cover loading access, parking, credentials, dressing space, catering, water, communications, merch, and guest handling when relevant.

For access, ask for the correct entrance, loading-door location, vehicle restrictions, clearance limits, unloading window, parking entitlement, and the contact who will open or direct the route. Vehicle, pedestrian, entrance, exit, and emergency-route conditions affect event safety, so access and parking deserve more than a casual “parking should be fine.” Put crowd controls in place

For credentials, confirm who needs a pass, where passes are collected, and whether crew can move between loading, stage, dressing, and merch areas. For dressing space, confirm location, access time, security, and whether the space is shared. For catering and water, state the agreed provision, service window, dietary information, and where water will be available during the performance. If the event is outdoors or weather-exposed, water, shade, and heat arrangements may become part of the event plan; England’s public-health guidance for mass gatherings supports identifying weather risks, monitoring forecasts, communicating with attendees, and planning changes for extreme heat. Hot weather advice: mass gatherings and planning events

Merchandise should have a named location, table or fixture, power needs if any, access time, sales or staffing arrangement, and a clear understanding of who handles inventory and settlement. Guest handling should identify the guest-list deadline, check-in process, allocation, plus-one policy, and the contact who can resolve an exception. These details may be contractual or venue-specific; the advance records the working method.

Communications should be practical. Confirm whether the day uses radio channels, a group message, phone calls, runners, or stage management. Do not assume that every person has the same access to the same platform. A short contact sheet with a backup method is often more useful than a long thread that nobody can search on the move.

Add the safety and contingency layer

Event preparation should include proportionate risk assessment, venue or site suitability checks, crowd-management planning, and emergency-response arrangements. UK guidance frames event safety as a cycle of planning, managing, and reviewing, with venue design, crowd management, barriers, and transport among the relevant topics. Event safety

The advance is not necessarily the document that performs the organizer’s full risk assessment. It is the place to surface questions and confirm that the responsible people have addressed them. Ask: Is the site suitable for the planned audience and production? Are entrances and exits clear? Are emergency routes protected? Who manages queues, barriers, front-of-stage pressure, and late arrivals? How will staff communicate if a route closes or crowd conditions change? Crowd-management planning should be proportionate to the event and reviewed as conditions change. Assess crowd safety risks and identify hazards

For an outdoor or weather-exposed event, determine whether a formal weather-preparedness plan is needed. The plan should identify relevant hazards, monitoring responsibility, thresholds or triggers as determined by the responsible organizers and competent personnel, and mitigation actions such as shelter, relocation, delay, cancellation, or equipment protection. Event-safety guidance covers weather, emergency planning, communication, temporary staging, and site design; the Event Safety Alliance’s weather standard specifically addresses hazard identification, monitoring, and mitigation for live events and temporary structures. ANSI ES1.7-2021, Event Safety - Weather Preparedness

Equipment protection belongs in the same conversation. Confirm whether instruments and production equipment can be kept dry, shaded, secured, and safely moved if weather changes. Do not improvise a shelter or continue work in hazardous conditions without direction from the responsible safety and production personnel. Entertainment production also includes fall, electrical, ergonomic, and other hazards, so workers need appropriate hazard information, training, and prevention measures. USITT and IATSE Alliance

Before the show, write down the decision path for a delay, show stop, evacuation, relocation, cancellation, or staff shortage. Identify who monitors conditions, who makes the decision, who tells the performers and crew, who communicates with the audience, and how the decision is recorded. Local emergency services, venue plans, contracts, and competent personnel control event-specific decisions. Safety, weather, crowd, labor, and venue obligations vary by jurisdiction and event type.

The one-page advance

A useful final document can fit on one page, with attachments for the technical details. Put the highest-value information first:

• Event name, date, venue, city, and current revision date.
• Artist, promoter, venue, and production contacts.
• Load-in, soundcheck, doors, sets, changeovers, curfew, settlement, strike, and departure.
• Loading entrance, parking, credentials, dressing room, catering, water, merch, and guest process.
• Technical attachments: stage plan, channel list, equipment or backline list, and venue capability confirmation.
• Emergency and weather contacts, communication method, show-stop authority, and contingency notes.
• Open questions, owner for each answer, and deadline for confirmation.

This structure gives the reader a route through the day and gives each participant a place to find their responsibility. It also makes gaps visible. If nobody is named for weather monitoring, settlement, loading access, or show-stop communication, the document is not finished.

An illustrative working example

Imagine a three-act indoor show with shared drums and a visiting headliner. The artist-side representative circulates the current stage plan and channel list to the venue production lead and engineers. The venue replies with the house console, monitor arrangement, available microphones, shared backline, loading-door instructions, parking limits, and the name of the day-of-show stage manager.

The promoter confirms doors, set order, changeover expectations, curfew, settlement location, guest-list procedure, and merch position. The stage manager confirms how a late-running soundcheck will be communicated. The production lead records which drum hardware is shared and which cymbals, microphones, playback devices, and instruments each act brings.

Because the event is indoors, the outdoor-weather section may be limited, but the team still confirms emergency exits, evacuation communication, crowd controls, and who can stop the performance. If the venue cannot provide a requested item, the advance assigns an owner and records the substitute. On show day, a revision is circulated if the loading door, engineer, schedule, or equipment list changes.

That example is illustrative. It does not establish a universal timing, staffing model, technical specification, or safety requirement. A festival, outdoor event, touring production, or unusual venue may require a much more detailed plan.

Final check before circulation

Read the advance as if you were arriving at the venue for the first time. Can you find the correct entrance? Do you know where to park and who will meet you? Can the engineer understand the stage and input requirements? Does every major promise have a confirmation or an open owner? Do performers and crew know how urgent changes will reach them? Is there a clear, venue-specific route for emergency decisions and a show stop?

Then send one current version to the people who need it, identify unresolved items, and set a next confirmation point appropriate to the show. On the day, treat the advance as a live reference: update it when facts change, tell the affected people, and preserve the final version for review. Event safety is not complete when the email is sent; planning, management, communication, and post-event review are connected parts of the work. Assess crowd safety risks and identify hazards

The professional habit is simple: make uncertainty visible early, assign it to a person, and close the loop in writing. A reliable advance protects time, attention, equipment, audience flow, and working relationships. It helps the show feel calm because the people behind it have already agreed how the day is supposed to work—and how they will respond when it does not.