Automate Fleet Inspections from
Pre-Trip to Compliance Review
Squarerigger delivers digital pre-trip inspection software that logs every DVIR, work request,
and annual inspection on one record for instant audit compliance.
Inspections That Create Accountability
Instead of Paperwork
An inspection program only works when defects, photos, and follow-up actions stay connected. Otherwise, the
inspection is just paperwork, and the defect rolls out with the truck.
1. The Driver Starts the Pre-Trip
The clipboard rides with the driver, and half the boxes are checked without a second look. The checklist hasn't changed in years.
The pre-trip runs on a phone. Mandatory fields cannot be skipped, and the checklist is configured to the asset type.
2. The Driver Finds a Defect
"Left tail light out" is written on paper and handed to a manager if and when the driver gets a moment.
A failed item creates a pending work request with a photo and note carried over. The shop sees it the moment the inspection is saved.
3. The Failed Item Lands in the Shop
Repair priority is set by who shouted the loudest. Some failures stay in a backlog because nobody logged them in the first place.
Pending requests sit in one priority queue. The technician picks them up from the same work screen.
4. The Same Asset Fails the Same Item Twice in a Month
The pattern is invisible. The fix is repeated and billed twice. The root cause is investigated only after the third breakdown.
Asset inspection history shows recurring failures. Next work order opens with prior repair history attached.
5. A DOT Inspector Asks for Records
Someone digs through binders. Time-stamps are missing. Some inspections cannot be produced and the audit gets a finding.
Time-stamped DVIRs and inspection records are retrievable per asset and per date. The audit packet is generated, not assembled.
1. The Driver Starts the Pre-Trip
The clipboard rides with the driver, and half the boxes are checked without a second look. The checklist hasn't changed in years.
The pre-trip runs on a phone. Mandatory fields cannot be skipped, and the checklist is configured to the asset type.
2. The Driver Finds a Defect
"Left tail light out" is written on paper and handed to a manager if and when the driver gets a moment.
A failed item creates a pending work request with a photo and note carried over. The shop sees it the moment the inspection is saved.
3. The Failed Item Lands in the Shop
Repair priority is set by who shouted the loudest. Some failures stay in a backlog because nobody logged them in the first place.
Pending requests sit in one priority queue. The technician picks them up from the same work screen.
4. The Same Asset Fails the Same Item Twice in a Month
The pattern is invisible. The fix is repeated and billed twice. The root cause is investigated only after the third breakdown.
Asset inspection history shows recurring failures. Next work order opens with prior repair history attached.
5. A DOT Inspector Asks for Records
Someone digs through binders. Time-stamps are missing. Some inspections cannot be produced and the audit gets a finding.
Time-stamped DVIRs and inspection records are retrievable per asset and per date. The audit packet is generated, not assembled.
How It Works
Step 1
The driver runs the pre-
trip on a phone
Step 2
Flags a defect
with a photo.
Step 3
Defects open work orders
in the shop's queue
Step 4
The shop completes the
repair before next dispatch
Step 5
The defect never
becomes a breakdown
How the Inspection Runs
DVIRs on Any Device
The inspection runs where the driver runs.
- Daily DVIRs from a phone, tablet, or desktop.
- Photos and notes inline.
- Digital signature and time-stamp on every record.
Failed Items Become Pending Work
The failure is the trigger, not a second step.
- Failed item raises a pending work request.
- Photos and notes carried over without re-entry.
- Failure visible before the driver leaves the yard.
Audit-Ready Inspection History
Compliance is a query, not a project.
- Time-stamped records per asset and per date.
- Designed for DOT, FMCSA, and OSHA requirements.
- Records linked to repair history and warranty claims.
Customizable Checklists
The checklist matches the asset, not the other way around.
- Templates per asset type, location, or role.
- Mandatory fields prevent skipped items.
- Standardized procedure across the fleet.
Scheduled Inspections
Monthly, quarterly, & annual inspections sit in the same engine.
- Automated reminders for DOT-required inspections.
- Reusable templates across recurring cadence.
- History retained per asset for the life of the truck.
DVIRs on Any Device
The inspection runs where the driver runs.
- Daily DVIRs from a phone, tablet, or desktop.
- Photos and notes inline.
- Digital signature and time-stamp on every record.
Customizable Checklists
The checklist matches the asset, not the other way around.
- Templates per asset type, location, or role.
- Mandatory fields prevent skipped items.
- Standardized procedure across the fleet.
Failed Items Become Pending Work
The failure is the trigger, not a second step.
- Failed item raises a pending work request.
- Photos and notes carried over without re-entry.
- Failure visible before the driver leaves the yard.
Scheduled Inspections
Monthly, quarterly, & annual inspections sit in the same engine.
- Automated reminders for DOT-required inspections.
- Reusable templates across recurring cadence.
- History retained per asset for the life of the truck.
Audit-Ready Inspection History
Compliance is a query, not a project.
- Time-stamped records per asset and per date.
- Designed for DOT, FMCSA, and OSHA requirements.
- Records linked to repair history and warranty claims.
Where the Inspection Leads
An inspection is the start of a maintenance event. The page that follows it is the work request;
the page after that is the work order.
Who Uses the Inspection Trail
Fleet Technician
Failed items arrive as work, not as a stack of paper. Inspection record carried into the WO.
Driver and Dispatcher
The pre-trip runs on the same phone the driver already uses. Dispatch sees readiness.
Fleet Maintenance Manager
Recurring failures by asset are visible. Pending requests do not get lost in a manager's inbox.
Fleet Safety Pro
Recurring failures by asset are visible. Pending requests do not get lost in a manager's inbox.
Fleet Executive
Inspection history is easily searchable whenever compliance is questioned.
Watch a Failed DVIR Become
Pending Work in the Shop
Thirty minutes is enough to see a pre-trip run on a phone, a defect become a work request
attached to the asset, and the inspection record retrievable for audit.
Common Questions
Can the checklist be customized per vehicle type?
Yes. Squarerigger's fleet inspection software allows custom DVIR templates per asset type, with mandatory fields configured at the fleet level.
What happens to existing inspection records during onboarding?
Existing inspection history is part of the data migration. Records imported during onboarding remain retrievable in the same audit workflow as records created after go-live.
How are failed items routed to the right technician?
A failed inspection item raises a pending work request. The shop reviews, prioritizes, and converts it into a work order, which is then assigned by skill, bay, or priority.
What records are retained for DOT and FMCSA audits?
Time-stamped DVIRs, scheduled inspection records, and the resulting repair documentation are retained on the asset record. Retention configurations align with the agencies the fleet answers to.
Can the inspection trigger a work order directly without a manager approving?
Yes. Routing rules can either send the failure to a request queue for manager approval or open a work order directly, depending on how the fleet wants to handle severity.