Tour Riders Explained

A tour rider is a set of advance requests that tells a venue or production team what your performance needs. It helps the people preparing the show understand your stage setup, sound requirements, equipment, schedule, access needs, and agreed hospitality. For an emerging artist, a good rider is not a test of how many demands you can make. It is a current, event-specific production brief that reduces uncertainty and gives everyone a shared plan before load-in.

The most useful rider is clear, realistic, and negotiable. It distinguishes what is essential from what is preferred, identifies what the artist will bring, and makes clear what the venue or purchaser is expected to provide. A rider may be a separate document or an addendum referred to by the performance agreement. Its contractual effect depends on whether the governing agreement incorporates it and the relevant parties agree to it; the label “rider” alone does not establish legal effect. Terminology and contract effect vary across jurisdictions, venues, and deal forms. Live Engagement Standard Contracts

This article is educational information about common live-performance practice. It is not individualized legal, financial, tax, contract, or royalty advice.

What a rider does

A rider communicates practical information in advance. Instead of waiting until the band arrives to explain where each musician stands, which instruments need microphones, what equipment is coming with the act, or whether someone needs a particular access arrangement, the artist sends the information ahead of time. The venue, promoter, house engineer, production manager, or other responsible team can then review it and confirm what is available.

The word “rider” can cover more than one kind of document. A technical rider focuses on the performance system: the stage, microphones, inputs, monitors, power, cables, desk, and backline. A hospitality or subsistence section covers items such as food, drinks, a buyout, or accommodation. An access rider communicates specific requirements that help a disabled musician or other performer work safely and effectively. A contract rider or addendum may record agreed details alongside the main booking agreement.

These categories can be combined into one package or circulated as separate documents. The important point is not the document’s title. The important point is that the people responsible for the event know what has been requested, what has been confirmed, and what remains to be negotiated. The Musicians’ Union describes riders as advance requests usually fulfilled by venues and recommends that requirements be specific, clear, and communicated with information about timing, negotiability, and any technology or support needed. Access Riders for Musicians

The technical rider: your performance map

For most bands and live acts, the technical package has three core parts: a stage plot or stage plan, an input or channel list, and an equipment or backline list. They may appear on separate pages or in one document. Together, they give the production team a visual and technical map of the show. What is a Technical Rider and why do I need one?

1. Stage plot or stage plan

A stage plot shows the act from the audience’s perspective or from a clearly labelled overhead view. It should show where performers and instruments are positioned. Depending on the act, it can also identify microphones, direct boxes, monitors, cables, power requirements, and which items are supplied by the artist or the venue.

For a small emerging act, the plot might show a vocalist at centre stage, guitar and vocal stage left, bass stage right, and drums upstage. It can mark each musician’s monitor position, the location of amplifiers, the keyboard or playback table, and any power points needed. If an instrument is supplied by the artist, label it. If the venue is expected to provide a microphone, stand, DI, cable, monitor, or backline item, label that too.

A plot does not need to be artistically impressive. It needs to be readable under pressure. Use names or instrument labels rather than assumptions. If “keys” means a keyboard, laptop, audio interface, and stereo DI, say so. If a drummer brings cymbals but needs the venue’s shells and hardware, make the division visible.

2. Input or channel list

The input list translates the stage setup into information for the sound team. It can identify the sound source, channel order, microphone or DI requirement, XLR connection, phantom-power note, preferred microphone, and stand type. The list should make it possible for an engineer to understand what reaches the desk and how many inputs are needed. Tech Specs and Stage Plots

A simple list might include:

• Lead vocal: microphone, boom stand, XLR.
• Guitar amplifier: microphone, short stand, XLR.
• Bass: DI, XLR, with the artist’s pedalboard.
• Keyboard left and right: two DI channels or another clearly stated stereo solution.
• Kick, snare, and overheads: microphones and stands, if the venue is providing the drum-miking package.

These examples illustrate the kind of information to communicate, not a universal minimum or required equipment list. Your actual inputs should match your current show. If you changed from mono playback to stereo, added a vocalist, removed an amplifier, or replaced an instrument, update the document.

Phantom power deserves careful wording. State where a DI or microphone requires +48V, where it does not, and whether the artist’s equipment has a specific connection requirement. Do not leave the engineer to infer whether “keyboard” means one channel or two. If a preferred microphone is unavailable, identify a technically acceptable substitute when you can. Illustrative production riders show how artists may distinguish preferred and substitute equipment and specify venue obligations, inputs, power, microphones, stands, and backline. Pierce Freelon Tech Rider

3. Equipment and backline list

