Why Most Completed Repairs Are Never Verified

Every property management system in the industry treats a closed work order as a resolved condition. None of them check. The tech finishes the repair. The ticket closes. The dashboard records a completion. The response time metric is calculated. The system moves on. No one asks: did the condition actually stay fixed? A plumbing patch that stops a leak on Tuesday may fail the following week. An HVAC repair that restores cooling may mask a compressor failure that returns under sustained load. A pest treatment that reduces activity temporarily may not have sealed the entry point. These are false completions. The system says the work is done. The building says otherwise. The gap between a completed repair and a verified repair is where repeat failures originate. Most recurrences happen within a predictable 90-day window. If the condition returns inside that window, the original repair failed. If it does not, the repair likely held. Operators who never monitor this window cannot distinguish between fixes that worked and fixes that merely delayed the next complaint.

Ninety days is not arbitrary. It reflects the operational reality of how apartment conditions recur. Many maintenance conditions are weather-dependent. A roof repair completed in a dry period will not be tested until the next sustained rain. A plumbing repair on a pipe that leaks under thermal expansion may not fail again until the next temperature swing. A pest treatment may appear effective until the next seasonal activity cycle. Ninety days provides enough time for most conditions to encounter the circumstances that test whether the repair holds. It is long enough to capture one full weather cycle in most climates and one full use cycle for most building systems. It is also short enough to be actionable. If a condition recurs at 45 days, the operator can escalate to a different repair approach while the original work is still recent. If the follow-up window is six months, the connection between the original repair and the recurrence is harder to establish, and the condition has had more time to cause secondary damage.

Without a post-repair follow-up mechanism, operators fall into a pattern that is invisible in their own data but obvious in retrospect. The same unit generates the same type of work order every few months. Each time, the repair is completed. Each time, the ticket is closed. Each time, the work order count and response time metrics look normal. But the repeat work orders are not normal. They are evidence that the repair approach is not working. The condition is recurring because the root cause was never addressed. This cycle can continue for months or years. The unit accumulates a long history of completed work orders for the same condition. The operator's system shows consistent task completion. It does not show that the same problem was repaired four times in 18 months without permanent resolution. When this pattern eventually produces a resident complaint, a public review, or a legal claim, the documented history of repeated repairs becomes evidence against the operator. It shows awareness and engagement with the condition paired with a failure to recognize that the approach was not working. For more on how repeat patterns build liability, see why repeat complaints matter more than single incidents.

A 90-day follow-up does not require checking every completed work order. It requires checking the work orders most likely to recur. Start with the categories that have the highest recurrence rates: plumbing, HVAC, pest control, water intrusion, and electrical. For each completed work order in these categories, set a follow-up flag at 90 days. At the 90-day mark, the system checks one question: has the same unit generated another work order in the same category since the original repair? If yes, the repair did not hold. The follow-up should trigger an escalated response: a different repair approach, a vendor change, or a root cause investigation. If no recurrence is detected at 90 days, the repair can be considered effective. The follow-up flag clears. This is not a manual process. Most property management platforms support automated follow-up scheduling or can be configured to flag units with repeat work orders in the same category. The data already exists in the system. The follow-up adds the query that turns completed repairs into confirmed repairs. For more on how to track conditions over time, see how maintenance history reveals hidden operational risk.

The 90-day window is also the most useful tool for evaluating vendor effectiveness. When an outside vendor performs a repair and the condition recurs within 90 days, the vendor's work did not resolve the problem. This is not a matter of opinion. It is a data point. Over time, 90-day recurrence rates by vendor and by condition category produce a clear picture of which vendors deliver lasting repairs and which deliver temporary fixes. This data gives operators an evidence-based foundation for vendor conversations, contract renegotiations, or vendor changes. Without the 90-day check, vendor effectiveness is evaluated subjectively. The vendor showed up. They completed the work. They invoiced. The operator paid. Whether the repair actually worked is not part of the evaluation. For more on how vendor performance affects operator liability, see how vendor and contractor failures create operator liability.