The product

From a site visit to a sealed report, in one pipeline.

InspectionVoice replaces the hours between leaving the jobsite and delivering the report. Six stages, each auditable, each editable by the human who owns it.

How it runs

Six stages, inspector-owned at every step.

The AI does the mechanical work. The inspector owns the judgment. Reviewers check it. The PE seals it.

01 · Capture

Cover page + plan snapshot

The inspector photographs the jobsite sign. Claude Vision extracts project, permit, scope, and AHJ, then auto-fills the inspection header. Plans PDF rasterizes in the background so annotations attach to the right page.

Cover page OCRPlan rasterizationProject auto-fill
02 · Voice

Session-based dictation

Each discipline (structural, fire, MEP) gets its own session. Recording is diarized, noise-tolerant, and queues locally when you're offline. The in-inspection Live AI Assistant answers code questions on-site without stopping the session.

Diarized transcriptionOffline queueLive assistant
03 · Extract

Structured observations

Claude Haiku 4.5 extracts candidate observations from the transcript: description, location, severity, checklist-item candidates, and photo references. Inspectors accept or edit each one — nothing gets committed silently.

Claude Haiku 4.5Severity gradingPhoto linking
04 · Cover

Coverage matrix

Every required checklist item is mapped against what the transcript actually covered. Gaps are highlighted before the inspector leaves the site. Multi-session inspections roll up into a single coverage view.

Gap detectionChecklist ↔ transcriptPre-seal QA
05 · Draft

Firm-style report generation

Claude Opus 4 generates the narrative in your firm's voice using a style profile trained on your prior reports. Every observation is cited to the code clause it came from — CBC, IBC, AWS D1.1/D1.3, ACI 318.

Claude Opus 4Style profileInline citations
06 · Seal

Reviewer → PE → AHJ

Reviewers approve, request changes, or reject with reason. PEs seal with a PAdES cryptographic signature tied to their license + state. AHJ-ready PDFs deliver with a verifiable hash URL for external audit.

Reviewer queuePAdES PE sealVerifiable hash
What it replaces

The reporting tax, deleted.

Reporting is the tax every firm pays on every inspection. InspectionVoice removes most of it and audits the rest.

−7 hrs / inspection

Hand-typed narrative

Replaced by Claude Opus 4 drafting in your firm's voice, with inline code citations.

Zero missed items

Manual checklist coverage

Replaced by automatic mapping of transcript → checklist and pre-seal gap detection.

One source of truth

Disparate photo / note apps

Replaced by a single session-based capture with photos, voice, and plan annotations in one timeline.

Adobe-verifiable

Paper or wet-ink seal

Replaced by PAdES cryptographic PE signatures with verifiable hash URLs.

Audit-proof delivery

Emailed PDFs

Replaced by AHJ-ready delivery with immutable receipts and a public verify URL per sealed report.

Same-day close

After-hours office work

Replaced by a draft waiting for you when you return. Reviewer approves the same afternoon.

FAQ

Product questions we get a lot.

Practical answers to the things buyers actually care about.

How long does the pipeline take per inspection?+

Transcription for a typical 20-minute site walk completes in 2–4 minutes. Full extraction + draft + PDF render adds another 1–3 minutes depending on report length. Most inspectors have a sealable draft before they're back at the office.

Can we edit the AI draft?+

Yes. Every observation, severity, citation, and narrative paragraph is editable by the inspector and then by a reviewer. Every edit is tracked with an author and timestamp for the audit log.

What about re-inspections and follow-up visits?+

Re-inspections link to the parent inspection and carry forward open observations as 'verify' items. When they pass on two consecutive visits, the system auto-closes them. Differential reports are generated automatically.

Can we connect this to Procore or Autodesk Construction Cloud?+

Yes. Finalized inspections push observations to Procore as Observations and to Autodesk as Issues. Photos and signed PDFs attach automatically. OAuth-based; admin controls per-project mapping and push/pull direction.

Can we access this programmatically?+

Yes. A scoped public REST API at /api/v1 exposes projects, inspections, observations, reports, webhooks, and analytics. Each API key has per-endpoint scopes and sliding-window rate limits. Outbound webhooks notify your ERP of inspection.sent, report.signed, and more.

Is it mobile or desktop?+

Inspectors use the mobile PWA — installable from Safari or Chrome on iOS and Android, with full offline support. Firms use the desktop admin for review, finalization, analytics, scheduling, and PE seal. Reviewers can work from either.

Start today

The next inspection can write itself.
Start your free trial today.

14 days, no credit card. We'll turn your first site visit into a sealed, cited, firm-style report before you're back at your desk.