Maintenance Metrics Your Team Should Know: What Belongs on a Maintenance Scorecard

Most property management teams track maintenance the way they track weather: they notice it when it turns bad. Work orders get counted, complaints get escalated, and the performance conversation runs on whoever remembers the worst week. A maintenance scorecard replaces that with a fixed set of numbers reviewed on a fixed cadence, so the conversation starts from what happened across the portfolio rather than from what stuck in someone’s memory.

The useful version of that scorecard is short and it is honest about ownership. Every metric on it should answer a question someone can act on, and it should be clear who that someone is. This guide covers the metrics that earn a place on a maintenance scorecard, what each one is really measuring, and the reading errors that send teams chasing the wrong problem.

Key Takeaways

• A maintenance scorecard should group metrics by what they measure: speed, service quality, quotes and approvals, volume and resident experience, and consistency.
• Averages hide your worst work orders. The same metric reported at the 80th percentile shows the experience most residents actually get.
• Quote approval time sits with the property management team, and it is frequently the largest single delay on higher-cost jobs.
• One-trip resolution is defined strictly, so a low rate often reflects job mix rather than field performance.
• An average resident rating means very little without the review count next to it.

What Are Maintenance Metrics?

Maintenance metrics are the standardized measurements a property management team uses to judge maintenance performance across a portfolio, covering how fast work gets done, how reliably it gets done right, and how residents experienced it. They convert a stream of individual work orders into a pattern you can manage.

The distinction that matters most is between activity and outcomes. Activity metrics count what happened: work orders opened, work orders closed, jobs per technician. Outcome metrics measure what the resident and the owner experienced: how long the repair took end to end, whether it held, whether anyone showed up inside the window they were given. A scorecard built only on activity will look healthy during a period residents spent waiting.

The Metrics That Belong on a Maintenance Scorecard

A complete maintenance scorecard covers five groups: speed and turnaround, service quality and reliability, quotes and approvals, volume and resident experience, and consistency. Each group answers a different question, and a portfolio reporting only one of them will be blind in a predictable direction.

Group	Metric	What it measures
Speed & turnaround	Speed of repair, assignment to processed	The full clock, from assignment through the work, quality check, and invoicing
	Speed of repair, assignment to completion by the Pro	The field-work portion only
	Time to process, completion to processed	The back-office portion only
	Days out of resident availability	Days between the resident’s first offered availability and the actual work
Service quality & reliability	One-trip resolution rate	Share of jobs fully resolved in a single same-day visit with no quote required
	On-time arrival rate	Share of appointments where the Pro arrived inside the scheduled window
	Pro app compliance	Share of work orders managed in-app rather than offline
Quotes & approvals	Time to submit quote	How long the service provider takes to get pricing in front of you
	Time to approve quote	How long your team takes to respond
	Quotes approved rate	Share of submitted quotes that were approved
Volume & resident experience	Total work orders completed	The volume baseline behind every rate and average
	Average resident rating	Satisfaction, straight from residents
	Total reviews	How much feedback that rating is built on
Consistency	80th percentile versions of the three speed metrics	The time within which eight out of ten work orders finished

Speed and Turnaround

Speed only becomes actionable when the clock is split by who controls each segment. One end-to-end number tells you a repair was slow. Three numbers tell you where it was slow.

The full cycle runs from assignment to processed, meaning the work is done, quality-checked, and invoiced. Inside that sit the field portion, which ends when the Pro marks the job complete, and the back-office portion, which covers quality assurance and close-out. A long back-office segment delays your invoicing and reporting rather than the resident’s repair, which makes it a real problem with a very different fix than a slow field segment.

Days out of resident availability is the segment most reporting ignores completely. It measures the gap between the resident’s first offered availability and when the work actually happened, which separates delays the maintenance operation caused from delays that came from resident scheduling. Without it, a job that waited nine days for a resident to be home reads as a service failure.

Service Quality and Reliability

On-time arrival rate is the promise-kept rate. Residents judge service on whether someone showed up in the window they were given, and a missed window costs a resident a day off work no matter how good the repair turns out to be.

One-trip resolution measures the share of work orders the Pro fully resolved in a single visit, on the same calendar day, with no quote required. That definition is strict on purpose, and it is worth reading twice, because it drives how the number should be interpreted.

Pro app compliance tracks the share of work orders managed through the app rather than offline. Teams tend to file this one under housekeeping, which is exactly why it becomes a problem. App usage is what produces live status, photos, and timestamps, so every job handled offline is a job you cannot audit, cannot bill damage back on, and cannot use to detect a failure pattern. It is also the metric everything else depends on: compliance gaps quietly corrupt every other number on the scorecard.

Quotes and Approvals

Quote metrics come in a matched pair by design. Time to submit quote belongs to the service provider. Time to approve quote belongs to your team. Putting them next to each other in the same row is what keeps the conversation factual.

