Most inspections happen on a phone. You can also record one in the browser — useful for typing up a paper check, or for inspecting something nobody takes a phone to.
The browser is also where every result lands, so this is where you go to see what your team found.
Record an inspection yourself
1. Start the inspection
Go to Assets → Inspections and click Create Inspection, then pick the checklist you want to fill in.
2. Choose the vehicle
The blank checklist opens. Search for the vehicle in Asset (Required). Once it is chosen, meter items show that vehicle’s last recorded reading, so you can tell straight away whether the number you are typing makes sense.
3. Work down the checks
Fill in each item exactly as an inspector would on the phone. When you mark a check as Fail, a Comment box and a photo uploader open underneath it — if the checklist requires evidence on failure, you must fill one in before you can finish.
Signature items are drawn straight onto the pad. Multi-select items list every fault that can be reported: leave the “all clear” option ticked when nothing is wrong, or tick the faults you found and explain each one.
4. Add any parts, then submit
If your organization records parts on inspections, add them under Parts Used. Then click Create New Inspection.
5. Deal with urgent failures
If a failed check was set to Urgent Action Required, the urgent message appears the moment you submit — along with the Issues that were just created, and the option to change the vehicle’s status on the spot.
Changing the status here is how you take a vehicle out of service after a serious failure. The warning does not stop anyone by itself — treat it as a prompt to follow your own process.
See what your team found
Find the inspections that need attention
Every completed inspection is in the Inspections list. Switch between the All and Failed tabs, and filter by vehicle, checklist, who did it, or when. You can also see a single vehicle’s history from its own page, under Activity → Inspections.
Open one to see the whole story
An inspection record shows the vehicle, who inspected it, how long they took, and the result of every single check — failed items in red, with the inspector’s comment beside them and a direct link to the Issue each failure opened.
On a long checklist, use the Only Failed Items and Only Items with Comments tabs to jump straight to what went wrong. Print produces a clean copy of the record, signatures included, for compliance files.
From a failed check to a repair
Each failed check links straight to the Issue it created, and that Issue arrives with everything maintenance needs — the vehicle, its severity, and what the inspector wrote.
Issues raised this way sit under Maintenance → Issues alongside every other Issue, with a Source of Inspection so you can tell where they came from. From there they can be prioritised, assigned, and turned into work orders.
Next