Will my photos or reports be used to train anything?

No. Every vendor that processes your content contractually agrees not to use customer inputs or outputs for training. Your photos and field notes stay yours. The full vendor list is on the security page.

I'm the licensed adjuster. Am I liable for what the software writes?

You are responsible for the report you sign — exactly as you would be for a draft a junior associate handed you. The report engine is built to write [ADJUSTER TO CONFIRM] rather than invent facts, and the editor surfaces every section so you can review and edit before exporting.

Will it inflate the scope to help my file?

No, and that is the point. It is instructed that completeness and clear justification are the goal and that exaggeration is not — no inflated quantities, no damage beyond what your notes describe, no severity your observations do not support. On our own demo claim it recommended cosmetic dent repair on a gutter rather than replacement, because the field notes called the gutter functional.

Does it write coverage arguments for me?

No, by design. It never quotes or characterizes policy language, coverage, limits, endorsements, deductibles, or code-upgrade provisions — none of that is in its inputs, so anything it produced there would be invention. Where the scope turns on a policy question it writes [ADJUSTER TO CONFIRM — verify against policy] and leaves the judgment to you.

What happens when the draft gets a fact wrong?

You catch it in the editor and edit it. The report engine refuses to invent measurements, dates, or names that aren't in your inputs — so the failure mode is usually 'too vague' (a [ADJUSTER TO CONFIRM] placeholder), not 'subtly wrong'. Every change to the engine is tested for accuracy against a library of real inspection scenarios before it ships.

Is there really a free plan?

Yes. 3 generated reports per month, all core features, no credit card required. Enough to run it against a file you have already written by hand and compare.

Can I cancel anytime?

One click in the Stripe customer portal, accessed from the billing page. Your plan stays active until the end of your current billing period. No prorated refunds, but no contracts either.

How long does a report actually take?

About 90 seconds end-to-end: 10 seconds to drag in photos, ~30 seconds for vision captioning to run in the background, ~30 seconds for the narrative to generate, and however long you want to spend editing before exporting. Compared to writing from scratch (60–120 minutes for a typical claim), it pays back fast.

Where does my data live?

Supabase (US region) for database and file storage, plus vetted vendors for narrative generation, transcription, and billing. Encryption in transit and at rest. Full vendor list and detail on the security page.

For public adjusters

Document the loss.
Justify the scope.

Upload your inspection photos and a quick voice memo. LossNarrative writes the narrative — scope of damage, cause analysis, an estimate-ready scope table, and a section showing why the scope you are asking for follows from what you documented. Export to Word in seconds.

Free plan: 3 reports per month. No credit card required.

7 sections: every report
~90 sec: upload to Word doc
Zero: invented facts or figures

generated narrative · 6 photos · 90-second memopolicyholder report

# Hail Loss Documentation Report

**Claim Number:** DEMO-HAIL-001
**Policyholder:** Marisol Vega
**Property Address:** 4218 Cottonwood Dr, Plano TX 75024
**Date of Loss:** April 12, 2026
**Inspection Date:** April 18, 2026
**Prepared By:** Public Adjuster of Record

---

## 1. Loss Summary

The subject property at 4218 Cottonwood Dr, Plano TX 75024 sustained hail damage on April 12, 2026, affecting the asphalt shingle roof, rooftop appurtenances, gutters, and interior ceiling finishes. The damage pattern — concentrated on the north and east slopes with clean south and west slopes — is consistent with a directional storm event. Secondary water intrusion through a hail-damaged bath vent boot p…

See the full sample report

Section 5

The report argues its own scope.

A carrier-side report states the scope. Yours has to survive someone reading it for a reason to pay less. So every report includes Basis for Recommended Scope — it introduces no new observations, it connects the ones you already documented to the repair you are recommending.

DEMO-HAIL-001 — Basis for Recommended Scopeunedited output

North and East Slope Replacement The field notes document approximately eleven hail strikes per one hundred square feet on the north slope, with significant granule loss across both the north and east slopes. This density and distribution of impacts is not confined to a discrete, patchable area; it extends across the measured field of both affected slopes. Spot repair of individual strikes is not practicable at this impact frequency — each strike represents a discrete point of mat bruising and granule loss, and the sheer number of impacts distributed across the slope surface means that any repair limited to individual strikes would leave a substantial portion of damaged shingle material in service. The south and west slopes are documented as clean, which establishes a defined boundary for the scope of replacement at the north and east slopes and supports a slope-by-slope replacement recommendation rather than a whole-roof replacement at minimum.