The quotes approved rate is the quieter of the three, and it measures something useful about the relationship: whether scoping and pricing are landing where you expect. A rate that drops means quotes are arriving priced or scoped differently than your team anticipated, which is a conversation to have early rather than at renewal.

Volume and Resident Experience

Total work orders completed is the baseline. On its own it says very little, because a high number can mean a productive period or a portfolio in trouble. Read it against work orders opened. When completions trail intake for two consecutive periods, a backlog is forming, and backlogs are where emergency spend comes from.

Average resident rating is the most direct read on satisfaction available, and it needs total reviews next to it to mean anything. A 4.8 built on twelve responses across a hundred jobs is a different signal than a 4.8 built on eighty. A rating that dips while review count climbs is usually a sampling change rather than a service change, and teams that report the rating alone will misread that every time. Maintenance experience also carries further than the work order itself, since it is one of the strongest factors in whether a resident renews their lease.

Consistency

The consistency group reports the three speed metrics again at the 80th percentile: the time within which eight out of ten work orders finished. Reporting both the average and the 80th percentile is what turns a speed number into a diagnosis.

Why Averages Hide Your Worst Work Orders

An average completion time describes almost none of your work orders, because maintenance timelines are skewed by a small tail of jobs that run far longer than the rest. The gap between the average and the 80th percentile tells you how long that tail is.

When the 80th percentile is dramatically faster than the average, most of the portfolio is being served well and a small group of jobs is dragging the headline number. That is a completely different problem from a portfolio that is uniformly slow, and it calls for a different response. Uniform slowness is a capacity problem: not enough coverage for the volume. A long tail is an exception-handling problem: a handful of jobs falling into a gap between systems, waiting on a specialty part, a hard-to-reach resident, an approval nobody chased, or an owner decision.

Chasing the average in a long-tail portfolio wastes effort on jobs that are already fine. Pull the tail instead. List every work order that took more than double the 80th-percentile time and read what happened on each one. The reasons repeat, usually in three or four patterns, and each pattern has a fix.

Which Delays You Control, and Which You Do Not

The most valuable thing a well-built scorecard does is assign delay to an owner. Four segments of the same timeline sit with four different parties, and treating them as one number is how teams end up solving the wrong problem for a quarter.

• The field segment sits with the service provider and the Pro. Slow here points to dispatch depth, trade availability, or routing.
• The back-office segment sits with the provider’s close-out process. Slow here delays invoicing and reporting rather than the resident’s repair.
• Resident availability sits with the resident. This one is context rather than a performance problem, and it exists on the scorecard so the other numbers can be read fairly.
• Quote approval sits entirely with your team.

That last one is the blind spot, because most reporting measures the vendor and stops there. When approval takes longer than the repair, adding technicians or pushing the provider for faster response will not move the resident’s wait at all. The queue is internal.

Two changes usually clear it. Set an internal approval SLA and put it on the scorecard directly beneath the provider’s submission time, so both halves of the handoff are visible in one place. Then raise the pre-approval threshold: every quote under a set dollar amount proceeds without a human decision, which removes most approvals from the queue and leaves your team reviewing only the ones where judgment adds value. Not-to-exceed limits do the same work further upstream, capping spend at intake so the job can proceed. SLA tracking covers how to structure those commitments across a portfolio.

Why a Low One-Trip Resolution Rate Can Be Misleading

One-trip resolution counts only the jobs a Pro fully resolved in a single same-day visit with no quote attached. Any work order that legitimately required a quote falls outside the definition, which means the rate is shaped heavily by job mix before field performance enters into it.

A portfolio running mostly small repairs will post a high rate. A portfolio in a heavy season for major systems, or one carrying deferred maintenance where jobs arrive larger, will post a lower one while the field work performs exactly as it should. Read the rate against total work order volume, the quote metrics, and the service categories driving the period. If quote volume climbed and one-trip resolution fell in the same period, those are the same event described twice.

Where the rate is genuinely low for its mix, the cause usually sits upstream of the technician. A job dispatched with a clear description, the right category, a photo of the actual failure, and a make and model number can arrive with the right part on the truck. A job dispatched as “sink broken” cannot. Better triage at the front of the process is what makes single-visit repairs possible, which is why AI maintenance triage moves this number more reliably than pressure on the field ever does.

Read speed and one-trip resolution as a pair, always. The fastest way to close a work order is to visit, diagnose, and leave for parts, so a team pushed hard on completion speed alone will watch one-trip resolution fall. Hold speed steady while resolution improves and the total resident wait drops, because the second trips stop happening.

Turning a Scorecard Into a Maintenance KPI Dashboard

A scorecard and a dashboard do different jobs, and teams get more out of both when they are built for those jobs rather than duplicated. A scorecard is a periodic snapshot for review and accountability. A maintenance KPI dashboard is the always-on view a coordinator works from during the day.

