One of the most refined skills in professional lighting design is the ability to build a show file that is genuinely usable — populated with functional cues, calibrated palettes, and a working programming structure — before ever standing in the venue, before the rig is hung, and in some cases before the final fixture specification has been confirmed. This capability is not a workaround for inadequate prep time. It is a professional discipline built on the intersection of detailed documentation practices, deep platform knowledge, and an experience-based understanding of how physical rigs translate from technical drawings to operational reality.
The history of pre-built show files in touring production accelerated through the 2000s as digital lighting consoles replaced analog dimmer control systems and made the show file a genuinely portable, reloadable artifact. The introduction of grandMA series consoles and ETC Eos family systems created platforms capable of storing complete show configurations — fixture libraries, palettes, cue stacks, effects engines — in files small enough to carry on a thumb drive, transferable between consoles of the same family, and robust enough to survive the hardware changes that touring productions inevitably require.
Starting With the Documentation Package
The pre-build process begins with the complete production documentation package: the lighting plot showing every fixture position, type, and unit number; the channel hookup mapping every fixture to its DMX address or network node; the focus chart describing the intended focus position for each fixture; and the gel and gobo schedule specifying color and pattern for every fixture that uses them. This documentation — produced in Vectorworks Spotlight and exported to both PDF and the console’s native fixture library format — is the foundation on which the pre-built show file is constructed.
A show file built without accurate documentation is built on guesses. When those guesses encounter the physical reality of the venue, every guess that was wrong becomes a programming correction that consumes rehearsal time. The value of investing in comprehensive, accurate documentation before the pre-build begins is measured in hours saved during the tech period — hours that can be applied to refining the design rather than correcting the infrastructure.
Building the Patch and Fixture Library
The first task in the pre-build is establishing the console patch — the mapping that connects DMX channel addresses to fixture identities in the console’s operational structure. In grandMA3, this means building the patch universe, loading or creating the GDTF profiles for every fixture type in the rig, and assigning each fixture its physical address and 3D position based on the lighting plot. In ETC Eos, the equivalent process uses the Eos Patch and Channel Discovery tools to build the fixture library and assign attributes.
The quality of the GDTF (General Device Type Format) profiles used for each fixture determines how accurately the console represents the fixture’s capabilities in the pre-build. Manufacturer-provided GDTF profiles from the gdtf-share.eu repository are the authoritative source. For newer or unusual fixtures that lack GDTF profiles, the designer must create a custom profile — a time investment during pre-production that pays for itself immediately in programming accuracy once the rig is live.
Palette Pre-Building Without Physical Fixtures
The most operationally valuable element of a pre-built show file is the palette library. Palettes — stored snapshots of fixture attributes that can be recalled instantly during live programming — are the building blocks of all subsequent cue construction. Position palettes, colour palettes, beam palettes, and effects palettes built during pre-production are immediately available as soon as the physical rig is focused and ready.
Building colour palettes before the rig is live is straightforward — colour attribute values for LED fixtures are mathematical and don’t require physical verification in the way that focus positions do. A complete colour palette library covering the full range of production colours — warm whites, cool whites, saturated spectrals, pastels, and specific brand colours from the event’s identity — can be constructed entirely in pre-production using the colour picker and gel library tools in grandMA3 or Eos, and will work correctly on the physical fixtures from the moment the rig is patched.
Position Palettes: The Pre-Build Estimation Problem
Position palettes — the focus points that define where each fixture points from its rigged position — are the element of the pre-build that most clearly require estimation rather than measurement. Without being in the room with the fixtures in their rigged positions, the designer must calculate pan and tilt values from the geometry of the lighting plot and the known dimensions of the venue and stage. This calculation is performed in the 3D visualization layer of wysiwyg, Vision, or grandMA3’s MA 3D — the designer positions virtual fixtures in the virtual room, focuses them to target positions in the model, and exports the resulting position palette values to the console.
The accuracy of these pre-calculated position palettes depends entirely on the accuracy of the 3D model. A model built from measured architectural drawings and a verified stage plot will produce position palettes that require minimal correction when the real rig is focused. A model built from approximate measurements will produce palettes that require significant physical focus refinement — but even imprecise pre-built position palettes reduce the physical focus time compared to starting from scratch, because they establish the correct neighborhood for each fixture’s focus before the crew climbs the ladder.
Cue Stack and Show Structure Pre-Building
With the patch, colour palettes, and approximate position palettes in place, the designer builds the cue stack architecture — the organizational structure of the show file that will hold all production cues. This includes creating cue lists for each show section, building the sequence and timeline structures that govern show flow, and establishing the macro and executor assignments that the operator will use during the live performance.
In grandMA3, this structure uses sequences, executors, and the layout view — configuring the console’s interface to match the operator’s working method before any live programming occurs. In ETC Eos, the equivalent is the cue list structure, playback configuration, and magic sheet layout. The goal is that when the designer and operator walk into the venue on the first tech day, the console is already configured as a familiar working environment — the tool is ready, and all available time can be spent creating the show rather than building the infrastructure that should have been built during pre-production.
