Demonstration · Illustrative data · BI Consulting Services
Vacation Races × BI Consulting Services

The 2026 season, park by park — registrations, revenue and the finance close on one board.

A race-series performance board built around the published 11-event calendar: pacing vs prior year, refunds and deferrals, add-on revenue, cost per finisher, and a month-end close view for the new finance seat.
Prepared for Jesse September 2026
Demonstration · Illustrative data
Region
Distance

Season scorecard — 2026 vs 2025

As of 4 Sep 2026 · completed + upcoming events

Registration pacing — cumulative, 2026 vs 2025

24 half-month periods · Jan–Dec
Solid line is 2026 to date (through early September); dashed line is 2025 over the same calendar. Bars show registrations taken in each half-month of 2026.
2026 cumulative2025 cumulative (same period)2026 per period

What this board answers

Three questions from the brief

The itinerary — 2026 race calendar across the parks

Bubble = registrations · Route = calendar order
Every event on the published calendar plotted where it is run. The dashed route joins the season in date order; the strip beneath is the same season as a timeline. Hover a park for its numbers.
Completed 2026Upcoming (registration open)Filtered out

Events ranked — registrations & net revenue

By event · vs prior year
Net registration revenue after refunds. Upcoming events show registrations to date against the same point in 2025.

Cost per finisher by event

Direct event cost ÷ finishers
Permits, shuttles, timing, medals and aid stations divided by finishers. Completed events only — upcoming events show budgeted cost against projected finishers.

Refunds & deferrals

Share of registrations · by event
Refunds leave the season; deferrals roll to next year's event and stay on the balance sheet as deferred revenue.

Merchandise & add-ons

Shuttles · iTab medals · photos · merch
Revenue on top of the entry fee, with attach rate (share of registrants who bought each add-on).

Finance close view — recognised vs deferred

Month-end · Jan–Aug 2026 actual, Sep–Dec plan
Entry fees are recognised when the event runs; everything collected for a future start sits in deferred revenue. Days-to-close is the finance team's own lag from month-end to books closed.
Recognised in monthDeferred balance at month-endDays to close

Ask the data

AI layer · mock
A natural-language question answered from the same model that drives this board — no exports, no pivot tables.
Which events are pacing behind last year, and how much revenue is at risk if they finish at today's gap?
Demonstration · Illustrative data · BI Consulting Services
Also from BI Consulting Services

Private AI on your own server

The "ask the data" ideas on this board are designed to run on a GPU server inside your own network — an open-weight model over your own documents, cited answers, no per-seat licence, nothing leaving the building. The short deck below explains how it works. Scroll through, or download it as a PDF.

Private AI Servers — slide 1 of 14
Private AI Servers — slide 2 of 14
Private AI Servers — slide 3 of 14
Private AI Servers — slide 4 of 14
Private AI Servers — slide 5 of 14
Private AI Servers — slide 6 of 14
Private AI Servers — slide 7 of 14
Private AI Servers — slide 8 of 14
Private AI Servers — slide 9 of 14
Private AI Servers — slide 10 of 14
Private AI Servers — slide 11 of 14
Private AI Servers — slide 12 of 14
Private AI Servers — slide 13 of 14
Private AI Servers — slide 14 of 14

Questions? Book 30 minutes: calendly.com/powerbiconsultingservices/30min