Lighting Tech Rider Requirements: Plot, Control, and Handoffs

TL;DR — A lighting tech rider should describe the show’s visual needs and the handoff required to deliver them: performance areas, lighting positions, fixture functions, control and patch, power, atmosphere, operator, programming time, cues, and safety responsibilities. Separate hard requirements from preferences, reconcile the request with the venue’s current inventory and restrictions, and record the accepted design instead of sending an unexplained fixture wish list.

Table of contents

1. Define the visual result
2. Build the lighting information package
3. Document control, patch, and power
4. Advance staffing, atmosphere, and cues
5. Verify the show-day handoff
6. FAQ

Define the visual result

A lighting tech rider is the section of a technical rider that communicates the artist’s lighting design, equipment, control, staffing, schedule, and venue interfaces. It may include a lighting plot and patch, but the rider also explains why each system is needed and who makes decisions when the requested design cannot fit the room.

Start with the performance rather than a copied equipment list:

• lineup, positions, risers, and movement areas;
• visual character, color limitations, and essential looks;
• moments that need isolation, audience light, or blackout;
• scenic, video, practical, or special-effect interactions;
• minimum visibility needed for entrances, exits, instruments, and cueing;
• whether the artist carries a design, console, show file, fixtures, or operator;
• what the venue or supplier must provide.

Label each item as a requirement, preference, or advance question. A fixture type may be a preference when another unit can produce the needed beam, color, output, position, and control. A safe illuminated exit path is not an artistic preference and remains under venue authority.

Build the lighting information package

Lighting plot

The plot should use a consistent stage orientation and show:

• stage outline and usable dimensions;
• downstage edge, upstage edge, centerline, stage left, and stage right;
• performer, backline, riser, scenic, and video positions;
• overhead, side, floor, balcony, or front-of-house lighting positions;
• fixture identifiers and intended functions;
• focus or coverage areas where they are essential;
• cable, floor-package, and control locations that affect stage use;
• a revision date and drawing scale or clearly marked dimensions.

Keep the lighting plot aligned with the artist’s stage plot. If a riser, keyboard, DJ table, or playback rack moves, both documents may need revision.

Fixture and responsibility schedule

Use a schedule that production can turn into a quote and patch.

Replace general phrases such as full professional lighting rig with usable functions. If an exact model or mode is essential because of a show file, accessory, optical behavior, or control footprint, state that reason and name the person authorized to approve a substitute.

Color, focus, and cue information

Document any color restrictions, front-light preference, focus areas, shutter cuts, practicals, and audience-light needs. Then provide one of these cue workflows:

1. touring operator runs an advanced show file;
2. touring designer programs on the house system;
3. house operator follows a cue sheet and artist direction;
4. house operator creates suitable looks from a set list and briefing.

Do not call a show fully time-coded unless the playback, timecode format, distribution, console workflow, and fallback have actually been advanced.

Document control, patch, and power

Console and show file

Record:

• console platform and confirmed software version;
• whether the artist carries hardware or supplies a show file;
• available control outputs and required gateways or nodes;
• venue network boundary and who configures it;
• universe allocation and patch ownership;
• external trigger or timecode interfaces, if used;
• backup and recovery process;
• operator position, sightline, communication, power, and footprint.

A DMX universe carries 512 control addresses, but a fixture may use multiple addresses depending on its selected operating mode. Therefore, a usable patch identifies fixture type, mode, universe, and start address—not only a channel number.

Patch and equipment data

For each controlled device, keep these fields together:

Do not allocate addresses around an assumed fixture mode. A mode change can change the footprint and create overlaps, so the supplier or lighting lead should validate the final patch.

Power and distribution

State carried equipment loads and connection requirements, then let the venue or qualified supplier design and approve distribution. Confirm:

• provider for fixtures, dimmers, distribution, cabling, and adapters;
• available service and system compatibility;
• location of power and data handoffs;
• separation from audio or video systems where required by the site design;
• cable routes and protection;
• who installs, tests, and operates the system.

Do not request improvised power connections or prescribe work beyond the touring party’s authority. Coordinate stage-level needs with Stage Power Requirements, and leave electrical and structural decisions to qualified responsible parties.

Advance staffing, atmosphere, and cues

