Property Remedial Works Tracking: From Finding to Completion

1. Capture a clear source finding

Record the property or asset, the observation, when it was identified, who identified it and the supporting evidence. Distinguish a confirmed defect from a question that needs further investigation.

2. Triage priority and responsibility

Assign an owner, target date and priority using your organisation’s approved process. Record why the priority was chosen, particularly when risk, access or operational constraints affect the response.

3. Define the required outcome

A remedial instruction should describe the outcome needed without discarding the original finding. Keep scope, access constraints, competent-person requirements and any approval boundary visible to those quoting or delivering the work.

4. Keep quotations and approvals connected

Where quotations are required, retain each submission and the approval decision against the same remedial record. This avoids losing the reason for the work when it moves into procurement or job delivery.

5. Track delivery as a job, not a replacement record

The job should inherit the property, asset, scope and finding reference. Site updates, variations, photographs and documents can then build a continuous history rather than a second disconnected version.

6. Collect proportionate completion evidence

Completion evidence may include photographs, notes, certificates or test results depending on the work. Record who supplied it and when. A contractor marking work complete is not necessarily the same as the customer accepting or verifying the outcome.

7. Verify and close deliberately

Record the verification decision, verifier, date and any residual action. If the outcome is incomplete, reopen or create a linked follow-up rather than overwriting the earlier history.

8. Report on ageing and exceptions

Useful operational views show overdue actions, work without an owner, items awaiting quotation, jobs awaiting evidence and completed work awaiting verification. These exception views help teams act without flattening every record into one status.