The Method
Method version 1 · published 28 Sept 2026
Every Claim Basis Report is made the same way, by the same published steps. This page explains them in plain words. The reviewer details are at the bottom.
What the report is
The Claim Basis Report is a neutral read of one claim file. It measures what the file contains and stops. It does not say whether anything is covered, what is owed, or who is right.
Same file, same report, whoever orders it: a contractor, an adjuster, an attorney, a carrier-side reviewer, or the insured’s representative.
What you send, what you get back
What you send
Whatever you have. Policy, estimates, letters, photos, invoices. Nothing is required to start, and anything missing is noted in the report, not held against you.
What we read
Every page. Each item we pull out is tagged with the document and page it came from, so you can find it again.
What you get back
One report, usually in 3 to 5 days. The facts and authority found on the record, the numbers checked line by line, the claim's dates set against the deadlines on record, and a list of open questions.
Open questions
Anything the file does not answer is listed, with the document that would answer it. For example:
- A deadline on record with no response in the file.
- An estimate line with nothing in the file to check it against.
- A policy provision the letters refer to but the file does not include.
- A date, party, or amount the documents disagree on.
Every report, in order.
You send the file
Send whatever you have. Anything missing is noted, not held against you.
We read every page
Policy, estimates, letters, dates. Each item is tagged with the page it came from.
Every fact gets a source
Nothing goes in the report without showing where in your file it came from.
We check the numbers
Each estimate line: it matches, it doesn't match, or the file can't tell us.
We list open questions
Anything the file doesn't answer is listed, with the document that would answer it.
We show our work
Every report includes a record of how it was made, so anyone with the same file can check it and get the same result.
What we never do
- Say whether something is covered.
- Say what is owed.
- Call anything a violation or bad faith.
- Take a side, or act for anyone.
- Make up a number. If the file does not support a figure, the report says so.
Same file, same result. Anyone can check.
Every report carries a record of how it was made and a fingerprint of the files it was made from. Anyone holding the same file can run it through the same method version and get the same report.
If they don’t, that is a defect in the method. We fix it with a new version number, never a quiet edit.
Order a reportTechnical details for reviewers
What the report records
- Facts and authority on record
- The policy provisions, adopted code, and cited authorities the file actually contains, each with a source reference to the document it came from.
- Amounts
- Every priced line reconciled against the file's own evidence, marked reconciled, variance, or undetermined. The report never asserts an amount owed.
- Handling record
- The claim's dated events measured against the published handling requirements of the jurisdiction on file. A requirement the file does not evidence is marked undetermined, not assumed breached.
- Undetermined items
- Every question the file does not resolve, stated with the document or fact that would resolve it.
- Derivation trace
- The method version, the rulebook version, the authority-index version, the extraction steps applied, and a sealed hash of the inputs, so any reviewer can verify the report reproduces from the same file.
The report does not determine coverage, does not represent a party, does not negotiate, and does not advise on settlement. It measures the file and stops.
Versioning
Each report names the versions it was produced under.
Method version
method-v1
The six-step procedure and the report's fixed structure. This page.
Rulebook version
rulebook-YYYY.NN
The measurement rules applied per jurisdiction and line type.
Authority-index version
authority-index@version
The edition of cited authorities (statutes, bulletins, adopted codes) the report measured against.
A version change is a published event: the version key increments and reports produced under it name the new key. Reports are never retroactively restated under a newer version. A re-run produces a new report carrying its own version stamps.
Reproducibility
A report’s derivation trace identifies the input documents by hash. Any party holding the same file can verify that the stated method version, rulebook version, and authority-index version produce the stated report. Where a reviewer reaches a different result from the same inputs and versions, that divergence is a reportable defect in the method. The method publishes corrections as version increments, not quiet edits.
Attestation
The Claim Basis Report is produced by a published, versioned method. A report is a measurement of a file, not the adjustment of a claim. ClaimNova does not adjust, handle, negotiate, or settle claims, and does not act for any party to a claim.