How to Write a Technical Rider That Actually Gets Read

You just booked a show at a real venue. They ask for your technical rider. You dig through your emails, find a PDF from two years ago, and send it without looking too closely. The sound engineer receives a document with your old band name, inputs for gear you no longer use, and no stage plot.

That's how soundchecks go sideways before you've even unloaded the van.

Your technical rider is the first technical contact the venue has with you. The other document your crew needs — covering schedule, transport, and contacts for the day itself — is a concert day sheet, which goes out to your team the night before the show. It tells their engineers whether you're going to make their day easier or harder. And in the world of small to mid-size venues, that reputation sticks.

What a Technical Rider Actually Is

A technical rider is the document you send to a venue before each show so their technical team knows exactly what you need to perform. It describes your stage setup, your sound and lighting needs, your monitoring requirements, and practical information about your act.

It's not a negotiation tool. It's not a list of demands. It's a working document, practical and precise, that lets the engineer prepare the room before you arrive.

A good technical rider means: the sound is patched when you get there, the monitors are configured, the lighting is preset to something coherent. A soundcheck that runs in two hours instead of four.

What Your Rider Needs to Cover

General Information

At the top of the document: your act name, the tour or project name, a version date, and your direct technical contact (name plus phone number). Not the manager, not the booking agent. The person the engineer can actually call on the day if something is wrong.

Stage Setup (Stage Plot)

A stage plot is a top-down view of your stage showing where each musician, each amp, and each monitor sits. It doesn't need to be a design masterpiece. A clean diagram is enough. What matters is that an engineer can understand it in ten seconds.

Also include the minimum stage dimensions you need (width and depth). Some small venues have tiny stages. Better to know in advance than discover it on arrival.

Backline

A list of what you're bringing and what you need the venue to provide, instrument by instrument. Guitars, basses, drums, keyboards, amps. Be specific about models if it matters (some amps have quirks). Mark each item clearly as "PROVIDED" or "NEEDED FROM VENUE."

If you're traveling light (fly dates, international shows), note what you can't bring and what you expect from the venue.

FOH Inputs (Front of House)

A list of every channel going into the main mix board. One line per source: instrument or microphone, channel number, connector type (XLR, DI, quarter-inch), and any useful notes ("passive DI," "built-in preamp," "balanced signal").

If you're traveling with your own FOH engineer, say so. If you're working with the house engineer, this list is what they'll use to build their patch before you arrive.

Monitoring

This is often the most overlooked section and the one that creates the most problems on the day.

Describe your monitor setup: how many separate monitor mixes you need, which musicians need them, and what they want to hear. A drummer mix heavy on kick and snare? A keyboard mix with click track and minimal bass? Write it down.

If anyone is on in-ears, specify it. If you need distribution boxes, list how many.

Lighting

For most independent bands in small to mid-size rooms, the lighting section is simple: note any specific requests (cold lighting, no strobes for medical reasons, a couple of effects you like).

If you have a more developed light show, you can include a separate lighting rider. If you have no particular requests, say so directly: "No specific lighting requests. We trust the house LD." Engineers genuinely appreciate the honesty.

Special Technical Needs

Samplers, playback, timecode, click send, video on stage, haze machines, confetti: anything outside a standard setup. The more you anticipate, the fewer surprises.

Classic Mistakes

Sending an old version. Every rider should be versioned and dated. "Tech rider v3 - Spring Tour 2026" prevents the venue from using your 2024 document.

No stage plot. The stage plot is often what the engineer looks at first. Without one, you lose ten minutes on arrival repositioning everything from scratch.

Unrealistic demands. If you're playing 200-capacity rooms, don't ask for a full in-ear system with six independent mixes for five people. Match your requests to the context. A credible rider opens more doors than one listing stadium-level gear requirements.

No direct contact. The engineer needs to be able to reach you the week before and on the day. Put a visible phone number, not just an email address.

Sending it too late. Send your rider at least two weeks before the show. Three weeks for larger venues. By 48 hours out, the engineer already has their other shows in motion.

A Basic Template

Here's what a tech rider for a mid-size band playing 100 to 500-capacity rooms should include:

[ACT NAME] — Tech Rider [version / date]
Technical contact: [First Last] — [Phone number]

LINEUP
[List of musicians and instruments]

STAGE PLOT
[Insert diagram or sketch]
Minimum stage dimensions: [X]ft wide x [Y]ft deep

BACKLINE
Drums: [Preferred kit or "standard"]
Guitar: amp [model] — PROVIDED or NEEDED
Bass: amp [model] — PROVIDED or NEEDED
Keys: [2x passive DI] — PROVIDED

FOH INPUTS
Ch 1 — Kick — XLR
Ch 2 — Snare — XLR
Ch 3 — Hi-hat — XLR
Ch 4 — Tom 1 — XLR
Ch 5 — Overhead L — XLR
Ch 6 — Overhead R — XLR
Ch 7 — Bass — Passive DI
Ch 8 — Guitar — XLR (amp cab)
Ch 9 — Keys L — DI
Ch 10 — Keys R — DI
Ch 11 — Lead vocals — XLR (dynamic mic)
Ch 12 — BGV — XLR

MONITORING
Mix 1: Drums (kick, snare, OH, vocals)
Mix 2: Lead vocals (vocals, guitar, bass)
Mix 3: Keys (vocals, piano, bass)
[All wedges unless noted otherwise]

LIGHTING
No specific requests. We trust the house LD.
No strobe lights.

NOTES
[Quirks, playback, samples, anything unusual]

Adapt this to your lineup. A guitar-voice duo doesn't need twelve FOH channels. A band running playback and samples has a very different setup.

What Otto Does with Your Rider

When a venue sends you their technical spec sheet or stage hospitality document, you can drop it directly onto the date page in Otto. The built-in AI reads the document and automatically pulls out contacts, set times, and technical notes into the right fields.

No more copy-pasting the engineer's phone number from a PDF into a spreadsheet. Otto handles it.

And your own rider, once uploaded, is accessible to your whole crew from the date page. No more "do you have the right file?" at 10pm the night before the show. For everything else you need to run a tour without a TM, there's more to cover.