How to Calculate MTTR and Why It Matters for Small Maintenance Teams

What MTTR actually means

MTTR stands for Mean Time to Repair. It measures the average time it takes to fix a piece of equipment after it breaks down — from the moment the failure is reported to the moment the machine is back in production. Some definitions include only wrench time. Others include diagnosis, parts procurement, and testing. For small teams, the most useful definition is the one that captures the full impact: total downtime divided by number of repairs.

The formula is straightforward:

MTTR = Total repair time ÷ Number of repairs

If your hydraulic press went down three times last quarter and the total repair time was 12 hours, your MTTR for that press is 4 hours. That's the number you want to shrink.

Why MTTR matters more than you think

MTTR tells you how fast your team recovers from failures. A low MTTR doesn't mean equipment never breaks — it means when it does break, you get it running again quickly. For a small factory where every hour of downtime costs real money, the difference between a 2-hour MTTR and a 6-hour MTTR is enormous.

Consider a shop billing $200/hour with 10 breakdowns per month. At a 2-hour MTTR, that's $4,000 in lost production. At 6 hours, it's $12,000. Same number of failures — $8,000 difference — just from how fast you recover.

MTTR also exposes systemic problems. If your MTTR on a specific machine is climbing, something has changed: maybe you're losing institutional knowledge, maybe parts are harder to source, maybe the machine needs a capital overhaul instead of another repair.

MTTR benchmarks by industry

Benchmarks vary widely depending on equipment complexity, team size, and parts availability. Use these as rough guides, not hard targets:

• General manufacturing: 2–4 hours for most mechanical equipment. CNC machines and complex automation may run 4–8 hours.
• Food & beverage: 1–3 hours target, driven by production schedule pressure and sanitation requirements.
• Fleet operations: 2–6 hours depending on whether the repair is done in-house or at a third-party shop.
• Facilities: 4–24 hours, with wide variance between a simple HVAC fix and a chiller compressor replacement.

The benchmark that matters most is your own. Track MTTR monthly for your top 5 critical assets and watch the trend. If it's going down, your maintenance program is working. If it's going up, dig into why.

How to track MTTR correctly

The biggest challenge with MTTR isn't the math — it's the data. You need two things for every unplanned repair: when the failure was reported and when the equipment was back online. If either timestamp is missing or estimated, your MTTR is a guess.

Here's what a reliable MTTR tracking process looks like:

1. Log the failure immediately. When a machine goes down, someone creates a work order. The timestamp on that work order is your start time. If nobody logs it until the next morning, your data is already wrong.
2. Record the completion. When the tech finishes the repair and the machine is running, they close the work order. That's your end time.
3. Tag it as unplanned. MTTR only applies to unplanned failures. Planned PM downtime doesn't count. Your tracking system needs to distinguish between the two.
4. Calculate automatically. Don't make someone pull timestamps from a spreadsheet and do the math. A CMMS calculates MTTR from the work order data your team is already entering.

Common mistakes that skew your MTTR

Most small teams that track MTTR get inaccurate numbers — not because the formula is hard, but because the input data has problems. Here are the most common mistakes:

1. Including planned maintenance. If you count a scheduled PM that took 3 hours as a “repair,” your MTTR is artificially inflated. Only unplanned, corrective repairs should be included.

2. Delayed logging. The tech fixes the machine at 2 PM but doesn't close the work order until the next morning. Your MTTR now includes 16 hours of phantom repair time. Encourage techs to close work orders immediately — even from their phone while walking away from the machine.

3. Lumping wait time and wrench time together. If a repair took 1 hour of actual work but the tech waited 5 hours for a part, your MTTR is 6 hours. That's technically correct for total downtime, but it hides the real problem — parts availability, not repair skill. Track both if you can: total downtime and actual wrench time.

4. Not tracking by asset. An overall MTTR of 3 hours is meaningless if one machine averages 8 hours and everything else averages 1 hour. Always track MTTR per asset. The aggregate number is nice for reports. The per-asset number is what drives decisions.

5. Too small a sample size. If a machine broke once last quarter and the repair took 7 hours, its MTTR is 7 hours — but that's one data point, not a trend. You need at least 5–10 repair events to get a meaningful MTTR for a specific asset.

How to improve your MTTR

Once you're tracking MTTR accurately, here are the levers that actually move the number:

• Stock critical spare parts. The #1 reason MTTR is high is waiting for parts. Identify the parts that fail most often on your critical equipment and keep them on hand.
• Document repair procedures. If only one tech knows how to fix the bagger, your MTTR depends on that person's availability. Attach step-by-step procedures to your work orders so any qualified tech can handle the repair.
• Improve fault diagnosis. Half of many repairs is figuring out what's wrong. Failure codes on work orders build a history that helps the next tech start with the most likely cause instead of guessing.
• Pre-stage tools and materials. If every repair starts with a 20-minute trip to the tool crib and a search for the right filter, that's built into your MTTR. Kitting parts and tools for common repairs eliminates this waste.

MTTR vs. MTBF: use them together

MTTR tells you how fast you recover. MTBF (Mean Time Between Failures) tells you how often things break. Together, they give you the full picture. A machine with a high MTBF and low MTTR is reliable and easy to fix — that's your best case. A machine with a low MTBF and high MTTR breaks often and takes forever to fix — that's your capital replacement candidate.

For most small teams, start with MTTR. It's easier to track because it only requires data from the repair itself, not ongoing uptime logs. Once you're comfortable with MTTR, layer in MTBF for your most critical assets.

Start tracking this week

You don't need perfect historical data to start. Pick your five most critical machines. Starting today, log every unplanned breakdown with a start time and end time. In 90 days, you'll have enough data to calculate a meaningful MTTR for each one — and you'll know exactly which machines need attention and which repair processes need improvement.

The formula is simple. The discipline of capturing accurate timestamps is the hard part. Make it easy for your team (phone-based work orders, QR codes on equipment, two-tap completion) and the data takes care of itself.