Name every operator and decision owner

Clarify who supplies and supervises:

• lighting designer or touring operator;
• house lighting operator;
• programmer;
• lighting crew and followspot operators, if required;
• rigger and electrical personnel;
• equipment supplier contact;
• production manager who accepts design changes.

State call times, programming access, focus time, rehearsal or soundcheck access, doors, show, curfew, and restore requirements. A sophisticated rig without enough access time may be less useful than a simpler confirmed design.

Haze and atmospheric effects

Treat haze, smoke, pyrotechnics, lasers, flame, confetti, and similar effects as separate approval items. For haze, confirm venue permission, device and fluid provider, fire-alarm procedure managed by the venue, operating limits, ventilation considerations, and who may run it. Never imply that an artist can disable safety systems.

For any regulated or hazardous effect, use properly qualified suppliers and obtain all venue and authority approvals. If approval is absent, record a lighting-only fallback.

Cue handoff

A concise cue sheet can include:

Use observable triggers rather than vague timing such as near the end. If cues are called by intercom, identify the calling position and communication path.

Advance and verify the lighting

Pre-send checklist

• Visual goals and essential performance areas are clear.
• Plot orientation, dimensions, positions, and revision date are present.
• Fixture requests describe function and essential attributes.
• Artist-carried, venue, and supplier responsibilities are separated.
• Console, version, show-file, control, patch, and backup are advanced.
• Fixture modes, universes, and addresses have a final owner.
• Power, rigging, cable routing, and safety remain with qualified parties.
• Haze and other effects have explicit approval or a fallback.
• Operator, crew, programming, focus, and show call times are confirmed.
• Lighting information matches the stage plot, schedule, and venue tech pack.

Show-day handoff

Before programming or focus, compare the installed rig with the accepted plot and patch. Confirm equipment, modes, addresses, positions, accessories, console version, network boundary, control outputs, and operator communication. Test work lights, show control, blackout behavior, and the agreed recovery path under venue supervision.

Record material substitutions and cue changes in the current production package. Use the Show Advance Checklist to keep approvals and due dates attached to named owners.

Common lighting-rider mistakes

Sending only a fixture list. It does not explain positions, purpose, control, staffing, or acceptable substitutions.

Treating the house inventory as guaranteed. Confirm the current installed and available package for the event date.

Omitting fixture modes. Model and address are insufficient when different modes use different control footprints.

Ignoring programming time. Access, patch verification, focus, and cue rehearsal must fit the production schedule.

Assuming atmosphere is permitted. Obtain explicit venue approval and prepare a no-haze or no-effect version.

Letting the lighting and stage plots drift. A visually elegant design still fails if it conflicts with performers, risers, cables, or sightlines.

FAQ

What should a lighting tech rider include?

Include visual goals, stage and lighting plots, fixture functions and quantities, positions, control console, software and show-file workflow, fixture modes and patch ownership, power and data handoffs, staffing, schedule, cues, atmosphere approvals, safety responsibility, substitutes, and revision date.

How do you write lighting requirements for a band?

Describe the required looks and performance areas first. Then list the equipment and control needed to create them, separating essentials from preferences. Assign providers and approval owners, reconcile the request with the venue package, and publish the accepted design.

Does a band need a lighting plot?

A simple act can often use the venue’s standard rig with a stage plot, set list, color preferences, and cue notes. A lighting plot becomes useful when positions, specials, floor fixtures, scenery, carried equipment, or a programmed design must be reproduced.

What is a lighting patch in a tech rider?

A lighting patch maps each controlled device to its console channel or fixture ID, device type and mode, control universe, start address, and often its physical position or circuit. It lets the operator connect the control file to the installed rig.

Who operates lighting at a concert?

The touring lighting operator, a house operator, or a locally supplied operator may run the show. The rider should name the operator, console workflow, cue method, programming access, and the person who approves changes.

Keep lighting connected to the production plan

Build the stage plot and technical package in Techrider.live, invite the production manager or lighting lead to edit and save the same Rider, inspect history after revisions, and share the confirmed handoff with the venue.

---

Last updated: 2026-08-03 · Reviewed for lighting plots, fixture schedules, control patching, power handoffs, staffing, atmosphere, cues, and production advance.