Event reports and operational checks

Event reporting combines registration, attendance, order, and revenue evidence. Use the reports to answer a defined question rather than assuming every event metric uses the same source.

#Open event reports

Open Events → Reports. The report index links to:

Report currency and locale follow the workspace money context where supported.

#Reconcile attendee status

Registration state, payment state, and check in state are separate:

• Registration answers who signed up and for which event or slot.
• Order and payment answer what was purchased and settled.
• Check in answers who attended at the registration desk.

A registered attendee can remain unpaid in a manual workflow. A paid order can require registration reconciliation. A checked in attendee must already have the intended registration identity.

#Read revenue carefully

Revenue reports can include invoice linked values and supported untaxed revenue. Confirm whether the question is sales booked, payment collected, invoice revenue, or net amount after refunds. These are not interchangeable.

Use the Sales orders view for order level evidence and Finance reports for accounting conclusions.

#Prelaunch checklist

1. Verify event name, slug, dates, timezone, and venue.
2. Confirm public publication state.
3. Test the registration path with safe data.
4. Verify linked products, prices, currency, tax, and Stripe readiness.
5. Confirm slots, capacity, tracks, and locations.
6. Review sponsor and booth public content.
7. Test email and SMS templates.
8. Confirm registration desk devices and badge workflow.
9. Review privacy, consent, and attendee sharing settings.
10. Assign an operator for payment and registration exceptions.

#Event day checklist

• Confirm registration desk access before doors open.
• Keep a separate verified path for payment exceptions.
• Do not share administrator accounts between desk staff.
• Watch slot and booth capacity in the system.
• Record no show and check in state accurately.
• Monitor scheduled communications and provider failures.

#Closeout checklist

1. Reconcile registrations, orders, payments, refunds, and check ins.
2. Review attendee and revenue reports.
3. Disable or unpublish obsolete public registration paths.
4. Export required operational evidence.
5. Close booth and sponsor exceptions.
6. Review failed communications.
7. Preserve event records according to workspace retention policy.

#Troubleshooting

#Attendee and revenue totals differ

They measure different entities. Filter both to the same event and period, then reconcile registrations to linked orders or invoices.

#The report uses an unexpected currency

Check the workspace currency and the currency stored on source orders or invoices. Do not relabel historical amounts without an exchange rate policy.

#A refund is not reflected

Confirm the provider refund completed and the local invoice or order evidence reconciled. Report timing can differ from the original sale period.

#The report shows the maximum row limit

Narrow the event, date, status, or tier filter and export in bounded periods. Do not assume a capped screen contains the complete history.