The operational problem
Choose the label recipients recognise, define the report scope, and retain a consistent issue model beneath the terminology.
“Punch list” is dominant in US construction, while “snag list” and “snagging” are common in the UK, Ireland, Australia, and other markets. Neither term alone defines the author’s authority, contractual effect, or technical scope.
Who this is for: Cross-border project teams, software buyers, owners, contractors, and consultants standardising field-report language across regions.
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
Choose market-appropriate language in the title and item labels.
Capture and review
State who performed the walk and what the report does and does not cover.
Issue and close
Use one structured lifecycle from observation through assignment, correction, and acceptance.
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.
- Recognisable regional term
- Explicit report scope
- Stable item reference
- Location and evidence
- Action owner and target date
- Closeout state and proof
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.