Hospitality Rider vs Technical Rider: What's the Difference?

TL;DR — A technical rider explains what the performance needs to work: stage layout, audio, monitors, backline, power, lighting, crew, and technical timing. A hospitality rider covers the people around the performance: meals, drinks, dressing rooms, towels, transport, accommodation, security, and guest arrangements. Keep the sections separate enough for the correct teams to act, but advance them together so quantities, schedules, contacts, and responsibilities agree.

Table of contents

1. The difference in one table
2. What belongs in a technical rider
3. What belongs in a hospitality rider
4. Where requirements overlap
5. How to write and advance both
6. FAQ

The difference in one table

An artist rider describes requirements associated with a performance. Depending on the booking, its terms may be attached to or incorporated into the performance agreement. The contract and agreed amendments determine what is binding; the title of a document alone does not.

The split is organizational, not a reason to create conflicting documents. Both should use the same show date, venue, touring-party count, contacts, schedule, and revision.

What belongs in a technical rider

A technical rider answers: What must be provided, carried, connected, placed, staffed, and checked for this performance?

Stage and audio

Include:

• a stage plot with performer and equipment positions;
• a numbered input list with source, microphone or DI, stand, and notes;
• monitor destinations and mix labels;
• minimum usable stage dimensions where the setup depends on them;
• PA and system handoff requirements;
• FOH and monitor console requirements;
• input split, stage-rack, network, or analog loom details;
• talkback, playback, recording, or broadcast handoffs when used.

The plot and input list should agree. If Lead Vocal is input 17, use that name and number everywhere rather than changing it to Vox 1 in another table.

Backline, power, lighting, and crew

State:

• artist-carried and venue-provided backline;
• acceptable substitutions and who approves them;
• stage power locations and equipment loads;
• lighting or video needs that affect the show;
• required operators, stagehands, patch crew, or specialists;
• load-in, setup, line-check, soundcheck, and changeover durations;
• known constraints and a workable fallback.

Avoid unsupported superlatives such as professional PA or festival-standard lighting. Describe the necessary system, coverage, connections, control, and staffing instead.

For a complete structure, use the Tech Rider Template. Build detailed equipment responsibilities with Backline Rider Requirements.

What belongs in a hospitality rider

A hospitality rider answers: What do the artist and crew need before, during, and after the performance, and who will arrange it?

People and timing

Begin with a count that the promoter can act on:

This is an example format, not a universal entitlement. Use the actual touring party and update it when personnel change.

Food, drink, and dietary information

Specify:

• number of meals and service times;
• dietary restrictions and allergies stated accurately;
• water and reasonable backstage drinks;
• whether catering, a venue meal, or an agreed buyout applies;
• the person who confirms changes.

Write quantities and timing rather than a vague request for food for the band. Do not label a preference as an allergy, and do not assume a buyout unless it has been agreed.

Rooms, access, transport, and accommodation

Where relevant, document:

• dressing-room quantity, access time, keys, furniture, mirrors, and nearby toilets;
• secure storage and who can enter backstage;
• towels, showers, laundry, or production-office needs;
• local transport, pickup point, vehicle size, driver contact, and timing;
• hotel dates, room count and types, parking, late arrival, and accessibility;
• guest-list process and deadline;
• artist liaison, runner, or security responsibilities.

Only request what the touring party will use. Clear, proportionate requirements are easier to price, confirm, and deliver than copied lists from a larger tour.

Where requirements overlap

Some facts affect both production and hospitality:

Choose one owner for each shared fact. The tour manager or production manager can maintain the master schedule while department owners confirm their parts.

Do not bury technical show-stopping requirements inside a catering page. Likewise, keep private dietary, accommodation, and personal details out of a widely shared stage plot or public link.

How to write and advance both

1. Start from the confirmed booking

Record artist, venue, room, show date, promoter, performance length, touring-party count, and primary contacts. Mark items that are still provisional.

2. Separate requirements by responsible team

Put audio, stage, lighting, power, backline, and technical labor in the technical rider. Put catering, rooms, travel, lodging, and artist support in the hospitality rider.

3. Name provider and approval responsibility

For every material item, state:

• who brings or supplies it;
• quantity and exact requirement;
• when and where it is needed;
• who may approve a substitution;
• whether it is confirmed, pending, or unavailable.

Venue to provide one short boom stand at stage right is actionable. Please provide all necessary equipment is not.

4. Reconcile the rider with the venue

The rider states the touring requirement; the venue tech pack states available systems and constraints. Compare them during the advance, record substitutions, and obtain agreement rather than silently rewriting either source.

Use the Show Advance Checklist to reconcile contacts, access, schedule, stage, audio, power, hospitality, and the final handoff.

5. Issue one current revision

Add a revision date and owner. Remove requirements that no longer apply. When a confirmed change affects multiple departments, update every affected section and send a concise change summary.

For technical pages, invite collaborators to edit the same Rider, save updates, and inspect history. Export the agreed technical version as a PDF when a fixed copy is needed for the venue or show-day crew.

Common rider mistakes

Copying another artist's hospitality list. The headcount, budget, travel, and venue may be completely different.

Mixing preferences with requirements. Identify what is essential, what has an acceptable substitute, and what is optional.

Leaving responsibility implicit. Every expensive, scarce, or operationally important item needs a provider and approver.

Sending incompatible schedules. The technical rider cannot call soundcheck at the same time the hospitality rider schedules off-site transport.

Exposing personal information. Share dietary, hotel, phone, access, and security details only with people who need them.

Treating the first rider as the final agreement. Advance it, record exceptions, and circulate the confirmed revision.

Pre-send checklist

• Technical and hospitality sections use the same show facts and revision.
• Touring-party counts match meals, rooms, passes, and transport.
• Every technical input, output, monitor, backline item, and power need is clear.
• Dietary and accessibility needs are accurate and shared appropriately.
• Provider and approval responsibility are named.
• Schedule times do not conflict across departments.
• Required, preferred, and optional items are distinguished.
• Substitutions and unresolved items are recorded.
• Personal details are limited to the correct recipients.

FAQ

What is the difference between a technical rider and a hospitality rider?

A technical rider describes the stage, audio, monitors, backline, power, lighting, crew, and technical schedule needed for the performance. A hospitality rider covers people-focused arrangements such as meals, drinks, rooms, towels, transport, accommodation, access, and support.

What goes in a hospitality rider?

Include the real touring-party count, meal timing, dietary needs, water and drinks, dressing rooms, secure access, towels or showers when needed, transport, accommodation, guest-list process, security, and responsible contacts. Requirements should be proportional and specific.

What goes in a technical rider?

Include a stage plot, input list, monitor plan, PA and consoles, backline responsibilities, power, lighting or video needs, technical crew, access, setup and check times, connectors, providers, substitutions, and fallbacks.

Is a rider part of a performance contract?

It can be attached to or incorporated into a performance agreement, but arrangements vary. The signed contract, referenced rider version, and agreed written amendments determine the parties' obligations. Obtain qualified legal advice for a specific dispute or contract.

Should technical and hospitality riders be separate?

They may be separate documents or clearly labeled sections of one rider. Separate sections help the correct teams work efficiently, while shared show facts, contacts, schedule, revision, and confirmed changes must stay aligned.

Keep production and people aligned

Create the technical Rider in Techrider.live, connect the stage plot and input list, invite the production team to edit it, and export the agreed version for the show advance.

---

Last updated: 2026-07-29 · Reviewed for technical and hospitality scope, ownership, privacy, schedule alignment, and show-advance workflow.