Compare the operating models
In this fictional example, Ada reserves three places for Ada/Bo/Cy. A company organiser reserves six places and supplies names later. One organiser record does not mean one attendee; six unnamed places are not six invented people.
| Business requirement | Party booking | Individual registrations |
|---|---|---|
| Single organiser | One booking contact | Could duplicate communication |
| Participant-specific attendance | Roster beneath booking | Each registration has its participant |
| Names supplied later | Reserve quantity, roster pending | Do not fabricate identities |
Work through the chosen model
A party record stores organiser, session, reserved quantity and payment contact where needed. Participants link beneath it, with names only when actually supplied. If people independently choose/pay/change sessions, individual registrations may fit better.
- Reserve the agreed party quantity
- Collect roster when needed
- Check attendance by actual participant
Party bookings simplify group contact but need participant detail when attendance matters. Individual records improve independence but can burden one organiser with repeated entry.
Ada has one booking, three places and three names. The company has one booking, six places and a pending roster. Total reserved places are nine, not two.
When the other model fits
Bo and Cy book and pay independently with separate change rights. Should Ada own their booking?
Show the worked answer
No. Keep their registrations independent and add a social/group link only if needed.