Guide
How to triage post-close warranty issues
Decide what needs attention first, what information is missing, and who acts next. Practical examples for incomplete, urgent, and reopened requests.
By LuceraUpdated First published
On this page
Warranty triage means deciding what needs attention first, what information is missing, and who should act next. It does not mean making a final diagnosis or coverage decision from a short message.
For each report, record the symptom in the homeowner’s words, screen for immediate risk, identify the missing facts, and assign the next action. Keep urgency, technical assessment, and coverage separate. That prevents a routine-looking request from sitting unnoticed and prevents an incomplete report from becoming a premature denial.
Make the first review answer five questions
- What is being reported? Capture the exact location and symptom. “Water appears below the upstairs window during rain” is more useful than “window issue.”
- Is there a reported immediate hazard or active damage? If yes or uncertain, use the appropriate escalation path rather than leaving it in the ordinary scheduling queue.
- What changed, and when? Ask when it began, whether it is ongoing, and whether the same symptom was previously repaired.
- What is needed for the next decision? This might be one safe photo, a prior repair note, the applicable warranty document, or a qualified assessment.
- Who acts next, and by when? Assign a named coordinator, next actor, and update commitment.
Let homeowners report symptoms without choosing the correct trade or coverage category. Those are routing decisions your team should help make.
Set priority from the situation, not the category name
Scroll the table horizontally to see all columns.
| Reported situation | Coordination response | Avoid |
|---|---|---|
| Possible immediate danger or rapidly worsening damage | Direct the homeowner to appropriate emergency help or a qualified professional. Notify the builder’s escalation contact promptly. | Waiting for an ordinary warranty appointment or promising emergency coverage your team does not provide. |
| Loss of use or a changing condition without a reported immediate hazard | Clarify impact and timing; obtain an appropriate assessment and a clear next update. | Assuming a category such as HVAC or plumbing always has the same urgency. |
| Stable cosmetic or adjustment request | Gather usable evidence, check the relevant documents, and coordinate the approved next step. | Calling it non-covered solely because it appears cosmetic. |
| Repeat or disputed issue | Link prior work and decisions, identify what remains unresolved, and route a focused review. | Treating the prior closed status as evidence that nothing is wrong. |
Temperature, occupancy, location, vulnerability, and whether a condition is actively changing can alter the response needed. This framework does not replace technical judgment. Do not ask a homeowner to open electrical equipment, enter an unsafe area, or perform a repair to prove that a problem exists.
Set internal response targets with the team that can actually respond. Clearly communicate routine hours and the urgent-contact path. A portal being available at night does not mean a qualified responder is monitoring it.
Four reports and the next useful action
“There is a stain on the ceiling.”
Ask whether water is currently appearing, whether the area is changing, and where it is located. If the report suggests active damage or danger, escalate accordingly. A dry photograph alone does not establish the source, the trade responsible, or coverage. Request an appropriate assessment when the facts do not support a repair-ready scope.
“The cabinet door still does not close.”
Check whether this is the first report or a return of the same symptom after a visit. Ask which door and what happens when it closes. A wider photo or short video may help if safe, but the homeowner does not need to diagnose a hinge. Review the prior trade note before sending the same instruction again.
“My air conditioning is not working.”
Clarify the reported loss of function and immediate impact, then route to the appropriate qualified contact. Do not assume the same priority in every home or season. Avoid giving improvised technical troubleshooting or safety advice. Record what the homeowner reports and what contact or assessment was arranged.
“This is not what I expected at closing.”
Separate an unresolved handover item, a requested change, and a reported defect. Retrieve the relevant handover notes and ask the builder to review the specific concern. Listen for the actual requested outcome; a vague disagreement is difficult to route, but it is still a report that deserves an owner and response.
Write a triage record another person can use
Keep observations, assumptions, and decisions visibly separate. “Homeowner reports” and “trade observed” identify evidence sources. “Builder approved” identifies an actual decision. A category assigned by software is neither a field finding nor an authorization.
Ask for the smallest useful piece of missing information
Explain why you need a detail and what it will unlock. Avoid repeatedly requesting material that is already attached or asking the homeowner to restart the report because it arrived through the wrong channel.
If the homeowner cannot supply the detail, decide whether a phone conversation or qualified visit is the appropriate alternative. Do not leave the status at “awaiting information” without a follow-up owner and date.
Hand off a decision-ready brief
The reviewer should receive the symptom, priority reason, relevant evidence and history, applicable records, and one clear question. Once the decision is made, record the approved scope and authority before scheduling the work.
Review a small sample of triaged requests each week. Look for wrong routing, repeated information requests, changing urgency, and visits that happened before the scope was clear. Those are more useful improvement signals than the number of categories your system can assign.
Use the complete warranty process for the steps before and after triage, and the tracking guide to keep the next action visible.
If gathering information and routing decisions repeatedly fall between people, use the managed service versus software guide to compare ways to support your team or hand off routine follow-up.