What to put in a band technical rider
A technical rider should make the show easier to advance, not give the venue homework. For most bands, the best rider is a concise document that shows the stage setup, lists the audio inputs and calls out the few production requirements that genuinely matter.
Band and contact details
Put the act name and a useful production contact at the top. Add the event or date when the rider is being prepared for a specific show. The technical team should be able to identify the document after it has been downloaded, printed or forwarded without the original email attached.
Stage plot
Include an audience-facing diagram showing performers, instruments, amplifiers, vocal positions and monitoring. Label everything clearly enough that somebody unfamiliar with the band can understand the setup. If an item is supplied by the band, a short label or note can prevent unnecessary venue preparation.
Input list
List every signal required at the mixing desk, with channel number, source and microphone/DI information. Add phantom-power requirements where they matter. Keep the channel list consistent with the stage diagram and avoid padding it with hypothetical inputs.
Monitoring
State how many independent monitor mixes are needed and whether each performer uses wedges, wired IEMs or wireless IEMs. Mention any band-supplied monitoring system and how it interfaces with the venue. If particular monitor content is critical to the performance, add a concise note rather than trying to specify a complete mix before soundcheck.
Backline and equipment responsibilities
Be explicit about what the band brings and what you expect the venue or promoter to provide. This is particularly important for shared drum kits, guitar/bass cabinets, keyboard stands and festival changeovers. Use wording such as band supplied, venue supplied, required or preferred so there is less room for misunderstanding.
Playback, tracks and special connections
If the show uses backing tracks, click, samples or laptops, explain how audio reaches the desk. State whether playback is mono or stereo and whether the band provides the interface/DI equipment. Mention any unusual networking, MIDI or power requirement only when the venue needs to prepare for it.
Power and stage notes
Call out unusual power requirements and the approximate locations where power is needed. You normally do not need to specify standard mains outlets beside every amplifier. The useful details are the exceptions: large pedalboard supplies, powered playback rigs, extra stage positions or equipment that cannot be moved easily.
Keep hospitality separate
A technical rider is about producing the show. If the booking also has hospitality, travel or dressing-room requirements, keep those in the appropriate agreement or hospitality rider rather than burying the sound engineer's information among unrelated requests.
Make it easy to update
Treat the rider as a living technical document. When the lineup, instruments, playback system or monitoring changes, update the source and export a new PDF. A date/event field and clear band name make it much less likely that an old rider will be used accidentally.
Related Stageplot resources
Free stage plot maker · Technical rider template · Band input list example · Stage plot examples
Build your own rider
Turn the information above into a clean stage plot, input list and technical rider. Stageplot is free and does not require an account.
Open the free builder