The operational problem
The result is a client-ready PDF, a focused contractor action list, a sortable CSV register, or a local project archive—not an unstructured camera roll.
A useful punch list has to do more than store photos. It must tell the recipient what is wrong, where it is, who owns it, when it is due, and whether the correction has been accepted. SiteReportKit keeps those details with the issue from first capture through closeout.
Who this is for: General contractors, owners’ representatives, architects, inspectors, developers, and specialty contractors who need a clear record after a walkthrough.
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
Create the project and set report details.
Capture and review
Capture photos, markup, area, trade, owner, priority, and due date offline.
Issue and close
Review open work, export the right handoff, then add after photos for closeout.
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.
- Offline issue capture
- Photo annotation and captions
- Assignee, trade, severity, status, and due date
- PDF report and scoped action list
- CSV issue register
- After photos and resolution notes
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.