Track construction defects with Claude without losing open actions

Track construction defects with Claude →

A defect register is useful when readers can trace an observation, its owner and the evidence behind its current status. Claude can prepare the Excel workbook, but a tidy summary does not replace checking the work on site.

Start from the approved register

Attach the reference workbook and dated updates. Keep a stable ID for each issue, even when its description changes. Include the trade, location, known contractor and source document. An unassigned issue is still outstanding and must remain in the summary.

The pack specifies three sheets: detail, summary and a trade breakdown. Treat the detail as the reference and check that the other views include the same records. Request an update to the existing file so that IDs and earlier observations survive.

Separate intervention from clearance

Fictional example: R01 concerns hall paint requiring repair; R02 is a loose handle. The contractor reports working on R02, but nobody has checked it afterwards. Both issues remain open. Record the reported intervention in the notes and request verification; do not invent a clearance date or approval.

Before accepting an overdue status, check the reporting date used to calculate it. Any template warranty dates need review against the project record. A prefilled duration is not a legal determination.

Check the workbook before circulation

Open Excel and recalculate formulas. Confirm that references use the actual worksheet names and that every record contributes to the totals. Our example contains two issues and no clearances; a different summary needs correction.

Keep a dated copy before editing and document each status change. For the original observation, also use the site visit report method. The register follows actions over time while the report preserves the circumstances in which they were identified.