The operational problem
Export construction evidence as a structured defect report, an outstanding action list, or a CSV register for downstream coordination.
A defect report should be precise enough to support coordination without pretending to replace professional judgment. SiteReportKit provides a consistent evidence record while the inspector remains responsible for classification and required action.
Who this is for: Site inspectors, quality teams, construction managers, design consultants, owner representatives, and contractors documenting active works.
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 the inspection and reporting context.
Capture and review
Record the location, trade, severity, description, action, owner, date, and annotated evidence.
Issue and close
Review, issue, follow up, and add closeout evidence when the correction is accepted.
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.
- Construction-specific issue register
- Severity and status fields
- Annotated evidence photos
- Required action and owner
- Outstanding-work PDF
- Closeout evidence page
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.