Public users see availability in broad terms. Behind confirmation is an operational timeline that includes preparation before departure and recovery after arrival. That is how double-booking is avoided.

Two timelines on every trip

Customer trip time runs from departure to arrival—the part guests experience. Operational blocked time starts earlier for preparation and ends later at final available time after return-to-base, grace, and any admin override.

Availability validation uses the operational window. That is why a van that “looks free” right after drop-off may still be recovering.

What admin review checks

• Driver conflicts on the blocked timeline
• Van conflicts on the blocked timeline
• Whether the request’s timing is realistic for distance and stops
• Notes that affect meals, tolls, or special instructions

Confirmed status is separate from payment status. A trip can be confirmed while payment details are still being arranged, depending on how the team manages the booking.

Why public pages stay high-level

Public availability should not expose client names, private notes, plate numbers, or full admin detail. You get enough signal to plan a request; ops keeps the sensitive schedule graph internal.

What you can do to help

Submit complete routes and flexible windows when you can. Hard constraints are fine—just label them. Clear notes reduce back-and-forth after the request lands.

When you are ready, send the request through booking. Confirmation follows review against real operational availability.