The continuity of the north and east slope surfaces as described in the field notes and Photo 2 — a continuous field of three-tab asphalt shingles — means that partial repair within those slopes would result in a visually discontinuous surface where new material meets aged material across the same unbroken plane. [ADJUSTER TO CONFIRM — verify material availability and match.]

Turbine Vent — Replacement The turbine vent housing is dented and has lost its paint coating. The field notes explicitly characterize this as a replace rather than repair item, and the observed physical deformation of the housing supports that determination. A dented turbine vent housing cannot be restored to its pre-loss geometry and function through repair in the field.

Generated from six captioned photos and a 90-second voice memo on a demo hail claim. No human edits.

What it is doing there

Bounding the ask. It scoped replacement to the north and east slopes and said the south and west were clean — a limit a reviewer can verify, not a whole-roof reach.
Tying damage to the cause. Interior ceiling damage is carried back to the hail-damaged vent boot, so the consequential item is not left floating.
Flagging the policy line. Where coverage of consequential interior damage matters, it stops and writes [ADJUSTER TO CONFIRM — verify against policy].

Restraint by design

What it refuses to write.

An overreaching report hands the other side a reason to discount all of it — including the parts you documented properly. Three things are held out of every report on purpose.

No dollar figures

Not a single number it did not measure. Pricing stays with you and your estimating platform — the scope table hands off clean, with quantities marked for confirmation where your notes did not include them.

No coverage opinions

No policy language, limits, endorsements, deductibles, or code-upgrade provisions. It has never seen the policy, so it does not pretend to. Those decisions stay with the licensed adjuster.

No facts you did not document

No invented measurements, dates, or names, and no severity your notes do not support. When something is missing it says so with a placeholder — so the failure mode is a visible gap, not a quiet fabrication.

How it works

From driveway to Word doc

Three steps, about 90 seconds of your attention.

Drop in your photos

Each photo gets an adjuster-grade caption automatically — location, scope, terminology, no speculation.

Record a voice memo

Talk through the inspection like you would on the drive home. We transcribe it so it becomes the substantive backbone of the narrative.

Export to Word

Seven sections, an estimate-ready scope table, photo log appendix, ready to send. Edit any section in-app first — or regenerate just that one.

Capture quality

The report is only as good as the capture

LossNarrative never invents facts. If a count, measurement, or date isn't in your photos, memo, or field data, the report says [ADJUSTER TO CONFIRM] instead. That protects you at desk review — but it means the report is decided on the roof. Here's the difference ten minutes of capture discipline makes.

A vague memo

"Roof's got a bunch of hail hits up top, gutters are dinged up too. Some water got in the bedroom."

What the report can say

Hail impacts were observed on the roof covering [ADJUSTER TO CONFIRM: affected slopes and impact counts]. Interior water damage was noted [ADJUSTER TO CONFIRM: room, extent, and measurements].

Every bracket is something a desk reviewer can kick back — and a re-inspection trip you pay for.

A precise memo — same 30 seconds

"North slope test square: eleven hits per hundred square feet, bruised mat, granule loss. South and west slopes clean — zero hits. Gutters at the northeast corner: multiple dents on the upper lip, still functional. Master bedroom ceiling: water stain about eighteen inches around the bath vent."

What the report says — generated, unedited

Inspection of the north roof slope revealed approximately eleven hail strikes per one-hundred square feet within the test square… The south and west slopes exhibit no comparable impact damage, which is consistent with a directional storm track.

Counts become findings; clean slopes become evidence for causation. Nothing to kick back.

Photos: shoot deliberately

Risk photo with the house number, then all four elevations — the clean ones are evidence too
Chalked test square on every slope, photographed wide, then close-ups of hits
Overview → close-up pairs for each damage item, with a tape measure or gauge card in frame
20–40 photos is normal for a roof claim; each gets an automatic caption that feeds the narrative

