1
Approval by default
Nothing reaches a driver without approval unless you wrote a rule allowing it.
Trust and security
Routite proposes; dispatchers decide. Every change is explained, approved and logged. This page also says plainly what is planned and what is not yet in place.
Our rules
Stop 01 · Principles
1
Nothing reaches a driver without approval unless you wrote a rule allowing it.
2
Each change carries the solver's reasons, in words a dispatcher can check.
3
Re-solves penalise changes to drivers who are on track.
4
We publish pilot results only with the partner's approval and the method attached.
5
Your history trains your models. Cross-customer learning needs your opt-in.
6
Overrides are logged and respected by the next re-solve.
Stop 02 · Method
Optimize produces a plan with a diff and reasons.
Approval rules decide whether it can go through or needs a person.
The dispatcher approves, edits or rejects in Copilot.
The decision, the person and the reasons are written to the change log.
Stop 03 · Regulatory context
| Area | Examples | How Routite helps | Status |
|---|---|---|---|
| Driver hours | EU drivers' hours rules, US FMCSA hours of service | Encodes shift, break and drive-time limits as constraints | In build |
| Data protection | GDPR, UK GDPR | Data residency by region, role-based access, retention settings | Planned |
| Security assurance | SOC 2 Type II | Controls and audit | Planned |
| Security management | ISO/IEC 27001 | Information security management system | Planned |
| Low-emission zones | City clean-air zones | Vehicle-type constraints per zone | Planned |
Stop 04 · Audit trail
The change log answers the questions that come up after a bad day: what moved, who approved it, and what the solver knew at the time.
Logs can be exported for your own audit or claims processes.
Change log · Zone 4
ExampleStop 05 · Security
Stop 06 · Questions
No. Routite is pre-launch. A SOC 2 Type II audit and ISO 27001 are planned; we will say when each is complete.
No tool can. Routite plans within the limits you encode and flags conflicts, but the operator remains responsible.
Not without your opt-in. By default your data trains only your own models.
Stop 07 · Destination
Next step
We answer honestly, including where something is planned rather than done.