< img src="https://mc.yandex.ru/watch/105870814" style="position:absolute; left:-9999px;" alt="" />

Zigong Yunyi Culture Co., Ltd

Yunyi Culture is a professional direct manufacturer in Zigong, China, specializing in large-scale traditional lanterns, modern iron wire light sculptures, and animatronic displays. We offer turn-key, custom lighting solutions and factory-direct pricing for global festivals and commercial events.

Run of Show Template for a Nighttime Light Festival

A run of show template turns an event plan into an operating sequence that a team can follow minute by minute. For a nighttime light festival, it must do more than list performances. It should coordinate the venue handover, weather decision, route inspection, display power-up, lighting cues, gates, guest-flow changes, technical calls, final admission, shutdown, and overnight repair window.

The most useful version is a single controlled timeline with named owners and confirmation evidence. It tells each person what must happen, when it may proceed, what can pause it, and how the next team knows the action is complete. The template below is designed for parks, zoos, botanical gardens, municipalities, attractions, and producers operating an outdoor lantern trail.

Lantern festival crew reviewing a run of show during a peacock gateway rehearsal

What is a run of show template?

A run of show is the time-ordered control document for an event day or operating period. It is different from the master project schedule, which may cover design through dismantling; the staffing roster, which shows who is working; and a technical cue sheet, which may contain only show-control instructions. The run of show connects those documents at the moments when one team must hand work to another.

A simple spreadsheet is enough if it is controlled properly. Use one row per observable action, not one row per broad department. A line such as “technical ready” is difficult to verify. A better line states that the route electrician confirms all approved distribution zones energized, unresolved faults isolated, and the status reported to the event control lead before the public gate opens.

Georgia Tech’s special-event template library includes a run-of-show resource. For complex operating periods, the FEMA ICS forms library also illustrates the value of recording objectives, assignments, communications, safety messages, and activity logs in controlled documents. A light festival does not automatically require an Incident Command System; the useful lesson is to make ownership, timing, status, and handoff explicit.

Use this night-trail run of show structure

FieldWhat to recordExample for a light festival
Control timeLocal clock time plus an offset from the public opening or closing milestone.17:10 / gates open minus 50 minutes.
Zone and systemThe exact route zone, gate, facility, display group, or control system.Zone 3 botanical sequence and adjacent accessible route.
Action or cueOne observable task written as a verb.Run scene preset and confirm the approved static fallback.
OwnerOne role accountable for the action, even when several teams assist.Show-control operator.
Ready inputThe condition or upstream confirmation required before action.Electrical release and clear maintenance enclosure.
ConfirmationWhat proves completion and who receives it.Operator reports “Zone 3 ready” to event control and marks the row.
Hold triggerA defined reason not to proceed.Open fault, unsafe route obstruction, or unapproved cue change.
Recovery pathThe approved fallback, next decision owner, and revised time.Use static scene, isolate the failed subassembly, update guest services.

This eight-field structure is the core asset. It prevents a cue from becoming detached from route conditions, responsible people, and proof. Keep instructions concise in the live sheet, then link to the detailed power plan, control patch, maintenance procedure, contact list, or emergency plan rather than copying those documents into every row.

Build the timeline around public promises

Start with the times already promised to guests and partners: parking access, box office, gate opening, timed-entry windows, programmed moments, last admission, retail close, route clear, and site handback. Work backward from each milestone to identify the readiness decisions that protect it.

Before the gate opens

Typical rows include venue access, weather review, contractor sign-in, route sweep, accessible-path confirmation, toilet and concession readiness, power energization, display inspection, control-system start, scene checks, ticket-scanner test, staff briefing, and a final go or hold decision. Use the same zone names found in the event logistics plan so a radio call, maintenance record, and run-of-show row refer to the same place.

During admission and steady operation

Record the first timed admission, scheduled control cues, performance or sponsor moments, planned patrols, capacity checks, transport updates, breaks for critical posts, and decision windows for route changes. A continuous lantern trail may appear visually steady, but the operating team still needs a rhythm for observation, reporting, and response.

Final admission, close, and reset

Sequence last ticket entry, public messaging, food and retail cutoffs, route sweeps, final guest exit, display shutdown, electrical isolation where required, fault logging, lost-property transfer, waste removal, charging, overnight repair access, and next-day readiness. Closing actions should protect both people and equipment; do not compress them into one line labeled “shutdown.”

Turn the route into control zones

A long outdoor trail is easier to operate when its creative scenes and venue areas share stable zone identifiers. Define an entrance zone, orientation area, route segments, major dwell scenes, intersections, facilities, food or retail areas, quiet or accessible options, exit, and dispersal space. Give each zone a visible owner during every operating phase.

