Events — admin

Who opens it: an organizer setting an event up, or coming back to change a detail a fortnight later.

What they came to do: see every event this organization is running, and open one to change its dates, its days, who may come, how they sign up, and when it goes live.

True when they leave: the event says what it is going to do, and every change has a name against it in the audit log.

Decisions already made

• Status moves one way, through the service. draft → published → live → closed → archived, and only EventService. Nothing sets a status by editing a column: publishing has to check the plan, open the registration forms and schedule what was scheduled, and a column edit would skip all of it.
• Draft is invisible. A draft event has no public page and no open form — its link 404s. Publishing is the moment anything becomes real, which is why the button says so.
• Days are the unit everything else hangs off. A ticket admits somebody to a day, a check-in point accepts named days, capacity is per day. An event with one day still has one — the organizer sees "Day 1" and the machinery sees a row.
• Times are stored UTC and shown in the event's own timezone, including in exports. A day that starts at 8 AM in Chicago starts at 8 AM on the screen of somebody reading it in London.
• Its parts live in the tabs below, each with its own page here: days and capacity, check-in points, registration forms, emails and reminders, rules, scanning devices.
• Start from an event template rather than an empty form when the shape is a shape somebody has done before: event-template-import.md and event-templates.md.
• Archiving is not deleting. An archived event keeps its registrations, tickets and check-ins, because a question about last year has to have an answer. Data goes when retention says so, not when a screen says so.

Open questions

• Nothing on this screen says what an event is costing against the plan's attendee cap; that lives on usage.md, one click away, and the first week of a big event is exactly when somebody wants both at once.
• Duplicating last year's event is "export it as an event template, then import it", which works and is not obvious.