The equipment list answers a practical question: who is bringing what? Backline can include instruments, amplifiers, drum kits, keyboards, stands, benches, pedalboard support, and other performance equipment. A rider can identify artist-provided gear, venue-provided gear, and acceptable substitutions.

Be precise about shared equipment. For example, “drums” is less useful than “five-piece acoustic kit with kick pedal, hi-hat stand, cymbal stands, throne, and hardware; artist brings cymbals and snare.” If you need a specific amplifier configuration, list the required function and then identify whether a comparable substitute can work. If substitutions must be approved before the event, say that in the agreed production terms rather than assuming the venue will know.

The same principle applies to power. Note the equipment that needs power and any unusual power or placement requirement. Include IEMs or monitor needs when relevant. The technical guidance from the Musicians’ Union includes positions, DI/XLR/+48V notes, microphone and stand details, power, IEMs, and monitors among the information that may belong in current technical specifications. Tech Specs and Stage Plots

Riders also cover the advance, not just the stage

A rider is more useful when it connects the technical plan to the event schedule. Before travelling, confirm load-in and load-out arrangements, parking, backline, the sound desk, soundcheck, doors, performance timing, subsistence, and access. These are booking details that can affect whether the show is workable even when the stage plot is perfect. Engagement Booking for Unsigned and Emerging Artists

A practical advance checklist might look like this:

1. Confirm the event date, venue, room, contact person, and current production contact.
2. Confirm the load-in time, route into the venue, stairs or lifts, parking or unloading arrangements, and where the vehicle can remain.
3. Confirm what backline is available, what condition or configuration is expected, and what the artist must bring.
4. Confirm the sound desk, house system, monitor arrangement, and whether the supplied system can support the input list.
5. Confirm soundcheck timing, doors, set time, changeover, and expected finish.
6. Confirm food, drinks, buyout, accommodation, or other subsistence terms where they have been agreed.
7. Confirm access requirements, including timing, support, technology, and any arrangement that must be in place before arrival.
8. Send the current technical documents and ask the responsible person to confirm receipt and flag conflicts.

The Musicians’ Union gives an example of details to agree in advance, including load-in and load-out, access, parking, backline, soundcheck, performance timing, doors, and food or drinks arrangements. Its example timing should not be treated as a universal rule: the packet supports the need to clarify these matters, not a single mandatory advance deadline. Engagement Booking for Unsigned and Emerging Artists

Hospitality and subsistence: ask clearly, expect negotiation

Hospitality is often the most misunderstood part of a rider. Food, drinks, a buyout, accommodation, dressing-room arrangements, and sometimes transport can appear in broader rider practice. But there is no universal hospitality entitlement supported by the evidence here. These are negotiable booking terms, and what is realistic depends on the event, budget, travel, deal, and agreement.

For an emerging artist, ask for what materially supports the performance. If the act is travelling through a meal period, state the number of people, dietary requirements, arrival timing, and whether food or a buyout is preferred. If accommodation is needed because of the schedule or distance, state the number of rooms or people and ask what is available. Avoid vague wording such as “proper hospitality.” A venue can respond more usefully to a specific request with a clear fallback.

For example: “Four people travelling; vegetarian and allergy information attached; please confirm hot meal or agreed buyout; arrival at 5:00 p.m.; water available backstage.” That is easier to accept, amend, or decline than an open-ended list. A request is not confirmed merely because it appears in a PDF. Make sure the parties understand which items are agreed and how they relate to the booking terms. Letting It Ride

Access requirements belong in the plan

Access needs should be communicated as early and specifically as possible. They can concern arrival, movement through the venue, stage access, timing, communication, technology, or support. Explain what is required, when it is required, and whether an alternative arrangement could work. If a request is negotiable, identify the negotiable part; if it is essential for the performer to work, describe the practical consequence of not having it.

Specific information helps a venue act. “Accessible access needed” may not tell the team whether the issue concerns the load-in route, a lift, a ramp, a seated rest area, accessible toilet access, stage height, or a support person. The appropriate details will differ from artist to artist. The purpose of the access section is not to make a demand sound formal. It is to give the venue enough information to prepare and to identify problems before the day of the show. Access Riders for Musicians

Access requirements and legal entitlements are not the same question. The evidence packet includes UK guidance, but the article covers mixed UK, Ireland, and United States practice. Do not assume that a statement in a rider determines legal entitlement in another jurisdiction. Confirm the practical arrangement with the venue and obtain any necessary agreement in writing.

How to make an emerging-artist rider realistic

