Build concert lights for touring bands as a measured system, not a collection of small fixtures. Start with the visual jobs the show must preserve, then document every packed case, the real van space, the crew workflow, repeatable control, and the venue resources that remain conditional.
In this guide, lightweight and fits in a van are project targets. They become defensible only after the complete package is measured, loaded, deployed, tested, struck, and approved for the actual vehicle, crew, route, and venues. There is no universal fixture count, cargo cube, payload, setup time, or crew size.
How this guide selects a touring light rig
This is a SHEHDS-owned guide using current first-party and authoritative sources, not an independent transport, vibration, photometric, or long-term reliability test.
| Step | Rule |
|---|---|
| Include | Give the candidate a defined show job and require current product, packed-system, control, power, handling, and venue evidence. |
| Exclude | Remove choices with unresolved variants, cases, profiles, access, infrastructure, handling, or no useful reduced-mode role. |
| Verify | Score the complete system, rehearse it with the actual crew and path, then approve full, reduced, and fallback modes. |
Candidates cover current SHEHDS band-lighting, PAR, wash, moving-head, controller, and accessory categories. The project score weights packed burden 25%, core visual role 20%, setup and crew 20%, control repeatability 15%, power and venue fit 10%, and redundancy and serviceability 10%. Evidence covers the formal corpus through August 11, 2026, and public sources through August 17, 2026. Price and availability are purchase-time checks, not ranking inputs.
Define van-friendly with a complete acceptance record
Bare fixture dimensions and net weight cannot establish tour fit. The record must include each complete case, accessories, actual cargo opening and usable space, competing backline and merchandise, vehicle limits supplied by the responsible owner, crew handling, the access route, setup dependencies, and a real dry run.
| Claim | Required evidence | Approval owner |
| Compact package | Complete packed dimensions, case count, and access measurements | Tour logistics owner |
| Lightweight package | Verified complete mass, contents, handling method, and crew acceptance | Responsible tour and handling owners |
| Fits in the van | Actual load plan, other cargo, vehicle limits, and successful measured trial | Responsible vehicle owner |
For United States road use, NHTSA advises securing cargo, avoiding excessive loads, and checking the load again. That guidance is not vehicle engineering. The actual vehicle limits, approved restraint method, and applicable law still govern.
Separate the touring core from the house enhancement
Carry the visual jobs that protect the band's identity when the venue offers very little. Treat the house rig as an enhancement only after it is advanced and confirmed.
| Visual job | Tour carries | Venue supplies | Must confirm | Fallback |
| Stable performer or stage wash | Documented core wash group when this role is essential | Compatible front or stage wash if available | Positions, throw, control, power, color, and operator | Stable tour-carried wash look |
| Scenic separation | Compact back or side color when it earns space | House backlight or scenic fixtures | Approved positions, sightlines, cameras, and haze policy | Simplified color state |
| Movement, beam, or gobo | Only when the scorecard and venue range justify it | Compatible house movers | Profiles, modes, positions, control access, and rehearsal | Remove the layer from reduced mode |
| Audience or atmosphere effect | Usually conditional | Venue-approved resource | Local rules, exposure, haze, cameras, and ownership | Omit the effect |
Use band stage lighting to compare categories only after these roles and fallbacks are defined. Do not assume a venue provides front light, haze, crew, positions, control, or compatible fixtures.
Build a case-level van-cube manifest
Give every case, trunk, stand, controller, cable kit, clamp, spare, and tool a line in the manifest. That makes support equipment visible before a fixture wins cargo space.
| Case or item | Contents and exact variants | Packed dimensions and mass | Handling | Load order and vehicle position | Show job | Setup dependency | Owner |
| Fixture case | Units, brackets, clamps, foam, cables |
Verified complete data or open
|
Handles, wheels, handlers, cart or lift question | Recorded position | Named visual role | Stand, power, data, focus | Tour owner |
| Control case | Controller, computer, interface, backups | Verified complete data | Handling and access | Available before addressing | Repeatable cues | Profiles, software, signal | Programmer |
| Cable or accessory trunk | Power, data, adapters, approved accessories | Verified complete data | Route and handling | Available before connection | System support | Venue handoff | Technical owner |
Browse stage lighting accessories only after the required cases, cables, clamps, stands, spares, and dependencies are listed. Do not calculate payload, axle distribution, stacking, restraint, or safe lifting here; those remain with the responsible owner and applicable requirements.
Score every fixture role against touring burden
The scorecard is a project decision aid, not a universal product ranking. Score each candidate from the same evidence set, record unknowns rather than converting them to zero, and name the owner of every open test.
| Criterion | Weight | Evidence to record | Exclusion trigger |
| Packed volume and total transport load | 25% | Complete case, accessories, handling, and vehicle plan | Packed burden or vehicle fit remains unresolved |
| Core visual role | 20% | Cue map and reduced-mode value | Duplicates another role without added show value |
| Setup time and crew | 20% | Actual dry-run result, dependencies, blockers | Cannot fit the real workflow or access path |
| Control repeatability | 15% | Profiles, modes, addresses, cues, backups | Required behavior is untested or incompatible |
| Power and venue fit | 10% | Advance, approved positions, service, connectors | Depends on unconfirmed infrastructure |
| Redundancy and serviceability | 10% | Failure impact, spares, parts, service plan | No workable failure or service path |
Wattage, price, popularity, and a portable label do not replace this evidence. Carry, source locally, or exclude the candidate according to its total score and any blocking trigger.
Compare compact PAR, wash mover, and 3-in-1 roles
The following current SHEHDS listings are documentation examples, not winners. Their figures remain attached to the exact named model and August 17, 2026 source date.
| Example | Documented fields | Touring role to test | Still missing before approval |
| Mini 7x18W aluminum PAR | Listing states 1.05 kg, 18.5 x 14.3 x 14 cm, variant power, and model-specific DMX modes | Simple, fixed color-wash candidate | Packed case, complete mass, output in the venues, profile, connectors, handling, and service |
| 7x12W wash moving head specification block | States 84 W, 10/15 channels, listed modes, 2.65 kg net, and a 19 x 19 x 16 cm / 3.5 kg package | Moving wash candidate when movement earns the burden | Exact variant, case, profile, control, position, clearance, output, and service |
| 160W 3-in-1 moving head | States 18 channels, 10-20 degree zoom, 7.5 kg net, 8.95 kg gross, and 48 x 32 x 29 cm packing | Multi-role movement, beam, or spot candidate | Case status, optics in the venue range, control, handling, mounting, and fallback value |
Compare LED PAR lights for a lower-complexity wash role. Review moving head lights only after their additional control, position, handling, and fallback burden is explicit. Do not transfer the 7x12W figures to the 7x18W option, and do not infer roadworthiness, output, compatibility, or suitability from product-page data.
Rehearse the door-to-stage workflow
Run the real sequence with the intended vehicle, cases, crew, and access path:
- Unload and stage cases without blocking the venue workflow.
- Place stands or use only approved positions.
- Position fixtures, then complete the named power and data handoffs.
- Set modes and addresses; focus the visual jobs.
- Test cues, reduced mode, fallback mode, and manual blackout.
- Run the show, then shut down under the documented process.
- Strike, inspect, log faults, repack, and reload against the manifest.
Record the owner, predecessor, blocker, actual measured time, and corrective action for each step. Use the result to compare candidates. Do not publish the dry run as a generic setup benchmark or turn it into a universal crew, lifting, cable, or rigging rule.
Advance the venue before the van arrives
Convert every venue dependency into a question with an owner, deadline, status, and fallback.
| Must confirm | Tour carries | Venue supplies | Owner and deadline | Fallback |
| Stage geometry, throw, ceiling or trim, and access path | Measured touring positions and cases | Current plan and restrictions | Production contacts before arrival | Reduced positions and cue groups |
| Approved floor or overhead positions and point data where applicable | Touring placement requests | Venue-approved information and contacts | Venue and competent planner | Floor-only or reduced design if approved |
| Electrical service, cable and data routes | Documented fixture and control requirements | Verified service and handoff | Venue and qualified technical owner | Reduced system or no-go for unresolved work |
| Local fixtures, console, profiles, haze, cameras, crew, and windows | Master show and tour core | Confirmed inventory and policies | Venue and tour programmer | Tour core and fallback show |
Industry guidance and local rules govern. The matrix does not replace competent production planning, venue approval, or exact capacity verification.
Keep power, data, and rigging responsibilities explicit
Assign every technical decision to a named responsible party before arrival.
| Area | Tour provides | Venue or qualified owner confirms | Status record |
| Power and flexible cords | Exact equipment requirements and intended routes | Service, connection, protection, route, and applicable rules | Approved, revise, or unresolved |
| Data and control | Models, profiles, modes, addresses, connectors, software, and backups | House interface, network ownership, and permitted connection | Tested or fallback |
| Mounting and rigging | Position request and exact fixture information | Venue approval, point data where applicable, planning, hardware, access, and competent responsibility | Approved or excluded |
In its United States workplace scope, OSHA identifies flexible-cord hazards including damage, wet connectors, abrasion, and loss of grounding. This is not a complete temporary-power standard. ICOPER calls for competent preplanning, venue approval, point-capacity verification, and electrical-service verification; it is industry guidance, while local law and venue requirements govern. This guide does not calculate power, choose rigging hardware, or approve installation.
Standardize profiles, addresses, and the master show file
Show-file portability is a documented configuration problem, not a compatibility promise. Build one control register before programming:
| Field | Record |
| Fixture identity | Exact model, variant, mode, channel count, profile source, connector, and protocol implementation |
| System identity | Controller, interface, software, firmware, and network owner where applicable |
| Show configuration | Address, group, musical function, cue role, position rule, and approved speed or movement limits |
| Version control | Master show-file version, change owner, backup location, recovery copy, and date |
| Acceptance | Signal-loss behavior, fixture-removal fallback, blackout, restore test, operator, and status |
Program musical functions such as stable wash, accent, texture, and movement groups rather than one venue's coordinates. Compare DMX controllers only after these verification fields are known. Every profile and fallback behavior must be tested on the selected hardware and software.
Program full, reduced, and fallback show modes
Three documented modes keep the show usable when venue conditions change.
| Mode | Trigger | Available groups | Cue limits | Operator action and restore test |
| Full | Every approved touring and house dependency is confirmed | Tour core plus approved house enhancement | Complete rehearsed cue set | Verify all groups, blackout, and restore before doors |
| Reduced | Time, position, power, control, or venue limits remove a layer | Tour core and only confirmed additions | No cues that depend on removed groups | Load reduced file or disable groups, then test transitions |
| Fallback | Fixture, data path, position, or local resource is unavailable | A few stable, recognizable looks | Simple cues and manual blackout | Named owner recalls fallback, isolates the fault, and tests recovery |
This is a planning architecture. Exact behavior depends on the selected fixtures, control system, venue, and operator. Rehearse each mode instead of assuming it will work after a failure.
Run a pre-tour acceptance test and change log
Release the rig only after the complete system passes a representative test:
- reconcile the packed manifest and labels;
- confirm vehicle and access fit under responsible ownership;
- run setup, power and data handoffs, profiles, addresses, and cue checks;
- test full, reduced, fallback, blackout, signal-loss, and fixture-removal states;
- complete shutdown, strike, inspection, fault logging, packing, and reload;
- verify that current documents, backups, venue-advance templates, and owners travel with the system.
After each show, log issue, evidence, owner, change, retest, and manifest version. Expand only when a new visual job, venue range, control need, or documented failure risk justifies the added burden. Passing this gate does not establish universal roadworthiness, reliability, safe lifting, cargo compliance, or venue fit.
Build your SHEHDS touring comparison brief
Send SHEHDS the show roles, venue range, touring-versus-house split, complete case manifest, responsible vehicle data, access path, crew and workflow, power/data/rigging handoffs, control register, full/reduced/fallback modes, service plan, market, and budget. The review can narrow current categories or documented models, identify missing packed and technical evidence, and define the test each candidate still needs.
Frequently Asked Questions
What lights should a small touring band carry?
Carry the smallest documented system that preserves the show's essential visual jobs and fallback. Start with stable wash and required scenic separation, then add movement or effects only when the complete burden earns its space. There is no universal fixture count.
How do I know whether the rig will fit in the van?
Measure every complete packed case and accessory, the actual cargo opening and usable space, and all competing cargo. The responsible vehicle owner must check vehicle limits and the load plan, followed by a measured loading and access trial.
Should the band carry front light or use the venue system?
Carry it when stable performer visibility is essential and cannot depend on an unconfirmed house resource. Otherwise advance the venue system with exact position, control, power, color, and operator questions, plus a tour-carried fallback.
Are moving heads worth the cargo space?
Only when their movement, focus, or multi-role cue value survives the scorecard. Include the case, control, position, handling, setup, service, and fallback burden, not just the fixture specifications.
How can one show file work on different stages?
Use exact profiles and modes, versioned groups based on musical functions, verified addresses and connections, scalable positions, and tested fallback behavior. One file does not guarantee cross-model or cross-venue compatibility.
What belongs in a fallback lighting look?
Use a few stable and recognizable looks built from the touring core, plus a manual blackout. Remove cues that depend on the missing fixture, data path, position, power, or house resource, and assign a recovery owner.
Make every case earn its place
A touring light rig becomes van-friendly through roles, a complete manifest, a rehearsed workflow, a precise venue advance, verified control, and usable fallback modes. Complete the comparison brief, then use it to shortlist current SHEHDS categories or models and close the remaining evidence and test gaps before the tour.
