Technical Rider for Musicians: Complete 2026 Guide

A technical rider is the document that separates a smooth show from a logistical nightmare. It's a detailed list of what an artist needs from the venue, front-of-house engineer and promoter to perform under agreed conditions: microphones, lines, monitors, stage size, backline, hospitality. For emerging bands, tour managers, booking agents and live producers it's a daily tool — and a poorly written one causes more problems than it solves.

In this guide we explain how to build a clear, realistic and useful technical rider, with concrete examples, common mistakes to avoid and the differences between technical rider, input list, stage plot and hospitality rider.

What a technical rider is

A technical rider is the contract annex describing the minimum technical conditions required by the artist to perform. It's not a wish list or a flex: it's an operational document that protects the promoter (who knows exactly what to provide) and the artist (who won't end up without monitors or with an under-specced PA). It's sent with the contract or, in more structured tours, through the tour manager's advance 2–4 weeks before the show.

A good rider answers six questions unambiguously: who plays what, which mics and DIs are needed, how the stage is laid out, which monitors and routing are required, which backline is necessary, what the hospitality and logistics needs are.

The components of a technical rider

A professional rider usually combines four documents, often merged into a single PDF:

1. Input list (channel list)

The table of audio channels, in numerical order. For each channel: number, source (instrument or vocal), recommended mic/DI, support (stand, clip, specifics like kick-in/kick-out), phantom power, preferred inserts. Example for a rock band with drums, bass, two guitars and vocals:

1. Kick In — Shure Beta 91A
2. Kick Out — Shure Beta 52A
3. Snare Top — Shure SM57
4. Snare Bottom — Shure SM57 (pad)
5. Hi-Hat — AKG C451B
6. Tom 1 — Sennheiser e904
7. Tom 2 — Sennheiser e904
8. Floor Tom — Sennheiser e902
9. Overhead L — Neumann KM184 / Shure SM81
10. Overhead R — Neumann KM184 / Shure SM81
11. Bass DI — Radial JDI + amp mic (Sennheiser e906 optional)
12. Guitar 1 — Shure SM57 (cab)
13. Guitar 2 — Sennheiser e906 (cab)
14. Lead Vox — Shure SM58 / Beta 58A / Sennheiser e945
15. Backing Vox 1 — Shure SM58
16. Backing Vox 2 — Shure SM58

Always list reasonable alternatives: "Shure SM7B, or alternatively Sennheiser MD421" is far better than "Neumann U87 mandatory" for a club gig.

2. Stage plot

The stage layout: a top-down (or perspective) graphic showing every musician's position, amps, monitors (wedges or in-ears), mics and AC outlets. Always indicate the number of monitor mixes and their destination (Mix 1: Lead Vox, Mix 2: Drummer – click+guide, etc.). Tools like StagePlot Pro, StagePlot Guru or a well-used Keynote/PowerPoint are enough.

3. Technical rider proper (PA, FOH, monitors)

Descriptive section covering:

• FOH system: minimum power, quality line-array (L-Acoustics, d&b, Meyer, Adamson, Nexo), even coverage, cardioid subs where needed.
• FOH console: preferred digital desks (DiGiCo, Midas Pro, Yamaha CL/QL, Avid S6L). Note if the house engineer brings their own show file.
• Monitor system: number of independent mixes, active wedges with parametric EQ per channel, or in-ear (IEM) system with dedicated stage box.
• Backline: drum kit brand/model (Yamaha Stage Custom, Pearl Export, DW Collector's), guitar amps (Fender Twin, Marshall JCM800, Vox AC30), bass amps (Ampeg SVT, Aguilar, Markbass), cab/head counts.
• Lighting: minimum requirements (moving heads, LED pars, atmosphere, haze), whether the artist brings an LD or the venue provides.
• Crew: FOH engineer, monitor engineer, stagehands, runner, backliner.
• Timing: arrival, load-in, soundcheck (minimum 45–60 min for a new band, 90–120 for complex shows), line check before doors.

4. Hospitality rider

Non-technical but essential needs:

• Dressing rooms: number, minimum size, bathroom/shower access, keyed with return, dedicated Wi-Fi.
• Catering: hot meal for artist and crew around soundcheck or pre-show, vegetarian/vegan/gluten-free options always, still and sparkling water, fresh fruit, coffee/tea, specific beverages.
• Towels: clean white towels (band members + 20%).
• Transport and accommodation if not covered by separate agreement.

How to write a technical rider: examples and best practices

Rules that distinguish professional riders from amateur ones:

• Short and readable: 4–8 pages. Iconic artists' 40-page riders are often irrelevant for 300-cap clubs and end up ignored.
• Realistic: adapt to the venue. A 200-cap club doesn't have a d&b Y-series PA. Ask for a decent line array and leave room for the house engineer to operate.
• Alternatives: "or alternatively…" solves 90% of problems.
• Clear contacts: name, phone and email of tour manager, FOH engineer and backline manager on page one.
• English version for international tours or festivals.
• Revision date: "Rev. 2026.04" signals if it's up to date.

A frequent mistake is copying someone else's rider: every band has different sources, technology and priorities. A generic rider is worse than none.

Technical rider vs input list vs stage plot

Quick recap:

• Input list: channel table, one row per source.
• Stage plot: stage layout graphic.
• Technical rider: descriptive document including input list and stage plot plus PA/monitor/backline specs.
• Hospitality rider: dressing rooms, catering, accommodation.

Together the technical rider and hospitality rider form the overall rider.

Rider for emerging bands: what to include (and what not to)

If you're an emerging band, write your rider pragmatically:

• Essential input list (don't ask for mics the venue doesn't own).
• Clear stage plot — even hand-drawn if well scanned.
• Monitor request: be precise about the number of independent mixes (minimum 2–3 for a 4-piece band).
• Backline: specify what you bring and what you ask the venue for.
• Restrained hospitality: water, basic meal, space to change.
• Timing: a 30-minute soundcheck is realistic for multi-artist nights.

Promoters read riders. A clean, realistic, English-language rider increases your chance of being rebooked.

Tools to build a professional technical rider

In 2026 the most-used tools are:

• StagePlot Pro — classic, great for stage plots and input lists, clean PDF export.
• StagePlot Guru — modern web app with templates and cloud sharing.
• Canva / Figma — for curated visuals, especially branded riders.
• Excel / Google Sheets — for input lists, exported as PDF.
• Keynote / PowerPoint — often enough for basic stage plots.

For multi-show tours, heavier platforms like Master Tour, Tourbase or Muzeek integrate rider, advance, settlement and logistics.

FAQ

What is a technical rider? The official document describing an artist's full technical and logistical needs to perform: input list, stage plot, PA, monitors, backline, lighting, crew, hospitality. It's attached to the contract and shared with the promoter.

How do I write a technical rider for the first time? Start from the input list (which audio channels you need), draw the stage plot, add monitor and backline requests, then the hospitality section. A trusted FOH engineer is invaluable in calibrating realistic requests for your band's level.

Difference between technical rider and hospitality rider? The technical rider covers everything related to performing (audio, stage, lights, backline). The hospitality rider covers care — dressing rooms, catering, towels, transport. Both belong to the overall rider.

How long should a technical rider be? For emerging bands 2–4 pages is plenty. For established artists with dedicated FOH and monitor systems 8–15 pages is common; 40+ pages is almost always overkill.

Is the rider binding for the promoter? Yes, if it's attached to a signed contract. The promoter commits to providing what's listed, apart from deviations agreed during advance. Serious failures may trigger disputes or reduced fees.

Who writes the rider? In structured projects, the tour manager or FOH engineer drafts it, signed off by the artist manager. Emerging bands often have the drummer or setup lead write it with a trusted engineer's help. The key is that a sound pro reviews it before it ships.

Do I need to translate the rider into English? Yes, if you're touring abroad or playing international festivals. A bilingual IT/EN or your local language + English is the standard for bands touring Europe.

Conclusion

A well-crafted technical rider is the first professional impression you give promoters, festivals and venues. It doesn't need to be long — it needs to be clear, realistic and easy to read. Two hours spent writing a clean rider saves you ten problems on show night.

🎵 Are you an independent artist or a music industry professional? On HAT Music you'll find the community, the tools and the professionals you need to grow your project. Join the community →