Use caseProperty claims

Shared review and annotation

An examiner, an attorney and an adjuster read one 46-page report. Remarks go by email and printout, and weeks on nobody knows what was settled.

Everyone annotates the same copyThe notes stay with the caseThe signed report is never altered

Actions on this report
The viewerNote on page 18

Drying equipment, 12 days: $6,420. Nadia: the daily rate looks high, can you justify it?

source · Adjuster report v1, p. 18
Where the review stands

A point goes back to the adjuster · the request is a task with a due date

01

The starting point

In two paragraphs

Three readers, one report, two printouts. The examiner checks the costs, the attorney checks the cause, the adjuster answers both. Their remarks end up in three inboxes and two marked-up copies, and before every call the examiner rebuilds the picture by hand.

In this setup every remark lives on the page it concerns. The report opens in the viewer inside the claim, and each reader annotates the same copy with the rights of their role. The examiner sees every remark where it applies, and the signed report stays exactly as the adjuster sent it.

Adjuster report PD-26-03158.pdfViewer
Three hands, one page. The notes of three readers on the same page, each with its author.
Claim PD-26-03158Case management
The review as tasks. Each open point in the claim, with an owner and a date.

Any claims team has seen these screens. What it rarely sees is them in this order: the report arrives in the case, three people annotate the same copy, and the corrected version is compared and approved on screen. Below, Nadia runs claim PD-26-03158 through it.

02

The report arrives

The adjuster's report lands in the claim and the examiner opens the review.

Step 1Workflow

The report is filed and the review starts

Brian Lockhart uploads his report on claim PD-26-03158: a washing machine hose leaked and damaged three units in a Chicago apartment building. Nadia Kowalski, the examiner, starts the review step. Oliver Mensah, the in-house attorney, gets a task to read the cause of the loss.

Adjuster report v1, 46 pagesLegal reading: OliverApproval: Nadia
Claim PD-26-03158Case management
Each reader gets a task, with a due date the team lead can see.
The review has an owner from day oneNobody wonders who is reading what. Each reader has a task in the claim.
Step 2Viewer

Highlight the cost line and write the question

Nadia opens the report in the viewer and scrolls to the repair estimate on page 18. The drying costs look high for 12 days of equipment. She highlights the line and writes her question in a comment.

Adjuster report PD-26-03158.pdfViewer
The comment carries its author and its time. The report file is untouched.
The question sits on the line it is aboutNo email quoting page 18. Whoever opens the page sees the remark.
Step 3AI check

The AI flags a figure that does not match

Before sending anything back, Nadia asks the assistant to look for inconsistencies in the report. It finds one: the ceiling repair on page 19 is priced on 450 sq ft, and the floor plan on page 31 gives 410 sq ft for the same apartment.

Ask about this documentAI console
Each finding cites its pages, so Nadia checks both in one click.
Think of your last disputed claim: how often does a wrong surface or a wrong total go through, because nobody had time to read page 19 against page 31?
The error is caught before the callNadia raises the right point with the adjuster, with both pages in hand.
03

Three readers

The attorney and the adjuster read the same copy, each with their own rights, and one correction is asked for.

Step 4Viewer

The attorney reads the cause of the leak

Oliver opens his task and lands on the report. On page 7 the adjuster writes that the hose seal had been leaking for weeks, then calls the damage a sudden event. Oliver highlights that sentence: a slow leak may fall under the repeated seepage exclusion.

Adjuster report PD-26-03158.pdfViewer
The highlight is a layer on the page. The text of the report does not change.
The legal point is on the page that raises itNadia reads Oliver's view next to the sentence, without chasing an email.
Step 5Portal

The adjuster answers on the same pages

Brian opens the report through the partner portal. His rights cover this report only: read and annotate, no download. He adds a note on page 18, the regional standard rate, and files his supplier's price list on the case.

This report onlyAnnotate: allowedDownload: not allowed
Partner portalViewer
The adjuster sees one document of the claim. The rest of the case stays closed to him.
The outside adjuster works on the real copyNo PDF sent back and forth. His notes land where Nadia's and Oliver's are.
Step 6Workflow

The correction is requested, with a due date

