Skip to content

Post-handover defect tracking: from report to checked repair

Inspections & quality Updated 11 November 2026 3 min read

After handover, new reports need a separate follow-up process. Keep the original handover record intact and track each report from receipt through assessment, access, repair and verification. Recording a defect in an app does not by itself satisfy contractual notice requirements.

Keep the handover baseline intact

Distinguish an item already listed at handover from a newly reported condition. Give the new report its own ID and reference the relevant handover item where one exists. Record what the reporter observed before deciding whether the cause is workmanship, equipment, maintenance or something still unknown.

For occupied premises, agree an access contact and appointment. Keep entry codes and unnecessary personal information out of a broadly shared register. An urgent condition needs the responsible team's response procedure rather than waiting for the next weekly defect review.

A register you can copy

FieldFictional example
ID / receivedPH-014 / 10 November
Location / observationRoom 2.06; door catches on frame when closing
Baseline / noticeHandover record H-01; no matching open item; notice reference N-014
Owner / next actionJoinery lead to inspect; responsibility not yet confirmed
Access / targetAppointment via nominated contact, 13 November
VerificationRepair evidence pending; check full opening and closing movement

Keep the reported date, notice date, target date and actual repair date separate. None of these alone decides the applicable liability or warranty period.

Run the follow-up loop

  1. Acknowledge and route

    Confirm receipt and record the notice reference. Send the report to the person who can assess it under the contract; do not promise coverage before assessment.

  2. Agree access and repair scope

    Record the planned visit, responsible contact and agreed remedy. Keep disputed responsibility visible while arranging appropriate next steps.

  3. Verify before closing

    Retain the repair note and useful photographs. Record who checked the result, when, and against which criterion. Reopen the item if the same condition remains.

Separate progress from legal acceptance

A task marked complete records progress. It does not automatically release liability or establish that a formal notice was served. Check your contract and local rules for recipients, deadlines and required delivery channels. In a Croatian project, the Special Usages on Construction are one relevant source to review alongside the contract.

Use the handover checklist to prepare the baseline and the snag list register for item-level repair tracking. The latter needs the notice and access fields above for post-handover use.

How it works in TerenIQ

Doing this in TerenIQ

Use a TerenIQ issue or task for the observation, location, responsible people, due date, comments and evidence. Put the handover and notice references in the description; record the assessment and verification in comments. This workflow does not assume a dedicated resident portal, automated warranty clock or legally served notice.

Explore the feature: Defects and handover

Frequently asked questions

Should I add new defects to the signed handover record?

Keep the issued record intact. Create a dated new report and link it to the handover baseline, with an explicit correction or addendum if the project requires one.

Does a photograph prove the defect is resolved?

It may support the repair record. Use an appropriate check of the required result, especially where appearance alone does not demonstrate performance.

Related guides

Run it in one app instead.

Daily reports, tasks, inspections, RFIs and safety briefs — on the phones your crews already carry. 14 days free, no card required.