Large Loss Notice: How to Report Faster and Keep Every Fact Traceable

A large loss notice tells senior claims leaders and, where the contract requires it, reinsurers that a claim has turned serious. This post covers the triggers, the facts a good notice carries, the cost of late notice and where automation helps.

‍

What a large loss notice is, and who reads it

‍

A large loss notice is a written report that flags a serious claim to the people who carry the financial risk. Inside the carrier, that means senior claims management, the large loss committee, reserving actuaries and finance. Outside it, the reader is often a reinsurer.

‍

Reinsurance is insurance bought by an insurer. The insurer that buys it is called the cedent. A treaty covers a whole book of policies under one contract. A facultative certificate covers a single policy or risk. Many treaties and certificates require the cedent to tell the reinsurer about certain claims, within a set time and in a set form. That duty is called reinsurance notification.

‍

So one notice often serves two jobs. It escalates the file inside the carrier, and it meets a contract duty to a third party. Good large loss reporting does both from the same set of facts. It goes out early, it is complete, and each fact can be traced to a page in the claim file.

‍

The sections below set out the triggers, the content and the common causes of delay. They end with where LLN automation fits. In this post, that means software that drafts large loss notices from the claim file.

‍

What triggers a large loss notice

‍

There is no single industry trigger. Each carrier sets its own referral rules, and each reinsurance contract sets its own notice clause. An industry commentary from IRMI notes that notice and reporting clauses vary greatly from company to company and from intermediary to intermediary. Read the clause in each treaty and certificate, and the internal guideline, before you rely on a general rule.

‍

Most triggers fall into three groups.

‍

Reserve or incurred thresholds

‍

Many clauses require notice once the reserve or the incurred amount reaches a set level. The level may be a fixed dollar figure or a share of the cedent's retention. The retention is the part of each loss the cedent keeps before reinsurance pays.

‍

A reserve trigger is only as good as the reserve. The same IRMI commentary points out that reserve-based triggers rely on the cedent's good-faith reserving. A reserve that lags the medical facts will also delay the notice. The post on how early file review changes reserve development covers that problem in depth.

‍

Injury types, regardless of reserve

‍

Many clauses also list injuries that require notice on sight, whatever the reserve or liability position. A sample clause quoted by IRMI requires immediate notice of claims involving death or severe injury, regardless of liability. Its list covers fatality, amputation, spinal cord damage, brain damage, blindness, extensive burns and multiple fractures.

‍

For bodily injury (BI) claims, this trigger is easy to miss. Take a rear-end collision first reserved as a neck strain. Four months later, a neurology note records a traumatic brain injury. Nobody screens that note against the clause, so the notice waits for the next reserve review.

‍

When does the clock start in a case like that? Some clauses start it when the cedent learns of the finding. Others use a different event, so check the wording.

‍

Policy-limit exposure and legal milestones

‍

Internal guidelines often add triggers tied to exposure rather than injury. Common examples are a demand near the policy limit, a suit in a high-risk venue, or a coverage dispute. A time-limited demand is a frequent one, because it puts a short clock on a large decision. See the 30-day playbook for time-limited demands for the handling steps.

‍

What a good large loss notice contains

‍

A notice is read by people who have not seen the file. They need the facts, the numbers and the plan in a few pages. The checklist below covers sections most templates share. Your treaty or template may ask for more.

‍

• Claim and coverage. What it should carry: Claim and policy numbers, insured, limits, retention, treaty or certificate reference, date of loss, date reported. Where the facts usually sit: Policy file, first notice of loss, coverage notes.
• Loss description. What it should carry: How the loss happened, parties, location, venue. Where the facts usually sit: Police or incident report, statements, photos.
• Injury and medical. What it should carry: Diagnoses, treatment to date, current status, future care recommended, with dates. Where the facts usually sit: Medical records, radiology reports, bills.
• Liability position. What it should carry: Liability assessment, comparative fault, open coverage issues. Where the facts usually sit: Investigation notes, expert reports, coverage letters.
• Reserves and payments. What it should carry: Indemnity and expense reserves, paid to date, reserve history and the reason for each change. Where the facts usually sit: Claims system, reserve worksheets.
• Legal status. What it should carry: Representation, demands and deadlines, suit details, defense counsel. Where the facts usually sit: Correspondence, pleadings, counsel reports.
• Plan and next steps. What it should carry: Strategy, open questions, date of the next update. Where the facts usually sit: Adjuster and manager notes.
• Source references. What it should carry: The document and page behind each key fact. Where the facts usually sit: Every section above.

The last row matters most when the reader asks a question. A notice that cites "MRI report, page 214" for a disc herniation lets a reinsurer or a claims executive find the fact quickly. A notice that only states the diagnosis invites a follow-up request and a slower answer.

‍

Keep facts and opinion apart. State what the record says, then state the handler's view and the reason for it.

‍

Why notices go out late or thin

‍

Late or thin notices can follow from the way serious BI files are built, not only from neglect.

‍

The facts are scattered

‍

A serious injury file can be long. The guide to building a medical chronology from a 400-page claim file shows how much reading that takes. Medical records arrive from many providers, out of order and in batches. The fact that triggers a notice may sit in one line of one report. If nobody reads that page soon after it arrives, the trigger passes unseen.

