A rider gets ignored when nobody can tell which parts are non-negotiable.
Tell us what really matters from the start. What's non-negotiable? We want to know what you'd really like, and what you're happy for us to substitute. Giving us that information gives us the best chance of delivering exactly what you need.
What to put in it
- Put the must-haves first.
- Tell us what is required and what is just preferred.
- Give us numbers. "Wireless mics" isn't enough, tell us you need six.
- Give us your stage size.
- Send a stage plot if you have one.
- Tell us what audio connections you need.
- Tell us your video resolution and format.
- Tell us who's bringing the presentation laptops.
- Streaming? Tell us exactly what you need for internet.
- Tell us about power.
- Tell us about rigging and weights if you're hanging anything.
- Happy with an equivalent piece of equipment? Great, tell us.
- Absolutely need that exact model? Also fine, tell us why.
- Put a date on the rider so we know which version we're looking at.
- Give us the phone number or email of somebody who can actually answer a technical question.
- And the biggest one: send it early. Give us enough time and we can normally figure almost anything out.
The most famous rider clause in the business
You have probably heard the brown M&M story, and it is worth telling properly because the lesson in it is the one that matters here. Van Halen's 1982 world tour rider really did carry a line under its "Munchies" heading reading "M&M's (WARNING: ABSOLUTELY NO BROWN ONES)", which Snopes has confirmed in an undated fact check. David Lee Roth's account, in his 1997 autobiography Crazy from the Heat, is that the clause was a buried test: a bowl of M&Ms with brown ones in it told the crew nobody had read the technical rider properly, so they would line-check the entire production before trusting any of it. Roth describes real venue failures behind that caution, including structures that could not take the weight, floors that gave way under it, and doors too small to move the gear through (Business of Software, excerpt analysis, 2013).
That explanation is Roth's own, so take it as his account rather than as an independent finding. But the underlying problem is a real one: a rider is only useful if somebody reads all of it, and nobody can read all of it carefully unless the important parts are impossible to miss. You do not need a trick. You need the must-haves at the top.
A rider is a contract document, not a wish list
This changes how you should write it. Trade guidance defines the technical rider as a contractual document setting out the audio, lighting, staging, power, and logistics that must be provided (Geo Events, "The Technical Rider: What Every Client Should Know", a production company guide that carries no publication date). So write it as something you would be comfortable seeing attached to a contract: dated, itemised, numbers instead of categories, and clear about which lines are requirements and which are preferences.
What happens on our side when your rider lands
Knowing what a receiving crew does with a rider should shape how you write it. A widely used receiving-side guide describes the same three steps that work: read the whole rider, flag anything that cannot be provided, and take specific alternatives back to the production manager before show day (Critical Listening Lab, tech rider guide, no date on the page). That is a conversation worth having three weeks out, on a call, with time to find the thing you actually need. It is a much worse conversation at eight in the morning on load-in day, when the honest answer is whatever is on the truck.
Unions have been formalising this since 1912
If you want proof that the write-it-down-early approach is not a modern preference, look at the yellow card. IATSE has used one since 1912: the card travels with a touring production and states, department by department, how many local crew are needed for load-in, for performances, and for load-out (IATSE, touring overview, with a public explainer from IATSE Local 26 in Washington, DC). IATSE is international, with locals across Canada and the United States, and the Local 26 page explains the system rather than any particular Canadian call. It is a crew rider, and it works for the same reason a good technical rider works. Nobody arrives guessing.
The version problem is the one that bites
Riders travel through several hands, and the copy being worked from is not always the copy you think has been sent. So date every version, and when something changes after a quote has gone out, send the new one and say in one line what moved. Two mic changes and a new stage size are cheap to absorb in July. In the week of the show they are a different conversation, and it is far better to have that conversation on the phone than to discover it on site.








