Work
One engine, deployed one operation at a time
We build a single system for a domain and configure it per company, rather than starting a new build for every client. The first is an inspection engine, in pilot with Road Safety Limited Company.
Product 01 / Inspection engine
Vehicle safety inspection for bulk haulage
Status
Phase 1, in pilot with Road Safety Limited Company. Not yet in general service.
What it does
Replaces a spreadsheet with a mobile application that captures the inspection in the field and holds up as evidence afterwards. Three inspection types: a 30-item pre-loading check that runs on every load, a 38-item routine check for light commercial vehicles, and a weighted bi-annual certification that produces a score and a letter grade.
The rules that do not bend
Nothing defaults to a pass
An unanswered item cannot pass
Every inspection carries the inspector who took it
Findings stay open until someone closes them
Works with no signal, and reconciles when it returns
Severity, and what it decides
*
Anomaly detected, vehicle can be used
Advisory. Recorded, verdict unchanged
**
Rectification required inside 30 days
Conditional pass, with a repair deadline
***
Anomaly affecting the integrity of the vehicle
Fail. Vehicle grounded, no exception
The marks come from the client's own checklist. The inspector records what they find; the engine decides the verdict.
First deployment / Road Safety Limited Company
The record had no inspector and no location.
Why they called
A driver loaded in the north and drove to Accra with the load uninspected. The pre-loading inspection was completed by telephone, by an inspector several hundred kilometres away. The vehicle later crashed.
Nothing in the process could have caught it. The workbook recorded no inspector and no location on any inspection, so there was no data in which the pattern could have been seen.
What we found in the workbook
No inspector and no location recorded on any inspection
113 of 201 vehicles with no unit type, so no checklist could be matched
Capacity held as both numbers and free text
Outcome and reason sharing one column, with 'COMPLIANT' used to mean a pass
23 failed certifications rescheduled as though they had passed
Axle count, the unit certification is billed by, present only in handwriting
Where it stands
The inspector application runs end to end, including with no signal. Bi-annual capture and grading, and the native application, are Phase 2.
Start a conversation
This is not a form. It is an evidence record.
Several rules in the system exist only to keep the record defensible after something goes wrong. Each one looks like friction until the day it is the reason an account holds up.
How the engine travels
The second company is not a second build
Written down before there was a second company, because the expensive version of that question is the one answered in a hurry.
1
One engine
Every deployment runs the same code at the same release tag. There is no fork, no branch per client and no second repository.
2
One database per company
A new company gets their own database and the same migrations. Nothing is shared, so there is no query that can show one company another's vehicles.
3
One folder per company
Sites, checklists, vehicle types and the words on screen live as versioned data beside the engine, not typed into a settings screen.
What configuration does not cover
Two companies may reasonably differ on what their sites are called, which items sit on a checklist, or how long a conditional pass lasts. Neither may decide that an unanswered item counts as a pass. A different workflow is engine work, not configuration, and we say which one you are buying before the contract rather than after it.
Tell us what's broken.
