How it works

What happens when the day goes off plan

A re-plan is a short, visible sequence. Machines do the measuring and the solving; a dispatcher stays in charge of what reaches drivers.

One re-plan, start to finish

  1. 0 sVan 3 reports a fault
  2. 1 s11 stops at risk
  3. <10 sNetwork re-solved
  4. ~1 minDispatcher approves
  5. Next stopDrivers see the change

Stop 01 · Sequence

Five legs, with timings

  1. 06:00before shift

    Morning plan

    The day starts from a full solve of all orders, vehicles and constraints, as it does today, but on GPUs and with tomorrow's learned ETAs.

    Who OptimizeApproved by Planner
  2. all dayevery 15 min

    Cadence re-solves

    Even with no incident, Routite re-solves on a cadence so ETAs reflect traffic and service times as they happen.

    Who OptimizeDefault 15 min, adjustable
  3. 0–1 sevent

    Disruption detected

    Breakdowns, new or cancelled orders, road closures and long stops are scored by how many windows they put at risk.

    Who ForecastsThreshold Set by you
  4. <10 sdesign target

    Event re-solve

    Affected routes are re-solved from the current plan, so drivers who are on track keep their order wherever possible.

    Who OptimizeRuns on GPU
  5. ~1 minhuman

    Review and execute

    Copilot summarises the change. The dispatcher approves, edits or rejects; Edge sends approved stops to drivers.

    Who DispatcherLogged Yes

Stop 02 · Responsibility

Who does what

StepRoutiteDispatcherDriver
Keep the live stateIngests feeds, flags missing dataFixes data the feeds get wrongConfirms arrivals in the app
Decide to re-planScores disruptions against thresholdsCan force or hold a re-planReports problems on the road
Produce the planSolves with every encoded constraintSets objectives and rulesNone
ApproveExplains what moved and whyApproves, edits or rejectsNone
ExecutePushes stop lists and ETAsCalls drivers when neededFollows the new stop order

Stop 03 · Configuration

Rules are written down, not remembered

Constraints and rules live in one versioned file per region. Changing a rule is a reviewed change, not a habit only one dispatcher knows.

The example below is illustrative; the final format will be settled with design partners.

region.zone4.yaml · example
region: zone-4
objective: [lateness, distance, overtime]
resolve:
  cadence_min: 15
  on_events: [vehicle_down, order_added, road_closed]
  late_risk_threshold_min: 10
approval:
  auto: [swap_within_route]   # everything else waits
  required_role: dispatcher
constraints:
  driver_hours_max: 10
  window_slack_min: 5

Stop 04 · Outcomes

What a pilot measures

We agree the baseline and the protocol with you before the pilot starts. No numbers are published without your approval.

Pilot measurekmper stop

Distance driven for each delivered stop.

Pilot measure%on time

Stops served inside their window.

Pilot measurehovertime

Driver hours past the planned shift.

Pilot measuresre-solve

Time from event to approved plan, against your current process.

Stop 05 · Questions

Questions dispatch teams ask

What if the data is wrong?

Twin flags gaps such as a van with no GPS fix or an order with no window. The dispatcher can fix it or tell Routite to plan around it.

Does a re-plan reshuffle every route?

No. Re-solves start from the current plan and penalise changes to drivers who are on track, so most routes stay as they are.

Can a dispatcher override the plan?

Always. Overrides are logged and become constraints for the next re-solve.

How often is too often?

That is a setting. Most fleets will want a cadence between 10 and 30 minutes plus event triggers; the pilot helps you pick.

Stop 06 · Destination

Next step

Watch a re-plan on one of your days

Pick a past day that went badly. We replay it and show each re-plan Routite would have proposed, with the timings.