8 connected modules on a single database. Maintenance, fuel, documentation, BI and ERIC AI, integrated with your telematics and ERP.
See the full platform →Real cases, technical guides and tools for maintenance, fuel and compliance decisions.
Go to the blog →The paper pre-trip checklist has several problems. It gets filled out in a rush, signed without checking anything, lost before it reaches the office, triggers no action when a fault is found and leaves no usable trail for an audit or a warranty claim. In most fleets it is compliance theater: someone signs a sheet, nobody reads it.
A digital checklist changes that. It is completed from a phone, it is stamped with date, time, location and signature, and each unit’s inspection history can be retrieved in seconds. It is one of the operational changes with the greatest impact on the real quality of a fleet’s maintenance.
But a poorly configured digital checklist is almost as useless as a paper one. Setting it up properly means thinking through what gets inspected, how each finding is reported and what happens next.
It is the form that the driver, or a designated technician, completes before using the vehicle, during the shift or at the end of it, to verify that the unit is in good condition. It covers everything from the obvious —lights, fluid levels, tires— to what is specific to each operation: secured cargo, accessory equipment, emergency kit.
The digital version adds three things paper does not have: traceability with date, time, geolocation and signature; visual evidence through photos; and a searchable history that does not depend on anyone filing a sheet.
A well-built checklist combines four field types.
Yes or no. For binary checks. Are all the lights working? It is the fastest field to complete and the easiest to audit later.
Numeric. For quantifiable values: current odometer reading, fuel level, tire pressure. They let you check the data against the vehicle’s parameters.
Image. For evidence. The photo of the odometer, of the worn tire, of the new dent in the bodywork. It is the field that adds the most value when a fault is reported, because it allows an assessment without physically going to the vehicle.
Signature. For accountability. The driver signs when closing the checklist, confirming the inspection was done.
Combining all four strikes the balance between completion speed and quality of evidence.
The catalog varies by vehicle type, but a reasonable minimum for an urban light commercial vehicle covers four blocks.
Exterior. Bodywork with no new damage; headlights, taillights, brake lights and turn signals; tires with proper pressure and tread; legible license plate; mirrors; windshield with no new cracks.
Interior. Cab free of loose objects, working seat belts, no warning lights on the dashboard, documents on board.
Basic mechanical. Oil, coolant and washer fluid levels; brake response; steering play; unusual noises, with an open field for a description.
Role-specific. Cargo secured and within limits for freight transport, thermostat in refrigerated vehicles, complete equipment for technical services, cylinders and gauges for hazardous materials.
A checklist of eighteen to twenty-five items takes three to five minutes to complete. More than thirty creates fatigue and automatic answers without verification. Fewer than twelve leaves blind spots.
When the driver reports a fault, someone has to act on it. The right workflow is: the inspection is recorded with its evidence, the maintenance lead reviews it and, if warranted, a corrective ticket is opened with the photo and description from the checklist as backup.
That step —from inspection to ticket— is what determines whether the system works. And it should be clear: it is a human decision, not an automatic one. Someone looks at the finding, assesses its severity and decides whether to open the ticket, whether the vehicle can keep operating or whether it has to be taken out of service.
What is key is closing the loop with the driver. If drivers do not see their reports lead to action, they stop reporting. And a checklist where nobody reports anything is exactly the same as having no checklist.
1. A checklist that is too long. Forty or sixty items that end up filled in with automatic yeses. When every item always comes back fine, the checklist controls nothing.
2. Ambiguous fields. “Is the vehicle in good condition?” is interpreted differently by every driver. Better: “Is any warning light on in the dashboard?”.
3. The report reaches no one. If the driver flags a fault and nobody reviews that inspection, the report is lost. It is the most common mistake and the most expensive one.
4. Unverified photos. If nobody checks the date and location of the photo, someone can upload one from the previous day or from another unit.
5. No consequence for skipping it. If a driver can head out without completing the checklist and nothing happens, the system becomes optional. Someone has to be watching which vehicles operated without the day’s inspection.
Avoiding these five in the initial design saves months of friction.
In the Inspections module:
Are your checklists good for anything more than signing a sheet?
With VEC Fleet every inspection is recorded with photo, signature and geolocation, and each unit’s history can be retrieved in seconds.
Between three and five minutes for a form of eighteen to twenty-five items on a light commercial vehicle. Longer if it requires several photos. The right duration is calibrated during the first month of use, by looking at how long drivers actually take.
Three things. Include mandatory numeric or photo fields, which require real action. Run random audits comparing what was declared with the vehicle’s actual condition. And above all, respond quickly to fault reports, so the driver sees that reporting is worthwhile.
It is one of the first things to verify when choosing the tool, because a good part of fleet operations take place in areas with intermittent coverage. It is worth testing under real conditions before rolling it out to the whole fleet.
In most countries in the region, yes, especially when it includes date, time, location and user authentication. For formal audits or litigation it is advisable to validate the format with local legal counsel, because requirements vary.
A collaboration between the fleet manager, who knows the operation, the maintenance lead, who knows the vehicle’s critical points, and the safety team, who knows the legal requirements. And before launching it to the whole fleet, validate it with two or three experienced drivers: they are the ones who spot confusing or redundant items.
Between three and five minutes for a form of eighteen to twenty-five items on a light commercial vehicle. Longer if it requires several photos. The right duration is calibrated during the first month of use, by looking at how long drivers actually take.
Three things. Include mandatory numeric or photo fields, which require real action. Run random audits comparing what was declared with the vehicle's actual condition. And above all, respond quickly to fault reports, so the driver sees that reporting is worthwhile.
It is one of the first things to verify when choosing the tool, because a good part of fleet operations take place in areas with intermittent coverage. It is worth testing under real conditions before rolling it out to the whole fleet.
In most countries in the region, yes, especially when it includes date, time, location and user authentication. For formal audits or litigation it is advisable to validate the format with local legal counsel, because requirements vary.
A collaboration between the fleet manager, who knows the operation, the maintenance lead, who knows the vehicle's critical points, and the safety team, who knows the legal requirements. And before launching it to the whole fleet, validate it with two or three experienced drivers: they are the ones who spot confusing or redundant items.