Live production guide
Technical rider template: what to include for a live show
A useful technical rider is not a wish list. It is a working agreement that helps the artist, venue, promoter and suppliers prepare the same show. This guide gives bands, engineers and tour teams a clear structure to copy and adapt.
Key points
- Put the show, revision date and technical contact on the first page.
- Separate non-negotiable requirements from preferences and acceptable alternatives.
- Keep the stage plot, input list, power and schedule consistent with one another.
- Close exceptions during the advance and store the approved version with the gig.
What a technical rider should achieve
A technical rider describes the conditions needed to load in, build, operate and load out a performance. Someone receiving it should be able to identify the show configuration, prepare the venue and contact the right person when a requirement cannot be met.
Keep technical production separate from hospitality, and do not use the rider as a substitute for a show advance or a local safety assessment. Its job is to turn the touring plan into decisions the receiving team can act on.
- Technical rider: audio, lighting, video, stage, power, rigging, communications and crew.
- Stage plot: the physical position of performers, instruments, monitors and power.
- Input list: every source, channel, microphone or DI, stand and relevant note.
- Hospitality rider: travel, dressing rooms, catering and non-technical arrangements.
A practical technical rider structure
Order the document the way production will use it. Start with identity and document control, then provide a short show overview before the detailed department sections. Number the pages and use a filename that contains the artist and revision date.
1. Show and document control
Artist, production, lineup, version, revision date and a technical contact with mobile number and email.
2. Schedule and operating overview
Access, load-in, setup, line check, soundcheck, doors, performance, curfew and load-out, plus visiting crew and show length.
3. Audio and stage
PA coverage, consoles, stage boxes, splits, inputs, outputs, monitors, RF, comms, recording, risers and backline.
4. Power, lighting, video and rigging
Supply requirements, distribution, control, universes, surfaces, positions, loads and responsibilities.
Write requirements without blocking the venue
Label each item as required, preferred, artist-carried or venue-provided. A model number can be a useful reference, but it should not hide the capability you need. State channel counts, connections, processing, capacity or the intended result, then define acceptable equivalents where they exist.
If an alternative would affect safety, setup time or the artistic result, explain the constraint and request written approval. This produces a better conversation than an unexplained list of brands.
From sending the rider to closing the advance
Sending a PDF does not mean the venue has accepted it. The advance is closed when a responsible person has reviewed the plan, recorded every exception and assigned each open action to an owner and deadline.
- Confirm the venue production contact and escalation route.
- Record the requested item, proposed solution, owner and decision date for every exception.
- Keep the input list and stage plot under the same revision identifier.
- Distribute one approved pack and move older versions out of the active folder.
- Attach the final rider to the correct show date and lineup.
Practical template
Copyable technical rider outline
Remove sections that do not apply. A short, complete document is more useful than a long file full of empty boilerplate.
TECHNICAL RIDER — [ARTIST / SHOW] Revision: [YYYY-MM-DD / V1] Technical contact: [NAME · MOBILE · EMAIL] 1. SHOW OVERVIEW - Lineup and visiting crew: - Set length: - Essential requirements: 2. SCHEDULE - Access / load-in: - Setup / line check / soundcheck: - Doors / show / curfew / load-out: 3. AUDIO - PA and coverage: - FOH / monitors / stage boxes: - Input list, patch, microphones, DIs and RF: - Communications and recording: 4. STAGE, BACKLINE AND POWER - Dimensions, risers and stage plot: - Artist-carried / venue-provided equipment: - Power and distribution: 5. LIGHTING, VIDEO AND RIGGING - System, control, positions and content: - Rigging points and loads: 6. CREW AND RESPONSIBILITIES - Local crew: - Artist supplies: - Venue/promoter supplies: 7. APPROVED EXCEPTIONS - Item · solution · owner · approval date
Frequently asked questions
How long should a technical rider be?
As long as needed to remove operational ambiguity. A small club show may need only a few pages, while a multi-department production needs appendices. Make information quick to find rather than targeting a page count.
Should a technical rider name brands and models?
Use them where compatibility matters, but also describe the required capability and acceptable equivalents whenever possible.
When should the rider be updated?
Whenever the lineup, patch, playback, backline, crew or show requirements change. Check contacts and revision details before every new run of dates.