The lantern trail storyboard can define the creative role and intended dwell behavior of each scene. The run of show then records when the scene is inspected, activated, observed, changed, or handed back. This keeps a creative cue from being approved without considering visitor flow and keeps an operational adjustment from accidentally breaking the narrative.

Write cues that can be called and confirmed

Give important rows short identifiers such as GATE-01, ROUTE-04, SHOW-07, or CLOSE-03. The identifier is not a secret code; it is a shared reference that prevents ambiguity when the timeline changes. Each cue should have a caller, receiver, required response, and fallback if the response is not received.

For a lighting cue, record the approved scene name, display group, intended start condition, transition, duration, completion state, and fault behavior. Detailed addressing remains in the DMX lighting control plan. The run of show should state the operational outcome, such as “activate welcome preset after route release,” rather than invite live edits to technical parameters.

Control rule: Never let two documents compete as the live authority. Name the current run-of-show version, owner, distribution channel, and cutoff for routine edits. Log urgent changes with the time, decision owner, affected rows, and who received the update.

Add hold points instead of optimistic timing

A hold point is a decision that must be positively released. Useful examples include authorizing energization, accepting the installed route, opening public gates, restarting after a local fault, changing a guest path, starting a synchronized scene, and confirming the site is clear before shutdown work.

Do not invent universal weather, wind, crowd, or electrical thresholds in the run of show. Those values belong in the approved venue plan, engineering documentation, equipment instructions, and local requirements. The row should identify the source plan, current decision owner, communication path, and fallback. This keeps a planning template from pretending to replace qualified technical, safety, or emergency judgment.

Rehearse transitions, not only headline moments

A tabletop review can find missing owners and impossible overlaps before the site is ready. An installed night rehearsal should then test the route at operating brightness, with actual radios, staff positions, guest-service channels, maintenance access, and realistic travel times. Include at least one controlled scenario: a delayed gate, a localized display fault, a blocked route segment, or a missed confirmation.

Measure whether the team notices the issue, reports the correct zone, reaches the decision owner, communicates the change to affected roles, applies the approved fallback, and records closure. A spectacular scene transition means little if the next row assumes a technician can cross a live route in two minutes when the actual journey takes ten.

Keep the live sheet readable

  • Freeze a baseline version before the operating period and show the revision time clearly.
  • Use local time consistently and include offsets from opening for quick scanning.
  • Assign roles rather than personal names in reusable templates; map names in the daily roster.
  • Keep one action per row and one accountable owner per action.
  • Mark required confirmations and hold releases so silence cannot be mistaken for approval.
  • Give recovery actions their own rows when they change timing or guest information.
  • Protect the original record after close and move lessons into the event debrief.

Example operating sequence

A compact example might begin with site access and weather review, continue through power release, route and access inspection, display and control checks, gate briefing, final opening decision, first admission, scheduled scene cues, patrol and capacity reviews, last admission, public close messaging, route sweep, shutdown release, fault transfer, and overnight reset. The exact times depend on sunset, venue access, ticket design, route length, local approvals, transport, and the installed technical system.

If the team uses Google Sheets or another shared tool, protect fixed fields, define who may edit the live version, keep a printable or offline fallback, and test access where connectivity is weak. The value comes from the operating logic, not the software.

Run of show checklist

  • Public promises and fixed venue milestones are entered first.
  • Every row names the zone, action, accountable role, and confirmation.
  • Power, route, access, display, control, ticketing, guest-service, and closing handoffs are visible.
  • Hold triggers point to approved plans rather than invented universal limits.
  • Each major cue has an approved fallback and decision owner.
  • The installed rehearsal tests real travel time and at least one disruption.
  • The live version and change log are controlled.
  • Close and reset receive the same detail as opening.

Once the operating sequence is stable, a custom display package can be organized around the same zones, cue states, access windows, and handover evidence. Explore our festival lighting projects service for the broader design and production path.

Planning a nighttime lantern event? Share the site plan, operating dates, public hours, route zones, creative brief, control needs, access windows, and approval structure. Contact Zigong Lanterns to discuss a custom display brief that can integrate with your venue’s run of show.

The run of show works best when each timed cue is supported by stable roles, authority, thresholds, procedures, and evidence. This event operations manual for a light festival connects opening gates, guest flow, lantern faults, weather decisions, communications, shift handover, and closing controls.

Tags:

Leave a Reply

Your email address will not be published. Required fields are marked *