Zoo light event planning
When your team asks “how long,” it may mean the public run, each night’s operating window, a guest’s route time or the scoped project timeline. Name the clock before you compare dates, responsibilities or supplier schedules.
Compare the Four ClocksShare Your Zoo Project Timing Questions
One phrase, four decisions
Why does one “duration” question create bad decisions?
A visitor asking how long an event lasts may be looking for tonight’s opening hours or the time needed to walk the trail. Your programming team may be discussing the number of public dates. Your operations team may be planning the nightly opening, inspection and close-down window. Your project team may be trying to compare design, production, transport and installation schedules.
Those are not interchangeable answers. A calendar date cannot prove that installation access is available. A route length cannot predict a guest’s experience time. A supplier timeline cannot be compared fairly when two proposals include different products, destinations or installation responsibilities.
The useful first question is therefore not “What is the normal duration?” It is: Which clock are we deciding, who owns that decision, and which current evidence supports it?
Decision matrix
What are the four clocks in a zoo light event?
| Clock | Decision | Source evidence | Responsible owner | Do not infer |
|---|---|---|---|---|
| 1. Public run | Which public dates and program period are under consideration? | Current venue calendar, program purpose, local constraints and approval state. | Venue programming and approval team. | Another event’s season fits your venue. |
| 2. Nightly window | Which nightly public and operating interfaces need local review? | Opening and closing plan, access, inspection, weather response and emergency procedures owned locally. | Venue and local operations. | The lantern supplier controls staffing, ticketing or daily operations. |
| 3. Guest route time | What experience time is being designed, and how will your team validate it? | Approved route, zones, pauses, queues, accessibility inputs and local visitor research. | Venue visitor-experience team. | Distance alone predicts time, capacity or satisfaction. |
| 4. Project timeline | What scoped work must happen before the intended opening? | Product scope, destination, logistics, access, installation responsibility and required approvals. | The agreed project parties within their confirmed scope. | A generic lead time or guaranteed opening date. |
Clock one
How should your team frame the public run?
The public run is a programming decision: the period during which the venue intends to offer the event. Start with the purpose of the program, the venue calendar, target season, local constraints and the status of internal approval. Keep proposed dates visibly marked as proposed until the responsible venue owner approves them.
Do not borrow another zoo’s dates as a template. Different venues may have different calendars, climate conditions, animal-area policies, public programs and approval paths. The supplier can respond to a stated target, but the target remains a venue decision until it is confirmed through the project.
If the route and venue context are still being defined, use our zoo lantern festival planning page to organise the site and program questions around that target season.
Clock two
What belongs in the nightly operating window?
The nightly window is more than the time printed on a visitor page. Your local operations team may need to distinguish public opening, staff access, route inspection, weather review, incident response and close-down. Which activities are required—and who may perform them—depends on the venue and local operating plan.
A manufacturer can prepare product and project information within the agreed scope. That does not make the manufacturer the owner of ticketing, security, staffing, animal-care decisions, emergency procedures or daily venue operations. Where an event company or operator is involved, separate event-operator responsibilities before the nightly window becomes a promise.
Record the public promise
Keep the visitor-facing opening and closing information under the venue’s approved program record.
Record the operating interfaces
Name the local owner for access, inspection, weather response, emergencies and close-down rather than hiding them inside one “event hours” field.
Clock three
How should guest route time be discussed?
Guest route time is an experience hypothesis until the route and operating conditions are approved and locally validated. Distance matters, but it is only one input. Zones, focal pauses, photo moments, queues, path width, accessibility, family groups, weather and operating choices can all change how guests move through the evening.
A useful route-time brief states what the experience is intended to do, where guests may pause, which sections are continuous and which need a choice or bypass. It then names how the venue will validate the assumption. It does not turn one distance measurement into a universal time, capacity or satisfaction claim.
For the physical questions that sit beside the experience plan, review the commercial site-readiness checklist without copying its access, power and ground checks into this timing decision.
Clock four
When can the scoped project timeline be discussed?
A meaningful project timeline starts after the work is defined well enough to expose dependencies. The product mix, destination, route, access, logistics, installation responsibility, local approvals and target opening context all affect what must happen next. If those inputs differ, two schedule statements may not describe comparable work.
Use a project timeline to connect confirmed scope and responsible parties—not to publish a universal lead time. Our lantern festival project process explains the sequence from venue brief through design scope, production planning, logistics and installation-support review. Exact timing remains project-specific.
Mismatch control
Where do the four clocks most often conflict?
Public dates precede access
A marketing calendar is announced before the project team has confirmed installation access. The opening date and the available work window are then treated as if they were the same decision.
Repair: name the access owner and record the latest approved access version beside the public-date decision.
Route time precedes route approval
A guest-time promise is copied into marketing before zones, pauses, accessibility inputs or queues are resolved.
Repair: keep the number as an unvalidated assumption until the approved route and local testing method exist.
Schedules hide different scopes
Two supplier timelines appear different because one includes a different product mix, destination, logistics handoff or installation responsibility.
Repair: compare the same scope and the same dependency owner before comparing dates.
Evidence discipline
What evidence should accompany every timing decision?
A date without provenance quickly becomes a promise. Give every clock a compact decision record so that your programming, operations, visitor-experience and project teams know which version they are using.
- Clock and decisionName the public run, nightly window, guest route time or scoped project timeline—and state exactly what is being decided.
- Source and locatorLink the venue calendar, route drawing, operating note, approved scope or other current source that supports the decision.
- Version and dateRecord which revision is current and when it was accepted. Do not combine a superseded route with a current program date.
- Responsible ownerName the venue, local operations, visitor-experience or agreed project owner who can approve or change the decision.
- DependenciesList the access, route, product, destination, responsibility or approval inputs that must be resolved first.
- Public-use statusMark whether the value is an internal assumption, approved planning input or visitor-facing promise.
This record is intentionally smaller than an RFP or full project schedule. Its job is to stop one team’s working assumption from silently becoming another team’s commitment.
Project handoff
Which timing questions should you bring into the project discussion?
Bring the four clocks as separate inputs. Share the target public period and approval status, the local owner of the nightly operating window, the route-time assumption and validation plan, and the scope dependencies that shape the project timeline. Where a value is unknown, identify its owner instead of filling it with a generic benchmark.
Use the full project assessment when you want to share a complete intake brief, including your venue, target season, route context, scope questions and known local responsibilities.
Next step
Share your zoo project timing questions
Tell us which clock you are deciding, what source you are using and which venue or project responsibility is still open.