Most stage riders die the same death: somebody opens the PDF, squints at four pages of clutter, closes it, and wings your soundcheck anyway.
I’ve been on both sides of that PDF. I’ve sent riders that got ignored, and I’ve been the engineer skimming one twenty minutes before doors. So here’s the format that actually survives contact with a busy production day — one page, four sections, zero fluff.
Why most riders get ignored
A rider isn’t a manifesto. It’s a work order. The engineer reading it has fifteen other things open and roughly ninety seconds of attention for you. Every extra page, every paragraph of backstory, every “we prefer a warm mix” — that’s time they don’t have and information they can’t patch.
The riders that get used share one trait: an engineer can act on them without reading a single full sentence.
The one-page rule
Everything on one page. If it doesn’t fit, you’re including things the venue doesn’t need. What belongs:
The band name, contact number, and set length at the top. Then three blocks: input list, stage plot, monitor mixes. That’s the whole document. Tech specs about your in-ears’ brand? Cut it. The story about your pedalboard? Cut it. One page.
The input list
Channel number, source, mic or DI, and who it belongs to. In that order, in a table, numbered the way you’d want them patched. Kick before snare, drums before bass, bass before guitars, vocals last. If you use the same order every show, the engineer can patch from memory by channel eight.
Two details that make engineers trust you instantly: mark phantom power where you need it, and mark stereo pairs clearly. Nothing says amateur like a mystery DI that turns out to be a stereo keyboard on one channel.
The stage plot
A simple bird’s-eye drawing: who stands where, amps and monitors as boxes, power drops marked with an X. It doesn’t need to be pretty — it needs to be true. The stage plot answers the question every stagehand has during changeover: “where does this go?”
Update it when your lineup changes. An out-of-date plot is worse than none, because the crew will set the stage confidently and wrong.
Monitor mixes
One line per mix: “Mix 1 — lead vocal: vocal loud, acoustic light, no drums.” Write what each person actually wants to hear, not just who the mix belongs to. Engineers can build a usable monitor mix in one pass from a sentence like that — and your first five minutes of soundcheck stop being charades.
Send it right, keep it current
Send the rider when the show is confirmed — not the night before. Attach it as a PDF with your band name in the filename, because “rider_final_v3(2).pdf” disappears into downloads folders forever. And when something changes — new drummer, added synth, dropped backing tracks — update the rider before the next send. The goal is that the document is never wrong.
Or build it in ten minutes
This exact format — input list, drag-and-drop stage plot, monitor mixes, clean one-page PDF — is what we built
My Music Rider to produce. It’s our free iOS app for working musicians and live-sound folks: punch in your setup once, export a rider that engineers actually read, and sync it across your devices as the lineup changes.
Either way — app or spreadsheet — send a rider worth reading. Your soundcheck will thank you.
Keep reading
