Worked guideFor care teamsAny market
The defect came back: how to record a repeat repair
A homeowner reports a defect your team had already recorded as repaired. This guide is for residential developers’ customer care teams handling aftercare after handover: how to keep the earlier history, record the new observation and decide what happens next.
Short answer
When a repaired defect is reported again, keep the original report, the work the contractor reported and your team’s review exactly as they were recorded. Add the homeowner’s new observation as a dated entry, then record the next decision: who assesses it, what they need and when the homeowner will hear from you. A similar symptom is a reason to assess, not proof that the first repair failed, so record the cause as unknown until someone has checked. Treat this as a working method, not a prescribed procedure.
Establish what the homeowner has noticed this time
Start with the new observation, in the homeowner’s words, before you look for a cause. Someone reporting a defect again has usually explained it once already, so ask only for what the earlier record does not tell you.
- When did they notice it again, and is it constant or occasional?
- Where exactly does it appear: the same spot as before, or nearby?
- What has changed since the repair: the symptom, the time of day, anything done in the home?
- What evidence can they send now: photos, a short video, the day it started?
The same observation or a separate issue?
An earlier review records what your team checked and decided at the time. A new observation records what the homeowner has noticed since. Keep them as separate entries: the new observation does not change what the review found, and the review does not settle what the homeowner sees now.
| What you have | What it may look like | How to record it |
|---|---|---|
| Possible recurrence | The same symptom in the same place as the earlier repair | A new entry on the original case, with the connection marked as uncertain until assessed |
| Newly noticed damage | Something near the repaired area that nobody recorded before, such as a scratch | Its own record, with a note that it was reported alongside the original case |
| Unrelated report | A different item in another part of the home | A separate case with its own reference |
When you are not sure which row applies, say so in the record. “Connection to earlier repair: uncertain, assessment requested” helps the next person more than a confident guess.
Preserve the earlier repair and review
Keep every part of the first repair as it was recorded, even if it now looks incomplete. The next assessor needs to know what was asked for, what was reported and what your team accepted.
- The original report, its date and the homeowner’s photos
- The work requested and the contractor or team it was assigned to
- Attendance: when the visit took place and who provided access
- The work the contractor reported, with their photos or notes
- Your team’s review: who reviewed it, when, what they checked and the outcome
Keeping the history is not the same as leaving the case status unchanged. The earlier entries stay as written, while the current status shows that the case needs another assessment. If your register has one status column, update it and add the reason to the history instead of overwriting the old review. The aftercare process guide covers the normal route to a review; for what to ask before the next closure, see what evidence a contractor should provide.
A repeat report can be more urgent than the first one. A door that no longer locks or water that has spread needs a fresh urgency review on the day the report arrives, before anyone reads the history.
Record each attempt separately
A repair-attempt record is one entry for each attempt to resolve a reported defect: what was requested, what was reported as done, what evidence came back and what the reviewing team concluded. It sits alongside the case record, not in place of it.
Use two references. The case reference stays the same for the whole history of one defect in one home. The attempt reference adds a suffix for each attempt, so EX-R01-A1 and EX-R01-A2 belong to the same case. Give photos, contractor notes and messages the attempt reference too.
A visit at which no repair took place is a visit outcome, not a failed attempt. If the contractor could not get in or needed a part, record that against the visit and keep the attempt open. What to record when a repair visit fails covers those outcomes.
Repair-attempt log
Use one row per attempt and keep the log beside your defect register: the register holds one row for each case, this log one row for each attempt. In a spreadsheet, freeze the first four columns so the references stay visible. Fill in the review columns only once your team has checked the work, and write “not yet” instead of leaving a gap.
| Case reference | Home and location | Original report date | Attempt reference | Report date for this attempt | Reason for this attempt | Connection to earlier work | Work requested | Work reported (who, when) | Evidence references | Review (who, when, what was checked, limits) | Outcome and outstanding points | Next action and responsible person | Target date, if set | Visit, if agreed | Next update to homeowner |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| EX-R01 | Example home 12, living room balcony door | Day 1 | EX-R01-A1 | Day 1 | Original report: door catches when closing | Not applicable (first attempt) | Assess the door and adjust it so it closes freely | Door contractor, day 9: door adjusted | EX-R01-A1 photos 1–2 (homeowner), photo 3 (contractor) | Care team, day 11: contractor photo reviewed; homeowner confirmed by phone. Limits: no on-site inspection; contractor note does not say what was adjusted | Case closed; nothing outstanding recorded at the time | None | Day 10 (set on day 2) | Day 9 (contractor attended) | None after closure |
| EX-R01 | Example home 12, living room balcony door | Day 1 | EX-R01-A2 | Day 52 | Homeowner says the door catches again near the top, mostly in the morning | Uncertain: same symptom and place, cause not assessed | Assess why the door catches before any further work | Not yet | EX-R01-A2 video 1 (homeowner) | Not yet | Open; question to contractor: what was adjusted on day 9? | Door contractor assesses; care team coordinator arranges | Not set until assessed | Day 60 | Day 61, after the visit |
| EX-R02 | Example home 12, trim beside living room balcony door | Day 52 | EX-R02-A1 | Day 52 | Homeowner mentions a scratch on the trim while reporting EX-R01 again | Not confirmed: reported alongside EX-R01, recorded separately | Review the photo and decide whether the trim needs work | Not yet | EX-R02-A1 photo 1 (requested from homeowner) | Not yet | Open; photo requested | Care team reviews the photo | Not set | Not agreed | Day 61, with the EX-R01 update |
Scroll sideways to see every column.
The rows follow the fictional example above. Say who made each conclusion, and write “uncertain” wherever a cause or connection has not been assessed.
Work through a fictional repeat repair
The example follows one balcony door through a first attempt, a later report and the next assessment. It stops at the assessment, because nobody yet knows why the door catches again.
Fictional example
Balcony door catches when closing
EX-R01Example development · Example home 12 · Living room balcony door
Attempt 1
- Day 1The homeowner reports that the balcony door catches when closing and sends two photos.
- Day 2The care team reviews the report, sets a deadline and assigns the door contractor.
- Day 9The contractor reports the door adjusted and sends one photo of it closed. The note does not say what was adjusted.
- Day 11The care team reviews the photo, and the homeowner confirms by phone that the door closes freely. The team records its review and closes the case.
Later observation
- Day 52The homeowner says the door catches again near the top, mostly in the morning, and sends a short video. They also mention a scratch on the trim beside the door.
- Day 52The care team adds the report to EX-R01 and marks its connection to attempt 1 as uncertain. The scratch becomes EX-R02, a separate record, and a photo is requested.
Attempt 2
- Day 52The care team reviews urgency: the door still closes and locks, so the case keeps its normal priority. Its status changes to awaiting assessment.
- Day 53An assessment is requested from the door contractor, with a question: what was adjusted on day 9? No answer yet.
- Day 55A visit is agreed for day 60. The homeowner is told the next update will follow on day 61.
Fictional example. The home, dates and details illustrate the method; they are not a customer case.
Three details matter. The first review stays on record with its limit: it relied on a photo and a phone call, not an inspection. The scratch has its own reference, because nobody has shown that it is linked to the door. And the open question to the contractor is written down, so whoever attends on day 60 knows what the first record lacks.
Decide the next action and update the homeowner
End every repeat report with a decision that someone can act on. Record four things before you move on:
- 1Who arranges the assessment, by name or role, and who will carry it out.
- 2What information they need: the earlier attempt record, the new evidence and any open questions.
- 3The visit, if one has been agreed, kept separate from any deadline for the work.
- 4The next update to the homeowner: a date when they will hear from you, even if the repair date is not yet known.
If your system cannot reopen a closed case, leave the original record untouched and create a follow-up record that names it, for example “Follow-up to EX-R01”. Put each reference in the other record so either one leads to the other. Aftercare software such as Toveta keeps this history with the case; in a spreadsheet, the shared reference does the same job.
Keep reporting dates and warranty decisions separate
Your repair-attempt record tracks the work; it does not decide warranty coverage or count as formal notice. Where a warranty scheme applies, its own procedure and dates still govern the claim.
Two Canadian examples show why this matters. In Ontario, Tarion’s conciliation guidance asks homeowners to provide supporting information if a builder’s repairs are considered inadequate. In British Columbia, BC Housing’s warranty-claims guidance says that repairs offered by a builder without written notice to the warranty provider do not count as a formal claim, and it describes a separate repair warranty for work completed under the policy.
Record the date the homeowner reported the issue again as its own field, and do not assume that another attempt changes any warranty period. Check the rules that apply to your homes with your adviser or the relevant warranty provider.
Where this applies
Customer care, warranty and aftercare teams at residential developers and housebuilders who follow defects after handover. The method does not depend on a tool and suits any market. Warranty coverage, notice requirements and deadlines differ by country and scheme; the Ontario and British Columbia examples are local context only. Check your contractual and statutory obligations with your adviser.
Sources
- Tarion. Conciliation process, assessment & resolution. Ontario, Canada; process context only, checked 3 November 2026
- BC Housing. Home Warranty Insurance Claims. British Columbia, Canada; coverage is specific to that province, checked 3 November 2026
Spotted an error or an outdated source? Email info@wisemonks.com and we will correct the page.