Nadia sends Brian a request for a corrected version: the ceiling area, the total on page 19, and the wording on page 7. The request is a task in the claim, and its timer is visible to the team lead.

Request for informationCase management
If the date passes, the escalation rule of the process applies.
Open points cannot get lostEach one is a line in a task, with an owner and a date.
04

The review closes

Version 2 arrives. Nadia checks it, approves it, and the review is filed with the claim.

Step 7Viewer

Compare version 1 and version 2 side by side

Brian files version 2. Nadia opens both versions on one screen with synchronized display. Additions, deletions and changes show in the text and in the layout.

Compare versionsViewer
The two versions scroll together, page against page.
The correction is checked in one screenNadia does not reread 46 pages. She sees what moved.
Step 8Assistant

The assistant explains what changed

Nadia asks the assistant what changed between the two versions. It lists three changes with their pages. She checks each one against her open tasks and closes them.

Area: 450 to 410 sq ftTotal: $2,214Cause reworded, p. 7
Adjuster report v2AI console
The answer proposes. Nadia closes the tasks herself.
Every request is matched to its answerThe tasks close on facts Nadia has seen on the page.
Step 9History

The final report is stamped, the review stays on file

Nadia stamps version 2 as approved. Version 1 stays in the case with every note on it, so Oliver can come back to the cause of the leak if subrogation against the tenant's insurer starts.

Claim PD-26-03158 · HistoryCase management
Each document keeps its versions, its notes and the actions taken on it.
The review is evidenceWho raised which point, on which page, and how it was settled. It is all in the claim.
05

The verdicts

A review closes accepted, sent back, or disputed. The outcome decides where the claim goes next.

Accepted as sent

Nothing to correct

The notes are answered on the pages and no figure is out of line.

Next: the examiner stamps the report and the claim moves on.
Corrections requested

A point goes back to the adjuster

A surface, a total, a wording. The request names the pages.

Next: a task with a due date; version 2 is compared on arrival.
Disputed

The legal reading changes the claim

The cause of loss points to an exclusion, noted on the page by the attorney.

Next: the examiner decides on coverage, with the attorney's note in the file.
What stays with people

It approves nothing and corrects nothing in the report. Across the nine steps on this page, the approval is Nadia's stamp, with her name and her time.

The AI flags an inconsistency and explains changes, each time with its pages. The notes and the tasks are written by people, and the signed report is never altered.

06

What it saves

These numbers come from one water leak claim. Your report types and your list of reviewers will give your own.

1 copyannotated by three readers, the outside adjuster included.
0 emailscarrying review remarks. Every note sits on its page in the claim.
3 changesbetween version 1 and version 2, seen on one screen.

Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.

Why these numbers hold

One copyProductivityEvery reader annotates the same report, with the rights of their role.
Zero lost remarksProcess reliabilityNotes stay on the pages, requests are tasks with a date.
Original intactEvidenceAnnotations are stored apart. The signed report stays as received.
07

The people involved

Three people sit around the same report, each with a different worry.

Business operations

Claims examiners

Before every call, the review gets rebuilt from three inboxes.

  • Every remark sits on the page it concerns.
  • The AI flags figures that do not match, with their pages.
  • Version 2 is compared with version 1 on one screen.
  • Open points are tasks with a due date.
Risk and compliance

In-house attorneys

A legal point gets lost in a thread nobody rereads.

  • Your note sits on the sentence that raises it.
  • Each note carries your name and the time.
  • The first version stays on file with every remark.
  • The signed report is never altered.
Partners

Independent adjusters and outside experts

Questions reach you in pieces, by mail, days apart.

  • The questions are on the pages of your own report.
  • You see this report, and only this report.
  • You annotate online, nothing to install.
  • The request for a new version comes with its due date.

Your first move

With one report type. Take the adjuster reports your examiners print most often, and open them in the viewer inside the claim.

It runs over the claims application and the repository your team already works in.

Your move

Review one of your reports this way

Pick a recent adjuster report and the people who argued over it. We will set up the same review in the viewer and walk your team through it.

The screens on this page are drawn to show one step at a time, with example data.

Uxopian Software helps organizations put AI to work across the systems they already run, without giving up control of their data, their infrastructure or their critical processes.