Fleet Digitalization Readiness Assessment
Failed rollouts are rarely about the software. They are about an asset register nobody trusts, an integration that was assumed, and no named person whose job it was. This assessment scores six weighted readiness dimensions and separates the gaps you can work around from the ones that will stop you.
Your numbers
0 = no single vehicle list that everyone agrees with. 4 = registration, VIN, odometer, owner and status are current and reconciled.
0 = nothing is fitted. 4 = every vehicle reports position and distance reliably, including the hired-in and subcontracted ones.
0 = the process is whatever each depot decides. 4 = the steps from job to invoice are written down and the depots follow the same one.
0 = nothing talks to anything. 4 = finance, fuel cards and your job source exchange data through an interface someone supports.
0 = nobody owns this. 4 = a named person has the rollout in their objectives and the authority to change how depots work.
0 = drivers and workshop staff have no device and no appetite. 4 = they already use apps daily and expect the tools to work.
Result
Readiness score
43 %
24 of 56 weighted points.
- Hard blockers
- 0 of 6
- Weighted points below pilot-ready
- 9.6
- Weighted points scored
- 24 of 56
- Weighted points lost
- 32
The formula
- Each dimension is scored 0 to 4 and carries a weight: asset register 3, telematics coverage 2, documented process 2, system integration 2, named owner 3, frontline capability 2
- Weighted points scored = sum of (dimension score × dimension weight)
- Weighted points available = sum of (4 × dimension weight) = 56
- Readiness score = (Weighted points scored ÷ 56) × 100
- Hard blockers = count of dimensions scored 0
- Weighted points lost = 56 − Weighted points scored
- Weighted points below pilot-ready = ((60 ÷ 100) × 56) − Weighted points scored, floored at 0
Assumptions and limits
- The weights are our judgement, published so you can disagree with them. Asset register and named owner carry 3 because every rollout we have watched fail did so on one of those two, not on a feature gap.
- The pilot-ready line at 60 percent is an editorial threshold, not a validated cut-off. It exists so the number has a decision attached to it rather than a mood.
- A hard blocker is reported separately because a score cannot express it. Scoring 0 on system integration while everything else is a 4 produces a comfortable overall number and a rollout that will still stall.
- Budget, procurement timelines and contract length are not modelled. They kill as many projects as readiness does, and none of them are visible from here.
- The assessment says nothing about which product suits you. A fleet can be perfectly ready to deploy exactly the wrong thing.
- Readiness decays. A register that was accurate at an audit six months ago is not evidence today, and the honest score is the one you could prove this afternoon.
The asset register is the whole project in miniature
Ask three people in a fleet how many vehicles it runs and you will often get three answers. Finance counts what is on the balance sheet. The workshop counts what comes through the door. Operations counts what can take a job today. The hired-in unit, the one on long-term VOR, and the one sold last month sit differently in each list.
Software does not resolve that. It inherits it. Every module you switch on afterwards — costing, maintenance, compliance — is built on whichever list got imported, and the reconciliation you skipped at the start returns as a data-cleanup project eighteen months in, with live users depending on the bad rows.
Why a named owner outweighs a feature list
Rollouts require someone to tell a depot manager that the old spreadsheet is finished. That is an authority problem, not a software problem, and it is why the named-owner dimension carries the same weight as the register.
The test is specific. Not who signed the purchase order, and not who attended the demo. Who has this in their objectives, who can overrule a depot that carries on as before, and who will still be in the role in a year? If any of those answers is uncomfortable, score it low. This assessment is worth nothing as a document to show your board.
Integration is where the optimism lives
Integration scores get inflated more than any other, because the question sounds technical and gets answered aspirationally. The fuel card provider has an API, therefore integration is fine. In practice the API returns transactions keyed to a card number, your register keys on registration, and the mapping between them is a spreadsheet a person maintains by hand.
Score what exists and is supported, not what is possible in principle. A file that someone exports monthly and emails is a 1. It works, and it will keep working exactly as long as that person does.
Frequently asked questions
It means the conditions a software rollout depends on are already true before the rollout starts: a vehicle list everyone accepts, data arriving from somewhere other than memory, a process the depots share, an interface to finance, one accountable person, and frontline staff who can use a device. None of that is software. All of it decides whether software survives contact with your depots.
It means buy less, later, in one place. A low score is a strong argument for a single-depot pilot with two modules rather than a fleet-wide programme with eight. The failure mode of low readiness is not that nothing works. It is that enough works to justify continuing while the data quietly rots underneath.
Because they are decisions and this measures conditions. A generous budget cannot buy you an accurate asset register, and a strong vendor cannot supply you an internal owner. Including them would let a well-funded fleet score its way past the two things that most reliably sink the project.
Partly. Register accuracy, documented process and naming an owner are mostly attention rather than expenditure, and they carry eight of the fourteen weight points here. Device coverage and integration are not free, and no amount of internal discipline substitutes for a vehicle that cannot report its own odometer.
Maturity asks how well you run today. Readiness asks whether a change would stick. The two diverge more often than you would expect: a long-established fleet can be genuinely capable on paper-based process and completely unready to move, because nothing in its operation has ever had to change quickly.
Stop estimating. Measure it.
Fleet Digitalization Readiness Assessment gives you the arithmetic. Platform gives you the live numbers from your own fleet.