What Is Mean Time To Repair (MTTR), and Why Should Maintenance Managers Track It?

Mean Time To Repair (MTTR) is a maintenance metric that measures the average time it takes to restore a failed asset to full operational service, from the moment a fault is detected through to confirmed resolution.  

It is one of the most direct indicators of maintenance team efficiency and process quality.  

A high MTTR signals that something in the repair chain is creating delay - whether that is slow fault detection, poor parts availability, unclear workflows, or inadequate access to asset history. Reducing it is one of the fastest ways to cut asset downtime and its associated costs.

How Do You Calculate MTTR?

The formula is simple.

MTTR = Total Repair Time ÷ Number of Repair Events

Total repair time includes every minute from fault detection to the point the asset is confirmed back in service. It covers diagnosis, parts sourcing, the physical repair, any testing or commissioning, and final sign-off. It does not include time the asset spends awaiting a scheduled maintenance window that was planned in advance.

Example: Single asset

A building's primary chiller unit experienced four failures over a 12-month period. The total time from each fault being reported to the asset being returned to service was 38 hours across all four events.

MTTR = 38 hours ÷ 4 failures = 9.5 hours per repair event

Example: Team-level MTTR

A maintenance team managed 22 corrective maintenance jobs across a commercial campus in one quarter. Total repair time across all jobs was 176 hours.

MTTR = 176 hours ÷ 22 jobs = 8 hours per repair event

This team-level figure is useful for tracking performance trends over time and benchmarking against previous quarters or similar facilities. If the following quarter shows MTTR climbing to 11 hours per event, it is a signal worth investigating before it becomes a pattern.

What Are Realistic MTTR Benchmarks?

MTTR benchmarks vary considerably by asset type, facility criticality, and sector. There is no single universal standard, but the following ranges can help reflect typical performance levels in well-managed facilities operations:

• Critical infrastructure (hospitals, data centres): target MTTR of under 2 hours

• Essential building services (HVAC, electrical, lifts): target MTTR of 4–8 hours

• General building and fitout assets: target MTTR of 8–24 hours

• Low-criticality or non-operational assets: target MTTR of 24–72 hours

High-performing maintenance teams in complex environments typically aim to keep MTTR for essential services under four hours. Facilities operating above these thresholds consistently should treat elevated MTTR as a process problem, not simply a workload problem.

What Causes High MTTR - and Where Does Time Actually Go?

Before reducing MTTR, a maintenance manager needs to understand where time is being lost. Most delays fall into one of five categories.

1. Slow fault detection and reporting  

If faults are only reported when an asset visibly fails or a complaint is received, the clock has already been running for some time before the repair process begins. Detection delay is often the largest hidden contributor to high MTTR.

2. Incomplete or inaccessible asset information  

A technician who arrives on-site without the asset's service history, wiring diagrams, or previous fault records spends the first portion of every repair job gathering information that should already be at hand. Every minute spent searching is a minute not spent repairing.

3. Parts and materials delays  

Waiting for parts that are not stocked on-site is one of the most common reasons repair times blow out. If parts sourcing is reactive rather than informed by failure patterns, delays are predictable and preventable.

4. Unclear or absent work order information  

A poorly scoped work order forces technicians to make assumptions about the fault, the location, and the expected resolution. Rework and revisits add directly to MTTR.

5. Approval and communication bottlenecks  

Repair jobs that require authorisation before work can proceed - and where that approval process is manual, slow, or unclear - accumulate waiting time that inflates MTTR without any productive repair activity occurring.

Five Process Improvements That Directly Reduce MTTR

Reducing MTTR is not primarily a technology problem. It is a process problem. The right systems support better processes, but the process changes themselves are where the gains come from.

1. Implement structured fault reporting with clear triage criteria. Define what constitutes a critical, urgent, and routine fault, and set response time targets for each. When the classification is clear at the point of reporting, dispatch and prioritisation happen faster. An asset criticality framework can help to streamline this process.  

2. Attach complete asset records to every work order. When a work order is raised against an asset, the technician should receive the asset's full profile - location, make and model, maintenance history, previous faults, and relevant documentation. Eliminating the information-gathering phase from each repair job has a direct and measurable impact on repair time.

3. Use maintenance history to pre-position common parts. If an asset class consistently fails in the same way, the parts required for that repair should be stocked locally. Analysing work order data across asset categories to identify recurring fault types gives maintenance managers the information they need to make stocking decisions proactively rather than reactively.

4. Automate work order escalation for time-sensitive faults. For critical assets, escalation should happen automatically if a fault is not acknowledged or actioned within a defined window. Manual escalation chains introduce delays; automated rules do not.

5. Review closed work orders to identify process bottlenecks. MTTR analysis is most powerful when it is broken down by fault phase - detection time, diagnosis time, parts wait time, and repair time. Reviewing completed jobs to identify where time is consistently lost allows targeted process changes rather than broad interventions with unpredictable outcomes.

How Tracking MTTR Alongside MTBF Sharpens the Picture

MTTR and MTBF (Mean Time Between Failures) work best as a pair. MTBF tells you how often assets fail; MTTR tells you how long it takes to recover when they do. Together, they give a maintenance manager a complete reliability profile for each asset and asset class.

An asset with a low MTBF and a high MTTR is a high-risk item - it fails frequently and takes a long time to restore. An asset with a high MTBF but a high MTTR may be acceptable in practice, provided it does not sit in a critical service area. Using both metrics together supports more nuanced maintenance prioritisation and capital planning decisions.

Ready to cut repair times across your facility? Book a demo with the FMI Works team to see how purpose-built maintenance management software can give your team the data and workflows needed to reduce MTTR and keep assets running.