I am registering three people: designing group registration for a workshop
Three people and two available places: design group registration, participant details, partial acceptance and a clear waitlist.
Article language: English

In this article
"Number of people: 3." One field, two clicks and done. Only on the next screen does it become clear that two places are available. Does the third person wait? Do all three wait? Or was only the coordinator registered, her name politely copied three times by the form?
In a fictional mosaic studio, Marta registers a team for a Saturday workshop. She is not attending; she is organising an outing for three colleagues. Two have already decided to go, while the third will join once the group is agreed. The registration design must accommodate this ordinary situation without turning Marta into a detective investigating three almost identical confirmations.
First decide what one registration means
A group can be one application with several participants. It can also consist of independent registrations linked by a contact person. The models lead to different changes and messages. In the first, Marta can easily see the whole group; in the second, each person can have their own confirmation and way to update their details. Choose the model that fits how the event is administered.
Separate the person registering the group from participation. Ask directly whether that person is also attending. If so, their details can be used for one participant and then made available for checking. If not, their name should not appear on the attendance list simply because someone had to provide a contact address.
Humanitix's guide to checkout questions distinguishes questions asked once for the whole order from those asked separately for each ticket. Its examples include a company name and an individual attendee's name. This distinction helps organise questions even when designing another registration system.
In our studio, the team name and Marta's contact details concern the entire group. A name and choice of exercise concern a particular person. Do not ask for the company name three times. Nor should the first participant's answers be copied to the others without a clear action: a shared organisation does not mean shared answers to every question.
Before designing fields, map out what staff will do with each piece of information. If the instructor needs a first name to prepare a workstation, that justifies asking for it. If a surname is useful only because an old spreadsheet had that column, reconsider the need. For a group, every extra question multiplies the registering person's work.
The basic purpose and scope of a contact form (in Polish) remains a good starting point: ask for information needed for the next action. Here there is also the question of whom the information describes. A field should explain whether the answer concerns Marta, her team or the person occupying the third workstation.
Check whether the form permits a shared contact address for several people if that is how registrations are organised. A repeated email does not prove that two places belong to the same person. On the other hand, accidentally adding Ewa twice should be visible in the summary. Agree with staff how participants are identified instead of relying on a single field alone.
Give each place a recognisable label. "Participant 2: Ewa" can be found when returning to the form. Three collapsed panels all called "details" require someone to remember the order. When the name is not yet known, keep a stable place label so that a later correction does not accidentally move answers to another person.
Two places for three people: show the decision
Before Marta starts entering details, show availability for the selected number of people and the specific date and time. "Places available" may mean one free workstation. A group needs an answer to its own question: can we fit together? Choosing a date and time (in Polish) should lead to availability for the right workshop, not just the number of a Saturday.
The organiser must decide whether partial acceptance of a group is allowed. If so, ask Marta whether she wants to confirm two people and put the third on the waitlist. If the group will attend only as a whole, offer another date or waiting for three places. The interface should not make that decision based on the order in which names were entered.
Each path has a different effect on the day's arrangements. Two people may attend while the third stays at the office; the entire team may choose the following week. It is not enough to hide the split in small print under the button. The choice should name its outcome before the registration takes effect.
Describe status for each person. In our example, a summary could look like this:
- Ewa: place confirmed for Saturday at 11:00.
- Tomasz: place confirmed for the same workshop.
- Lena: on the waitlist, without a confirmed place.
- Marta: contact for the registration, not attending the workshop.
This describes an example, not a template for every event's policy. Under another model, all three could wait together. Still show who is waiting and what action follows when places become free. The recipient should not have to infer this from a general label such as "group status: in progress".
Also test changing the number of people after entering details. If Marta reduces the group from three to two, the person being removed should be chosen explicitly. Simply subtracting the last row can erase the wrong participant's information, especially after panels have been reordered. Name the person and the consequence, and provide a reasonable way to undo an accidental change.
Walk through a situation where two places were free at the start but one was taken before confirmation. Show the new result and ask for a decision about the changed offer. Do not automatically accept one person if Marta agreed to two being accepted. Retain the entered details so choosing again does not require reconstructing the entire group.
If places are temporarily held while the form is being filled in, say until when and what happens afterwards. Separate retaining answers from retaining a place. A form may remember names after a break even though availability must be checked again. Do not call a saved draft a confirmed registration.
Details can be completed later, but which ones must be clear
Marta wants to register three people, although she will not know the third person's details until tomorrow. The organiser should decide whether places can be reserved before the group is named. If complete details are required immediately, explain that condition before a long form. If they can be added later, show the missing information as a task to complete.

