REPORT FIELD GUIDE
A report another
reviewer can follow.
Preserve the reasoning and the evidence, including the parts that remain uncertain.
Choose the right format
- Readable HTML
- A standalone review for a person to read in a browser. The insurance version includes incident details, timeline, findings, questions, next actions, limitations and supporting captures.
- Structured JSON
- A machine-readable case/evidence record for inspection or an agreed downstream workflow. It is not a claim of compatibility with every insurer’s system.
You can print the HTML from a browser. A dedicated PDF export of the new insurance review is not documented as implemented.
Read the report in this order
- Confirm the vessel, case reference and purpose.
- Separate analyst-entered incident details from provider observations.
- Read the timeline’s source, timestamp quality and demonstration labels.
- Open the capture links for each structured finding and review the stated relationship.
- Review contradicting evidence, unanswered questions, next actions and limitations.
Supporting, contradicting and context links are analyst assessments. Unlinked findings and missing-support notices should prompt follow-up rather than an assumption of verification.
Know the report boundary
An insurance report is based on its saved review and the captures available up to that review. To include later evidence, save a new review and generate the corresponding report. Keep report versions distinct during a handover.
Hash verification can identify changed stored capture contents against a reference. It does not certify source accuracy, identity, trusted time, legal admissibility or protection from an administrator rewriting the store. The new evidence report is not a digitally certified insurance audit.