How Long Should a Rental Repair Actually Take? Resolution-Time Benchmarks from 193,000+ Work Orders
When a tenant submits a repair request, the only number anyone in the chain actually cares about is how many days until it closes. Most landlords have a gut sense of that number for their own portfolio and almost no sense of what is normal across the market. We pulled more than 193,000 first-party rental maintenance requests from our platform, spanning eight years and all 50 states, and measured how long each one took to resolve. (See the full report here). The numbers below are benchmarks you can hand to vendors, write into SLAs, and use to set tenant expectations.
The key findings:
- The typical rental repair resolves in 13.1 days (median). The arithmetic average is 50.2 days, but the average is pulled up by a long tail of multi-month outliers and does not describe a normal repair.
- Resolution time varies 4x across categories. Locksmith work closes fastest at a median of 7.9 days. Roof repair closes slowest at a median of 33.9 days. Emergency-adjacent categories close in days; capital-intensive categories take months.
- The fastest 1 in 4 repairs close in under 4 days. The slowest 1 in 4 stretch past 5 weeks. The worst 1 in 10 take more than 4 months. The shape of the distribution matters more than the headline median.
- Hemlane-coordinated repairs resolve in 10.1 days median, 31% faster than self-managed repairs (14.7 days). The category-level gaps are largest in vendor-sourcing-heavy work: locksmith (48% faster), electrical (33%), handywork (32%).
This guide walks through each finding, names the caveats inline, and translates the numbers into vendor SLAs you can actually use.
Median Resolution Time Varies 4x Across Categories
The first thing to get straight is what "normal" looks like by category, because it is not one number. Resolution time spans a 4x range from the fastest category to the slowest. Emergency-adjacent work that arrives with scope and urgency built in (a tenant locked out, a furnace down in January, water on the floor) closes in single-digit days. Capital-intensive work that requires estimates, owner approvals, multiple vendor visits, or a weather window (a roof, a contractor remodel, a large appliance replacement) stretches into weeks or months.
A landlord setting vendor SLAs can use this table directly. Target a 10-day SLA for the emergency-adjacent block (locks through garage door). Target 15 to 20 days for the mid-block (appliance, pest, handywork). Treat 30-plus-day timelines as the realistic floor for roof and general contracting work. Anything well outside those bands on your own log deserves a closer look at the vendor, the approval chain, or the parts pipeline.
What a Fast, Typical, Slow, and Worst-Case Repair Actually Looks Like
The median is the right benchmark for the typical repair, but it hides the shape of the distribution. A portfolio's tenant experience is shaped at least as much by the long tail as by the middle. Here is what that distribution looks like in plain terms.
Two things stand out. The bulk of the dataset closes in a tight band between a few days and a few weeks. And the long tail goes much further than most landlords assume: the worst tenth crosses a four-month boundary, and a small share crosses seven months. These are real wall-clock stories of repairs that hit insurance disputes, owner indecision, special-order parts, contractor scheduling, or scope changes mid-project.
The right operational question is not "what is our average." The average gets distorted by the tail. The right questions are: where is our typical repair, and how thick is our tail. A portfolio with a 14-day median and a 30-day worst tenth is in good shape. A portfolio with the same 14-day median and a 4-month worst tenth has a tail problem hiding inside a healthy headline.
One technical note. Resolution time is wall-clock days from submission to closure. That includes idle time waiting for parts, tenant availability, owner approval, and weather windows. It is not active-work time. Reopened tickets show the last closure timestamp, which inflates resolution time slightly for the small share that got reopened.
Why Emergency-Adjacent Repairs Close in Days and Capital Projects Take Months
The category ranking is not random. It tracks two underlying drivers: how urgent the repair feels to everyone in the chain, and how many handoffs it requires before it can close.
Emergency-adjacent work (locks, HVAC, plumbing, garage doors) closes fast because the scope is obvious from the request itself, the vendor knows what to bring on the first visit, and everyone treats it as urgent. Tenants are home for the appointment because they cannot live without the fix. Owners do not need to be looped in for approval on a $200 plumbing call. One visit, one truck, one fix, done.
Capital-intensive work runs the opposite playbook. A roof repair or a contractor remodel starts with an inspection, then an estimate, then an owner approval, then a scheduling conversation that has to thread weather, contractor availability, and tenant access. Each step adds days of idle time even if the active labor is small. By the time the calendar slots line up, two weeks have already gone by before anyone picks up a tool.
Appliance, pest, and handywork sit between the two patterns. Appliance repair stretches because parts get ordered. Pest control stretches because most treatments require multiple visits over weeks. Handywork stretches because the scope drifts mid-job. For SLA-setting, the lens is simple: if a category should be a single-visit fix, treat anything past two weeks as a flag; if it inherently requires multiple visits or owner approvals, build that into the SLA you advertise to tenants.
Plumbing Resolution Time Varies 2x by State
The most-cited number for plumbing in this dataset is the 9.9-day national median. That number is real, but it conceals a meaningful 2x spread across states.
Ohio plumbers close work at almost twice the speed of Nevada plumbers in this dataset. Most other states sit in a middle band between 10 and 14 days. Vendor density drives most of the spread: tight markets like Nevada and parts of California have fewer plumbers, longer dispatch queues, and more competition for the same trucks. Permit complexity, construction style (slab vs basement plumbing), and the local rental mix layer on top. The practical takeaway: do not write the same plumbing SLA into an Ohio portfolio and a Nevada portfolio. A 10-day SLA is easy in Ohio and aggressive in Nevada. Calibrate to the market.
Don't Lead With the Average When You Pull Your Own Log
A landlord who exports their own maintenance log and averages the days-to-close column will get a number close to 50. The temptation is to read that as a problem. It almost never is. Almost every portfolio's average looks bad for the same reason the dataset average does: a handful of long-tail repairs pull the mean dramatically up.
The right way to benchmark your own log against this study is in three numbers, not one.
- Pull the median. Sort the days-to-close column and pick the middle value. That is the typical repair on your portfolio. Compare it to the 13.1-day all-category median or to the per-category table above.
- Pull the 75th-percentile value. The value where three-quarters of your repairs close at or under it. The dataset benchmark is roughly 5 weeks. If your number is much higher, your slow repairs are slower than the market, not just your average pulled up by outliers.
- Count the long tail separately. How many of your repairs took longer than 4 months? In the dataset, that is the worst 10%. If your share is closer to 20 or 25%, you have a tail problem worth diagnosing (owner approvals stalling, vendor handoffs failing, parts orders disappearing).
Use the average only when you need a portfolio-level dollar figure for budgeting, and know that a handful of outliers are doing most of the work to inflate it.
How Hemlane's Coordinated Maintenance Compares to Self-Managed on Resolution Time
The single largest gap in the data is not between categories or states. It is between repairs that ran through Hemlane's coordinated maintenance service and repairs that landlords managed themselves on the same platform.
Hemlane-coordinated repairs resolve at a median of 10.1 days. Self-managed repairs resolve at a median of 14.7 days. That is 31% faster. Coordination wins across every category we measured, with the biggest gaps in vendor-sourcing-heavy work where the value of a ready vendor network is most direct.
Hemlane's coordinated maintenance is a defined service tier, not a generic coordination label. When a tenant submits a request on a Hemlane-coordinated account, a repair coordinator on Hemlane's team picks up the ticket, dispatches a vendor from the vetted local network in the right market, manages the tenant communication through the lifecycle, and tracks the request to closure. The service runs 24/7 across all 50 states. The numbers above compare requests that ran through this service tier against requests the landlord managed themselves on the platform.
Two things to flag inside the result. The gap is largest where vendor sourcing is the bottleneck. Locksmith and electrical are the categories where "do you have a vetted vendor ready to dispatch" matters most, and that is exactly where Hemlane-coordinated repairs pull the furthest ahead. The gap is real but smaller on HVAC, where physical scheduling constraints (the vendor still needs a truck and a slot on a busy week in January) matter more than coordination speed. Coordination buys the most time back where the friction was sourcing a vendor, not where the friction was the calendar.
What This Means for Your Portfolio
The right move on resolution time depends on the portfolio you actually run. The table below maps the benchmarks to action.
For operators across multiple states or running PM through a brokerage, the value compounds with standardization. A category-by-state SLA grid that everyone in the chain sees the same way is worth more than any single faster vendor.
About Hemlane
Hemlane is property management software with a built-in service layer. The platform runs the full rental workflow (rent collection, leasing, maintenance, and accounting), and on its paid tiers it adds real people behind the software: 24/7 repair coordination, dedicated leasing coordinators, and a vetted local vendor network across all 50 states. That combination of software plus service is what separates Hemlane from software-only tools.
The 31% faster resolution-time finding above is the most direct proof of what the service layer changes. The Hemlane-coordinated cohort in that comparison is the repair coordination feature in action: a Hemlane coordinator takes the request, dispatches the vendor, manages tenant communication, and tracks closure. Per-portfolio response-time reporting surfaces the SLA back to owners and brokerages.
Hemlane serves operators running roughly 10 to 200 units, across single-family and multifamily portfolios. That includes property management groups scaling their door count, real estate investors and brokerages adding property management as a service line, remote and out-of-state landlords, single-family investors with portfolios across multiple markets, and landlords scaling from DIY to operator. State-specific lease templates across all 50 states, 24/7 repair coordination, and online rent collection all run from the same platform.
Frequently Asked Questions
How long does it take to fix a plumbing issue in a rental?
Across 193,000+ first-party rental maintenance requests, the median plumbing repair resolves in 9.9 days. Performance varies 2x by state: Ohio is fastest at 7.9 days, Nevada is slowest at 14.7. Plumbing runs faster than the 13.1-day all-category median because plumbing requests tend to arrive with clear scope and built-in urgency.
How long does it take to fix HVAC in a rental property?
The median HVAC repair resolves in 9.6 days. HVAC has strong climate-driven seasonality: Northern and Midwestern markets peak in January (heating failures), Sun Belt markets peak May through August (AC failures), and Western markets peak in June and July. Hemlane-coordinated HVAC repairs run 12% faster than self-managed ones in the dataset.
How long does an electrical repair take in a rental?
The median electrical repair resolves in 13.1 days, in line with the all-category median. Electrical work is sensitive to vendor availability and permit complexity, which is why Hemlane-coordinated repairs run 33% faster than self-managed in the same category.
What is the average rental property repair time?
The arithmetic average across 193,000+ work orders is 50.2 days. The average is inflated by a long tail (the worst 10% of repairs stretch past 4 months, and the worst few percent stretch past 7 months). The median of 13.1 days is the more useful benchmark for the typical repair.
Why is the average so different from the median for rental repairs?
The distribution is skewed by a long tail of multi-month repairs. About 1 in 4 repairs close in under 4 days. Half close in under 2 weeks. But the slowest 1 in 10 stretch past 4 months, and those long-tail repairs drag the simple average up to about 50 days. The median describes the typical repair; the average describes the budget impact of the tail.
How long do plumbing repairs take by state?
In the dataset, Ohio resolves plumbing fastest at 7.9 days median. Nevada is slowest at 14.7 days. Florida and Colorado sit at 9.9, California at 11.1, New York at 11.3, Georgia at 12.0, and North Carolina at 14.1. Vendor density, permit complexity, and tenant scheduling all drive the spread.
Does Hemlane's coordinated maintenance speed up repairs?
Yes. Hemlane-coordinated repairs resolve at a 10.1-day median versus 14.7 days for self-managed (31% faster). The gap is consistent across every category measured, with the largest gaps in vendor-sourcing-heavy categories: locksmith (48% faster), electrical (33%), and handywork (32%).
Methodology
This analysis is based on first-party data from our production database covering August 2018 through May 2026. The primary dataset is more than 193,000 maintenance requests, of which 178,780 were closed at the time of analysis. Resolution time is measured as the elapsed wall-clock time from “created_at” (when the tenant or owner submitted the request) to the “updated_at” timestamp when the request status changed to "Closed." Wall-clock time includes idle periods (parts, tenant availability, owner approval, weather windows); it is not active-work time. Reopened requests show the last closure timestamp, which inflates resolution time slightly for the small share of requests that were reopened. Category-level medians use only requests with a category assigned at submission; the "Other / Uncategorized" bucket is excluded. State-level plumbing figures use requests with both a "Plumbing" category and a state-confirmed property address. The "Hemlane-coordinated" cohort consists of requests routed through Hemlane's coordinated maintenance service tier, where a Hemlane repair coordinator dispatched the vendor, managed tenant communication, and tracked closure. The "self-managed" cohort consists of requests managed by the landlord on the platform without coordination. Both cohorts run on the same Hemlane platform; the comparison isolates the service layer, not the software. All figures are first-party data; no third-party sources were used, and no personally identifying tenant information was included. View the full report.
Get the Latest in Real Estate & Property Management!
I consent to receiving news, emails, and related marketing communications. I have read and agree with the privacy policy.
