The operational problem
The sample demonstrates a cover, summary, issue index, evidence pages, action ownership, and closeout structure generated from one project record.
A blank template can standardise headings, but it cannot keep dozens of photos, assignees, due dates, and status changes aligned by itself. The better workflow is to structure each item during capture and generate the presentation at export.
Who this is for: Teams evaluating report formats, replacing Word or spreadsheet templates, or setting a consistent punch list standard across site visits.
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
Download and review the real sample output.
Capture and review
Agree the required item fields and naming conventions before the walk.
Issue and close
Capture consistently, then generate the full report and filtered action list from the same source.
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.
- Project and client identity
- Unique item reference
- Area and precise location
- Description and required action
- Annotated photo evidence
- Owner, priority, due date, and status
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.