Performance Rider Generator

Create organized technical hospitality travel and production requirements for performers while assigning responsibilities priorities approvals and exportable event documentation for venues clearly and efficiently.

1. Performer and Event Details

Required fields marked *
Preset values can be edited after loading.

2. Performance, Stage and Timing

3. Audio, Input List and Backline

Input List

SourceMic / DIStand48VNotes

4. Lighting, Video and Power

5. Hospitality, Dressing Rooms and Travel

6. Load-In, Crew, Security and Merchandise

7. Accessibility, Effects and Venue Information

8. Stage Plot Builder

Performer / EquipmentPositionDetails

9. Responsibility and Priority Matrix

ItemProviderPriority

10. Custom Requirements, Revision and Approval

PDF becomes available after generating the rider. CSV exports event, technical, hospitality, input-list, and responsibility data.

How a Performance Rider Helps Event Production

A performance rider turns artist expectations into practical event instructions. It gives promoters and venues one reference for technical, hospitality, travel, security, and scheduling needs. Clear requirements reduce last-minute questions and help production teams prepare equipment before arrival. A rider should identify which requests are mandatory and which remain negotiable. This distinction helps both sides focus on essential show conditions first.

Technical details usually cover stage dimensions, audio, lighting, power, backline, video, and crew support. An input list explains each channel, microphone, stand, and phantom-power requirement. A stage plot adds visual context by showing performer and equipment positions. Together, these details help engineers plan patching, monitoring, cable runs, and changeovers. Outdoor performances should also address weather protection and safe power distribution.

Hospitality, Travel, and Venue Coordination

Hospitality requirements should stay specific and reasonable. Typical sections include meals, beverages, dressing rooms, towels, parking, transport, hotels, and Wi-Fi. Dietary needs should be written clearly because they affect purchasing and catering preparation. Security details may define backstage access, credentials, barriers, escorts, and vehicle protection. Merchandise requirements can clarify table space, power, staffing, commissions, and settlement procedures.

A useful rider also assigns responsibility for every important item. The venue may supply production equipment while the promoter handles hotels and transport. The artist may bring instruments, playback devices, or specialty equipment. Responsibility tables prevent assumptions and make negotiations easier to document. Revision numbers and issue dates also prevent teams from working from outdated versions.

Final Review and Approval

Before sending a rider, confirm event details and remove irrelevant requests. Mark safety-sensitive effects for venue approval and local compliance. Accessibility needs deserve the same visibility as technical requirements. Add contact details for production questions and emergencies. Finally, record representative names and acceptance dates when agreements are finalized. A concise rider supports smoother communication throughout event production. Good documentation helps crews deliver consistent shows across venues.

Example Performance Rider Requirements

CategoryExample RequirementTypical ProviderPriority
AudioProfessional PA with four monitor mixesVenueMandatory
StageMinimum 24 × 16 foot performance areaVenueMandatory
HospitalityHot meal and drinking water for touring partyPromoterPreferred
BacklineQuality drum kit with hardwareVenue or rentalNegotiable
SecurityCredentialed backstage accessVenueMandatory
MerchandiseSix-foot table near main audience trafficVenuePreferred

Frequently Asked Questions

What is a performance rider?

A performance rider documents operational requirements connected to an engagement. It commonly covers production, hospitality, travel, security, and venue responsibilities.

Are all rider requests mandatory?

No. A strong rider separates mandatory requirements from preferred, optional, or negotiable requests. Contract terms determine what becomes binding.

What should an input list contain?

An input list normally includes channel order, source, microphone or DI choice, stand requirements, phantom power, and engineering notes.

Why include a stage plot?

A stage plot shows where performers, instruments, monitors, risers, and equipment belong. It helps venue crews prepare before soundcheck begins.

When should a rider be sent?

Send it early enough for equipment sourcing and technical review. Larger productions usually require more preparation than simple performances.

Can venues request changes?

Yes. Venues may propose alternatives when equipment, safety rules, laws, or building limitations affect requested arrangements.

How does PDF download work?

Generate the rider first, then use the PDF button. The browser creates a formatted PDF from the generated rider preview.

What is included in the CSV file?

The CSV contains key event details, technical requirements, input-list rows, hospitality needs, and responsibility assignments for spreadsheet use.


Related Calculators

Magic Trick Idea GeneratorCircus Act Sequence GeneratorJuggling Pattern GeneratorMagician Stage Name GeneratorIllusion Concept GeneratorClown Act Idea GeneratorAerial Silk Routine GeneratorAcrobatic Routine GeneratorVentriloquist Script GeneratorPuppet Show Script Generator

Important Note: All the Calculators listed in this site are for educational purpose only and we do not guarentee the accuracy of results. Please do consult with other sources as well.