‍

Large loss reporting waits for the reserve

‍

When the only trigger anyone tracks is the reserve, notice follows the reserve change. If the reserve review is due next quarter, the notice may wait until then. Injury-type triggers exist to close that gap. They work only if someone screens new records against them.

‍

Each update starts from a blank page

‍

Some treaties require follow-up reports as the claim develops. Handlers may rebuild each report by hand from the file and the last report. That takes time on a long file, so updates can slip behind busier work.

‍

What late reinsurance notification can cost

‍

Reinsurers ask for prompt notice for practical reasons. Many contracts give the reinsurer a right to associate. That is the right to join in the defense and handling of a claim. IRMI notes that a reinsurer can only use that right with notice in sufficient time to exercise it in a meaningful way.

‍

When notice is late, the result depends on the contract wording, the governing law and the facts. Courts do not agree on one rule, as IRMI commentary on late notice where notice is a condition precedent explains. A condition precedent is a step that must happen before the other side has to pay. Some courts require the reinsurer to show prejudice, meaning real harm caused by the delay. Others do not.

‍

Cases that show the range

‍

• In Unigard Security Insurance Co. v. North River Insurance Co. (1992), New York's highest court ruled on this point. A reinsurer must show prejudice before late notice relieves it of its obligations.
• In Pacific Employers Insurance Co. v. Global Reinsurance Corp. (2012), the Third Circuit applied New York law to a facultative certificate. Its clause called for prompt notice of claims involving death, serious injury or lawsuits. Because prompt notice was an express condition precedent, the reinsurer did not need to show prejudice.
• In United States Fire Insurance Co. v. Unified Life Insurance Co. (2025), the cedent gave notice only after judgment in the underlying suit. By then, a class had also been certified. The Fifth Circuit held the delay objectively unreasonable and material. So the reinsurer had no duty to indemnify.

These cases do not predict any one outcome. They show that a late notice can turn a routine recovery into a dispute, and at times into a loss of cover. Wording such as "condition precedent" or "in the opinion of the company" can change the result. Ask coverage or reinsurance counsel how your contracts and governing law treat late notice.

‍

LLN automation: faster drafts, same accountability

‍

LLN automation addresses the causes above, not the judgment. Software reads the claim file, pulls the facts into the notice template and cites the source page for each one. The large loss manager then reviews, corrects and approves the notice before it goes anywhere.

‍

What automation can take on

‍

• Screening. Checking each new record against the injury-type and exposure triggers in the guideline, so a buried finding is flagged when it arrives.
• First draft. Filling the checklist sections from the file, with page references, instead of a blank template.
• Updates. Showing what changed since the last notice, so a follow-up report starts from the differences.

What stays with the large loss manager

‍

• Deciding whether a notice is due, under the contract and the guideline.
• Setting and explaining the reserve.
• Stating the liability view and the strategy.
• Checking every pre-filled fact against its source page before sign-off.

Software can miss a page, misread a scan or attach a fact to the wrong date. Page references make those errors easier to find. The guide to checking a claims AI answer against the source page sets out a review method. The named manager stays responsible for what the notice says.

‍

Questions to ask of any LLN tool

‍

• Does every pre-filled fact link to the exact document and page?
• Can the tool use your own template and your treaty wording?
• Does it flag injury-type triggers from new records, or only from reserve changes?
• Can a reviewer see what changed between drafts and who approved them?
• Where is claim data stored and processed, and who can see it?

amaise offers an Automated Large Loss Notices product as part of its platform for bodily injury claim file review. As with any such tool, its output is a draft, and the manager signs off.

‍

A large loss notice is only useful if it arrives early and holds up when read. Know the triggers in each contract, and screen new records against them. Build the notice from facts a reader can trace. Automation can shorten the drafting, while the large loss manager keeps the judgment and the signature.

‍

Common questions

‍

Is a large loss notice the same as a notice to reinsurers?

‍

Not always. A large loss notice often serves both internal escalation and reinsurance notification. The internal guideline and each reinsurance contract can set different triggers, deadlines and content. Check both before you send one report to every reader.

‍

Who should sign off on a large loss notice?

‍

The large loss manager, or the person named in the claims authority guidelines. Software can draft and pre-fill a notice. A named professional should review the draft and approve the final version.

‍

Does late reinsurance notification always void cover?

‍

No. The result depends on the contract wording, the governing law and the facts. Some courts require the reinsurer to show prejudice. Others enforce a condition precedent without it. Ask counsel about your contracts.

‍

Key takeaways

‍

• A large loss notice serves two readers: senior claims management inside the carrier and, where a treaty or certificate requires it, the reinsurer.
• Triggers are set by each contract and internal guideline. Common ones are reserve thresholds, listed injury types such as brain or spinal cord damage, and policy-limit exposure.
• A good notice covers coverage, loss facts, injury, liability, reserves, legal status and plan, with a source page behind each key fact.
• Late reinsurance notification can lead to disputes or loss of cover, and courts differ on whether the reinsurer must show harm from the delay.
• LLN automation can screen records and pre-fill drafts, but the large loss manager reviews the draft and signs off.

‍