Before Approving the Replacement, Can You Find the Warranty?
A failed water heater puts warranty records to the test. Before approving the estimate, property managers need to know what is covered and what the property will still pay.
OperationsSector Playbook
Jesse Wright explains who owns follow-up after an incomplete repair, when residents should hear from the team, and how to keep delayed work orders from falling through the cracks.
So what: Name a follow-up owner, separate visit completion from resident resolution, and give every delayed work order a waiting reason and next-touch date.

Most property teams are good at opening a work order.
A resident reports a leak. Someone creates the ticket. A tech is assigned. Parts are ordered if needed. The calendar shows a visit. That first loop is familiar, and most operators have a system for it.
Where portfolios quietly lose trust is the second loop: the visit happened, the resident still has a problem, and nobody is sure who owns the next message.
I’ve supported property-management teams that hire and manage ops assistants around work orders, resident follow-up, and owner updates. The pattern is consistent. First visits get attention. Incomplete repairs get polite silence until the resident calls again — or leaves a review.
This piece covers that second loop: who owns follow-up when a repair isn’t resolved on the first visit, when residents should hear from you, how delayed tickets stop falling through the cracks, a sample communication cadence, and a checklist you can adapt. It stays practical and vendor-neutral on purpose.
A tech can correctly mark a visit complete and still leave the resident with an open problem.
Common cases:
• Temporary fix while a part is on order
• Diagnosis only; a specialist return is required
• Access issue; the unit wasn’t ready
• Scope grew mid-visit (mold behind the drywall, electrical behind the leak)
• Resident wasn’t home for the second half of a two-part job
If your system treats “visit complete” as “resident issue closed,” follow-up becomes optional. Optional follow-up is how tickets age without anyone feeling responsible.
Treat resident-resolved as a different status from visit complete. The first visit can be successful operations work and still leave an open resident promise.
A simple test: pull ten recently “completed” tickets and ask whether the original issue is fully fixed. The share that say no is your real incomplete-first-visit rate.
“The maintenance team” is not an owner. Neither is “the property manager, somehow.”
In portfolios that keep delayed work orders under control, one seat clearly owns the communication and chase after an incomplete first visit. That person may not swing the hammer. They own:
• Confirming what the tech found and what remains open
• Setting the next resident-facing update
• Tracking parts, vendor ETAs, and re-access windows
• Escalating when a ticket ages past the team’s own SLA
• Closing the loop with the resident when the issue is truly resolved
On smaller sites that seat is often the property manager or assistant manager. On larger or multi-site portfolios it is often a property-management assistant or ops coordinator whose day is built around queues, not tours.
Write the ownership rule in one sentence:
After any work order that is not resident-resolved at first visit, [Named role] owns the next resident update within [X hours] and owns chase until resolution or formal escalation.
If two people think they own it, nobody owns it. If nobody is named, the resident becomes the project manager.
Also name a backup for days off so silence never becomes the default.
Residents do not need a novel. They need a predictable rhythm.
A useful default after an incomplete first visit:
| Moment | Who reaches out | What the resident should learn |
|---|---|---|
| Same day as the incomplete visit (within 2–4 business hours) | Follow-up owner | We know it isn’t fully fixed; here’s what happened in plain language; here’s the next step |
| When a part / vendor / specialist is booked | Follow-up owner | Date or date range for the return visit; what access is needed |
| If the date slips | Follow-up owner | New timing before the missed window, not after |
| Day before a scheduled return (or morning-of for same-day trades) | Follow-up owner or monitored reminder | Confirm access window; who to call if plans change |
| After the resolving visit | Follow-up owner | Confirm the issue is closed from the resident’s point of view; invite a same-day “still broken?” reply |
Two principles matter more than the exact hours:
No silent gaps longer than your published promise. If you say “we’ll update you within one business day,” surface tickets that breach that promise.
Bad news early beats silence. “The valve is on backorder through Thursday” is frustrating. Hearing nothing until Friday is how you get a one-star review about a valve.
Use SMS or the resident portal for routine updates; reserve calls for access problems or frustrated residents. Emergency life-safety issues stay on your emergency path.
Delayed tickets rarely disappear because someone is careless. They disappear because the workflow has holes:
• Statuses that hide waiting (parts, vendor, resident access) inside a generic “in progress”
• No age report for “visit done, resident not resolved”
• Follow-up notes trapped in a tech’s phone instead of the work-order record
• Owner/PM updates that skip the resident channel
• Handoffs between shifts or properties with no named receiver
A practical anti-crack design:
Add a visible waiting reason. Parts / vendor / access / scope change / resident reschedule.
Run a daily “open after first visit” list. Sorted by age. Owned by the follow-up seat. Fifteen focused minutes beats monthly archaeology.
Require a next-touch date on every delayed ticket. No next-touch date means the ticket is unmanaged.
Escalate by age, not by volume of resident anger. Example ladder: day 3 manager review, day 7 regional/owner visibility, day 14 formal exception note. Adjust the numbers to your asset class; keep the ladder.
Separate resident communication from vendor chasing. One person can do both, but the checklist should show both happened.
When I see teams recover a messy queue, they almost always start with the age-sorted list and the named owner — not with a new software module.
Use this for non-emergency work orders that remain open after the first visit.
Day 0 — incomplete first visit
• Tech notes: what was done, what remains, parts/vendor needed, access notes
• Follow-up owner: same-day resident message with next step
• Ticket fields: waiting reason + next-touch date
Day 1
• Confirm parts ordered or vendor scheduled
• If no ETA yet, tell the resident when they will hear next
ETA known
• Send the return window and access needs
• Update the next-touch date
If ETA slips
• Notify the resident before the old window passes
• Reset next-touch
24 hours before return visit
• Access reminder
• Internal check: part on site / vendor confirmed
Resolving visit complete
• Ask: “Does this fully resolve what you reported?”
• Only then mark resident-resolved
If the resident says no
• Re-open clearly; do not bury under the old “complete” history
• Restart ownership rules immediately
Keep language human. “Ticket #45821 status updated” is not communication. “We replaced the supply line today; we’re waiting on the shutoff valve and will update you by Wednesday” is.
Copy this into your ops doc. Strike what doesn’t fit; keep the ownership lines.
After every first visit
[ ] Visit result coded: resolved / not resolved
[ ] If not resolved: waiting reason coded
[ ] Tech notes include what the resident should expect next
[ ] Follow-up owner assigned by name/role
Same day
[ ] Resident contacted with plain-language status
[ ] Next-touch date entered
[ ] Parts/vendor action started or explicitly queued
While open
[ ] Daily review of “open after first visit” aging list
[ ] Resident update sent whenever the plan changes
[ ] Escalation ladder checked against ticket age
At resolution
[ ] Resident confirms the issue is actually fixed
[ ] Ticket closed as resident-resolved (not only visit-complete)
[ ] Pattern note if this failure mode is repeating (same unit, same vendor, same part)
Weekly ops hygiene
[ ] Count of tickets open >7 days after first visit
[ ] Top waiting reasons
[ ] Any ticket with no next-touch date (should be zero)
Follow-up is not an apology tour. It is project management with manners.
Residents forgive delays they understand. They do not forgive being ignored. Owners forgive a parts delay with a clear ETA. They do not forgive learning about a two-week open work order from a resident email.
If your team is thin, shrink the cadence before you abandon it. A short, reliable update rhythm beats an ambitious policy nobody runs.
First visits get the glory. Second loops protect the reputation.
Name the follow-up owner. Separate “visit complete” from “resident-resolved.” Give every delayed ticket a waiting reason and a next-touch date. Tell residents what happens next before they have to ask. Review the aging list every day you operate.
None of that requires a new platform. It requires a rule people can follow on a busy Tuesday.
About the author: Jesse Wright is co-founder of Talentige, an overseas recruitment agency.
A failed water heater puts warranty records to the test. Before approving the estimate, property managers need to know what is covered and what the property will still pay.
ResiHome will manage Southern Waters Capital’s new Florida rental community, with a public grand opening scheduled for November 16.
Treplus, Greystar, United Plus and Sparrow Living show how leasing, staff training and resident participation shape active-adult property operations.