Publish it. Fill it. Check them in.
Event Manager is the operational half of Turnout: events with real occurrences and capacities, registrations that belong to a person, and a check-in write that makes attendance a fact instead of a hope.
Four steps, one data path
Each step writes to the same tables the analytics and the agent API read, so there is no nightly export to trust.
Draft and publish
An event carries occurrences (date, start time, timezone, capacity). Publishing is a deliberate act and cancelling is reversible — both require confirm: true when driven by an agent.
- ▸ Occurrences with explicit timezone
- ▸ Capacity per occurrence
- ▸ Draft → published → cancelled
Collect RSVPs
Registrations land against an occurrence, not against a spreadsheet. Each participant row has a status the door can trust: registered, attended, no-show, cancelled.
- ▸ One participant row per person
- ▸ Status history preserved
- ▸ No duplicate registration per email
Check in at the door
Check-in flips a participant from registered to attended. That single write is what turns a sign-up list into a verified attendance number.
- ▸ Search by name or email
- ▸ Attended is written, never inferred
- ▸ Cancellations excluded from the denominator
Read what happened
Attendance rate, no-shows and repeat visitors are computed from those rows, each printed as numerator / denominator so the number can be argued with.
- ▸ Every rate shows its denominator
- ▸ Zero denominator renders as —
- ▸ Repeat attendance, not just reach
Query the public event feed the way an agent does
This panel runs in your browser against the public endpoint. It is the same query language the MCP tools use, and the same rows the platform home prints — events published inside Turnout, never imported or staged ones.
| Event | City | Starts | Price | Mode |
|---|
Events & occurrences
Recurring or one-off, each occurrence with its own start time and capacity.
Open the console →Participant list
Import or collect registrations, then work the list by status at the door.
See a guest list →Check-in
One write per arrival. Verified attendance is what every later metric divides by.
Then read Analytics →