How to Advance a Show: Production Checklist and Timeline

TL;DR — To advance a show, exchange the current rider, confirm the venue and tour contacts, reconcile schedule and access, agree on sound, stage, monitors, backline, power, lighting, video, and hospitality, then turn every exception into an owned action with a deadline. Finish with one written summary that states the approved plan, unresolved items, document version, and next check-in.

Table of contents

1. What advancing a show means
2. A practical advance timeline
3. The complete show advance checklist
4. How to reconcile a rider with venue reality
5. Production advance email template
6. Day-of handoff
7. FAQ

What advancing a show means

Advancing a show is the pre-event process in which the touring and local teams turn the artist's requirements and the venue's capabilities into one confirmed operating plan. It is not merely emailing a tech rider. A successful advance identifies conflicts early, assigns responsibility, records substitutions, and gives the day-of crew a plan they can execute.

The advance usually connects several documents:

• the technical and hospitality rider;
• stage plot and input list;
• venue technical specification;
• show schedule and contact sheet;
• backline order or local equipment list;
• lighting, video, rigging, or power documents where relevant;
• a final issues and decisions summary.

The rider describes the touring baseline. The advance describes what will happen at this specific venue on this specific show.

A practical advance timeline

There is no universal schedule. Festival complexity, rentals, travel, staffing, and contract deadlines determine when work must begin. Use this as a planning pattern and move critical decisions earlier when lead times require it.

Do not wait for a fixed number of days if a decision affects rental availability, transport, permits, staffing, or safety. The right deadline is the latest date on which the team can still act without unnecessary cost or risk.

The complete show advance checklist

1. Contacts and authority

• Artist / tour manager and production manager
• Touring FOH and monitor engineers
• Venue production manager and house audio lead
• Promoter or buyer contact
• Lighting, video, backline, security, hospitality, and transport contacts as needed
• Day-of mobile numbers and preferred communication channel
• Person authorized to approve substitutions and added costs

2. Venue and access

• Correct venue room and address
• Loading location, vehicle limits, dock, stairs, lift, and push distance
• Parking and bus / trailer arrangements
• Stage dimensions, trim, roof, wings, and backstage access
• Curfew, noise limits, house rules, and local restrictions
• Accessibility requirements for artists and crew

3. Schedule and staffing

• Load-in, crew call, setup, soundcheck, doors, set, and curfew
• Support-act and changeover timing
• Local crew count, roles, and call duration
• Meal and break timing
• Guest, press, or meet-and-greet activity affecting production
• Weather decision points for outdoor events

4. Stage and backline

• Current stage plot reviewed against real stage dimensions
• Risers, rolling requirements, stairs, rails, and drum orientation
• Every backline item assigned to artist, venue, promoter, or vendor
• Exact models where necessary; acceptable substitutes approved
• Stands, stools, carpets, hardware, and small accessories included
• Changeover storage and pre-build area confirmed

5. Audio and inputs

• Current input list and total channel count
• FOH and monitor console plan
• PA coverage and system responsibility
• Stage boxes, sub-snakes, split, patch, and cable runs
• Microphones, DIs, stands, phantom power, and specialist inputs
• Playback, recording, talkback, and communication paths
• Show file transfer and compatibility where applicable

An input list describes source requirements; a local patch sheet assigns those sources to the venue system. Do not force a touring channel order into an unrelated house patch without discussion. See Input List vs Patch Sheet.

6. Monitors and wireless

• Mix count, performer ownership, and mono / stereo format
• Wedge, sidefill, wired IEM, and wireless IEM destinations
• Touring versus house monitor engineer
• Artist-carried transmitters, receivers, and bodypacks
• Frequency coordination owner and required device information
• Ambient, click, cue, and talkback sources where used

7. Power, lighting, video, and rigging

• Touring equipment voltage and power locations
• Venue electrical distribution reviewed by qualified personnel
• Lighting fixture, control, haze, key light, and blackout needs
• Video playback, screen format, signal, camera, and timecode needs
• Rigging points, loads, motors, permits, and qualified providers where relevant
• Backup plan for show-critical playback or control

