Manage closures and capacity

Scenario and measures

Example: A service shares two devices and uses shorter holiday hours. Leave scope empty for an organization-wide closure. Use only the device scope for maintenance. Limit concurrent reservations to the real device count. Add a cleanup gap after service. Review remaining capacity by time, reservations rejected by conflicts, delays, and manual exceptions.

Close a period

1. Create an item in Availability rules. Select closure as the rule kind.
2. Enter the start and end of the closed period.
3. Leave the scope value empty to close the entire organization.
4. Enter a scope key and value to close one equipment or staff resource.
5. Save the rule. Check the closed period in the booking screen.

A closure includes its start and excludes its end. A closure from 09:00 to 12:00 does not block a 12:00 booking when all other rules allow it.

Limit concurrent bookings

1. Create a capacity rule.
2. Enter the maximum number of concurrent bookings.
3. Enter the time bucket size in minutes.
4. Enter the custom field key when capacity is separate for each resource.
5. Create bookings up to the limit. Confirm that the next booking is blocked.

Cancelled, no-show, and completed reservations do not consume current capacity. A rescheduled reservation does not count itself twice. The system checks capacity again at the new time.

Add a gap between bookings

1. Create a gap rule.
2. Enter the minimum gap in minutes.
3. Enter the same scope key when the gap belongs to a resource.
4. Confirm that new bookings are blocked inside the gap around an existing booking.

Capacity counts bookings inside fixed time buckets. A gap measures before and after each booking. Use a gap for cleaning time that must apply regardless of the booking position.

Check the result

• The time picker shows the closed period as unavailable.
• A time at maximum capacity appears full.
• A new booking cannot enter the configured gap for the same scope.
• Separate resources do not share capacity or gap counts.

Use Resolve availability problems when the result differs.