How to Follow Up on Rental Repairs

Follow-up on a rental repair means confirming the vendor actually did the work, verifying that the tenant's original problem is genuinely gone, checking for damage the repair itself did not address, and saving the invoice, photos, and warranty terms before the request is closed. A work order marked complete is not proof that the problem is solved.

A Closed Work Order Is Not a Solved Problem

A maintenance request can look finished long before the tenant's actual problem is solved. A vendor submits an invoice, the landlord pays it, and the tenant stops sending messages. None of those events confirm that the repair worked.

Consider a tenant who reports a washing machine leaking onto the laundry closet floor. A plumber comes out, replaces the supply line, and the invoice says the job is done. That invoice proves a vendor visited and charged for work. It does not prove the leak has actually stopped, that the closet floor was not damaged underneath the machine, or that the same fitting will not fail again in a few months.

Follow-up closes that gap: confirming the visit happened, recording what the vendor actually found and did, verifying with the tenant that the original problem is gone, checking for damage the repair itself did not fix, and keeping the invoice, photos, and warranty terms where they can be found again. None of this requires a formal system. For a landlord with one or two rentals, a short note after each step is usually enough. It is the operational version of resolving a problem instead of just marking the repair complete.

Confirm the Appointment Actually Happened

A scheduled repair visit is not the same as a completed one. A technician can be delayed, a tenant can be unavailable when the vendor arrives, or access instructions can go missing somewhere between a phone call and a truck pulling into the driveway. Without a quick check, the landlord, the tenant, and the vendor can each assume someone else is handling the next step.

Worth recording after every appointment: whether the vendor arrived, whether they actually got into the property, whether the visit was completed, canceled, or needs to be rescheduled, and who is responsible for setting up the next date if one is needed. Access itself is usually simple. A lockbox code, a spare key left with a neighbor, or a scheduled time when the tenant is home covers most cases, and whatever method is used should match both the access and notice terms in the lease and any applicable local rules on entry.

A visit logged as done when the vendor never actually got inside the unit is worse than no record at all. It tells a future reader that something happened when nothing did.

A Vague Repair Note Helps No One Later

"Fixed the leak" is a common note and a nearly useless one. It does not say what was wrong, what the vendor actually did about it, or whether the fix was expected to hold.

A more useful note for the washing machine example might read: "Plumber found the rubber supply line had cracked at the connector. Replaced both hot and cold supply lines and the shutoff valves, ran the machine for a full cycle, no leaking observed. Advised replacing the lines again if the washer is ever moved." That single note tells a future reader what failed, what was replaced, how it was tested, and what might cause it to fail again. A note that just says "fixed leak, $180" tells them almost nothing.

The record does not need technical precision. It needs enough detail that the landlord, the tenant, or a different vendor could understand what happened without a phone call. Good notes also reveal patterns. If the same appliance, drain, or panel keeps coming up in the repair history, that history is what eventually makes replacement look like the more sensible choice than another repair.

A Temporary Fix Needs Its Own Status, Not the Word "Done"

Some repairs stop the immediate problem without correcting its cause. A cracked supply line might be clamped temporarily while the right part is ordered. A pest treatment might knock down an active problem without addressing the gap or crack that let pests in to begin with. A roof leak might be patched from the inside while the actual roofing repair waits for dry weather.

None of that is a bad decision. Stopping the damage from getting worse is often the right first move. The mistake is recording it the same way a finished repair gets recorded. A request should show whether the property is temporarily stabilized, waiting on a part, waiting on further diagnosis, scheduled for a follow-up visit, or actually finished, not simply open or closed.

Some repairs cannot be confirmed the same day no matter how thorough the visit was. A roof patch needs to be checked after the next real rain, not the afternoon it was applied. A pest treatment needs a week or two before anyone can tell whether the activity actually stopped. In these situations, marking the request "monitoring" or "awaiting confirmation" is more accurate than closing it, and it is worth deciding upfront who is watching for a recurrence and when the landlord will check back in if nobody has reported one.

Specific Questions Get a Better Answer Than "Is Everything Okay?"

The tenant is usually the best source for whether a problem is actually gone, since they are the one using the fixture, appliance, or system every day. A vague check-in gets a vague answer. A specific one is more likely to catch a problem that is still there.

A short message after the washing machine repair might ask:

"The plumber replaced the supply lines on the washing machine yesterday. Has there been any more leaking or dripping under the machine since then, and is the closet floor still dry?"

That question is easier to answer than "how did the repair go," and it is more likely to surface a problem the tenant might not think to mention on their own. Useful follow-up questions generally cover whether the original symptom is still happening, whether the vendor left anything unfinished, and whether there is any remaining water, odor, staining, or debris.

