A Saturday that was meant to be sunny
Your farm park has outdoor fields, a play area, animal barns, an indoor soft play and a café. On a dry day, visitors spread across the site. On Thursday, the forecast for Saturday was sunny, and you sold a full day. By Friday evening, it has changed to heavy rain all afternoon.
On Saturday, the outdoor areas are empty after lunch and the barns, soft play and café are packed well beyond comfortable. Staff are moved from outside to manage queues indoors. Families who paid full price leave early, unhappy, and some ask for refunds.
The ticketing system had no idea the weather had changed. It kept selling walk-up tickets at the gate until the car park was full.
Why capacity ignores the weather
Capacity at most attractions is a single number per day, based on the whole site being usable. But the real capacity depends on which areas are open and how people use them, and the weather changes that more than anything.
Your team knows this. The manager watches the forecast and makes a call on the day. But that call is not connected to the ticketing system, so online sales carry on at the sunny-day level until someone remembers to change them.
Indoor areas often have their own limits, set by your own risk assessments and policies, which a whole-site number does not respect.
What weather-blind capacity costs
| Gap | Result |
|---|---|
| One capacity for all weather | Indoor areas overcrowded on wet days |
| Walk-up sales continue | More people arriving into a squeezed site |
| Decisions made on the morning | No time to tell booked visitors |
| Staff plans set for sun | People in the wrong places on a wet day |
| No record of weather against visits | Future planning based on memory |
What capacity is safe for each area is decided by your own policies and risk assessments. The problem is getting those decisions into the ticketing system in time.
Linking capacity to forecast and open areas
We add a small capacity planner that sits beside your ticketing system.
- You set capacity rules per area and weather type, based on your own assessments: for example, the indoor limit on a wet day, or a lower total when the outdoor fields are closed.
- Forecast data from a weather service with an API is checked several times a day for the days ahead.
- When the forecast changes enough to trigger a different rule, the planner proposes new ticket limits and alerts the duty manager to approve them.
- Once approved, limits are updated in your ticketing system for online and walk-up sales.
- Booked visitors can be sent a message about what to expect, such as areas likely to be closed or wet weather clothing, and your options if they want to change date.
- After each day, actual weather, visitor numbers and area use are recorded, building a picture for next season.
The duty manager always approves changes. The planner prompts; people decide.
Situations it covers
- High winds that close outdoor play equipment or tall structures, following your own rules.
- Very hot days where shaded or indoor areas become the constraint.
- Forecasts that change on the morning itself, when only walk-up sales can be adjusted.
- Events on the same day, such as a lambing weekend, with their own area limits.
A wet Saturday afterwards
On Friday afternoon, the planner flags the new forecast and proposes a lower limit. The duty manager approves it. Online sales stop at the new level, walk-up sales are capped, and booked visitors get a message offering a date change. Staff plans are adjusted before Saturday. Indoor areas are busy but manageable.
- Capacity that reflects which areas are usable
- Changes approved in time to affect sales
- Booked visitors told what to expect
- A record of weather and visitor patterns
Does this happen at your attraction?
- You sell the same tickets whatever the forecast.
- Indoor areas overflow on wet days.
- Capacity changes are made on the morning, if at all.
- Walk-up sales carry on when the site is squeezed.
- You plan next season from memory, not records.