Guide
How Availability Conflicts Work
An availability conflict in Kasura is a booking whose dates overlap an existing active booking on the same asset, determined directly from Kasura's own booking records.
What availability means
Availability describes whether a given asset can be booked for a given period, and in Kasura it is never tracked as its own separate record. It is computed at the moment it is needed, directly from the bookings that already exist for that asset. This means availability and actual bookings can never quietly drift apart — there is only one source they both come from.
Partial availability
A period is partially available when only some of it is free. This is the most common of the three states in everyday use: it appears whenever an existing booking starts or ends partway through the day or range being checked, leaving the rest of that day open. It can also appear when a pending public booking request overlaps part of the range, since that request has not yet been accepted or rejected. A period ending exactly when another begins counts as fully available, not partial, since the two do not actually overlap.
Unavailable periods
A period is unavailable when every part of it is already covered by an active booking on that asset. There is no partial credit here — if any slice of the requested range is free, Kasura reports that range as partially available rather than fully unavailable.
Conflict validation
Kasura validates a booking's dates against existing bookings at two points: while the form is open, so the calendar can visibly mark the range before anything is submitted, and again at the moment the booking is saved. Re-checking at save time closes the small gap between what the calendar showed a moment earlier and what is actually true when the record is written, which matters most when two people are working on the same asset close together in time.
Booking conflicts
A booking conflict is the specific outcome of a failed validation: a new or edited booking whose period includes any unavailable time on that asset. Kasura rejects the save rather than allowing it with a warning, and only bookings still counted as active — not cancelled, not a no-show, not already completed — can produce a conflict.
Operational implications
Because availability and conflicts both come from the same booking data, staff can trust what the calendar shows without cross-checking a second system. The trade-off is that this visibility only extends as far as what has actually been entered into Kasura — a booking held elsewhere is invisible to it, and there is no synchronization with an external calendar or booking channel to close that gap automatically.
What this guide does not mean
- A day marked partially available is not a soft suggestion — the specific unavailable portion within it still causes a conflict if a new booking's dates land inside it.
- Availability is not compared against any external or third-party calendar; it comes exclusively from bookings already recorded in Kasura.
- Partial availability is not a data error or a sync delay — it is the expected, correct state whenever a booking starts or ends partway through the range being viewed.