Learn — By WATMM Desk —
How to write a stage plot, input list and tech rider
A tech rider tells a venue what your show needs before you arrive. Its core is a stage plot and an input list, ideally on one page. This guide covers what goes on each, how to order the channels, when to send it and the mistakes that annoy sound engineers, with sources checked on 31 Oct 2026.
Key facts
- ProSoundWeb calls the input list and stage plot "the audio core of any technical rider" and recommends putting both on one page where possible.
- ProSoundWeb suggests ordering channels by instrument type, starting with drums and ending with vocals.
- ProSoundWeb suggests emailing an updated rider a month or a week (or both) before the gig.
- Sonicbids advises keeping the plot simple, and notes that specific mic and outboard requests are only safe if you travel with that gear.
A tech rider is the document that tells a venue what your show needs before you walk in. For most independent acts it does not need to be long. Its working core is two things: a stage plot (where everyone and everything stands) and an input list (every channel the engineer has to patch). Get those right and you have done most of the job. Sources were read on 31 Oct 2026.
What a tech rider is for
NAMM's session on festival stage plots describes a single document combining an input list with a stage plot as the "vital core of every audio technical contract rider", built so local crews get "accurate details in writing ahead of time". ProSoundWeb's Letting It Ride makes the same point: the input list and stage plot are "the audio core of any technical rider", and the best practice is to put both on one page where possible.
Everything else in a rider (backline requests, power, hospitality, set length) can sit on a second page. The engineer mostly needs page one.
The stage plot
SoundGirls defines a stage plot as "literally a diagram of what your onstage setup looks like", showing the relative position of everything on stage (SoundGirls). On it, mark:
- Each player and their instruments, with names, so the engineer can talk to a person, not a position.
- Vocal mics, amps, DI points and monitor wedges. Sonicbids says to label these clearly, along with power outlets, and to note whether an amp has a direct out or needs a DI (Sonicbids).
- Drum kit size (how many pieces), per the same guide.
- Monitor notes: what each member needs in their mix, and what they don't.
- A contact: Sonicbids suggests the name and number of the most tech-savvy band member.
Keep it plain. Sonicbids says a simple layout from a word processor works, and a full-colour poster is overkill.
The input list
The input list is a numbered table, one row per channel. Sonicbids recommends listing each input's function, the mic or input type, the stand needed, and any outboard requests. A minimal version:
| Ch | Source | Mic / DI | Stand | Notes |
|---|---|---|---|---|
| 1 | Kick | Dynamic (kick) | Short boom | |
| 2 | Snare | Dynamic | Short boom | |
| 3 | Bass | DI | Bring own DI | |
| 4 | Keys L | DI | Stereo | |
| 5 | Keys R | DI | Stereo | |
| 6 | Lead vocal | Own mic | Tall boom | Phantom off |
ProSoundWeb suggests ordering channels by instrument type, starting with drums and ending with vocals, labelling inputs with stage positions (such as DSL for downstage left) so the patch tech knows where each mic sits, and using columns for things like phantom power and stand choice. That drums-first order is how most engineers already lay out a desk, so matching it saves them re-patching.
When to send it
ProSoundWeb notes that riders go stale because agents often book shows long before the band has rehearsed or the crew is hired and send an old version. Its fix: email an updated one-page rider "a month or a week (or both) before the gig", and bring printed copies to load-in. Sonicbids adds that festivals often ask in advance, but you can send it whenever you advance a show. Our gig booking guide covers the rest of that confirmation, and the electronic press kit guide explains where the rider lives alongside your photos and bio.
Mistakes engineers mention
- Asking for gear the room can't supply. Sonicbids gives the example of a 100-person venue where the engineer suggests four or five drum mics instead of the 12 on your list; specific mic and outboard requests only hold if you travel with that gear. The engineer knows the venue; defer to them.
- Over-designing the plot. Pretty is not the goal; readable is.
- Vagueness about monitors, placement or power.
- No date on the document, which makes old versions impossible to spot.
What we think
Most small-venue acts treat a rider as something "real" bands have, then spend soundcheck explaining their setup out loud. That is backwards: the smaller the gig, the less time you get, so the more a one-page plot earns its keep. Our advice is to date every version in the corner, keep one master file you edit rather than new copies, and write the input list from the engineer's side: drums first, vocals last, the same order they will patch. If you play with a laptop or tracks, give playback its own clearly labelled stereo pair; our guide to backing tracks for live shows covers why. And a rider is a request, not a contract you win. A venue that sees a realistic, honest list is more likely to help with the one thing you really need.
Once the rider is sent, the soundcheck checklist picks up on the day itself.
Sources
- Festival Stage Plot: Tech Rider Update, NAMM (primary source). Accessed 31 Oct 2026.
- Letting It Ride, ProSoundWeb. Accessed 31 Oct 2026.
- How to Create a Stage Plot and Input List That Sound Techs Will Love, Sonicbids. Accessed 31 Oct 2026.
- How to Make an Input List, Stage Plot and Patch a Stage, SoundGirls. Accessed 31 Oct 2026.
Researched with AI assistance, written and checked by WATMM Desk.