Use case · Site review reports
Draft your site review reports in Fermito.
Site Review Reports (also written FRR or Field Review Report) are the numbered, photo-anchored report a P.Eng writes from a site visit. Fermito drafts the report from voice notes captured on the site and photos taken during the walk, in the firm's house format, ready for the engineer's review and seal.
Drafts today
Site Review Reports (SRR / FRR) are the workhorse template. Fermito drafts them end-to-end today, in the firm's house format. The Structural FRR template is downloadable from the templates page.
The recurring scenario
What this letter solves on the ground.
It is Tuesday morning. The PE arrives at an active garage repair site for the third visit on a six month repair contract. Concrete patching crews are working on the level 2 ramp; waterproofing is queued for the upper deck on Thursday. The engineer walks the work, photographs eight conditions, talks through observations on the way back to the car, and adds a recommendation list for the GC to address before next visit.
The deliverable is the same shape every time: a numbered observation list with photo anchors, a recommendation column, the standards referenced (CSA S413 for parking structures, the original repair specification, the OBC sections governing the field review), the visit number against the project's review schedule, and the signature block sized for the firm's PE seal. Each observation has a location reference, a description, and where applicable a recommendation tied to a standard or specification clause.
Fermito drafts the report from the voice transcript captured on the visit, the photos auto-captioned by Claude Vision, and the firm's prior reports as the voice reference. The engineer reviews the numbered list, edits anything the photo evidence does not support, and seals.
What Fermito drafts
A draft, in your firm's voice, in the structure your reviewers already trust.
Below: the shape of the document Fermito assembles for this use case. Headings, sequence, and limitations bands are encoded against your firm's house template, not a generic schema.
Sealed letter, draft preview
Visit 03 of 12 - garage repair, level 2 ramp.
Project information
Documents reviewed
Observation 01 (photo anchored)
Observation 02 (photo anchored)
Recommendations
Where the engineer stays in the loop
Fermito drafts. The engineer decides.
Sealed work belongs to the licensed professional. The list below names what Fermito does not decide for the engineer on this letter type. The engineer reads, edits, and seals.
- Every numbered observation. Fermito drafts the description from the engineer's voice notes and the photo caption; the engineer signs the description, not Fermito.
- The recommendation column. Whether an observation needs immediate action, monitoring, or no follow-up is a professional judgment the engineer owns.
- The standards cited. Fermito surfaces the standards the firm typically cites on this work; the engineer confirms each citation actually applies.
- The seal. Fermito will not export a sealed Word file without the engineer's explicit attestation. The seal stays with the licensed engineer, every time.
How Fermito drafts it
Four mechanisms, on every draft.
The same four mechanisms apply across every sealed letter Fermito assembles. Each card links to the matching section of the longer How Fermito Thinks read.
Voice-in
The engineer talks through the visit on the phone they already carry. Fermito holds the live transcript on-device and resumes through dropped signal.
How it worksPhoto-anchored
Each photo is captioned by Claude Vision and grounded in the draft. If the text says concrete and the photo shows steel framing, Fermito flags the mismatch.
How it worksFirm-template-aware
Cover, header, footer, distribution, signature block, and the firm's standard phrases are encoded once and reused on every draft. Output reads like the firm wrote it.
How it worksEngineer-attested
Fermito will not export a sealed document without the engineer's explicit confirmation. The seal stays with the licensed engineer, every time.
How it works
Read the primer
Anatomy of a defensible sealed review under OBC 1.2.2.2.
Long-form read on what makes a site review report defensible: the chain from observation to standard, standard to finding, finding to recommendation, and the photo evidence that anchors every link.
Try Fermito on an FRR you have already issued
Audit a sealed FRR you have already issued. You get a peer-reviewer read back: what holds up, what a reviewer would flag, and the questions a careful reviewer would ask before sealing. Independent, no signup, no product pitch inside the read itself.