Downtime Measurement,
Answered the Moment You Ask
Ask a plain-language question and get the exact time a truck's been down, service time and idle time both, and start
closing the gap between a truck that's down and a truck that's earning.
Full Downtime Story, beyond Wrench Time
Ask Riggs about fleet downtime just like you’d ask your shop foreman—“How much downtime did we have last quarter?” Squarerigger’s AI assistant instantly pulls accurate breakdowns by asset, shop, vendor, or date range.
Get the true out-of-service duration, not just wrench time, pulled directly from your shop's existing work order history.
A Record That Doesn't Forget
Every mark-out and mark-in event lives on the vehicle's record, so nothing about a
truck's downtime depends on someone remembering it later.
Equipment Status
A truck's status reads Active or Out of Service the moment someone updates it, so you're never the last to find out a unit is down.
Out-of-Service History
Every mark-out and mark-in pair adds its elapsed time to the running total, calculated per truck and rolled up across the whole fleet.
Downtime VS Labor
The exact time down and the repair's logged hours stay on two separate numbers, so a slow repair never hides in a blended total.
From One Truck
to the Whole Fleet
A truck on the road earns money. A truck that's down doesn't. The same downtime record
scales from one truck to the whole fleet.
One Trip Instead of Two
Knock out upcoming PMs while a truck is already down for unexpected repairs.
- Parts checked against stock ahead of time.
- Work gets folded into the same visit.
- Low-stock parts reorder on their own.
Shop Management
Identify problems before they create downtime and costs.
- Downtime compared shop to shop.
- Syncs with Multi-Shop Management data.
- The slow yard surfaces on its own.
Replace Instead of Repairing
A truck whose downtime keeps climbing is telling you something about its future.
- Feeds into Lifecycle Management strategy.
- Weighed alongside repair frequency.
- Turns a guess into an actual call.
Some Trucks Are Down Too Often
A truck running downtime well above the fleet average is worth a closer look.
- Could be a bad part or a repair pattern.
- Could be a unit nearing its end of life.
- Either way, the record flags it first.
A Vendor Is the Bottleneck
A vendor that's slow to turn a truck around is hard to spot from cost alone.
- Downtime compared vendor to vendor.
- Cross-references Vendor records.
- The slow vendor becomes easy to spot.
One Trip Instead of Two
Knock out upcoming PMs while a truck is already down for unexpected repairs.
- Parts checked against stock ahead of time.
- Work gets folded into the same visit.
- Low-stock parts reorder on their own.
Some Trucks Are Down Too Often
A truck running downtime well above the fleet average is worth a closer look.
- Could be a bad part or a repair pattern.
- Could be a unit nearing its end of life.
- Either way, the record flags it first.
Shop Management
Identify problems before they create downtime and costs.
- Downtime compared shop to shop.
- Syncs with Multi-Shop Management data.
- The slow yard surfaces on its own.
A Vendor Is the Bottleneck
A vendor that's slow to turn a truck around is hard to spot from cost alone.
- Downtime compared vendor to vendor.
- Cross-references Vendor records.
- The slow vendor becomes easy to spot.
Replace Instead of Repairing
A truck whose downtime keeps climbing is telling you something about its future.
- Feeds into Lifecycle Management strategy.
- Weighed alongside repair frequency.
- Turns a guess into an actual call.
The Same Record Connects to
How the Rest of the Fleet Runs
The out-of-service record isn't an island. It attaches to the same work order, parts,
and planning data everywhere else in the shop.
PMs
A truck already sitting in the bay gets checked against its next upcoming PM schedule.
Parts and Inventory
Stock levels and purchase requests are what keep a missing part from adding an extra day.
Multi-Shop
Comparing shops on downtime uses the same cross-location reporting already run for cost.
Vendor Management
If outside shops repair your trucks, you can clearly see which one impacts downtime the least.
Lifecycle Management
Downtime trends are one of the signals already feeding the repair-vs-replace call.
Who Reads the Out-of-Service Record
Ops Director
Sees which trucks are down, which are back, and which routes shift, without calling the shop.
Inventory Pro
Gets the parts list for an upcoming PM before the truck that needs it is already on the lift.
Dispatcher
Checks equipment status directly instead of calling the shop to find out if a unit is back.
Fleet Executive
Reads how long trucks are down against the hours logged on repairs, not the repair total alone.
Ask a Downtime Question and
Watch the Number Go to Work
Ask Riggs how long a truck's been down and watch the exact answer come back, then see what that number
changes, starting with a PM caught early on a truck that's already in the bay.
FAQ
Can We Get a Downtime Answer without Building a Report?
Yes. Riggs, Squarerigger's AI assistant, answers a plain-language question about downtime by vehicle, pulling from the same out-of-service and work order records behind the rest of the page.
What Counts as Downtime?
The full time a truck is marked out of service, including time spent waiting on a part or a technician, not just the hours a technician actively spent on the repair.
Is Downtime Tracked per Truck or across the Fleet?
Both. Out-of-service events roll up at the individual vehicle level and at the fleet level, so the same record supports a single-truck question and a fleet-wide trend.
Does This Replace Labor or Wrench-Time Reporting?
No. Downtime measures how long the truck itself was down; labor hours logged on the work order still show the time a technician spent on the repair. The two numbers stay separate.
How Does a Vehicle Get Marked as Down?
A technician or manager marks it out of service, and that action starts the record. The same person marks it back in service when the truck returns to work.
What Happens to Downtime and Service Records We Already Have?
Existing service and status history is part of the data migration step in onboarding, so downtime reporting starts with a baseline instead of starting blank.