Run the business
Drive-time scheduling
Booking that scores every open slot by the drive from the last job — so a day of visits clusters instead of crisscrossing the metro.
The problem
A field day dies in the truck: a job across town, then back for the next, then out again. The calendar says you're booked; the map says you spent three hours driving.
How it works
The scheduler generates the open slots across every crew's availability, then scores each one: a short drive from the previous job scores higher, a long haul lower, a morning start and the customer's preferred crew add a little, and a first job near home base adds more. Best-first, so the slot you offer is the one that keeps the route tight.
It reads a resource's recurring hours and dated exceptions (time off, special hours), refuses a booking that overlaps another or leaves too little time to drive between jobs, and warns when the buffer is tight. Coordinates come from geocoding the address; the whole thing runs on a keyless Haversine estimate out of the box and upgrades to traffic-aware Google drive times the moment a maps key is set — with a database cache so the bill stays small.
It pairs with the estimator: save an instant estimate and the very next step is booking the measurement on a scored slot, which lands on the calendar and links back to the quote.
- Every slot scored by drive time from the previous job, best first — the route clusters itself
- Recurring availability plus dated exceptions, with overlap and travel-buffer guards on every booking
- Keyless out of the box (straight-line estimate), traffic-aware with a maps key — configuration, not a flag — and a drive-time cache to hold down cost
- Wired to the estimator: quote → book the measurement on the smartest open slot, linked to the estimate
npm install @adminigloo/schedulingBook a callAll features