The evaluation process
There are five steps from watching a scenario to signing a contract. The first three take a few hours, on your own or with us. The Pilot (trial run) is the step where both sides commit.
From a scenario to a contract
- 1
Watch a scenario
Industry scenarios on simulated data, no account needed.
See the sample scenarios - 2
Compare one day of your data
Pick a day in the file you already use; the page sets the Route4Green dispatch plan beside your current one.
Compare dispatch plans - 3
Guided demo
We run one day of your data and read the result with you.
Book a demo - 4
Pilot (trial run)
Eight weeks: two weeks of data preparation, then six weeks running alongside your current operation.
- 5
Contract
Go or stop, decided on the Pilot acceptance report.
What the Pilot consists of
- Eight calendar weeks: two of preparation, six of running. The clock only starts once the data has passed the data thresholds (the IT section below); waiting for data is time before the Pilot, not a longer Pilot.
- At least 10 past operating days, including a Monday, a Friday and your peak day.
- Shadow running: each day the Route4Green dispatch plan is built on the same real orders and set next to the routes you actually ran. No change to dispatch, and drivers use no app.
- One mandatory live shift run on the Route4Green dispatch plan, with odometer readings, to compare plan with reality.
- Up to 300 orders per optimisation run. Larger networks are split into a smaller scope.
- One named operations lead with decision authority signs the acceptance criteria before day one. One named data owner answers the rejected-rows report within one business day.
- It ends with a report that shows the denominator of every figure, a table of rejected rows by reason and by day, and acceptance minutes signed by both sides.
Six default acceptance criteria
Both sides agree and sign these thresholds before day one. These are the defaults; they can be adjusted to your network before signing.
- Km per tonne against your current dispatch plan, averaged over the Pilot
- at least 12% lower
- Share of the orders you supply that get routed
- at least 95%
- Share of planned arrivals inside the delivery window
- not lower than the current dispatch plan's rate
- Overloads on any leg
- zero
- Live shift: odometer against plan
- within 8%
- Share of data rows rejected
- no more than 5%
The eight-week schedule
- 1Weeks -2 to 0, preparation: you answer the questionnaire, fill in the data template, run the checks until the data is clean, and both sides sign the acceptance criteria. The clock does not start until the data passes.
- 2Week 1: data loading, rule setup and one trial run.
- 3Weeks 2-3: ten operating days of shadow running.
- 4Week 4: one live shift with odometer readings.
- 5Week 5: the report and a review session with you.
- 6Week 6: signed acceptance minutes and the go or no-go decision.
Measured results
From a Pilot (trial run) with a national postal operator: -21% km per tonne of cargo, plan versus plan over 5 operating days. The Route4Green dispatch plan covered about 62% of the tonnage actually moved. See the figures and how they were normalised
Data thresholds for your IT team
The Pilot uses these thresholds. A one-day file of your own is checked against the ones that apply to a single day: Compare dispatch plans
- Sites with coordinates or a resolvable address
- at least 98%
- Orders with a usable weight_kg
- at least 95%
- Orders whose site_code matches the sites sheet
- at least 99%
- Readable dates and times
- at least 99%
- Current dispatch plan routes with an identifiable vehicle
- at least 95%
- Current dispatch plan routes per day with stop_weight_kg
- at least 90%
- Share of rows rejected
- no more than 5%; above 10% the Pilot does not start
- Peak orders in one optimisation run
- no more than 300 orders per run (per day and shift), not per day
- Operating days covered
- at least 10 days, including a Monday and a Friday
Fits the system you already run
Route4Green takes orders, vehicles and sites through the API or a file, and returns the route plan to your TMS or ERP. Your current dispatch system stays in place. The step-by-step connection guide and the API docs live on route4green.com.
If the final decision sits with the General Director, the acceptance minutes are the document to present.
Start with one day of data
Request a guided demo and we will get in touch to receive one day of data in whatever file you already have.