From Field to Final Report.
The structural compliance OS for modern infrastructure.
FCCIS is the operating system for commercial structural inspection firms. Voice-first field capture, jurisdiction-aware code references, and engineer-reviewed report synthesis — the full 4:1 field-to-office workflow compressed into one auditable evidence trail across Florida, Georgia, and Texas.
Inspectors spend four hours writing for every hour on site.
Commercial structural inspection is document-heavy and liability-sensitive. A single condition assessment generates hundreds of observations, photos, and code references — most of which are transcribed by hand into defensible narratives. Principal engineers end up rewriting junior reports line-by-line and approving findings that should have been routed for review.
- Voice memos, paper notebooks, and unstructured photos that need re-keying.
- Code citations pasted from PDFs with no review history or applicability check.
- Senior PEs rewrite junior reports because the narrative shape is wrong.
- Audit trails are reconstructed after-the-fact when a finding is challenged.
- 4:1 field-to-office time ratio caps how many assets a firm can take on per quarter.
- Voice-first capture writes structured observations as the inspector talks.
- Missing-data prompts force crack width, section loss, and scale before leaving site.
- Findings map to a controlled FBC / HVHZ / IBC Ch.17 / TDI catalog — never pasted.
- Every significant finding is routed to a licensed PE before issue. AI never approves.
- One auditable record from observation → media → code ref → reviewer → issued report.
Six coupled modules. One operational record.
Voice-first observations, photo metadata, GPS, automatic missing-data prompts.
Controlled code-reference catalog scoped by state, family, and review status.
Deterministic pipeline: normalize → group → cite → compose → review gate.
Human-in-the-loop signoff with audit trail, never silent AI approval.
Metered per AI-Certified Report alongside monthly seats.
One source of truth for the firm's inspection record, not a PDF factory.
From permit to issued report in three operational moves.
The same three steps drive the public marketing narrative and the in-app onboarding checklist — there is no separate “demo” flow.
- Step 01Create your firm workspace
Register your practice, link a licensed reviewer (PE/SE), and choose your launch jurisdiction — Florida, Georgia, or Texas.
- Step 02Upload a permit or capture an observation
Drop in a permit PDF or open a field session — voice notes, photos, and GPS attach to the right asset automatically.
- Step 03Generate a review-ready report
FCCIS drafts the narrative against the controlled code catalog, surfaces missing data, and routes every significant finding to your engineer.
Built around licensed review, not around AI throughput.
FCCIS is liability-aware by construction. The platform never silently approves a finding, never invents a code citation, and never issues a report without a licensed engineer of record.
Every significant finding routes to a state-licensed engineer before any report is issued.
FBC, HVHZ, IBC Ch.17 special inspections, and TDI windstorm — mapped, not pasted.
Code references stored as reviewed records with effective year, applicability, and review status.
Observation → media → code reference → report section → reviewer → issue. Every hop logged.
Permit-to-remediation, under the same review discipline.
Three committed modules extend FCCIS from field-to-final-report into permit intake and contractor remediation — without relaxing the engineer-review gate or the controlled code-reference catalog.
Ingests native and scanned permit PDFs, extracts a controlled set of fields, and routes them through reviewer accept before any live project is created.
- ·Extracts permit number, AHJ, site address, contractor / license metadata
- ·Extracts scope of work, drawing / spec references, inspection checkpoints, required evidence checklist
- ·Every field carries confidence score, source page, and bounding-box citation
- ·Low-confidence fields flagged for reviewer accept; no silent project promotion
Ranked suggestions drawn from a reviewer-curated catalog of failure modes and historically-approved corrective-action patterns. A suggestion surface, not an engineering directive system.
- ·Matches observations against a curated failure_modes catalog
- ·Ranks corrective_action_patterns by historical approval frequency and jurisdictional fit
- ·Reviewer accept / edit / reject per suggestion, attributed and audit-logged
- ·Pattern text is paraphrased and reviewer-controlled; jurisdictional anchors cite controlled code_references
Token-scoped portal that exposes a single project's reviewer-accepted findings to an assigned contractor, with deep-links into controlled Florida Building Code (and GA / TX) references.
- ·Per-project, expiring, revocable tokens; hashed at rest, emailed once
- ·Reviewer-curated contractor_portal_links bind scopes to controlled code_references rows
- ·No verbatim code text; paraphrased summary_text + reviewer-authored context_note
- ·Optional forward links only to allow-listed AHJ sources (FBC, GA DCA, TDI)
- ·Full audit log of portal opens, section views, reference opens, questions, acknowledgements
Roadmap — not yet active in this prototype. Specs in docs/feature-expansion-spec.md. Schema staged in db/migrations/003_feature_roadmap.sql (planning-safe, not applied to live Supabase).
Every significant finding routes to a PE or SE. The platform never silently approves.
Code references are stored as reviewed records with review status, effective year, and applicability notes. No verbatim code text.
Observation → media → code reference → report section → reviewer → issue. Every hop logged.
Pilot with a structural inspection firm we already understand.
Our pilot intake is sized for commercial structural firms in Florida, Georgia, and Texas with at least one licensed PE/SE on staff. Tell us a little about your practice and we'll reply within one business day.
- · Field-to-final-report compression for condition assessments
- · FBC, HVHZ, IBC Ch.17, TDI windstorm scope
- · White-label add-on for multi-PE practices
Built for principal engineers and firm owners.
FCCIS is in pilot with commercial structural inspection firms across Florida, Georgia, and Texas. Request access to evaluate the workflow against your current reporting stack.