Start with the show you are actually performing, not the largest production you hope to have someday. Build the technical document from your current personnel, instruments, tracks, and monitor needs. Separate “must have” from “preferred.” A must-have item is necessary for the performance to function safely or musically. A preferred item improves the show but may have an acceptable substitute.

A realistic rider should also show flexibility without hiding important requirements. “Preferred microphone: X; acceptable substitute: equivalent dynamic vocal microphone” gives the engineer a decision path. “Artist brings pedalboard and cables; venue provides vocal microphone, stands, house PA, and two monitor mixes, subject to confirmation” makes the division of responsibility visible. The exact number of monitors or mixes is not a universal emerging-artist benchmark, so request what your act genuinely needs and be prepared to discuss alternatives.

Keep the package short enough to use, but complete enough to prevent avoidable questions. One or two clear pages may be appropriate for a small act, while a larger production may need more detail. There is no authoritative universal page count, monitor count, hospitality list, or emerging-artist request benchmark. The right scope varies with the act, venue, production, and agreement. Illustrative riders range from compact technical documents to detailed, quantified production requirements. Berlin — Australia Technical Rider 2023

The document should carry a version date or event identifier. Send an event-specific, current version early enough for the venue and production team to prepare. Do not send last season’s rider unchanged if the lineup, inputs, instruments, or access needs have changed. The technical guidance specifically emphasizes accuracy, currency, event specificity, and early circulation; it does not establish one universal deadline. Tech Specs and Stage Plots

A worked example

Imagine a four-piece emerging band playing a club show. The band has lead vocal and guitar, bass, drums, and a backing track from a laptop. The guitarist brings a pedalboard and amplifier. The bassist brings a pedalboard but wants the venue’s DI or a confirmed equivalent. The drummer brings cymbals and snare but needs the venue’s kit, hardware, and throne. The band wants a soundcheck before doors, two front monitors, and a clear load-in route.

The band’s rider could communicate the following:

• Stage plot: vocalist/guitar centre-left, bass stage right, drums upstage, laptop table near the vocalist, amplifier positions, two monitor positions, and power locations.
• Input list: vocal microphone, guitar amplifier microphone, bass DI, kick, snare, two overheads, and stereo playback, with each channel labelled.
• Equipment list: artist-provided guitar, bass, pedalboards, amplifier, cymbals, snare, laptop, and playback interface; venue-provided drum kit, hardware, vocal microphone, stands, DIs, PA, desk, and monitors, subject to confirmation.
• Advance: load-in time and route, parking or unloading instructions, soundcheck time, doors, set time, changeover, and load-out plan.
• Hospitality: water backstage and a confirmed meal or buyout if included in the booking terms.
• Access: any specific arrival, movement, communication, technology, or support arrangement required by a member of the band.

The band should then ask the venue or promoter to confirm what is available and identify substitutions before travel. If the venue cannot provide stereo playback, the band can decide whether mono is acceptable. If only one monitor mix is available, the band can decide whether to simplify its request or change the arrangement. The rider creates a route to that conversation; it does not eliminate the need for one.

What to send and what to confirm

Send the rider to the person advancing the show, using the contact supplied by the promoter or venue. Include the event name and date in the filename and document title. If the technical information is separate from hospitality or contract details, label the files clearly. Keep a copy that matches the version sent.

Ask for confirmation of the items that could stop the performance from working: inputs, power, monitors, backline, desk, soundcheck, load-in, access, and any agreed subsistence. If the venue proposes a substitution, record the result. If the rider is intended to form part of the deal, make sure the main agreement refers to the relevant addendum and that the parties agree to it. A separate sheet labelled “rider to contract” can contain additional details when the contract refers to that addendum, but the label by itself is not the source of contractual force. Live Engagement Standard Contracts

The final check is simple: could a house engineer, production manager, or venue contact use this document without calling you to decode it? If not, revise it. Remove obsolete gear, clarify ambiguous terms, identify who supplies each item, mark preferences and essentials, and update the event details.

Bottom line

A rider is a communication tool for making a show possible. Build it around three technical documents—stage plot, input list, and equipment or backline list—then add the advance information, hospitality terms, and access requirements relevant to that event. Send a current, event-specific version early, ask for confirmation, and keep requests specific and negotiable where appropriate.

There is no universal rider size or emerging-artist entitlement. A useful rider is one that accurately describes your performance, respects the limits of the event, and turns assumptions into confirmed arrangements. Because this evidence combines UK, Irish, and United States sources, and because contract effect varies by governing law and signed agreement, treat the rider as educational production guidance and confirm the actual terms for each booking.