The operational problem
A structured closeout pack helps the next reader understand the original condition, the response, the evidence, unresolved exceptions, and the final status at issue date.
Marking a row complete does not show what changed or who accepted it. Closeout should preserve the original issue, record the claimed correction, and distinguish contractor completion from reviewer acceptance where the project requires it.
Who this is for: Contractors, project managers, owner representatives, design teams, quality managers, and handover coordinators closing punch, snag, or defect registers.
What a reliable field record needs
Every item should be understandable without relying on the inspector’s memory. Keep the description factual, make the location findable, show enough photographic context, and write the required action as an outcome that can be checked. Responsibility and due dates make the register actionable; status and closeout evidence make it traceable.
| Stage | Useful output |
|---|---|
| Capture | Area, trade, owner, priority, status, date, notes, and photographs stay attached to one item. |
| Handoff | Generate a full report, a focused action list, or a CSV register from the project record. |
| Follow-up | Retain the original condition, add resolution notes and after evidence, and issue a closeout record. |
A three-stage workflow
Prepare
Freeze or reference the issued action list so item identifiers remain stable.
Capture and review
Collect resolution notes and after evidence, then review against the stated required action.
Issue and close
Reopen inadequate work, record acceptance appropriately, issue the final report, and retain the source project and exports.
Field and report checklist
Adapt the checklist to your role, contract, jurisdiction, records policy, and the technical scope of the visit. SiteReportKit organises information; it does not confer inspection authority or make professional judgments for the user.
- Stable source item reference
- Original evidence retained
- Correction description
- After photo with useful context
- Reviewer state and acceptance note
- Final open-item exceptions
Report quality checks before issue
- Confirm the title, author, date, site, client, scope, and intended recipient.
- Check that item references are unique and locations use one consistent hierarchy.
- Remove duplicates and split conditions that require different owners or closeout decisions.
- Verify captions, annotations, names, dates, status, and required actions against the field record.
- Open the exported PDF, XLSX, or CSV, inspect image legibility, page breaks, filters, and counts, then store the issued version under the project’s records process.