Start with what each number means
One order can contain multiple tickets, so paid order count differs from ticket count. Confirmed arrivals measure check-ins rather than payments. The example presents these figures together at different stages. All days and quantities are fictional, not customer results or a forecast for your event. Use consistent definitions when comparing editions and discussing progress.
Use consistent definitions when comparing editions.
Track paid sales separately from reservations
Pending and expired reservations are not completed sales. Check order states when assessing revenue and availability. The actual overview loads relevant records according to permissions. These controls only switch fictional scenarios. The chart illustrates a sales distribution, not a live connection or a promise that every analysis and filter appears exactly this way in the app.
Reconcile against real orders and provider records.
Gross revenue is not profit
Ticket revenue is a sales measure, not the complete event settlement. Platform and provider charges, refunds and production expenses affect the amount remaining. Food or other ticket inclusions also change the budget. Use the separate costs page for an illustration and actual accounting records for final figures. Do not treat attendance growth as additional revenue.
Track revenue, costs and payout as separate amounts.
Use arrivals to support the admission team
At the entrance, the useful questions are who has arrived and who is still expected. Restrict data access to the relevant roles and check the selected event. Records are current when retrieved or refreshed; this page does not promise a continuous push update for every screen. Agree how the team checks information during connectivity problems.
Agree when and how the team refreshes the overview.