The operational problem
A transparent value proposition: inspect the real output, verify the advanced evidence workflow, and pay once when the store listing is live.
Many field-reporting tools split useful exports and report controls across recurring plans or add-ons. SiteReportKit is targeting a USD 9.99 one-time, store-restorable Pro unlock while keeping local projects and previews available free. Taxes and regional storefront conversion may vary.
Who this is for: Independent inspectors, consultants, small contractors, developers, and focused field teams assessing SiteReportKit before public availability.
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 a real report and action-list sample.
Capture and review
Compare XLSX/PDF deliverables, privacy controls, audit history, and locked issue handoffs with your requirements.
Issue and close
Use the website contact route for access; confirm the final localized price on the live storefront before purchase.
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.
- No account required for the core local workflow
- Offline-first field capture
- Professional PDF, XLSX, and CSV outputs
- Privacy blur and measurement annotations
- Timestamped activity and locked issue handoffs
- Drawn, typed, or imported signatures
- Original evidence with SHA-256 integrity records
- Local project archive
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.