Home is the first thing you see when you log in. It's a deliberately minimal v1: a few headline numbers, a short list of things that need a decision, and your upcoming bookings. Deeper analysis lives on other pages, which we point to below.
Here's what each part means.
The three tiles
Today · covers
Total guests in confirmed bookings for today. A "cover" is one guest — a party of 4 booking a class = 4 covers. Underneath, a smaller sub-label shows the booking count for the day ("N bookings"), so you can see covers and party count at a glance.
Next 7 days · covers
The same idea for the next 7 days. Covers for the rolling week ahead, with the booking count as the sub-label.
The periods are fixed — Today and Next 7 days. There's no today/this-week/this-month selector, and there's no separate "Reservations" tile: the booking count is always just the sub-label under covers.
Deposits due
The sum of unpaid balances across your open invoices — what guests still owe you. The sub-label shows how many invoices are open ("N open invoices").
There's no automatic reminder tied to this tile. If an invoice goes unpaid, nothing is sent on its own; overdue balances surface in Needs attention (below) for you to act on.
What's deliberately not on Home
Home is the whole team's landing page, so it shows no revenue figure on purpose — a forward or recognized revenue number isn't for every employee's eyes. The money and performance views live elsewhere:
- Recognized / accrual revenue lives on the Accrual page (/accrual). That's the accrual-basis number your bookkeeper wants — a March booking paid in January is recognized in March, when the experience happens, not when the cash landed.
- Backlog — confirmed covers by week for the weeks ahead — lives in Analytics, under "Confirmed covers by week," your forward book of business.
Needs attention
A short list of bookings that need a decision from you. Only two kinds of item appear:
- Overdue invoice. An invoice past its due date with a balance still owed. Decide: send a reminder, extend, or cancel.
- Buyout with no card on file. A full-store buyout that has neither a saved card nor a live invoice backing it — there's no money path yet. Decide: collect a card or send an invoice.
This list shouldn't be longer than a couple of items most days. If it's growing, that's a signal to spend a half-hour clearing it.
Upcoming bookings
Below Needs attention, Home shows your next bookings in chronological order — guest, party size, experience, and start time — each linking through to that day on the run sheet. When there's nothing on the books yet, you'll see a short empty state instead.
Where the deeper analysis lives
Home tells you what to do today. The Analytics page tells you what to do next quarter:
- Booking funnel. Where guests drop off between browsing and paying.
- Class / experience performance. Utilization and results per experience.
- Guest mix. New vs. returning guests for confirmed bookings.
- Where guests live. Which ZIP codes your guests come from, with bookings, covers and average party size per ZIP, and a CSV you can drop into a mapping tool. More on this below.
- Backlog. Confirmed covers by week for the next several weeks.
Analytics is a section in its own right — there's no separate "Cohorts" report; repeat-vs-new behavior is the guest-mix view above.
Where guests live
The "Where guests live" section on Analytics shows the ZIP codes your guests come from, for confirmed bookings with an event date in the date range you've picked at the top of the page. It's the footprint of your trade area: where your paying guests actually drive in from, not where you guess they might.
Where the ZIP comes from
When a guest pays by card at checkout — or a card is saved for a deposit or a prepaid booking — the card form asks for a billing ZIP code. That ZIP is kept on the guest's record and refreshed each time they pay by card again. Nothing extra is asked of the guest, and only US ZIP codes are kept.
Because it comes from the card form, some bookings have no ZIP:
- Reservation-only bookings, where no card is collected.
- Walk-ins and in-store payments on the Square register.
- Bookings made before September 2026, when ZIP capture was added. There is no way to backfill these.
That's why the section leads with Bookings with a ZIP — the share of the range's bookings the table actually describes. If it reads 40%, the ZIP list explains 40% of your bookings, and you should read it with that in mind. Coverage grows over time as more guests pay by card.
Reading the table
Each row is one ZIP code, sorted by bookings:
- Guests, bookings, covers. How many distinct guests from that ZIP booked in the range, how many bookings they made, and how many seats those bookings filled.
- Avg party. Covers ÷ bookings. This is the number to watch for group trends: a ZIP with a handful of bookings but a high average party is sending you birthday parties and team outings, even if it never tops the bookings list.
- Revenue. The booked value of those bookings at list price.
- Share and cumulative. That ZIP's share of the ZIP'd bookings, and the running total down the list — so you can see at a glance that, say, your top five ZIPs account for 60% of bookings.
The page shows the top 25 ZIPs. If you run two or more locations, a second table lists each location's coverage and top ZIPs side by side, so you can see whether each store draws from its own neighborhood or whether they overlap.
Downloading the CSV
Download ZIPs (CSV) gives you the full list for the date range — one row per location and ZIP, with guests, bookings, covers, average party size and revenue. It contains ZIP-level totals only; no guest names, emails or booking details leave with it, so it's safe to hand to an agency or a landlord.
Two things it's good for:
- Mapping. Excel's 3D Maps, Google My Maps and most mapping tools will plot a spreadsheet by ZIP code directly. Use bookings or covers as the size and you have a heat map of your trade area.
- Site selection. If you're weighing a second location, the ZIPs your current guests already come from are the strongest evidence of where a new store would draw.
Bookings whose guest has no ZIP appear as a "(no ZIP)" row per location, so whoever reads the file can see the coverage too.
For franchisors
If you manage franchisees, the Franchisee analytics page has the same section: coverage and top ZIPs per franchisee, a network-wide ZIP table, and its own CSV download with one row per franchisee and ZIP.