Separate session space from event space
Imagine three reading discussions, each with eight seats. Each discussion needs its own capacity of eight. If there is no further restriction on the program, leave the event-wide Attendee limit empty. Setting that total to eight would cap the entire program, even with seats left in other discussions.
Sometimes both limits are useful. A room might hold thirty people while each activity has eight places. In that case, the room's total and each activity's capacity represent different constraints. A signup must fit both; an open activity cannot override a full event.
Try a group reservation against the remaining seats
Our reading discussion has eight seats, with five already used. One reader and two friends need three seats in total. With whole-party counting enabled, that reservation fits exactly. A group of four needs another session.
Afternoon reading discussion
5 of 8 spots filled
Party size counts toward spots.
How many people want to join?
An exact fit: all eight seats would be filled
5 reserved + 3 in this party = 8 of 8 seats. The person filling out the form is included in the party.
- 1
Set the session capacity
Give the discussion slot eight places. Keep its real date and time visible so guests can choose the correct session.
- 2
Allow a group reservation
Enable Allow group signups if one reader may reserve for others. A party of three includes the person filling out the form; it is not three extra guests.
- 3
Count each person against the slot
Enable Count whole party toward slot capacity for the discussion. Collecting a group size and counting that group against a slot are separate choices.
| The reservation is for | Slot places used | Whole-party counting |
|---|---|---|
| Three readers in a discussion | 3 seats | On |
| One family conference | 1 appointment | Off |
| One dish brought by a family | 1 contribution | Off |
Understand a full slot and a temporary hold
Availability can change while someone is looking at the page. If two visitors try for the last place, Signup Bubble checks and claims capacity in the database. The later request may need another slot, even if the page originally showed a place available.
When email confirmation is enabled, pending signups temporarily hold their places. A nearly full event can therefore include people who have not confirmed yet. Check the signup statuses before reporting a final attendance count. Unconfirmed holds expire if the person does not complete confirmation.
If a guest cancels, review the current availability before offering the place to somebody else. Avoid promising a seat based on an old screenshot or an earlier count.
Keep capacity and timing decisions separate
A slot limit prevents too many commitments to that slot. It does not prove that one person can fulfill two commitments at the same time. Enabling Allow multiple slot selections is useful for a volunteer working successive shifts, but it does not check for overlaps.
When guests should attend exactly one discussion, require a slot and keep multiple selection off. When guests may help twice, label each shift with its time and ask them to choose compatible assignments. Review overlapping responsibilities yourself when they matter.
Check three cases before sharing
Use the guest preview to inspect the form, then compare these cases with the saved settings. A preview helps you see the experience; the actual limits determine whether a submitted reservation can fit.
- One person wants the last seat: one signup should consume one seat.
- A party of three wants the last two seats: whole-party counting should prevent that reservation.
- A session is open but the event is full: the event-wide cap should be intentional.
- A family reserves one appointment: extra family members should not consume additional appointment slots.
- Pending and confirmed signups are distinguished when you review attendance.