Can Carrier Claims Review Keep Pace with Plaintiff AI?

Evaluating Claims Review Capabilities in the Age of AI
As plaintiff firms accelerate their adoption of AI, carriers need to evaluate whether their own claims review capabilities are keeping pace.

What Morgan & Morgan Announced
On September 14, Morgan & Morgan announced that its in-house AI platform, MX2, is running at scale with nearly 5,000 monthly active users. According to the announcement, MX2 supports both pre-litigation and litigation work, and its capabilities include medical record extraction, chronology building, and alerts. The firm also said it plans to make MX2 available to other law firms.
The announcement places MX2 within a broader technology and AI investment: roughly $300 million in prior technology and AI spending over five years, and a minimum commitment of $1 billion over the following ten years. Those figures describe the firm's overall technology and AI program, not spending on MX2 alone.
What Adoption May Mean for Carriers
The rest of this article is our analysis, not a description of Morgan & Morgan's operations.
Plaintiff-side AI does not change the merits of any individual claim, and its use says nothing about whether a demand is accurate or a course of treatment appropriate. What it can change is pace. If plaintiff firms can organize medical records and assemble demand packages faster, carriers may receive more complete, better-organized submissions on shorter timelines.
That raises an operational question for claims leaders: how long does it take your team to move from an incoming demand to a documented assessment of the evidence, and how consistently is that review performed across adjusters, offices, and vendors? On medically complex casualty claims, the answer often depends on who picks up the file and how much time they have to read it.
What Keeping Pace Means
Keeping pace is not about matching anyone's technology spend. It is about four review steps your team can perform quickly and consistently on every file:
1. Understanding the demand.
What injuries, treatment, specials, and terms are being asserted, and what amount is requested?
2. Reviewing the supporting medical record.
What does the treatment history show, in order, across every provider?
3. Tracing material findings to source pages.
Can a reviewer point to the page that supports each finding that matters?
4. Routing unresolved questions.
Are open issues put in front of the right professional, whether that is a nurse reviewer, a medical specialist, or counsel?
The outcome of that review should follow the evidence. A well-supported claim may warrant prompt resolution. Uncertainty may require additional information or specialist review. In both cases, the file should show what was reviewed and why the decision was made.
A Medical-Review Example
Hypothetical
A carrier receives a demand on an auto bodily injury claim following a rear-end collision. The package includes a 30-page demand letter and roughly 600 pages of records from five providers. It asserts a cervical injury, several months of physical therapy, and a recommendation for a surgical consultation.
A structured demand summary lists what is asserted, including the injuries, treatment dates, billed amounts, and the response deadline. A medical chronology organizes every visit by date, with each entry linked to its source page. Reading the two side by side, the reviewer notices that the demand letter references an MRI, but no imaging report appears in the records provided.
That is an information gap, not evidence that the MRI did not happen. The next step is a records request. The chronology also shows an earlier visit for neck pain that predates the accident. Whether that history bears on the surgical recommendation is a clinical question, so it goes to a nurse reviewer. The adjuster documents what was reviewed, what remains open, and who owns each open item.
Nothing in that example requires AI to make a medical or causation determination. It requires the information to be organized, cited, and routed quickly enough that the right people can do their work.
Where AI Fits: AI Analyzes; Claims Professionals Decide
360 DemandReview structures demand-package information so reviewers can identify what is being asserted and what needs closer attention. 360 MedReview organizes medical findings and treatment history into a chronology with source-page citations for professional review.
The 360 Claims Intelligence Suite connects intake, demand and medical review, and claim questions across the workflow your team agrees on. 360 MailStream handles incoming correspondence, and Ask360 lets reviewers ask questions of the claim file.
In each case the software prepares the material and the claims professional makes the call. Faster cycle times and more consistent review are outcomes to measure in your own environment, on your own claims.
A Practical Assessment Approach
You can assess your current position without new technology. Take a sample of recent medically complex casualty claims and work through five questions:
1. Cycle time.
How many days pass between demand receipt and a documented assessment of the evidence?
2. Consistency.
If two reviewers worked the same file, would they identify the same assertions, findings, and open questions?
3. Traceability.
Can each material finding in the file be traced to a source page?
4. Escalation.
How are open medical questions routed, to whom, and how long do they wait?
5. Documentation.
Does the file record what was reviewed and why the decision was made?
The answers will show where review time goes and where consistency breaks down. That is the baseline for deciding whether, and where, AI belongs in your workflow.
Talk Through Your Demand and Medical-Review Workflow
We would welcome a conversation about how your team reviews demands and medical evidence today, and where structured, cited review could help.
Morgan & Morgan is not affiliated with 360 Intelligent Solutions. Facts about MX2 are drawn from the firm's September 14, 2026 announcement.
.png)



Comments