Venue Readiness Guide
Commercial Lantern Festival Site-Readiness Checklist
Separate what your team can share at first contact from what must be verified before installation scope, construction release or public opening. Record each field, evidence owner and unresolved gap before deeper assessment.
Start with the right level of detail
Separate first-contact basics from deeper evidence
The first conversation should be easy to start. Share the venue type and location, proposed event zone or route, target opening and working windows, and the site information your team already has. These basics help frame the discussion; they are not a substitute for project-specific verification.
As the project becomes more defined, add evidence at field level. For every item, record what is known now, who supplies or maintains it, who must verify it, what remains missing and what decision comes next.
| Current information | What is known now and which version is current |
|---|---|
| Evidence owner | Who supplies or maintains the information |
| Project verifier | Who reviews it for this site and jurisdiction |
| Gap | What is missing, conflicting or still assumed |
| Next decision | Proceed, request evidence, route to an owner or hold |
If your team is ready to share the initial context, share your project basics for assessment. The detailed readiness checklist stays separate from the inquiry form.
Site-plan evidence
Build a usable site-plan evidence set
A useful plan does more than show a general location. Identify the current plan version and owner, then mark the interfaces that affect a lantern-festival review: event and work-area boundaries, existing structures and sensitive areas, fences and controlled-access points, public entrances and exits, the proposed visitor route, delivery and service access, and known utility or restricted zones.
Record which details are measured, which remain indicative and who can verify them. The required drawing detail and approving authority will depend on the site, project stage and local process.
Installation access
Record access and logistics interfaces
Separate the public route from the route used for delivery and installation. For each access path, record gates, turns, clearances, unloading areas, lifting constraints, temporary storage, permitted working hours and shared pedestrian or vehicle movements.
Useful evidence can include a marked logistics route, measured access notes, dated photographs tied to map locations, and venue rules for loading, storage and work windows. Equipment and installation methods should be selected only after the exact constraints and responsibilities are known.
Keep the question bounded
This checklist identifies the access evidence your team should organize. It does not set a universal vehicle, lifting method, clearance or installation specification.
Electrical interface
Document power and service information early
Bring the proposed layout and operating assumptions into the electrical conversation early. Record known supply points and their owner, available capacity information and its source, indicative product or zone demand assumptions, service and cable-route constraints, exposure to public areas, water or weather, backup expectations, isolation points and operating hours.
Name the local professional responsible for verification and connection decisions. Voltage, load, protection, distribution and connection responsibility remain project- and jurisdiction-specific.
Ground and anchoring
Connect every proposed location to ground evidence
Record what the site can currently tell you about each proposed installation area: surface or soil type, slopes, sensitive landscape or paved zones, underground services, permitted anchor or ballast approaches, restoration expectations and access for local review.
Connect photographs and notes to exact locations. If ground information is incomplete, label the gap and name who can supply the survey, utility record or engineering review. A generic product image cannot establish that one anchoring method or load basis suits every location.
Weather governance
Define who monitors, stops and reopens
Use the venue’s project weather basis rather than a generic seasonal assumption. Record the conditions relevant to the event window, the sources used, and the people responsible for operating decisions.
The readiness record should identify who monitors conditions, who can stop or cancel work or public access, how affected zones are isolated, what evidence supports inspection, and who authorizes reopening. Thresholds and actions need to match the exact configuration, venue plan and local responsibilities.
Outdoor use is a project context; weather suitability must be verified for the exact configuration and venue.
Route accessibility
Review the visitor route as a connected journey
Record slope, surface, usable width, entrances and exits, mobility-device conditions, alternative paths, rest or bypass options, and any quiet or sensory-access considerations relevant to the venue.
Identify where weather, queues, temporary installations, cable routes or barriers could change the usable path. Then name the venue or local accessibility owner who will verify the final arrangement. A general route description can support early review, but it does not replace a site-specific accessibility assessment.
Responsibility ownership
Assign evidence owners, verifiers and decision owners
For each readiness field, separate who provides information from who verifies it and who makes the decision. Depending on the project, the map may include your project lead, venue operations and facilities teams, event organizer, lantern supplier, local engineer or electrician, installation and logistics contractors, and the relevant authority or approval body.
Use the map to expose unassigned work and conflicting assumptions. The final allocation belongs in the project scope and local approval path; a generic responsibility table is not a contract.
Evidence hierarchy
Separate preliminary media from executable evidence
Maps, photographs and descriptions are valuable when they are current, located and owned. They can show the route concept, access conditions, surface appearance, nearby services and visible constraints.
They cannot, by themselves, confirm utility capacity, buried services, structural calculations, anchoring suitability, electrical design, permit status or public-opening approval. When the next decision depends on one of those subjects, record the specific technical document, measurement or professional verification required.
- Current plan and version owner
- Dated, located photographs
- Named measurement or survey
- Project-specific technical file
- Local professional verification
- Decision and approval record
Decision gates
Separate concept acceptance from release and approval
A venue may accept a concept direction while route details, interfaces or responsibilities remain open. A design may be reviewed while construction information is incomplete. Installation completion may still require inspection, handover or a separate public-opening decision.
For each gate, record the decision, version, owner, conditions, open items and next approver. The names and order of gates will vary by contract and jurisdiction, so use the project’s actual approval path rather than assuming a universal sequence.
Your next action
Turn open site-readiness fields into an owned project record
Consolidate each unresolved item as ready for the next discussion, evidence requested, routed to a named owner or held. Then share the venue type, route or zone, working windows, access, plan status, utilities, ground, weather and accessibility context already available.