Botanical garden program planning
Before your venue publishes tickets or compares project scope, label what the standard admission includes, what needs a separate booking and which experiences run only for a particular audience or date.
One experience, six records
What should your team record before describing an experience?
A program label is only useful when every team means the same thing by it. Give each experience a working name, then record six fields: the visitor promise, the season or status, the booking rule, the local operating owner, the supporting evidence and the supplier interface.
What will this visitor actually receive?
Describe the experience in plain language without implying that every ticket, date or audience receives it.
Which version is current?
Mark the item confirmed, proposed, historical or still open for the named season rather than carrying last year’s wording forward.
Included or separately arranged?
Name the ticket, reservation or booking condition that controls availability. “Included” without a named context is incomplete.
Who confirms the promise?
Record the venue or local team that owns the visitor information and the current source that supports it.
What must the project team know?
Identify only the program decision that affects product scope, access, installation, testing or handover.
What remains UNKNOWN?
Keep an unconfirmed field visibly open until the responsible team resolves it; do not fill the gap with another venue’s practice.
A matrix, not three boxes
How do included, add-on and special-session labels work together?
Included versus optional is a booking dimension. Special session is an audience or calendar dimension. They are not three mutually exclusive categories. The same session may contain the standard trail, an extra booking and audience-specific operating choices.
| Program record | What it answers | Example decision | Required evidence |
|---|---|---|---|
| Core included | What a named standard admission includes. | The approved route and confirmed features available to that admission. | Current ticket or visitor-program record for the named season. |
| Optional add-on | What needs a separate reservation, ticket or local arrangement. | Dining, private hospitality or another venue-run experience booked apart from the base admission. | Current booking rule, availability and operating owner. |
| Special or limited session | When the program changes for a named audience or date. | A member preview, family program or quieter-access session that may still include the core route and may also offer add-ons. | Current session description, audience, calendar status and local owner. |
Core included layer
What belongs in the core light-trail promise?
The core layer describes what a visitor receives with a specifically named admission. It can include the approved route and features the venue has confirmed for that ticket and season. It should not become a generic list copied across every date, sales channel or audience.
Start with the visitor-facing promise, then connect it to the current program record. If part of the route, a display zone or a supporting activity changes, update the relevant season and channel together. For route, access and garden-site decisions, use our guide to plan the garden route and site constraints rather than expanding this program record into a site-design brief.
Optional booking layer
When should an experience be treated as an add-on?
Treat an item as an add-on when a visitor must make a separate booking, reservation or local arrangement beyond the named base admission. Dining, private hospitality and venue-managed spaces can fit this layer, but the exact offer belongs to the venue and may change by season or session.
Record the booking rule and the team that owns availability. An add-on offered during a member preview is still an add-on; the preview does not turn it into a core inclusion. Likewise, a separately arranged experience does not automatically change the lantern product scope unless the project brief identifies a physical or scheduling interface.
Audience and calendar layer
How should special or limited sessions be recorded?
A special session identifies a particular audience, date or operating format. Member previews, family-focused evenings and quieter or sensory-considered sessions are examples of program formats a venue may choose to define. Their availability, access arrangements and visitor wording must come from the responsible local team for that season.
Record which core elements remain available, which add-ons are offered and which operating conditions change. This prevents a limited-session promise from appearing as a standing feature across every ticket or date.
Responsibility boundary
Where does the visitor program meet lantern project scope?
The venue program and the lantern project can affect each other without becoming the same responsibility. Your venue team owns ticket wording, hospitality, staffing, accessibility decisions, local operations and public information. A lantern supplier works within the confirmed project scope for design, production, delivery and any agreed installation-support interface.
| Decision area | Venue or local owner | Project or supplier interface |
|---|---|---|
| Admission and booking | Ticket type, reservation rule, refunds, visitor communication and availability. | Only the confirmed event dates, access windows or physical interfaces needed for scoped work. |
| Hospitality and supporting program | Food, private spaces, member benefits, performers and service staffing. | Placement, access or coordination inputs only when included in the confirmed brief. |
| Special sessions | Audience definition, operating plan, accessibility decisions and public promise. | Relevant route, lighting or access constraints supplied as project inputs. |
| Lantern installations | Site approvals, local operations and responsibilities outside the confirmed supplier scope. | The products, deliverables and support explicitly confirmed for the project. |
Conflict check
Which program inconsistencies should be resolved before publication?
Included in one channel, optional in another
Identify the exact ticket, session and season each statement describes. If they differ, label them separately instead of forcing one universal answer.
Historical wording presented as current
Attach the year or season to the source and confirm whether the item continues before it appears in current visitor information.
Limited session shown as everyday availability
Name the audience or calendar restriction wherever the experience is mentioned.
No operating owner
Keep the item proposed or UNKNOWN until the responsible venue team confirms the promise and booking rule.
Program feature treated as supplier scope
Ask whether the statement describes a visitor offer, a local operating task or a contracted lantern deliverable.
Channels updated at different times
Record the source and update date for tickets, event pages, member messages, booking tools and project briefs.
Bounded public examples
What can current garden programs teach without becoming a template?
The Missouri Botanical Garden Garden Glow page (accessed September 14, 2026) separates standard event features from separately promoted dining or private hospitality and from named member or family occasions. That public structure shows why booking status and special-session status need separate fields. It does not establish a universal package for another garden.
Our Festival Insights guides provide other bounded examples. The VanDusen Festival of Lights guide distinguishes general visitor information, sensory-friendly access and group or rental questions. The Christmas at Kew guide keeps current visitor information separate from season-specific program details. The Cary lantern festival guide separates the route, supporting program and next-season planning questions.
Use these named examples to see how organizers publish different layers. Then return to your own season, tickets, owners and evidence. You can also compare public garden and venue examples without treating any one event as your operating model.
Planning worksheet
Which six fields should be complete before teams compare scope?
- 1. Experience labelUse one working name across the program page, ticket record and internal brief.
- 2. Season and statusMark the named season and whether the item is confirmed, proposed, historical or UNKNOWN.
- 3. Visitor promiseState what the visitor receives and the audience or date to which the statement applies.
- 4. Booking ruleName the admission, reservation or separate arrangement that controls access.
- 5. Owner and evidenceIdentify the venue team responsible for the current source and public wording.
- 6. Supplier interfaceRecord the route, access, schedule or product input that crosses into confirmed project scope.
When these fields are complete, marketing can publish a bounded visitor promise, operations can prepare the right local plan, procurement can compare like with like, and the project team can see which interfaces still need confirmation.
Next step
Map your garden event program before you compare scope
Tell us which experiences belong to your core trail, which require separate booking, which are limited to a named session and which venue–project interfaces remain open.