We lend cameras and other equipment to different teams, and each booking has a pickup date and a return date. Can Busabase check whether an item is already booked for any part of the requested period and warn us before saving an overlapping booking? We also need to keep past bookings for reference while making returned equipment available again.
You can keep the booking history in Busabase, but a Base does not currently warn or block an overlapping booking automatically when someone saves a record.
A practical starting structure is an Equipment Base and a Bookings Base. Link each booking to an equipment item, and record its pickup date, planned return date, actual return date and status. Keep completed bookings as history; mark an item returned rather than deleting its booking. A view filtered to open bookings makes the current schedule easier to review.
Before approving a new booking, check that item's open bookings for any period that intersects the requested dates. An Agent can help review the dates and submit a proposed booking for someone to check, but this is still a review step, not an automatic guarantee against two people booking the same item at once. A save-time warning or hard block would need additional validation beyond the current Base form.
Would a warning be enough, or must the system refuse overlapping bookings? Should pending requests already reserve the item? Those choices affect how availability should work.
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in