How do booking rules and slot quotas work?

ReserveringBeheer

Kai's booking rules ensure fair access to shared assets through configurable restrictions. Rules can be group-wide or asset-specific, and asset-specific rules layer on top of group rules.

Slot quotas

Limit how many bookings a member can hold over a period:

Hours per period — total booking hours over a day/week/month/quarter/year
Slot count per period — number of bookings allowed in a window
Quotas reset at the start of each period

Duration limits

Cap how long a single booking can be:

Maximum booking length (e.g. 8 hours)
Maximum consecutive days
Minimum booking duration

Advance booking window

Control how far ahead a member can book:

Minimum advance notice (e.g. book at least 2 hours ahead)
Maximum lead time (e.g. no more than 90 days ahead)

Blackout periods

Block bookings during specific date ranges — maintenance windows, owner-reserved periods, holidays.

Day-of-week restrictions

Allow or deny bookings on specific weekdays. Useful when an asset is shared with a non-Kai user on certain days.

Consecutive booking limits

Enforce cooling-off periods so one member doesn't monopolise the asset — e.g. require a gap of N days between consecutive bookings by the same person.

Special reservations

Annual extended-booking privileges:

Longer reservation windows (e.g. a 2-week vacation)
Require advance notice
Limited per year per member

Usage-based rules

Block further bookings once a member exceeds usage thresholds (hours flown, kilometres driven, etc.) — often combined with billing.

Weekend / peak-time weighting

Treat weekend or peak-hour bookings as worth more slots than off-peak ones.

How rules combine

When you try to book, Kai checks every applicable rule. If any rule fails you'll see a message explaining which limit was hit and why. Asset-specific rules override group-wide rules when both apply.