The operational problem
Use Letter paper where appropriate, deliver a client PDF or trade action list, and preserve a CSV or local archive according to your project’s own records procedure.
US closeout workflows vary by contract, company, state, and project. SiteReportKit supplies the documentation layer: structured observations, photographic evidence, assignments, due dates, status, and report output.
Who this is for: US general contractors, owners’ representatives, architects, developers, inspectors, and specialty contractors completing pre-final, final, or internal quality walks.
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
Align fields and terminology with the project’s contract and closeout plan.
Capture and review
Capture and review punch items with consistent locations and responsible parties.
Issue and close
Issue, track, verify, and retain exports under the project team’s approved process.
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.
- Punch item reference
- Building, level, room, and location
- Responsible contractor or trade
- Target completion date
- Before and after evidence
- Letter-size report option
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.