A tenant's confirmation is not a technical inspection. They are reporting what they can see and feel in their own home, not certifying the quality of the vendor's work. That is still valuable information. It is often the only way to know whether a repair that looked complete on the invoice actually held.

The Repair May Not Fix Damage It Already Caused

Correcting the source of a problem does not always correct what the problem already caused. Stopping the washing machine leak does not dry out flooring that has been damp for a week, and patching a roof does not repair the ceiling stain the leak left behind.

Worth checking after any repair involving water, in particular: whether flooring, baseboards, or cabinetry underneath or around the repair are still damp, whether there is any visible staining or warping, and whether the affected area has had enough time to dry. Extensive, ongoing, or concealed moisture, especially inside a wall or under flooring, is a case where bringing in a specialist for a qualified assessment is more reliable than guessing at it.

It is often more useful to treat the original repair and any resulting cleanup or restoration as two connected but separate tasks, even when two different vendors handle them, rather than folding both into one work order. That keeps the scope of each job clear while the shared history still shows how they relate.

Reopen the Request Instead of Starting a New One

A repair should be reopened, not closed, when the original problem comes back, the fix did not hold, or the vendor left part of the job unfinished. Reopening the same request keeps the original report, the appointment history, the vendor's notes, and the invoice together in one place, instead of scattering the same problem across two or three unconnected records.

A repair that reveals a different problem is a different situation. If the plumber who replaced the washing machine's supply lines also notices that the dryer vent behind the unit is crushed and no longer venting properly, that is a new issue worth its own request, even though it surfaced during the same visit.

Problems that keep coming back deserve a closer look before another vendor gets sent out. A garbage disposal that has jammed three times in four months, for instance, is not necessarily a new problem each time. Checking the repair history first, whether the same vendor handled it before, whether a permanent fix was ever recommended and postponed, whether the unit is still under warranty, can save the cost of a fourth visit that treats the symptom instead of the cause. A problem that affects safety or an essential service, or one that has already failed more than once, generally deserves that closer look sooner rather than later.

Save the Invoice, Photos, and Warranty Terms Before Closing the File

Before a request is closed, it is worth confirming that a few things are actually saved, not just remembered. Useful records for the washing machine repair would include the original report from the tenant, photos of the damage before the work started, the plumber's invoice, a photo of the completed connection, and the warranty terms for the parts and labor.

Warranty information is easy to lose once it is buried in an email or a paper invoice. Worth recording separately: how long the labor is covered, how long any replaced part is covered, and who to call if the same problem happens again within that window. Before paying for another visit on the same item, it is worth checking whether the earlier work is still covered rather than assuming it is not.

The invoice itself is worth a second look before the request closes: whether it matches the unit and the work that was actually authorized, whether an unfinished item is called out rather than buried in the total, and whether it has already been logged as paid. This does not need to slow down a legitimate payment. It only needs to happen before the file is treated as closed, so the financial record and the repair record describe the same job.

Keeping this record does not need to be complicated. Keep it findable for as long as it stays operationally useful, which for a repair record usually means at least the rest of the tenancy. If a security deposit deduction is ever considered for related damage, records like these are what support it, but deposit deduction rules and any applicable retention requirements vary by state and locality, so confirm what applies before relying on a repair record for that purpose.

Tell the Tenant What Happens Next, Even Without a Final Answer

When a repair is not fully resolved, the tenant should not have to ask twice whether anyone is still working on it. A short update covering what happened during the visit, what is still unresolved, and when the tenant should expect to hear something next keeps an open repair from feeling abandoned, even when there is no final date yet to give.

This is a narrower version of a standard that applies to every open request, not just repairs still being verified: acknowledge quickly, investigate carefully, and provide the next update before the tenant has to ask. What follow-up adds is the part that comes after the vendor leaves: making sure the update reflects what was actually confirmed, not just what was scheduled.

Close the Request Only After the Outcome Is Actually Verified

A repair request does not need to stay open forever, and closing one does not require absolute certainty that the problem can never return. It requires reasonable verification: the vendor showed up and did the work, the work is recorded well enough to be useful later, the tenant confirmed the original problem is gone, any secondary damage has been identified, and the invoice, photos, and warranty terms are saved somewhere they can be found again.

A closing note can be short. For the washing machine example: "Plumber replaced both supply lines and shutoff valves on March 4. Tenant confirmed on March 6 that no further leaking occurred. Closet flooring was dry, no additional damage found. Invoice and one-year parts and labor warranty saved to the file."

That is not a lot of extra work for most repairs. It is the difference between a work order that looks finished and a problem that is actually resolved, and it is one of the ordinary, repeatable habits that let a landlord earn a tenant's trust over the course of a tenancy, one closed repair at a time.

Updated July 2026