How to Build a Simple Tech Rider That Venues Actually Read

🎛️ Googling tech rider template, DJ rider example, band rider checklist? Riders usually flop two ways:

1. useless vagueness (“just… good PA?”)
2. fifty-page novels nobody prints before soundcheck

Sound humans skim on phones next to a rack — front-load the stuff that prevents fights.

When gigs mutate → last-minute gig changes.

---

🪪 Page 1 — identity block (only essentials)

• artist / DJ / hybrid descriptor
• day-of mobile that actually gets answered
• timing cliffs — how long line check really needs if vocals are fragile

Not here: your life story — that’s promo pack territory.

---

⚡ Inputs — tables beat vibes

Feed	Source	Notes
Stereo DJ send	Laptop / controller	Balanced pair preferred 🎯
Wireless vocal	Venue supply	Say what class / pattern if you care

Add notes where it matters: stereo vs mono OK?, isolators, ground buzz history — ambiguity becomes buzz + blame mid-show.

---

🔊 Outputs — say what you need plainly

• wedges vs sidefills vs DJ booth cue expectations
• sub policy (“coupled OK / no thanks”)
• whisper intros / dynamics — flag before FOH is surprised

Engineers prioritise avoiding disasters — clarity = respect.

---

🗺️ Stage plot — messy sketch beats fancy wrong CAD

Readable beats ornate:

• where humans stand
• cable egress
• minimum booth space
• power drops

Photo + markup counts — metric/imperial consistency matters if you tour internationally.

---

🥤 Hospitality — keep it proportional

Wild rider screenshots go viral for a reason — match asks to billing tier and role.

Separate hospitality from tech so crews don’t side-eye your whole PDF.

---

📎 Version naming (please)

Act_TechRider_v2026-05.pdf

Bump version when outputs change — old riders misroute blame faster than a missing fog machine line.

---

🧳 Travel overlap

Rider clarity + packing brains → gear protection · travel gig checklist.

---

❓ FAQ

How long should the PDF be?

First 1–2 pages = decisions. Rest = appendix optional.

DJ solo — still need a plot?

Yeah minimal — footprint + cable direction + power still prevents assumptions.

Hospitality tied to tech?

Separate sections — less side-eye, cleaner forwards.

---

Readable rider = fewer fights + cleaner shows — StagePay features doesn’t replace tech comms; it just saves admin elsewhere.