An event calendar is a portfolio. Living Lab shows what each event returned to the destination and which slots are worth fighting for. It also shows how to sequence the year so the routes, rooms, and local firms can carry it, on the same numbers.
One model of the whole calendar and everything it draws on: every event with its class and history, every route and its seat capacity by week, hotel supply and rate, paydays and holidays in each origin market, weather, competitor dates, and the search interest and sentiment there. Signal137 measures what each event delivered. Demand137 ranks the candidates, dates, and rights for next year by expected demand and exposure, with the binding constraint named for each slot.
What each event in the calendar delivered: attendance by origin, visitor spend, room nights, GVA, tax, and jobs, net of displacement and net of the calendar around it. Which events earned their slot and which were carried by their neighbours. Where two events competed for the same rooms and routes. Event over event, year over year, on one method.
Which events, dates, and rights to hold, add, move, or drop across next year. Every slot scored on calendar collisions, holidays, paydays, weather exposure, and the access ceiling for the week, with the binding constraint named. Expected attendance range, break-even gap, and exposed demand per slot. The mix that maximises what the whole year returns. Every number marked observed, derived, or inferred.
| Product | Your question | You get | What it changes |
|---|---|---|---|
| Demand137 | Which combination of events to commit to across the calendar | Net incremental demand each event adds once the rest of the calendar is accounted for | The mix that maximises calendar-wide value, not the sum of individual bids |
| Demand137 | When and where to sequence events across the year | Seasonal demand pattern and capacity headroom by month, with the shoulder weeks priced | Events placed where they fill gaps or defend strength |
| Demand137 | Does this new bid duplicate or reinforce an existing event? | Overlap in source markets, venues, dates, and audience with events already committed | The bid accepted, adapted, or declined on its net effect on the calendar |
| Demand137 | How do we sequence so the supply chain grows with the calendar? | A calendar paced to absorptive capacity: caterers, ground transport, airlift | Local firms scale into the demand instead of losing it to imports |
| Demand137 | How far ahead can a calendar be planned this way? | One to three years where bids, venues, and hotel supply are defined; scenario-based beyond that, and stated as such | The horizon states where certainty ends |
| Signal137 | What did last year's calendar deliver, event by event? | Every event ranked on jobs, tax, GVA, room nights, and retained value, on one method | The productive events supported; the mix optimised for retained value |
| Signal137 | Did the two spring events cannibalise each other? | Displacement between events in the same catchment and window, measured | The clash seen in the data before it is repeated |
| Signal137 | How does a one-off tournament compare with the ordinary calendar? | The one-off tournament beside a full year of the ordinary calendar, on one method | The next bid priced against what the calendar already pays every year |
| Both | Does this replace our bid-evaluation process? | No. Your process tests whether one event stands up; this tests whether the approved mix makes a strong calendar | The two run side by side |
| Both | Who holds this, and where? | Model, data, and a trained team inside your jurisdiction | The capability survives the change of official or consultant |
Each event ranked by net incremental contribution: GVA, tax, jobs, and retained revenue added on top of what the rest of the calendar already delivers. The anchor events identified.
Both candidates modelled against the existing calendar, the same hotel capacity, and the same workforce. The one that displaces less and retains more ranks first.
Weeks with underused hotel and venue capacity mapped against candidate events by economic return. The destination bids to fill gaps.
Capacity tested by week: hotel rooms, venue availability, transport access, and workforce. The calendar rebalanced to spread load and sustain employment through the year.
Every event assessed against its contribution to the whole. The portfolio view shows what to keep, what to replace, and what timing change would improve the year.
A hotel pipeline decision is usually made on an occupancy trend, extrapolated forward. That answers a different question from the one a planner, a developer, or an investor faces: is the market short of rooms overall, or short of rooms on the 18 nights a year when demand peaks?
A new route photographs well on launch day. Whether it is still flying in year three, without deep discounting, and still worth the airport incentive that started it, is a quieter question, and it is the one that comes up at renewal.
A race track, an arena, a stadium: each is built for a peak it reaches a few dozen times a year. The gap between peak and off-peak operational need is the commercial challenge behind every sports-anchored development, and the reason mixed use is the answer rather than the fashion.
Most destinations run near capacity for part of the year and well below it for the rest. A visitor added in the peak displaces one already there. A visitor added in the shoulder fills an empty room and is served by staff who would otherwise be idle. Almost no destination runs the calculation before fixing a date.
We turn messy event and tourism data into decisions that help communities grow. Bring curiosity and rigour. We will hand you questions nobody has answered yet.