Memo: say every number

Name the slope or room before each finding: "on the east slope…"
Speak numbers as numbers: "eleven hits," "eight years old," "twenty-eight squares"
State negative findings — "south slope clean, no interior leaks" — they prevent supplement disputes
Close with your cause statement and repair-vs-replace intent

Field data: exact numbers win

Type per-slope test-square counts into the claim — enter 0 for inspected-and-clean; a zero is evidence, a blank is a re-inspection
Roof age, size in squares, pitch, stories — the values that must be exactly right
Typed values override the voice memo on any conflict
The app checks for documentation gaps before you generate — while you're still on site and can still go back up

Ten minutes of discipline per inspection. First-pass reports instead of re-inspection trips.

Field notes

The capture craft, written down

Routines that keep files from bouncing back — useful whether or not you ever sign up.

July 8, 2026 · 6 min read

Repair vs. replace: writing cause language that holds up

Every property file comes down to two sentences — the cause and the repair-or-replace call. How to write both so they survive desk review and supplement disputes.

July 8, 2026 · 5 min read

Test-square documentation done right

A test square that was counted carefully but photographed carelessly might as well not exist. Placement, the three-shot sequence, and counts that survive desk review.

July 8, 2026 · 6 min read

What desk reviewers actually kick back — and how to preempt it

A bounced file isn't bad work — it's missing proof. The five things that actually get adjuster reports sent back at desk review, and how to preempt each.

All articles

Pricing

Simple pricing

Start free. Move to a paid tier when you need volume.

Free$0

Kick the tires before subscribing.

3 reports per month
All core features
Watermark on .docx exports

Common questions

What adjusters ask before signing up. If yours isn't here, email us.

Will my photos or reports be used to train anything?: No. Every vendor that processes your content contractually agrees not to use customer inputs or outputs for training. Your photos and field notes stay yours. The full vendor list is on the security page.
I'm the licensed adjuster. Am I liable for what the software writes?: You are responsible for the report you sign — exactly as you would be for a draft a junior associate handed you. The report engine is built to write [ADJUSTER TO CONFIRM] rather than invent facts, and the editor surfaces every section so you can review and edit before exporting.
Will it inflate the scope to help my file?: No, and that is the point. It is instructed that completeness and clear justification are the goal and that exaggeration is not — no inflated quantities, no damage beyond what your notes describe, no severity your observations do not support. On our own demo claim it recommended cosmetic dent repair on a gutter rather than replacement, because the field notes called the gutter functional.
Does it write coverage arguments for me?: No, by design. It never quotes or characterizes policy language, coverage, limits, endorsements, deductibles, or code-upgrade provisions — none of that is in its inputs, so anything it produced there would be invention. Where the scope turns on a policy question it writes [ADJUSTER TO CONFIRM — verify against policy] and leaves the judgment to you.
What happens when the draft gets a fact wrong?: You catch it in the editor and edit it. The report engine refuses to invent measurements, dates, or names that aren't in your inputs — so the failure mode is usually 'too vague' (a [ADJUSTER TO CONFIRM] placeholder), not 'subtly wrong'. Every change to the engine is tested for accuracy against a library of real inspection scenarios before it ships.
Is there really a free plan?: Yes. 3 generated reports per month, all core features, no credit card required. Enough to run it against a file you have already written by hand and compare.
Can I cancel anytime?: One click in the Stripe customer portal, accessed from the billing page. Your plan stays active until the end of your current billing period. No prorated refunds, but no contracts either.
How long does a report actually take?: About 90 seconds end-to-end: 10 seconds to drag in photos, ~30 seconds for vision captioning to run in the background, ~30 seconds for the narrative to generate, and however long you want to spend editing before exporting. Compared to writing from scratch (60–120 minutes for a typical claim), it pays back fast.
Where does my data live?: Supabase (US region) for database and file storage, plus vetted vendors for narrative generation, transcription, and billing. Encryption in transit and at rest. Full vendor list and detail on the security page.

Concerned about a specific compliance regime or carrier requirement? Read the security page or email us directly.

Get your evenings back.

Write the report from the driveway, not the dining table. Three free reports a month — no credit card, no contract.

Document the loss.Justify the scope.