Terminology — admin

Who opens it: an Owner or Admin who winced at the word "attendee".

What they came to do: make the product say what their organization says — Volunteer, Delegate, Student, Shift, Badge, Gate.

True when they leave: every screen, email, ticket and badge uses their words, and nothing anywhere has to be re-translated by a reader.

Decisions already made

One noun, one place. No attendee-facing word is hardcoded in a view or an email — it is term('attendee'), and that is a law in CLAUDE.md. This screen is the one place the words are set.
Singular and plural, both typed. English plurals are not a function, and "Staff" is its own plural. Asking for both is shorter than getting one wrong.
The variants matter. check_in_point renames the general idea; check_in_point.gate, .satellite and .zone rename the three kinds, because "Bus Boarding" and "Venue Entry" are not the same word in the same organization.
An event template brings a vocabulary with it. Importing one sets these words — the School Field Trip calls a day a Trip, the Conference calls a ticket a Badge — and anything already renamed by hand is kept.
A word this release does not rename is refused with a reason, not silently dropped, so an event template written for a later version says what it could not do.
24 characters; letters, spaces, apostrophes and hyphens. A noun has to fit on a badge and in a column heading.
Cached, and cleared on save. The words are read on nearly every request, so they are cached per organization for an hour and forgotten the moment one changes.

There is no preview. Saving and looking at a ticket is the way to see the effect, which is one step too many.
Nothing warns that a word collides with a different concept — calling a day a "Ticket" is allowed and would be cruel.