Split the metrics accordingly. Anything a coordinator can act on inside the current period belongs on the dashboard: quotes waiting on approval, appointments at risk of missing their window, work orders past a set age, jobs held on resident availability. These are queues, and a dashboard exists to keep them short.

Rate and average metrics belong on the scorecard instead. On-time arrival rate, one-trip resolution, and average resident rating are unstable over short windows and low volume, so watching them daily produces noise and prompts reactions to swings that carry no signal. Give them a longer window and a fixed review.

The rule that keeps a dashboard useful: every tile answers a question someone would otherwise have to ask. Tiles nobody acts on get removed, no matter how good they look in a leadership meeting.

How to Run the Scorecard Review

The scorecard earns its keep through the review that follows it. Thirty minutes on a fixed agenda handles it:

1. Read the trend, not the number: A single period tells you almost nothing. Three periods of direction tell you what is happening.
2. Pick the one metric that moved most: Discuss that properly instead of skimming all sixteen.
3. Pull five work orders behind it: Metrics show that something changed. Individual jobs show why.
4. Assign one owner and one change: Every review produces a single named action, not a list of observations.
5. Check last review’s action first: Reviews that never revisit prior actions stop producing them.

Segment before you interpret. A portfolio-wide average blends a well-served market with a struggling one and hides both. Break the numbers out by market, by property type, and by service category, and the outliers name themselves.

Treat published industry benchmarks carefully. They come from portfolios with different property types, climates, and staffing models, so they set direction rather than targets. Your own first quarter of data is the more honest benchmark, and every period after that is measured against your own trend.

Common Mistakes When Tracking Maintenance Metrics

Plenty of property management companies collect maintenance data and still run rising costs, growing backlogs, and unhappy residents. The problem is rarely the volume of data. It is which metrics get chosen and what happens after they are read.

• Tracking everything: A report carrying dozens of indicators buries the few that require action. Metrics that have never once changed a decision should come off.
• Counting activity and calling it performance: Tasks completed and hours worked describe effort. They can stay high while resident wait times get worse.
• Watching only the work you dispatched: A maintenance scorecard covers the reactive work that flowed through the system. It cannot see whether your preventive program is running on schedule, and skipped preventive work is what turns into next quarter’s emergencies. Track preventive maintenance compliance separately and read the two together.
• Reviewing too late to act: Metrics reviewed only at quarter end surface problems residents already lived through.
• Reading portfolio averages alone: One underperforming market can sit inside a healthy-looking average for months.
• Treating benchmarks as targets: Benchmarks are reference points shaped by other portfolios’ asset age, climate, and staffing.
• Reporting without acting: The most common failure of all. When numbers get presented and nothing changes, teams stop taking the review seriously, and the reporting becomes an artifact rather than a tool.

Where the Numbers Come From

Reliable metrics require every work order to move through one system, because a portfolio running maintenance across email threads, phone calls, and separate vendor portals cannot produce a trustworthy timestamp. Consistent measurement is a byproduct of consistent process, which is why centralizing maintenance usually has to come before reporting improves. It is also why app compliance matters so much: the timestamps get captured at each handoff by the people doing the work, rather than reconstructed afterward.

Lula reports these metrics back to property management teams on a regular cadence, drawing on a network of 9,000+ vetted Pros across 50+ markets, with quality assurance and documentation built into every completed job. The scorecard assembles itself because the work runs through one system.

If your maintenance reporting today is stitched together by hand from several sources, that effort is the signal worth acting on. Talk to Lula about what a scorecard for your portfolio would show.

Maintenance Metrics FAQ

Should a maintenance scorecard be reviewed weekly or monthly? 

Weekly for operational metrics a coordinator can act on immediately, like quotes sitting in the approval queue. Monthly or quarterly for trend and executive reporting, where a longer window smooths out the noise that makes rates jump around on low volume.

Should maintenance metrics be reported per property or across the portfolio? 

Both, at different cadences. Portfolio-level for trend and executive reporting, segmented by market or property type for diagnosis. Per-property is worth pulling on demand when a specific address keeps appearing in the exception list.

Who should receive the maintenance scorecard? 

Operations leadership and whoever owns vendor relationships at minimum, since most of the actions a scorecard triggers sit with those two roles. Sharing a simplified version with owners builds real trust, though it works best once the numbers have a few periods of stable history behind them.

How many metrics is too many? 

The constraint is not how many numbers a system can produce, it is how many a team can discuss in one meeting and act on before the next one. A grouped scorecard can carry more than a flat list, because people read it by section rather than top to bottom.

How is a maintenance scorecard different from a vendor scorecard? 

A maintenance scorecard measures your portfolio’s maintenance performance overall, including the internal steps your own team owns. A vendor scorecard compares individual service providers against each other for selection and renewal decisions. The metrics overlap, the decisions they support do not.