The operational problem
Use the downloadable sample to evaluate structure, then define your mandatory capture fields before adopting a report format.
Beautiful formatting cannot rescue incomplete field data. The template needs a reliable hierarchy: report context, summary, issue index, evidence pages, action ownership, status, and sign-off or limitations appropriate to the visit.
Who this is for: Teams designing an inspection standard, comparing report tools, or moving away from manually assembling documents after every site visit.
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
Define report identity, audience, scope, limitations, and approval route.
Capture and review
Choose mandatory issue fields and a consistent evidence standard.
Issue and close
Test the template with a real project, review readability on screen and paper, and revise before rollout.
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.
- Cover and report identity
- Executive summary and counts
- Indexed findings
- Evidence and annotations
- Action ownership and dates
- Status, closeout, and sign-off context
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.