The operational problem
SiteReportKit packages the same field data into a full client report or a lean outstanding-work list, so each recipient gets the appropriate level of detail.
Snagging often breaks down between capture and communication. Photos end up detached from notes, room names vary, and contractors receive a document that is difficult to filter. A structured snag record removes that ambiguity.
Who this is for: Residential inspectors, developers, client representatives, fit-out teams, property managers, and contractors completing handover or pre-completion inspections.
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
Set up the property, client, inspector, and report identity.
Capture and review
Walk room by room and record annotated evidence with a consistent area and trade.
Issue and close
Filter outstanding snags, issue the action list, and document accepted corrections.
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.
- Room and location fields
- Before and after photo evidence
- Priority and status tracking
- Trade and assignee grouping
- Signature-ready report output
- Local project archive
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.