How to run the ticket tracker from the office, start to settlement. Everything a first-timer needs, on one page.
A batch from 1 to 2,000 is 2,000 tickets, not 1,999.
It is the last ticket a customer actually took — not the last ticket printed on the roll.
Your work is kept on this computer as you type. Save is what sends it to everyone else.
Use the Event dropdown in the blue header. It is the only place the year changes — the Year box on Settings just shows you which event you're in.
Starting a fresh year? + New Event copies the prices, batch sizes and split percentages from the most recent year, and copies none of its ticket numbers.
Ticket prices, tickets per sheet, wristband prices, and the batch size for each ticket type. Batch size decides how a delivery gets chopped into rows — 2,000 for singles means a delivery of 20,000 becomes ten rows.
Changing a price recalculates the whole event, including batches already entered. Changing a batch size only affects rows you create afterwards.
On each ticket tab, type the first and last number from the vendor's delivery note into the yellow box and press Generate Batches. The rows appear already split by batch size, all marked Untouched.
A second delivery later? Run it again. Batches are only ever added, never replaced. If a range overlaps rows you already have, nothing is added at all and the clashing batches are named — fix the range and try again.
Each batch moves through five statuses as the weekend goes on. Pick the status first — it decides whether you can type a number at all.
| Status | What it means | Last # Sold |
|---|---|---|
| Untouched | Still in the box. Counts as zero sold. | locked |
| Out for Sale | Out at a booth and still selling. The number changes by the minute, so nothing is recorded yet. | locked |
| Returned | Back in the office with tickets left on the roll. This is where you type the count. | type it |
| Sold Out | The whole roll went. The last number fills in for you. | filled in |
| Final Check | Counted and verified at the end of the event. | type it |
Nothing is locked into that order. Move a batch backwards whenever someone corrects a count, and edit an automatically filled number if the roll didn't quite finish.
Saturday and Sunday each get three counts: what you started with, what was left at the end of the day, and how many were handed out before the event. The app works out what sold:
The price is greyed out here because it lives on Settings. The money from pre-distributed wristbands is entered separately, as Presale Revenue.
At the end of each day, go to Totals and press Close Friday (or Saturday, Sunday). It records what has sold so far, less whatever the earlier days already claimed, into the Daily Sales Summary.
This is a snapshot for comparison, deliberately an estimate. It changes no revenue or settlement figure — those always come from the batch tables. Closing early costs you nothing: tickets sold afterwards land on the next day you close.
Closing a day that already holds figures shows you what it will write, old beside new, for each ticket type. Read it. Re-closing Friday on Saturday evening makes Friday claim both days' sales — the app can't tell Friday's tickets from Saturday's, because batches carry no times. If the new number isn't right, press Cancel; nothing is written.
The Not yet closed row is not a fourth day. It's the gap between what the closed days account for and what the batches actually say — it reads zero once every day is closed. Event total is the real figure, and the one the settlement uses.
Rides Total is each day's ride revenue: single tickets + ticket sheets + wristbands. It's money only — the three are counted in different units, so their counts don't add up. Triple tickets sit after it because they aren't ride revenue. A day that isn't closed shows a dash here even when its wristbands already have figures, because wristbands alone would understate that day. Its Event total matches Ride Revenue in the Revenue Overview.
Three separate pots, settled three different ways. Getting this straight is the whole point of the Totals tab.
Wristbands are inside ride revenue, so they're already counted once they appear there — the separate wristband line above it is a breakdown, not an addition. Triple tickets are outside it entirely, and appear again only in Final Settlement.
Like tax brackets: each percentage applies only to the money that falls inside its band, not to the whole total. A higher band never re-rates the money below it. The last band always catches everything above the one before it.
Presale Revenue is the one figure on that tab you type yourself — it sits in the Revenue Overview card, and it's dollars, not a ticket count.
It's still Untouched or Out for Sale, or the Last # Sold is empty. Those two statuses always count zero — that's why the field is locked.
Normal. The header reads the batch tables live; the summary only knows about days you've closed. Close the remaining days, or read Event total. Corrections you make to a batch after a day is closed land on the next day you close.
A later day is already closed, and days close in order. The message beside the button names the day to clear — clear that one, and this button comes back.
Clear it and close it again later, as long as no later day is closed. If the weekend has moved on, accept it: the missing tickets land on the next day you close, and the totals still reconcile. There's no way to reconstruct what belonged to which day after the fact.
Remaining plus presale is equal to or bigger than the starting inventory. Recheck all three counts for that day.
It overlaps batches that already exist, and the message names them. Nothing was added. Adjust the start or end number and go again.
The red × deletes a row on the spot, with no confirmation and no undo. Import your last export from Settings to get it back.
Someone else saved over them, or the page was reloaded with unsaved work on it. Settings → Import JSON restores any backup you exported.