"Participant 3: add a name by Thursday" says more than an empty row. Also explain how to return to the registration. With a form completed over several visits (in Polish), recognising saved work and what is missing matters. A message with a link is not enough if, after opening it, the person cannot tell what still needs an answer.
Decide who may change details. Marta may remain the sole contact, or participants may receive their own invitations to complete information. In the second case, show Marta that an invitation was sent, but do not call the details complete. The recipient may not have opened the message yet.
Separate invitations need their own statuses: address not supplied, message awaiting sending, sent, details completed. Choose them to suit the tool's capabilities and the coordinator's needs. Do not show "delivered" if the system confirms only that the message was handed off for sending. That distinction determines whether a reminder makes sense.
When replacing a participant, check the associated answers. If Lena chose an exercise with small pieces, the new person should not inherit that choice without checking it. Changing only the name can leave someone else's preferences behind. The design should indicate which information belongs to the place and which to the individual.
Distinguish replacing a person from giving up a place. The first action may retain a confirmed place and require new details. The second may release the workstation to the waitlist. Do not design a single "remove" button if users cannot predict what will happen to the place when they press it.
A waitlist begins with an honest verb
"Register me" sounds like participation. "Join the waitlist" describes waiting. After the second action, confirm that the request has joined the queue, not that a workshop place has been secured. Preserve that difference on screen, in messages and when the person later returns to the registration.
Humanitix explains to people on a waitlist that an offer sent by email may not guarantee a ticket; it may be first come, first served. This is a specific example of why a notification of availability is not always confirmation of attendance. For your event, the message must reflect the rules actually adopted.
Decide whether a released place is held for the recipient for a specified time or whether the message offers an opportunity to register alongside others. In the first case, show the response deadline and its consequence. In the second, do not write "your place is waiting" if someone else can take it first.
For a group, specify what the offer covers. If three people were waiting and one place becomes free, Marta must decide whether to accept part of the offer. The message should lead to a view with that number and the earlier choice about keeping the group together. Do not silently change an agreement to "come together" into three independent waits.
When an older message is opened, check the current state of the offer. If the response deadline has passed, the screen should say so and indicate whether the group is still waiting. After the offer expires, show its result instead of an active accept button. If the offer has already been accepted, show confirmation rather than allowing the same request to be submitted again by accident.
Also provide a way to withdraw interest. Someone who has found another date should be able to stop waiting without cancelling the other confirmed places. For a partially accepted group, action names must distinguish those two outcomes. After a change, show the current status of the whole registration so Marta does not have to piece it together from several old messages.
The confirmation must work for both sides
At the end of the process, show the workshop name, date, location, list of people and each person's status. Add what still requires action: missing details, waiting for a place or a response to an offer. The page shown after submitting a form (in Polish) should confirm the actual result, not just a successful button press.
Give staff the same breakdown. The instructor needs a list of confirmed participants; the person handling registrations also needs those waiting and missing details. If both groups enter one spreadsheet without statuses, it is easy to prepare a workstation for someone who never received a place or overlook someone added later.
In the organiser's summary, distinguish the number of registrations from the number of confirmed people. Marta's one group can mean two occupied workstations and one person waiting. A counter saying "three registrations" alone does not allow staff to prepare materials or assess free places. Agree on names for those figures with the person who will use them before the workshop begins.
During a seasonal peak in enquiries (in Polish), this clarity reduces the need to reconstruct the situation manually from correspondence. Choose one recognisable registration identifier and keep it when the group changes. It helps connect a conversation with Marta to the right group, even if a different name now appears in the message.
Review the registration through one complete journey: three people, two places, adding the missing name, replacing a participant, and then an offer to a person on the waitlist. Look at Marta's view, the messages and the instructor's list. Each should describe the same situation after every change.
At Aeneia Design, that journey can be translated into a page and interaction design before implementation. Start by deciding when you accept a group and how you confirm individual places. The fields, buttons and messages follow from those rules; reversing the order usually ends with a note nobody noticed.
When Marta closes the page, she should know who will come on Saturday, who is waiting and what she still needs to do. If she has to call only to decipher the word "registered", the form has passed work on to the staff. On Saturday, the instructor should be able to prepare the right number of workstations without another call to Marta.