8. Hospitality, security, and settlement interfaces

• Dressing rooms, towels, water, meals, dietary and allergy information
• Guest list and credential process
• Stage, backstage, and equipment security
• Merchandise location, power, connectivity, and timing
• Local transport and hotel movements affecting schedule
• Person responsible for any production-cost approval

Keep commercially sensitive settlement details in the appropriate controlled workflow. The production summary should contain only what crews need to execute the show.

9. Final documentation

• Current Rider live link shared
• Dated PDF attached for offline use
• Venue specification version recorded
• All substitutions summarized in writing
• Open items have owner, deadline, and consequence
• Final schedule and contact sheet distributed
• Superseded files clearly withdrawn or archived

How to reconcile a rider with venue reality

Treat every mismatch as a small decision record:

This format is better than a long email thread because it preserves the requirement, the constraint, and the decision. Use the same approach for backline substitutions, reduced stage depth, fewer monitor mixes, or a schedule change.

Do not overwrite the touring baseline to make one venue look compliant. Store the local exception with the show, then decide after the run whether it should become a permanent Rider change. Reusing One Rider Across Multiple Shows explains that separation.

Production advance email template

Subject: [Artist] — [Venue, City] — [Show Date] — Production Advance

Hello [Name],

I am advancing [Artist] for [show/date]. The current technical Rider is available at [live link]; I have also attached a dated PDF for offline use.

Please confirm:

1. the schedule, access, and local production contacts below;
2. the attached stage plot and input list against the room and house system;
3. backline and monitor items marked as venue-provided;
4. the proposed substitutions listed under “Open decisions”; and
5. any venue constraints not covered in the current specification.

Confirmed so far

• [decision]
• [decision]

Open decisions

• [item] — owner: [name] — needed by: [date]
• [item] — owner: [name] — needed by: [date]

Key schedule

• Load-in:
• Soundcheck:
• Doors:
• Set:
• Curfew:

Day-of contacts: [tour] / [venue].

Thank you, [Name and role]

The email should link to structured information, not duplicate the entire rider. Keep the requested response specific enough that “looks good” cannot hide an unresolved substitution.

Day-of handoff

At load-in, verify the highest-impact assumptions first: correct room, schedule, stage footprint, supplied backline, console and patch plan, monitor inventory, power, and crew. Record necessary deviations and tell the affected department immediately.

Use the advance as the baseline, not as a weapon. Real rooms change. The goal is to preserve safety and show intent while making controlled decisions. After the show, update the reusable Rider only for durable changes and save venue-specific lessons with the show record.

FAQ

What does advancing a show mean?

It means confirming and reconciling the artist's production and hospitality requirements with the venue's capabilities before the event, then documenting the agreed plan, responsibilities, substitutions, schedule, and open issues.

What should be in a show advance?

Include contacts, venue access, schedule, staffing, stage, sound, inputs, monitors, wireless, backline, power, lighting, video, hospitality, security, current document versions, approved substitutions, and owned open actions.

When should you advance a concert?

Begin early enough to act on the longest-lead requirement. Rentals, crew, transport, permits, and complex technical changes may need earlier decisions than a simple club show. Set deadlines from operational lead time, not a universal day count.

Who is responsible for advancing a show?

Responsibility varies by production. A tour manager, production manager, artist representative, promoter, or venue production manager may lead, while department specialists approve technical details. Name one coordinator and one authorized approver for each consequential decision.

Is sending a tech rider the same as advancing?

No. Sending the rider starts information exchange. Advancing is the two-way process of checking it against venue reality, resolving differences, assigning work, and confirming the final plan.

Advance from one current source

Build and reuse your Rider with Techrider.live, invite the appropriate editors, and send a dated PDF plus a current view-only link. For the document itself, start with the complete Tech Rider Template.

---

Last updated: 2026-07-14 · Reviewed by the Techrider.live team for club, festival, and touring production handoffs.