The adjuster's PDF did not read properly
What the parser's warnings each mean — a scan with no text in it, lines the carrier struck out, subtotals that disagree with what we read — and why every number on the finished quote is still yours to check.
The adjuster's PDF did not read properly
Open + Create → Insurance estimate, choose
the carrier's PDF, and read the notices before the numbers. The reader works on the text
inside the file — a picture has no text — and the parser never guesses: where it
cannot be sure it flags the line, and nothing reaches a quote until you build one.
Nothing read at all
"No priced scope lines in that file" means exactly that — usually a scan or a photo,
since a picture of an estimate has no text. The claim header may parse while the lines do
not. Three steps:
- Open the PDF and drag across a line: if nothing selects, that page is an image.
- Ask the carrier for the digital original, or the text export from the program that
wrote it (Symbility/Cotality). - Come back and press Upload a different estimate.
Lines that arrived missing
- "Struck through in the PDF — excluded. Check On to include." Carrier software
strikes out lines it replaced; the parser keeps them switched off and says "N line(s)
struck through in the PDF and excluded". If the line is part of the job, tick
Include. - A row you excluded yourself. The reconciliation counts included rows only:
"Carrier RCV: $X · your included lines: $Y ✓ matches". When it says "differs, check
the flagged section", the cause is usually a row switched off — yours or the
carrier's. - A line with no price. Flagged, counted in a material takeoff, and priced when you
set your own figure.
Reading the confidence banner
| What it says | What it means |
|---|---|
| Read with our carrier estimate rules | Layout recognised, every printed subtotal reconciles with the items above it, nothing flagged |
| This looks like <program> / We don't recognise the program that made this file | Read with the general reader; the check is still the document's own arithmetic |
| This one needs your eyes | A printed subtotal disagrees with the items above it, or more than one line in ten is flagged |
When it adds "More than half the printed subtotals disagree with what we read", believe
it: the file is a poor scan or compressed copy and the text is garbled. Get a better
original.
Work the flags
The strip asks you to verify each line against the PDF. Two flags matter:
| Flag | What to do |
|---|---|
| Verify Qty | A quantity was not readable. Type it against the PDF — the parser will not invent one |
| Set Price | No price yet. Set it, or leave it: an unpriced line still counts in a material takeoff |
✓ Looks right clears a row once checked. Press Build quote from this estimate with
flags remaining and Clavoz asks first: "N line(s) still flagged for review and M
struck-through line(s) excluded — build the quote anyway?" — Build anyway or Keep
reviewing.
When the file was never a scope
Sometimes the parse is fine and the document is the wrong one: a contractor proposal (already
marked up) locks margin at 0%, so your markup is not charged twice; a supplement /
counter-quote package holds two scopes; a supplement / reinspection claim adds to a
prior claim, not the whole job; a settlement statement of loss is the payments, not the
work; and an independent appraisal / public-adjuster estimate needs its tax and overhead
columns checked.
Still yours to check
The parser is a fast reader, not an authority, and Clavoz never sends anything on its own.
The Carrier Reconciliation export — overhead, profit, depreciation — is for the carrier
or adjuster, never a homeowner. Read
Your Responsibility for Quotes, and check every
flagged line against the PDF before the proposal leaves.
If a layout defeats the reader, send that file to hello@clavoz.com
(Getting Help); see also
Parsing Carrier Estimates.
Found something out of date? The guides live in the repository's
docs/ directory — fixing the guide is part of fixing the feature.