How to break repair time (MTTR) into fixable buckets

Most teams track MTTR (mean time to repair) because it’s simple. But MTTR is also frustrating, because it’s a mash-up of a dozen different delays. When you treat it like one number, you end up with one solution: “work faster.”

A better approach: keep MTTR, but break it into buckets you can actually fix, especially if you’re using a CMMS, asset tracking software, or asset management software to capture timestamps.

Step 1: Pick one “clock” and stick to it

Decide what you mean by “repair time”. For example:

Start: work order marked “In Progress” (tech on the job)
End: work order marked “Completed” (equipment back to service)

This avoids arguing about whether the clock starts when someone notices the problem or when maintenance arrives.

Step 2: Use the 6-bucket MTTR breakdown

For the next 20 breakdown work orders, tag the biggest delay into one bucket (don’t overcomplicate it):

1) Access delay — waiting for shutdown, permit, LOTO, escort, or area clear.
2) Diagnostics delay — time spent figuring out what’s wrong (symptom hunting).
3) Parts & materials delay — waiting on stores, purchasing, delivery, or kitting.
4) Labor/dispatch delay — waiting because the right skill/team isn’t available.
5) Approval/admin delay — quotes, sign-offs, photos, paperwork, or “who owns this?”
6) Repair execution time — the actual hands-on fix and testing.

Step 3: Turn each bucket into one concrete countermeasure

Here are practical moves that don’t require a big transformation:

Access delay: pre-approved lockout plans + a 2-minute “ready for maintenance” checklist for ops.
Diagnostics delay: add a required “symptom + context” field (what happened, when, under what conditions).
Parts delay: create top-25 “frequent flyers” kits and tie them to common assets/BOMs.
Labor delay: define a simple on-call rotation or a dispatch rule by site/priority.
Approval delay: set dollar thresholds + pre-approved vendors for repeat jobs.
Execution time: standard job plans for repeat work (tools, steps, photos of ‘done right’).

Step 4: Make your dashboard tell the story

Instead of one MTTR number, show:

MTTR overall (trend)
% of jobs by delay bucket (last 30 days)
Top 3 assets with the most delay time (not just count of work orders)

Now your weekly meeting becomes: “Which bucket are we fixing next?”

Conclusion

MTTR improves fastest when you treat it like a story with chapters. Break it into buckets, fix the biggest chapter, and repeat. Within a month, you’ll usually see a real shift… without asking techs to sprint all day.

Bulbthings is an AI, all-in-one asset management platform for growing businesses. It helps teams capture cleaner timestamps, add lightweight delay reasons, and turn maintenance data into actions, not debates.