The operational problem
The same project record can support a client-facing report, an issue register, a contractor action list, and a later closeout pack.
Post-visit report writing introduces delay and interpretation. Structured capture at the point of inspection preserves the connection between location, observation, evidence, responsibility, and requested action.
Who this is for: Construction managers, consultants, owner representatives, property teams, inspectors, and contractors conducting quality or progress-related site walks.
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 the inspection scope and report identity.
Capture and review
Capture each observation with the fields needed for action and traceability.
Issue and close
Review consistency, export the appropriate report, and retain the project for follow-up.
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.
- Inspection context and date
- Observation category and location
- Photo evidence and caption
- Responsible party
- Priority, status, and due date
- Review and closeout trail
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.