Building capacity

Max Capacity is the most people a building may hold at one time. Switch capacity checking on and Axiom refuses any booking that would take the building past that number.

It is the building that is checked, not the room. Two rooms let at the same hour are counted together, which is what makes this different from the capacity you set on a room.

Go to Facility → Buildings, open the building, and you will find two things beneath the address:

The number is always collected, so turning enforcement on later is one tick - there is no data to go back and fill in.

Both are warnings, not refusals: you can carry on and save.

• Saving a room whose capacity is larger than its building’s maximum tells you that bookings using the room’s full capacity will be refused.
• Setting a building’s maximum below a room already in it tells you the same thing from the other end.

Neither appears while capacity checking is switched off for that building, because nothing would be refused.

Axiom counts the size each booking is made for at the moment they overlap.

Only the overlap counts. Twenty people from two until half past, and twenty more from half past until three, is never forty at once - so a busy day of back-to-back hires does not add up against you.

A session provider with no Default Building is never checked at all - there is no building to fill.

You do not have to save to find out. Once the booking panel is complete, a message appears at the top and Add Bookings is disabled:

Village Hall will exceed its maximum capacity because this booking allows up to 120 people.

Lower Maximum Attendees, or move the booking to another time, and it clears.

Repeating bookings are checked date by date. In the preview grid, dates that would overfill the building go red alongside any that clash with an existing booking, and red rows are not created. Saving the series creates the green dates and skips the red ones.

If the building fills between the panel checking and you saving - someone else taking the last places - the save is refused and a Building at Capacity message explains it, naming the building, its maximum, how much of it was already booked at that time, and what this booking asked for.

Editing a repeating booking is refused whole rather than in part. Occurrences that already exist are in the diary and people are expecting them, so Axiom will not quietly drop one - adjust and save again.

Customers booking through your portal are checked in exactly the same way, before any payment is taken.

A portal booking has no Maximum Attendees field, so it is counted at the room’s full capacity. A repeating booking is refused whole if any of its dates will not fit - Axiom never takes payment for a series and then quietly leaves dates out of it.

• It is not a fire or licensing limit, and it makes no claim about who is in the building on the day.
• It does not report on how full the building has been, or what would have been refused.
• It never changes an existing booking. Switching it on affects what can be booked from then on.