In an ideal world, every lighting designer has access to a full-featured previsualization (previz) suite, detailed CAD drawings, and generous programming time before stepping into a venue. But the reality is often quite different.
Many professionals find themselves programming on-site only, without the luxury of previz tools. Whether you're jumping onto a touring rig last minute, lighting a one-night gala, or programming with limited resources, this article provides practical strategies for thriving in real-world, on-the-ground scenarios.
Understand the Limitations — and Embrace Them
First, acknowledge what you don’t have:
No virtual model of the space
No fixture mapping previews
Limited programming time on-site
Possibly unfamiliar console layout
Rather than seeing these as deal-breakers, treat them as design constraints. A minimalist toolkit can sharpen creativity and decision-making.
Start with a Strong Patch Strategy
When you only have venue access, your patch needs to be bulletproof from the outset. Tips include:
Group fixtures by location and function
Pre-label fixture types and channel modes in advance
Use consistent naming for cues (e.g., “Wash_Front”, “Spot_LX2”)
Mirror symmetric rigs with logical universes or fixture IDs
A clean patch layout reduces thinking time during cue recording — critical when every minute on-site counts.
Build a Skeleton Cue Stack Before Focusing
You won’t have time to “feel it out” mid-show. Instead, construct a basic cue structure before you begin:
Entry/Walk-in state
Stage looks (warm/cool, backlight, keylight)
Scene shifts (blackouts, changes)
Looks for possible musical interludes or speaking events
End state or walk-out
Even if you tweak intensities later, having this skeleton ensures you’re never building from zero during a live moment.
Prioritize Focus Positions That Work for Most Scenes
Without visualizing beforehand, aiming fixtures can be risky. Use these strategies:
Use cross-focusing from opposing sides for balanced key
Focus on “zones” instead of pinpoint targets
Create safe fallback palettes: front wash, center stage, upstage wall
If time permits, mark spots with tape or placeholders before final programming
Use Palettes and Presets Aggressively
When programming on-site only, speed is everything. Save focus positions, colors, gobos, and effects as palettes so you can:
Apply looks quickly across multiple cues
Recover from errors without rebuilding
Reuse balanced positions when time runs out
This “build-once, apply-often” strategy is essential for tight timelines.
Program in Layers, Not Looks
Instead of creating one full look per cue, separate elements:
Cue 1: front wash
Cue 2: color shift
Cue 3: gobo overlay
Cue 4: FX movement
This gives you modular control to stack or fade effects in real time, saving programming time while increasing flexibility.
Use Default or Legacy Templates (When Safe)
If you’re working with a console you’ve used before:
Load a previous show file with pre-made effects
Use house-provided templates for LED chases or dimmer profiles
Even a “basic showfile” can save hours if patched well
Just ensure you double-check DMX addressing and fixture types to avoid mismatches.
Communicate With Stage Managers & LDs Early
On-site only programming means no second chances. Avoid:
Ask questions before touching the console:
Will presenters walk or be stationary?
Is there backline equipment affecting sightlines?
Can you get a quick rehearsal, even just walk-through?
Accept Imperfection — and Deliver Consistency
The harsh truth: when programming without previz, you will not have time to perfect every scene. What matters most is:
Consistent levels across similar cues
Smooth transitions between cue stacks
No major surprises (blinding flashes, blackout delays)
An “80% done right” show beats a “100% fantasy” show you can’t deliver.
Conclusion
Programming without previsualization is a reality for many working professionals. With the right mindset, solid patch strategy, and a modular cue structure, you can still deliver a visually strong, technically stable show — even under pressure.
It’s not about perfection; it’s about preparation, prioritization, and presence at the console when it matters most.
READ MORE：
