Worked guideFor care teamsAny market
Duplicate report or recurring defect? How to keep the records
When several homeowners describe the same symptom after handover, the care team has to decide which reports belong to one case and which need their own. This guide works through six reports from five homes in a fictional development.
Short answer
A duplicate submission is the same observation sent twice, so it becomes one case with both sources kept. A later recurrence is a new observation in the same home after earlier work. Similar observations in separate homes stay separate cases, each with its own history, and can be compared in a restricted review matrix. A possible relationship between homes is something to investigate. It does not establish a shared cause until a qualified reviewer has assessed the evidence.
Classify the relationship between the reports
Start by deciding how a new report relates to the ones you already hold. Four relationships cover most cases, and each tells you what stays together and what needs its own history.
| Relationship | What it looks like | How to record it |
|---|---|---|
| Same report sent twice | One home, one observation, sent twice. Same location, same photo or date. | One case. Keep both submissions as sources, so nobody thinks the second message was ignored. |
| Later observation in one home | The same home reports the symptom again after earlier work. | A new entry linked to the earlier case, so the earlier work stays visible. See how to record a repeat repair. |
| Similar observations in separate homes | Different homes describe a similar symptom on a similar component. | Separate cases, one per home. Link them in a review matrix if the similarity is worth checking. |
| Unrelated issues with similar wording | Reports share a category or a word, such as “cupboard”, but describe different things. | Separate cases with no link. A shared category is not evidence of a shared problem. |
The rule underneath the table: merge only when you are confident it is one observation in one home. Everything else keeps its own case in the defect register, because each homeowner needs their own record of what was reported, agreed and done.
Work through the five-home example
The example has six incoming reports from five homes, all about kitchen cupboards. Read the reports first, then the classification, and check whether you would reach the same decisions from the evidence supplied.
Fictional example
Six cupboard reports from five homes
EX-P05Example development · Blocks A, B and C · Kitchens
Reports received
- 6 OctA12, portal: the upper cupboard door by the hob hangs lower at one side. Photo attached.
- 7 OctA12, email: the same owner sends the same description and photo.
- 9 OctA14, portal: an upper cupboard door has dropped and rubs the next door. Photo attached.
- 12 OctB07, portal: a cupboard door is crooked again. Its hinge was adjusted in August (D-2026-011).
- 13 OctB09, email: a mark on the surface of a cupboard door. Photo attached.
- 15 OctC03, phone: “a cupboard doesn’t close”. No photo, no location.
First classification
- A12Likely duplicate: the same owner sent the same description and photo on 6 and 7 October. One case, D-2026-031, with both submissions kept as sources.
- A14Separate home, separate case: D-2026-032. Similar to A12, so it goes into the review matrix.
- B07Its own case, D-2026-033, linked to D-2026-011. Similar symptom, but earlier work and a different reported installation date.
- B09D-2026-034. Same broad category, but a surface mark is not a hinge observation. Not in the review group.
- C03D-2026-035. Too little information to classify; the team asks for a photo and location.
Review question
- 17 OctThe care manager sends the quality manager a restricted matrix of the three hinge cases and asks for a qualified assessment.
- 17 OctEach owner receives their own next step. No owner sees another home’s details.
Fictional example. Homes, dates, references and reports illustrate the method. They are not research data or a customer case, and no cause has been established.
Two decisions remain uncertain. B07 might belong with A12 and A14, or its August adjustment might explain the change, so the matrix records both possibilities. C03 stays outside the group until the owner replies; a clearer first report, such as one made with the defect report template, could have helped the team judge whether it belonged in the review group. B09 is the contrast: it shared a category with the hinge reports, and that alone was no reason to group it.
Build a restricted issue matrix
An issue matrix is the care team’s working table of the cases to be reviewed together. It sits beside the register, not in place of it: each row points back to one case, and each case keeps its own history.
- Link every row to a case. Use the case reference and the internal home reference, never the owner’s name or address.
- Keep the original wording. Quote the owner’s description in the symptom column. Put a consistent component label beside it, not in its place.
- Record only attributes you actually know. If the installation date or product is unknown, write “unknown” instead of leaving the cell blank or assuming it matches.
- Write the differences down. A difference is as useful to the reviewer as a similarity.
- State the hypothesis as a hypothesis. “Possibly related to D-2026-031” is accurate; “same defect” is a conclusion nobody has reached yet.
Consistent descriptions make rows easier to compare. Some regulators publish structured defect descriptions, such as the Building Defects Library from Building Commission NSW, written for certifiers and councils in New South Wales. A list like that can help a team agree its wording, but its classifications are local, not definitions to adopt everywhere.
Similar reports matrix
Copy these columns into a new sheet beside your register, or into your existing system’s notes. Use one row per case, never one row per group of homes, and fill each cell only with what you know. The example rows follow the fictional five-home case above.
| Case reference | Home | Location and component | Report date | Observed symptom (owner’s words) | Source and evidence | Previous work | Known comparable attributes | Differences | Missing information | Relationship hypothesis | Reviewer and conclusion | Next action and person | Case status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| D-2026-031 | A12 | Kitchen, upper cupboard by the hob | 6 Oct 2026 | “The door hangs lower at one side” | Portal 6 Oct and email 7 Oct; same photo | None recorded | Block A; upper door; photo shows a gap at the door edge | None noted yet | Cupboard and hinge type | Two submissions, one case; possibly related to D-2026-032 | Awaiting quality review | Arrange inspection visit (care coordinator) | Open, visit being arranged |
| D-2026-032 | A14 | Kitchen, upper cupboard | 9 Oct 2026 | “The door has dropped and rubs the next door” | Portal; one photo | None recorded | Block A; upper door; similar gap in photo | Door rubs the neighbouring door | Cupboard and hinge type | Possibly related to D-2026-031 | Awaiting quality review | Ask owner for access dates (care coordinator) | Open, awaiting access dates |
| D-2026-033 | B07 | Kitchen, upper cupboard | 12 Oct 2026 | “The door is crooked again” | Portal; no new photo | Hinge adjusted in August (D-2026-011) | Upper door; similar symptom described | Earlier adjustment; different reported installation date | Photo; August job notes | Possibly related, or linked to the earlier work | Awaiting quality review | Contractor to bring August notes to the next visit | Open, linked to D-2026-011 |
| D-2026-034 | B09 | Kitchen, cupboard door surface | 13 Oct 2026 | “A mark on the door surface” | Email; one photo | None recorded | Same broad category only | Surface mark, not a hinge observation | None for this question | Not related to the hinge group | Not part of the review | Assess as a single case (care coordinator) | Open, under assessment |
| D-2026-035 | C03 | Kitchen, location not given | 15 Oct 2026 | “A cupboard doesn’t close” | Phone call; no photo | Unknown | Unknown | Unknown | Photo; which cupboard; when it started | Not classified yet | Not part of the review | Ask owner for a photo and location (care coordinator) | Open, waiting for information |
Scroll sideways to see every column.
Keep a short review brief on a second sheet: the cases considered, verified common observations, relevant differences, the evidence list, the question for assessment, the responsible reviewer and the next review date. Keep the matrix internal and share only limited extracts.
Prepare a question for technical review
The care team’s job is to give the reviewer a clear question and its evidence, not to diagnose the cause. Five rows can justify a closer look; they cannot explain why the doors moved.
An observation is what someone saw: a door hangs lower on one side. A cause explains why, and it needs someone qualified to assess the home, the product and the installation. Research works at a different scale. A 2024 study by Lambers and colleagues used reported defect records from new Queensland homes and a practitioner survey to examine frequent defects and their correlated causes. It can inform a quality team’s thinking, not what happened in a particular kitchen.
Observed pattern
- Three homes, A12, A14 and B07, report an upper cupboard door that has dropped or hangs unevenly.
- A12 and A14 supplied photos showing the gap at the door edge.
- All three reports arrived within one week.
What still needs checking
- B07 had a hinge adjustment in August, and its kitchen has a different reported installation date.
- Whether the three homes have the same cupboard and hinge type is unknown.
- C03 may describe a similar symptom, but there is no photo yet.
- Nobody has inspected any of the three doors since the reports arrived.
Keep each homeowner’s next step visible
A shared review moves at its own pace, while each home still needs its own next step. Track the investigation in the matrix and each home’s access, work and communication in its case.
| Case | Investigation | This home’s next step |
|---|---|---|
| D-2026-031 (A12) | In the review group | Owner told that both messages arrived and one case was opened. An inspection visit is being arranged. |
| D-2026-032 (A14) | In the review group | Owner asked for access dates for an inspection visit. |
| D-2026-033 (B07) | In the review group, earlier work noted | Contractor asked to bring the August job notes to the next visit. |
| D-2026-034 (B09) | Not included | Assessed on its own as a surface mark. |
| D-2026-035 (C03) | Not classified yet | Owner asked for a photo and the cupboard’s location. |
Tell each owner what is happening in their home. You can say the team is checking whether similar reports need a common approach, without mentioning other homes or suggesting a cause. For wording while a date is still open, see what to tell a homeowner when the repair date is unknown.
Keep the full matrix inside the care team and give each recipient a deliberately limited extract. Homeowners should not see neighbours’ names, photos, messages or access details; a contractor needs only their assigned cases. Hiding or filtering spreadsheet rows is not access control, because the other rows stay in the file. This is an operating principle, not a claim that the template meets any legal standard.
Record what the review concluded
When the reviewer answers, add the conclusion to the matrix, then carry its consequence into each case separately.
- 1Record the conclusion, who gave it, when and on what evidence. Keep it attributed, not rewritten as the care team’s own finding.
- 2Note any change of scope: a case that joins the group, one that leaves it, or a question that needs more evidence.
- 3Update each case with its own next action. A shared conclusion can change the work in several homes; each case still records its own visit, work and review.
- 4If the first grouping was wrong, keep the earlier hypothesis and add the correction and its reason beside it. A matrix that changes silently loses the reasoning the next reviewer needs.
- 5Close each case on its own basis, after the care team has reviewed the work in that home, as in the aftercare process.
Aftercare software such as Toveta keeps each home’s case history in one place. A spreadsheet can do the same job if one person owns the matrix and keeps it in step with the register.
Where this applies
For customer care and quality teams at residential developers who handle defect reports after handover, in any market. The method is a working practice, not a legal procedure. Where a shared investigation touches warranty obligations, notices to homeowners or data protection, check local rules with your adviser.
Sources
- Bond University research portal. Key residential construction defects: a framework for their identification and correlated causes. Queensland, Australia; published 2024. Research context only; it does not establish the cause in any particular home
- NSW Government, Building Commission NSW. Building Defects Library. New South Wales, Australia; taxonomy context only, not definitions for other markets
Spotted an error or an outdated source? Email info@wisemonks.com and we will correct the page.
