Band rider template
“Band rider” usually means the whole package: what the show needs technically, and what the band needs off stage. Both halves travel together.
Technical and hospitality requirements are not the same thing
The technical requirements are read by the sound engineer and the stage crew: stage plot, channels, monitoring, backline, power. The hospitality requirements are read by the promoter and the venue manager: dressing rooms, catering, parking, accommodation.
They go to different people, and that is exactly why they belong in one document with a clear split. One file to send, two clearly labelled halves to act on.
What a complete band rider usually contains
- Cover page: act name, show date or tour, version and contacts
- Stage plot with performer positions and backline
- Input list with channel numbers, sources, microphones and DI
- Monitoring: number of mixes, wedges or in-ears
- Backline and equipment, split into what you bring and what you need
- PA, power and stage size requirements
- Schedule: load-in, soundcheck, doors, set length
- Hospitality: dressing rooms, catering, drinks, parking, guest list
Keep it proportionate
A twelve-page rider for a 200-capacity club gets skimmed; a three-line email for a festival gets you an unusable stage. Say what changes the outcome, mark what is essential versus preferred, and leave the rest out.
How ArtistRider combines both parts
- One document containing technical sections and hospitality requirements
- Shared libraries for people, instruments and equipment across projects
- Separate riders per project, so a festival version and a club version can differ
- A single PDF export, or a share link the promoter opens without an account