The operational problem
Create a traceable record with photos, locations, trades, owners, severity, status, due dates, and closeout evidence while applying your own approved project procedure.
Defect terminology, notice requirements, inspection authority, and retention duties differ across contracts, organisations, states, territories, and building classes. The app provides structured documentation, not jurisdiction-specific legal advice.
Who this is for: Australian builders, superintendents, consultants, developers, owners’ representatives, inspectors, and subcontractors managing quality observations and handover work.
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
Confirm the inspection authority, scope, terminology, and required notice process.
Capture and review
Capture evidence and action fields consistently during the site walk.
Issue and close
Review and export the report, then retain and distribute it under project requirements.
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.
- A4 presentation
- Area, element, and trade
- Annotated photographic evidence
- Required action and responsibility
- Due date and status
- Closeout evidence
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.