Section image

A regional property management firm managing 200 units across four properties in Central Florida spent about $340,000 on maintenance in 2023. By mid-2025, running a similar portfolio with the same physical properties, they were spending $248,000 — a 27 percent reduction. Occupancy held steady at 94.1 percent. Tenant satisfaction scores went up, not down.

That gap didn't come from cutting corners or delaying repairs. It came from changing when maintenance work gets done and how it gets grouped. The shift is less dramatic than it sounds in theory. In practice, it takes about 14 months to see the full effect, and the first six are uncomfortable because you're building a data record before the scheduling logic kicks in.

Here's what they did.

The Starting Problem

Before any changes, maintenance at this firm ran mostly reactive. Tenant submits a ticket, property manager reviews it, vendor gets dispatched. On a good day, that cycle ran 3 to 5 days. On a bad week with multiple concurrent issues, it stretched to 11 or 12.

Emergency work — the kind billed at premium rates — made up 34 percent of total maintenance spend in 2023. HVAC failures in summer, water intrusion issues, appliance failures that led to further unit damage. Most of these weren't unpredictable in hindsight. HVAC units over eight years old in Florida's climate fail at a well-documented rate. The units that failed in summer 2023 had shown declining performance patterns months earlier but nobody was tracking it.

The second problem was dispatch inefficiency. Vendors were being called for single-item jobs when those same vendors had three or four other tasks pending at the same property. A plumber coming out to address one low-pressure complaint left without touching two other reported items that could have been handled in the same visit. Coordination happened by phone and email, and fell through the cracks regularly.

Phase One: Building the History

The first thing the team did was start logging every maintenance event by unit, not just by ticket. The distinction matters. A ticket records "HVAC service call, Unit 14B, June 2023." A unit history records every maintenance event that touched 14B going back five years — HVAC services, appliance replacements, plumbing, flooring, everything. When you have that record, you can see which units are consuming disproportionate maintenance attention and why.

After 120 days of logging, patterns emerged. Twelve units across the four properties were responsible for 41 percent of all reactive maintenance calls. Not because those tenants were difficult — because those units were older, had components approaching end of useful life, and had underlying issues that had been patched rather than resolved. Addressing the root problem in those twelve units cost $31,000 in preventive work. The reactive cost those units were generating was running at approximately $67,000 per year.

Phase Two: Scheduling by System, Not by Ticket

The bigger structural change was shifting from ticket-driven maintenance to system-driven maintenance. Instead of waiting for a tenant to report that the hot water heater is underperforming, water heaters past a certain age threshold get inspected on a scheduled cycle. HVAC units in older buildings get pre-season servicing in March and September regardless of reported issues. Roofing systems get inspected after any storm event above a defined intensity threshold.

The cost difference between a scheduled water heater replacement and an emergency water heater failure with attendant unit damage and temporary accommodation costs runs about 3.8x. For this portfolio, shifting 60 percent of water heater replacements from reactive to scheduled over 14 months avoided an estimated $19,000 in emergency premium billing and unit damage costs.

Vendor batching was the other half of Phase Two. Instead of dispatching on a per-ticket basis, maintenance coordinators now review all open and upcoming work at each property weekly and group vendor visits by trade. A single HVAC technician visit handles four or five units rather than one. Travel time gets charged once. The technician is already on-site and familiar with the building systems. Per-unit cost on grouped visits runs 22 to 31 percent lower than on single-issue dispatches.

Phase Three: The Feedback Loop

The piece that makes this durable rather than a one-time fix is closing the feedback loop after each visit. When work is completed, the unit record gets updated with what was found, what was done, and what the technician flagged as likely future work. That flag goes into a scheduled review queue, not into a forgotten email thread.

A technician noting that a garbage disposal is showing early bearing wear adds a 90-day review item to that unit's schedule. Nine times in ten, a $220 replacement gets scheduled before the disposal fails and causes a tenant complaint. The tenth time, the bearing holds longer than expected and you've wasted a 15-minute inspection. That's an acceptable miss rate.

What the Numbers Look Like at 14 Months

By month 14, the 200-unit portfolio had shifted its maintenance cost breakdown significantly. Emergency work as a share of total maintenance spend dropped from 34 percent to 18 percent. Vendor grouping efficiency meant cost-per-visit decreased an average of 26 percent. Twelve high-frequency units had been addressed at the root cause level and were no longer driving outsized ticket volume.

Total maintenance spend: down from $340,000 to $248,000 annually. Tenant satisfaction with maintenance response: up 14 points on internal surveys, largely driven by faster resolution times on non-emergency items because coordinators weren't constantly triaging emergencies.

The investment to get there: about $12,000 in system setup and staff time for the first 90 days of history-building, plus the $31,000 in targeted preventive work on the twelve problem units. Total outlay of roughly $43,000 against an annual saving of $92,000 and continuing.

What This Requires

The method works. The question is whether your current maintenance workflow can generate the unit-level history that makes predictive scheduling possible. If your tickets live in email inboxes and your vendor calls are logged in a spreadsheet someone updates when they remember, you're starting from zero on the data side.

That's not disqualifying — it just means the first 90 days are about building the record, not optimizing the schedule. Every portfolio has a predictive scheduling opportunity in it somewhere. Finding yours requires knowing what your units have cost you over time, not just what they cost last month.

Get Full Maintenance History Across Every Unit

NestView logs every maintenance event per unit and surfaces scheduling patterns that reduce reactive costs. See what your portfolio's history looks like in one place.

Book a Demo