Every observation.
No opinions.
Your photos and a voice memo become a documentation report: observed conditions area by area, corroborating indicators, and an explicit list of what the inspection did not establish. The scope call stays yours.
Free plan: 3 reports per month. No credit card required.
- ~90 sec
- upload to Word doc
- 6 sections
- every documentation report
- Zero
- inferred facts
It tells you what you missed.
Every report ends with Documentation Gaps — what this inspection did not establish. Areas not accessed, components not inspected, measurements not taken. You see the edge of what you verified while you can still do something about it.
The following items were not established by this inspection and associated documentation:
East slope strike count: A discrete impact point count was not recorded for the east slope. Granule loss was noted as significant, but no per-100-square-foot count analogous to the north slope count is available.
South and west slope photo documentation: No photographs of the south or west slopes appear in the provided photo log. Clean condition on these slopes is supported by field notes only.
Rooftop bath vent boot — exterior condition: No field note or photograph documents the condition of the bath exhaust vent boot at the roof surface. The association between the interior stain and vent boot condition rests on field note inference, not a documented exterior observation of the boot itself.
Vinyl siding — surface condition: No inspection observations regarding the presence or absence of impact indicators on the vinyl siding surface (north and east elevations) were recorded in the field notes or photo captions.
Additional roof penetrations: The presence, location, and condition of any roof penetrations other than the turbine vent and bath exhaust vent were not documented.
Twelve gaps on this claim. Generated from six captioned photos and a 90-second voice memo. No human edits.
Why this earns its place
- It is a reinspection list. Written while the file is fresh, not discovered when someone asks for the photo you never took.
- It separates fact from assumption. On the demo claim it flagged that clean south and west slopes rested on field notes with no supporting photos.
- It is honest on your behalf. Naming the limits of an inspection is what makes the rest of the document credible.
What it deliberately leaves out.
This is a record of the inspection, not an adjusting opinion. Being one thing cleanly is what makes it defensible as that thing.
Three inputs, one document.
Photograph the loss
Drag in your inspection photos. Each returns a one-sentence caption naming location, scope, and terminology — no speculation about cause.
Talk it through
Record the walkthrough the way you would describe it on the drive home. Exact numbers can be entered as structured field data, which overrides everything else on any conflict.
Review and export
Every section is editable and any single section can be regenerated on its own. Export to Word when it reads the way you would have written it.
Also work policyholder files?
Report type is a per-claim setting, not an account type. Policyholder files get the advocacy version, which adds a section justifying the recommended scope. See the public adjuster side.
Questions worth asking.
- Does it write my scope or recommendations?
- No. This half of LossNarrative is a documentation deliverable: it records what you observed, in detail, and lists what the inspection did not establish. The scope, the repair-vs-replace call, and the estimate remain yours. What it removes is the writing time between the inspection and a finished document.
- Why no opinions?
- So the document is exactly one thing and defensible as that thing. A report that mixes observation with judgment invites a reader to discount the observations along with the judgment. Here every line traces to something in your photos, your voice memo, or your field data — nothing is inferred.
- What is the Documentation Gaps section?
- A plain list of what the inspection did not establish: areas not accessed, components not inspected, measurements not taken. On the demo claim it caught that clean south and west slopes rested on field notes with no supporting photos. It is a reinspection checklist you did not have to write.
- Am I responsible for what it writes?
- You are responsible for the report you sign — as you would be for a draft from a junior associate. It is built to write [ADJUSTER TO CONFIRM] rather than invent facts, every section is editable, and every exported Word document carries an author-of-record and software-assist disclosure.
- I also work policyholder files. Can I do both here?
- Yes. The report type is set per claim, not per account. Policyholder files get the advocacy version, which adds a section justifying the recommended scope. Same workspace, same capture flow.
- Is there really a free plan?
- Yes — 3 generated reports per month, all core features, no credit card. Enough to run it against a file you have already documented by hand and compare.