The word has a bad reputation, mostly from stories about touring bands and bowls of sweets. That reputation costs working performers real money, because it stops them writing the one document that reliably prevents the evening going wrong.
A rider is not a list of demands. It is a specification. It says what has to be true at the venue for the performance the client is paying for to actually happen, and it exists so that both of you find out about a problem four weeks early rather than forty minutes before the first guest arrives.
It Is Really Two Documents
The technical rider
Everything about sound, power and space. This is the half that prevents disasters.
- An input list. Every source that needs a channel — each vocal, each instrument, each playback feed. A client cannot guess this and a sound supplier cannot quote without it.
- A stage plot. A simple drawing of who stands where, which side the drums are on, and where the power sockets need to be. Hand-drawn and photographed is completely acceptable; the point is that the person setting up has seen it.
- Monitoring. How many monitor mixes you need, or whether you use in-ears. The most common reason a singer sounds flat is that they could not hear themselves.
- Space and power. Minimum stage area, and how many independent power outlets you need at the stage position. If your rig draws heavily, say so — a circuit shared with the catering is a real hazard.
- What you bring versus what you need supplied. The single most valuable line in the whole document, and the one most often missing. Write it as two lists.
- Timings. How long you need for load-in, setup and sound check, and how long load-out takes. Clients plan schedules; give them the numbers to plan with.
The hospitality rider
Everything about the human beings. Not indulgence — the practical minimum for people who will be on site far longer than they are on stage.
- A room to change and wait in, secure enough to leave instrument cases in.
- Drinking water at the stage.
- A meal if the call is longer than about five hours, and any dietary requirements stated once, up front.
- Parking, and how close the vehicle can get to the load-in door.
- Accommodation and travel, where the booking involves either — including how many rooms and for how many nights, since that is a real cost the client must plan for.
Being specific here reads as professional, not difficult. Being vague and then unhappy on the day reads as the opposite.
How to Write One That Actually Gets Read
One page. A rider that runs to six pages will be filed and not read, and you will have the argument anyway. If yours is long, it is because you are describing an ideal rather than a requirement.
Put the deal-breakers at the top. Three lines, before anything else, stating the things without which the performance genuinely cannot happen. Everything below them is preference and should be marked as such. A client who knows which is which will fight for the right three.
Separate essential from preferred, explicitly. Two columns or two headings. This is the difference between a document that helps a client and a document that makes them defensive.
Write it in plain language. The person reading it is often an event coordinator, a bride's cousin, or an office administrator, not a sound engineer. "Two speakers on stands, one on each side of the stage, raised above head height" is more useful than a model number.
Send it at confirmation, not the week of. A rider is only useful while there is still time to fix what it reveals. Sending it three days out converts a specification into a complaint.
The Two Common Mistakes
Copying a touring band's rider from the internet. These circulate widely and they are written for a completely different scale of production. Sending one to a wedding family makes you look inexperienced and creates a conversation about why you need something you do not need.
Having none at all. Far more common, and more costly. Without a rider, every technical requirement gets communicated verbally, on the day, to whoever is standing nearby — and when it turns out there are no monitors, it is your performance that suffers and your reputation that carries it.
Riders for Solo and Small Acts
If you are one person with a guitar, you still need a rider. It is shorter, and it is arguably more important, because clients booking a solo act frequently assume no equipment is involved at all. Four lines will do: what you bring, what you need supplied, how much time you need, and how much space. That document has saved more small gigs than any amount of negotiation on the day.
Where It Lives on idlidu
Be clear about this, because an earlier version of the site implied otherwise: there is no rider upload field on an artist profile. What there is, is a message thread attached to every booking, and that is where the document belongs — sent at the point the booking is confirmed, so it sits with the date, the venue, the duration and the agreed price rather than in an email neither of you can find in March.
Your public profile carries your instruments, genres, experience, portfolio and rate. The rider is the operational half, and it goes to the client who has actually booked you. For what to do with everything after it is agreed, the day-of runsheet is the client's half of the same conversation, and how much sound a room needs explains the reasoning behind the technical lines you are writing.
One last note on tone. A rider is a service to your client, and framing it that way in the covering message changes how it is received: "here is everything your venue needs to know, so nothing about the stage gets decided on the day." Nobody argues with that sentence — the same reframe that makes the deposit conversation easy.