Product · Generate
The first draft, in the firm’s own format.
Generation is the surface that separates Fermito from a general-purpose drafting tool. The output is not a generic field review report. It is a draft in the firm’s template, with the firm’s callouts, written in the voice the firm’s seniors have spent years teaching their juniors.
No prompt to compose. No schema to populate. The visit record is the input; the firm's template is the form; the draft is the result.
What generate does
Four properties of a draft worth reviewing.
Each property is a deliberate design choice — and a deliberate refusal to behave like a general AI assistant.
01 · Templates
Templates encoded to the firm — not a generic report schema.
Every firm has a structure its principals would recognize across forty reports without looking at the cover. Fermito encodes that structure: section order, header conventions, signature block, the way distribution lists are formatted. The first draft does not look like an AI tool's idea of a sealed engineering deliverable. It looks like the firm's report.
Per-firm template · cover, header, footer, distribution · house format from the first draft
02 · Standard phrases
The firm's own callout language, pulled from a standing library.
Phrases that recur across reports — guarded openings, conditional approvals, the firm's preferred wording for outstanding items — live in a standard phrase library that the firm itself maintains. Generation pulls from the library before reaching for general drafting language. The voice that comes out is the voice the firm has spent years teaching its juniors.
Editable phrase library · per-firm scope · injected into the generation prompt
03 · Visit-grounded
Drafted from the visit record, not from a prompt the engineer wrote.
The engineer does not write a prompt. The engineer walks the site. Generation reads the entire visit record — voice transcript, photo captions, extracted documents — and builds the draft against it. Observations the engineer dictated come through as observations. Photos referenced in the transcript end up in the photos section. The structure is inferred; nothing is asked again.
Reads transcript + photos + extracted docs · 3–15s typical · Vercel Pro fluid-compute timeout
04 · Bilingual at the source
English or Farsi in. House-format English out.
Some Fermito firms have engineers more comfortable dictating in Farsi than in English. Fermito accepts the field notes in the language they were spoken and produces the draft in the firm's signing language. Translation is a generation-time concern, not a workflow concern the engineer has to plan around.
Claude Sonnet · native bilingual handling · sign-out language is the firm's setting
The line Fermito will not cross
Generate produces a draft. Not a report.
The word draft is load-bearing in everything Fermito does. A draft is the starting point for review. A report is what an engineer signs. Fermito produces the first; the engineer produces the second. The product surface enforces that line — there is no auto-seal, no auto-distribute, no path from the generation step to a finished document that does not pass through the review surface.
Generation is fast — a typical draft lands in three to fifteen seconds — but speed is not the value proposition. The value proposition is what the engineer reads on the other side: a first pass close enough to the firm’s house format that review becomes review again, instead of rewriting from a blank page.
PEO Practice Bulletin — Use of AI Tools treats AI-generated drafts as a starting point for a practitioner’s judgment, not a substitute for it. Generate is built to that bulletin’s spirit, not around it.
Next surface
The draft is on screen. Review begins.
Revise is where licensed judgment lands on the page — by voice, by keyboard, with every change held in diff until the engineer decides to keep it.