Smarter Driver Availability in Dispatch Planner

March 27, 2026

We released a major upgrade to how driver availability works in Dispatch Planner to eliminate manual PTA tracking and give your planning team data they can actually trust.

Driver availability is now calculated automatically using two configurable parameters: Minimum Available Duration and Average Dwell Time. Instead of relying on appointment window end times, availability now factors in realistic turnaround so you're seeing when a driver is actually free, not just when a load delivers.

You'll also notice new columns in the Drivers table:

• Available For — how long the driver is available (e.g., 14h 30m, or ∞ if no next commitment)
• Next Planned At — when their next commitment starts
• Next Planned In — where the next commitment is
• Available In (formerly Final Stop) — where the driver becomes available, synced with the new calculation

Why it matters

This was the #1 gap preventing operations from trusting Planner availability data. Local ops need 1-hour windows, regional needs 12 hours, long-haul needs days — now each operation can define what "available" actually means for them.

How to configure it

Settings are available at three levels: Alvys defaults, tenant-level overrides, and fleet-level overrides. Your admin can adjust Minimum Available Duration and Average Dwell Time under Dispatch Planner Settings. We've set sensible defaults, but you'll get the most value by tuning these to match how your operation actually runs.