Technical Rider Basics: Professional Documentation for Gigs

A technical rider communicates equipment and infrastructure requirements to venues. This document details everything needed to produce the show successfully, from PA specifications to power requirements to hospitality needs. Understanding technical rider basics helps bands create effective documentation that venues can actually fulfill.

Purpose of Technical Riders

Technical riders establish expectations before booking confirmation. Venues assess whether they can meet requirements before committing to the show. This prevents arrival at venues incapable of supporting the performance.

The document protects both band and venue. Bands avoid unsuitable venues; venues avoid surprise requirements they cannot meet. Written agreements on technical matters prevent day-of-show disputes.

Riders also demonstrate professionalism. Well-prepared documentation signals that the band takes performances seriously. Venue managers and engineers appreciate working with organized acts.

Core Sections

PA system requirements specify the sound reinforcement needed for the performance. Front of house speakers, monitor systems, and any special requirements belong here. State realistic minimums rather than ambitious ideals.

Mixer requirements specify channel count, auxiliary send count, and any needed features. “32-channel mixer with 8 auxiliary sends” communicates basic needs. Digital mixer preferences, specific models, or must-have features may be included if critical.

Microphone and DI requirements list what the venue should provide. Reference the input list for detailed channel-by-channel specifications. The rider may summarize: “See attached input list. Venue to provide all microphones and DI boxes as specified.”

Backline requirements specify any equipment the venue provides. Drum kits, amplifiers, keyboards, and stands commonly appear on backline lists. Be specific: “5-piece drum kit with 22-inch kick, snare, hi-hat stand, two crash stands, ride stand” leaves less to interpretation than “standard drum kit.”

Stage Requirements

Stage dimensions specify minimum acceptable performance space. State width, depth, and any height requirements. Consider actual positioning needs rather than aspirational requests.

Lighting requirements may be minimal for bands focused on sound. Basic wash lighting and front lighting prevent performing in darkness. Specific lighting designs require detailed documentation beyond basic rider content.

Power requirements specify electrical service needed. State total amperage required and number of circuits. Note any three-phase power needs for high-power situations. Location of power drops may reference the stage plot.

Monitor Requirements

Monitor system specifications detail stage monitoring needs. Number of monitor mixes, number of wedges per mix, and any special requirements belong here.

In-ear monitoring requirements specify whether the band provides their own system or expects venue support. IEM systems provided by venues require specification of transmitter and receiver models, earphone provisions, and antenna systems.

Side fill and drum fill needs may exceed basic wedge specifications. Large stages may require substantial side fill systems for adequate coverage.

Sound Engineer Provisions

Some riders specify whether the band carries their own engineer or requires venue staff. “Band will provide own FOH engineer; venue to provide qualified monitor engineer” clarifies responsibilities.

Communication systems between stage and FOH may be specified. Intercom, wireless belt packs, or other communication tools facilitate smooth shows.

Soundcheck time requirements state minimum adequate preparation time. “60-minute soundcheck with full band” establishes expectations. Some venues schedule tightly; stating requirements prevents inadequate soundcheck allocation.

Hospitality Section

Hospitality requests address non-technical needs. Dressing rooms, parking, meal provisions, and beverage requirements appear here. Keep requests reasonable; excessive hospitality demands damage professional reputation.

Load-in and access requirements specify door sizes, loading dock availability, elevator needs, and parking for equipment vehicles. These practical details prevent arrival surprises.

Guest list procedures, credential requirements, and security considerations may appear in riders for larger productions.

Writing Effective Riders

Match requirements to career level and venue type. A club band requesting touring production level support appears unrealistic. Requirements should reflect what similar bands at similar venues typically expect.

Distinguish between requirements and preferences. “Must have” items represent deal-breakers; “preferred” items accept alternatives. This distinction helps venues assess whether they can accommodate the performance.

Update riders as needs evolve. Band growth, equipment changes, and learned lessons from problematic shows inform revisions. Annual review ensures current documentation.

Formatting Standards

Professional presentation builds credibility. Clean layout, consistent formatting, and error-free text suggest attention to detail. Sloppy riders suggest sloppy production.

Include contact information prominently. Phone number and email for technical contact enables questions before problems become emergencies.

Date and version documentation prevents outdated rider circulation. Clear file naming and document dating maintain currency.

PDF format ensures consistent appearance across different computers and software. Editable formats may display differently on recipient systems.

Common Mistakes

Excessive requirements alienate venues. Requesting 48-channel digital mixers for 8-input bands suggests unfamiliarity with industry norms.

Vague specifications leave too much to interpretation. “Adequate PA” means different things to different people. Specific parameters prevent misunderstandings.

Forgetting essentials while including luxuries reflects poor priorities. Nail the technical fundamentals before requesting hospitality extras.

Assuming venues provide everything the band uses leads to disappointment. If the band relies on specific equipment, either carry it or specify it explicitly in the rider.

Inflexibility damages relationships. Reasonable alternatives accommodate venue limitations while maintaining show quality. “Or equivalent” language allows acceptable substitutions.