2026.06 · Tech rider template
A tech rider template should make a band’s production needs easy to act on, not longer than necessary.
RigFlow keeps the stage plot, input list, equipment notes, setlist, and contact details together, then exports those details as one production PDF the venue can prepare from.
Use this tech rider template when you need to explain what a band tech rider should include, how each production detail relates, and what to send to a venue without overcomplicating the production PDF.
PDF example
Build the PDF the venue needs
The stage plot shows where people and gear go. The input list shows what the sound desk receives. Equipment notes, setlist details, and contact details explain what the venue should prepare and who to ask.
A tech rider turns show details into preparation
A band tech rider should include the show identity, production contact, a clear stage plot, the input list, equipment notes, setlist context, and any venue requests that affect setup.
Small bands do not need to imitate a touring production book. If the venue can see who stands where, what needs a channel, what gear is brought, and who to contact, the rider is already useful.
The best tech rider is not the longest one. It is the one a venue can prepare from without guessing.
What to include in the template
- Band name, venue, show date, and contact details
- Audience-facing stage plot with performer positions
- Input list for microphones, DI boxes, playback, and channels
- Equipment notes for brought gear and venue requests
- Setlist, changeover notes, and lighting or playback context
How to prepare the tech rider
- 01
Add show and contact details
Start with the band name, venue, date, production contact, and any urgent notes so the PDF is identifiable when forwarded.
- 02
Create the stage plot
Place performers and gear from the audience view so the venue can prepare positions, backline, power, and monitor areas.
- 03
Connect the input list
Add microphones, DI boxes, stereo sources, playback, monitors, and power notes around the performer who needs them.
- 04
Review equipment notes and setlist
Mark what the band brings, what the venue should provide, and any setlist notes that affect changeovers or lighting.
- 05
Export the production PDF
Preview the final pages in RigFlow, then export the production PDF you can send to a venue or sound engineer.
Keep it practical for small bands
Do not split every detail into a separate spreadsheet unless the show needs it. A readable PDF that connects positions, channels, gear, and songs is often easier for a small venue to use.
Use equipment notes for exceptions: borrowed amps, personal microphones, playback, power needs, or anything the venue should confirm before show day.
Common mistakes before sending
- Sending a long rider without a readable stage plot
- Listing instruments without an input list or channel context
- Hiding equipment notes in email instead of the PDF
- Leaving out contact details for production questions
- Making a small-band rider so complex that nobody checks it
Checklist before exporting the PDF
- Show identity and contact details are visible
- The stage plot and input list agree
- Equipment notes separate brought gear and venue requests
- The setlist context is included when it affects production
- The exported production PDF is ready to send to a venue
Frequently asked questions
What should a band tech rider include?
Include show details, contact details, a stage plot, input list, equipment notes, setlist context, and any venue requests that affect setup.
Should small bands make a full technical rider?
Small bands should keep it practical. A clear PDF with the setup, channels, gear, songs, and contact details is better than a long document nobody reads.
Can RigFlow export a tech rider?
RigFlow exports the connected stage plot, equipment details, and setlist information as a production PDF that can be sent to a venue.