Sold tickets are only part of the guest count

For nonprofit event capacity planning, choose one unit—usually people or usable seats—and make every registration option consume that unit. An individual ticket may use one place, while a table package uses eight or ten. Sponsor allocations, complimentary admissions, and holds also belong in the same count before public ticket sales open.

The practical rule is: public inventory plus reserved inventory must never exceed the event limit your team has approved. A list of ticket products is not yet a capacity plan.

Start with one approved limit

Record the event's approved limit and the person who owns it. For a seated gala, the useful unit may be usable seats. For a general-admission gathering, it may be people. Do not mix tables, orders, and people in the same total.

This article does not set a legal occupancy number. Use your venue agreement, safety requirements, accessibility plan, catering commitments, and qualified guidance to determine the limit. Once that number is approved, registration should protect it.

Current Eventbrite capacity documentation distinguishes the quantity available for each ticket type from the event capacity across ticket types. Current Givebutter guidance makes the same operational distinction with a gala example: a category can have its own limit while all categories still draw from one overall capacity.

That is the model to preserve even when your software uses different labels.

Give every registration option an admission multiplier

Create a capacity worksheet before building the ticket page. Use one row for every way a place can be claimed:

• individual paid or free ticket;
• table, family, or group package;
• sponsor allocation;
• complimentary admission;
• staff-created registration; and
• ticket or seat hold.

For each row, record the number of products available and how many admissions one product creates. Multiply those numbers to get the capacity consumed.

Suppose a gala has an approved limit of 240 people. Your worksheet might allocate 120 individual tickets, eight public tables of ten, two sponsor tables of ten, 12 complimentary admissions, and eight held places. The product quantities look unrelated, but the admission count is exact: 120 + 80 + 20 + 12 + 8 = 240.

Current Humanitix package guidance describes a table of ten as a package containing ten individual tickets. TryBooking's capacity documentation likewise says a group ticket's capacity must reflect the number of people it admits. The interface differs; the control is the same. One table purchase cannot subtract only one place.

Keep reserved places inside the total

A sponsor table consumes capacity before its guest names arrive. So does a complimentary block or a staff hold. Do not leave those places in a private spreadsheet while the public ticket page continues offering the whole room.

Current Eventbrite hold documentation says a hold removes tickets from public sale so they can be released later or given to specific people. Treat every reserved allocation as one of three states:

1. Held: unavailable to the public and attached to a purpose, owner, and review date.
2. Claimed: converted into actual admissions without changing the total capacity consumed.
3. Released: returned to public inventory through a recorded decision.

Unknown guest names do not make the seats empty. Names belong to the later buyer-and-attendee workflow; capacity belongs to the admission commitment.

Test the shared count before launch

Use a preview or test event to exercise each path. Start from a written expected-remaining count, then:

1. claim one individual ticket and confirm availability falls by one;
2. claim one full table and confirm availability falls by every included seat;
3. create a complimentary registration or hold and confirm public availability falls without a paid order; and
4. release the hold and confirm only those places return.

Then place a mixed order if the platform allows it. The event total should remain the controlling limit even when a ticket type still has unused category inventory.

This catches the exact confusion one organizer described when three price tiers appeared to create 525 tickets against a 175-person event limit. That discussion is one example, not evidence of how often the problem occurs. It shows why the team should prove the configuration instead of assuming three ticket quantities share a pool.

Keep later event workflows separate

Capacity answers how many admissions may exist. It does not assign guests to tables, decide who gets a released place, transfer an issued ticket, or check anyone in.

After registrations exist, build the event seating plan from confirmed guests and visible holds. If the event reaches its limit, use a capacity-aware waitlist rather than increasing inventory in a second system.

Registration is ready to open when every public and reserved path has an admission multiplier, the total cannot exceed the approved limit, and the mixed-path test matches the worksheet. That gives your team one number it can defend from the first sale through the final allocation.