Product · Capture
Walk the site. Talk through the work.
Capture is the first surface a Fermito firm touches each day. It runs on the phone the engineer already carries — voice notes, photos, and supporting documents land in a single dated visit record before anyone gets back to the office.
Field review under OBC 1.2.2.2 is documentation work as much as engineering work. Fermito treats the documentation layer the way the practice deserves — attributable, auditable, and authored on the visit, not in the evening hours that follow.
What capture does
Four inputs, one visit record.
Each input below is a real surface in the product today. None of them are roadmap promises — Fermito firms walk sites with this loop running.
01 · Voice
Voice notes, structured at the source.
An engineer walks the slab and talks. Fermito holds the live transcript on-device and streams chunks as the network allows. A dropped LTE signal in a stairwell does not lose the last forty seconds of context — the recording resumes against the same visit record on reconnect.
Whisper transcription · 5-minute capture window · resume across network drops
02 · Photos
Photos with AI-assisted captions, ready for review.
Each photo is timestamped, attributed to the visit, and run through Claude Vision for an initial caption. The engineer keeps walking instead of stopping to type. Captions are draft text — the reviewing engineer rewrites or accepts them on the way to seal.
Claude Vision captioning · stored on Vercel Blob · embedded in the export
03 · Documents
Drawings, specs, and prior reports — extracted in place.
Drop a structural detail PDF or a previous DOCX report into the visit. Fermito extracts the text server-side — DOCX through mammoth, PDF through Claude's native document API — and merges the content into the same transcript thread the engineer is dictating against. Prior observation language is available before drafting begins.
DOCX + PDF · 10 MB upload limit · text merged into the visit thread
04 · One record
Every input attaches to a single visit, attributed to one engineer.
Voice, photos, and documents are not loose files. They are children of a single dated visit record, attributed to the engineer who walked the site. The visit is the unit of work — it is what generation reads from, what review references, and what the export header reflects.
Visit = unit of work · engineer-attributed · auditable from capture to export
Field documentation, by the rule
Capture is built around what PEO actually expects from a site-visit record — field review, condition assessment, envelope investigation.
The Ontario Building Code requires that field reviews under OBC 1.2.2.2 be performed by — or under the direct supervision of — the practitioner responsible for the design. Fermito captures the record in the practitioner’s voice, on the visit, attributed to the engineer present.
PEO Practice Bulletin — Field Reviews expects contemporaneous documentation: dated, attributed, and tied to the visit it describes. Capture is contemporaneous by construction. There is no “transcribe the notebook on Friday” step to fail.
Standards referenced in observations — CSA O86, CSA A23.3, CSA S16 — stay searchable in the visit record, not flattened into prose the engineer has to re-find later.
Next surface
Capture lands. Generate begins.
Once the visit record closes, Fermito reads it end to end and assembles a draft in the firm's house format — templates, callouts, and phrasing pulled from the firm's own library.