Day change

Moving a person from one day to another after they registered — the IV Day "came for Day 1, is coming on Day 2" request — from the person's page ("Change day").

Who does it: an organizer or registration-team member, often at the help desk, sometimes the night before.

What they came to do: put the person (and their family) on the right day without anyone ending up with a ticket that lets them in on the wrong one.

What must be true when they leave: the old ticket no longer works and says what replaced it, the new ticket works at the new day's gate, the family is still together on one ticket, and the change is on record with who did it and why.

Decided

• Tick the days the person should be on; the confirmation lists what will happen, person by person, before anything changes. Days are named with the weekday of their date ("Day 1 (Saturday) → Day 2 (Sunday)"); a stored day name never carries a weekday (Pilot Day, C1).
• After the change the page reloads, so the tickets table shows the new ticket (C4).
• Their ticket is replaced by a ticket for the new day. Scanning the old code shows "Void ticket" and the new code.
• The family moves with them when the event is set up that way; the organizer can switch that for one change.
• A child admitted on a chaperone's ticket cannot be moved to another day alone, and neither can the chaperone.
• Someone already let in on the day they are leaving can be moved only with "Change anyway" and a reason — and the gates for the new day will still refuse them (see decisions-pending).
• A full day refuses the change; one-day registrations stay on one day.

Open

• Letting a person admitted by mistake in on the new day (owner decision).
• The same change over the API (week 14).