Parcelarc runs a constrained re-optimization loop every 10 minutes between 4:00 a.m. and 7:30 a.m., absorbing driver changes, late parcels, and time-window conflicts before drivers depart.
Continuous solving from 4:00 a.m. through 7:30 a.m. local time
Measured against original dispatch sequence on re-optimized routes
Time previously spent absorbing exceptions by hand each morning
Per-route savings on routes that received a re-optimized sequence
Recompute route sequences every 10 minutes during the pre-departure window
Each solve runs against the full constraint set and produces a replacement stop sequence for any route with a net improvement above a dispatcher-configured threshold.
Use real driver positions and status flags as re-optimization constraints, not assumptions
Parcelarc maintains a live connection to Samsara and Motive ELD feeds, consuming driver GPS position, hours-of-service status, and mobile-app check-in signals every 30 seconds.
Push revised stop sequences directly into Route4Me and OnFleet before driver app sync
Drivers see the correct sequence in their existing mobile app without any change to their workflow. Dispatchers see a change summary with a one-click rollback option.
Flag and auto-resolve time-window violations introduced by late-arriving parcels
Conflicts that cannot be resolved within driver hours or vehicle capacity constraints surface in the dispatcher exception queue rather than silently failing.
Quantify the stop-reorder impact on miles driven, fuel cost, and on-time delivery rate
Operations managers can drill into individual routes or drivers to identify recurring problem patterns. Data exports to CSV for existing reporting tools.
Automatically reroute around construction, road closures, and weather events before departure
Dispatchers receive a notification with the recommended detour and estimated delay impact on affected time-window stops, giving them time to contact customers if necessary.
Parcelarc connects to the systems carriers already use and writes revised sequences back before drivers sync their manifests.
Parcelarc reads the locked dispatch queue from Route4Me or OnFleet and begins consuming real-time parcel scan events and driver ELD signals.
Late manifest additions, driver call-outs, vehicle failures, and road closure events are ingested and queued as constraint changes on the next solve cycle.
Every 10 minutes, the re-optimization engine solves the modified vehicle routing problem using the current dispatch queue as the warm-start state.
Improved stop sequences write back to the dispatch platform before driver app sync. Dispatchers see a change summary and retain one-click rollback.
Average time a dispatch team spends manually patching route sequences each morning at a 40-route regional carrier operation, documented across a 6-month observation period.
Typical number of post-cutoff exceptions arriving between midnight and 6:00 a.m. — driver status changes, late inbound parcels, and time-window conflicts — at a 500-stop carrier.
Reduction in total miles driven on re-optimized routes observed in the first two weeks of testing at the founding team's original carrier, against routes that had been manually patched.
Bring a week of morning dispatch logs and we'll show you what a re-optimization layer would have changed on your routes.