MTTR: Meaning, Calculation and Common Measurement Mistakes

ServiceLeaf team·2026-09-29·6 min read

This article is general professional information. Product-specific sections are identified separately.

What does MTTR measure?

MTTR means Mean Time To Repair or Mean Time To Restore. It describes the average time between a failure and the equipment returning to operation. A lower result indicates a shorter interruption after an unexpected stop.

MTTR describes restoration duration, not failure frequency. Track the number of failures too: a machine that fails rarely but stays down for a long time needs a different response from one with frequent short interruptions.

How do you calculate MTTR?

MTTR = total duration of unplanned stops ÷ number of unplanned stops, for the same period and the same asset or asset group.

Example using fictional data: a packaging machine has three unplanned stops in a month, lasting 2, 4 and 6 hours. Total downtime is 12 hours, so MTTR is 12 ÷ 3 = 4 hours.

Which time is included?

Decide where measurement starts and ends. Two common definitions are:

  • Full restoration time: from the start of the stop until the machine restarts, including reporting, travel, waiting for parts and repairs. This reflects production interruption.
  • Active repair time: only the technician’s hands-on work. It measures repair activity but excludes waiting.

Document your definition and apply it consistently across assets so the figures are comparable.

How can maintenance managers use it?

  • Find bottlenecks: if parts account for most of the wait, improve stock management rather than technician speed.
  • Compare equipment: identify the assets with the longest restoration times and examine the causes.
  • Review trends: check whether a new procedure, checklist or training programme changes MTTR over time.
  • Plan disruption: estimate how long a critical asset may remain unavailable after a failure.

Common measurement mistakes

  • Missing start times: records entered later from memory can be inaccurate. Record a stop when it begins.
  • Mixing planned and unplanned stops: planned maintenance is not a failure and can distort the average.
  • Forgetting to close records: a restored machine left marked as down can dominate the result.
  • Too little data: an average from two or three events is a signal, not a reliable trend. Review a longer period or asset group.
  • Outliers: weeks spent waiting for a part can hide ordinary repair patterns. Examine causes as well.
  • Different definitions: mixing full restoration time and hands-on repair time makes the total difficult to interpret.

MTTR in ServiceLeaf

Manage records on Asset Management → Downtime. Start a record from the central page or the asset’s Downtime Tracking card, then end it when the machine is operational. Downtime is entered manually; ServiceLeaf does not detect stops automatically.

The page shows currently stopped equipment, total downtime, unplanned share and mean restoration time for the chosen period, with cause and asset breakdowns. Export further analysis through Reports → Asset Analytics → Downtime Analysis. See downtime tracking and maintenance reports.

For a wider view of data-based maintenance, read Industry 4.0 and the future of maintenance.

Ready to digitise your maintenance?

Try it free for 14 days, or book a live demo.

14 days free · €0 · no credit card · free plan for up to 25 assets afterwards