Litigation Hold vs. Retention Enforcement: The Distinction P&C Insurers Can’t Afford to Blur

Retention enforcement and litigation hold both stop documents from disappearing. Treat them as the same control, and you will eventually fail an audit, a lawsuit, or both.

In my last post I argued that records governance has become a front-line compliance discipline for P&C insurers. One distinction sits at the center of getting it right — and it is the one I see blurred most often, in conversations and in Microsoft Purview configurations alike: the difference between retention enforcement and litigation hold.

Two controls that look alike

Both controls keep content from being deleted. That surface similarity is exactly why they get merged in people’s minds. But they answer different questions, fire on different triggers, are owned by different teams, and live in different parts of Purview. Confusing them is not a semantic nitpick — it is the root cause of two very expensive failure modes.

Retention enforcement: the routine lifecycle

Retention enforcement governs the normal life of a record. It is time- and event-driven, rule-based, applied broadly, and it ends in disposition when the clock runs out. In Purview, this is the world of retention labels and retention policies, translating NAIC and state schedules into automated rules.

• Trigger — time or a business event (policy expiry, claim closure, renewal).
• Scope — whole categories of records, applied at scale.
• Outcome — retain for the required period, then dispose on schedule.
• Owner — records management and compliance.

Litigation hold: the exception that overrides

A litigation hold — also called a legal hold or preservation — is the exception that overrides the routine. When litigation or an investigation is reasonably anticipated, you have a legal duty to preserve relevant evidence, even content that your retention rules would otherwise dispose. In Purview this lives in eDiscovery holds, not in retention policies.

• Trigger — reasonable anticipation of litigation, a claim dispute, or a regulatory investigation.
• Scope — specific custodians and a specific matter.
• Outcome — preserve until the matter is released, regardless of retention.
• Owner — legal.

Why blurring them is dangerous

There are two failure modes, and P&C insurers are exposed to both because claims litigation, bad-faith suits, subrogation, and regulatory inquiries are routine.

1. Using retention as your hold mechanism. If you rely on retention rules to preserve evidence, your automated disposition will eventually delete something that was under a duty to preserve — opening the door to spoliation claims, sanctions, and adverse-inference instructions. The very automation that keeps you compliant becomes the thing that destroys evidence.
2. Using legal hold as your retention mechanism. If your answer to risk is “hold everything, forever, in case of a lawsuit,” you never dispose, ROT accumulates, and you have recreated the keep-everything problem with a legal veneer — higher discovery costs, more breach surface, and a tenant your AI tools will happily mine.

The schedule-driven lifecycle and the matter-driven hold must coexist without interfering with each other. That is a design problem, and it is solvable.

Getting it right in Microsoft Purview

1. Design them as separate controls. Retention labels and policies for the lifecycle; eDiscovery holds for preservation. Do not simulate one with the other.
2. Make preservation win. Purview’s principles of retention are designed so that a hold takes precedence over disposition — verify in your configuration that an active hold genuinely blocks deletion before you trust it.
3. Scope holds narrowly. Hold the custodians and content the matter requires, not the whole tenant. Over-holding revives ROT and inflates review cost.
4. Release holds deliberately. When a matter closes, release the hold so normal retention resumes. Holds that are never released quietly become accidental forever-retention.
5. Document the trigger. Record when and why each hold was placed and released. Defensibility lives in that paper trail.

The takeaway

Retention enforcement answers one question: how long do we keep this by rule? Litigation hold answers a different one: what must we freeze for this matter? Keep the two distinct — separate controls, separate owners, preservation overriding disposition — and you can run an automated lifecycle without ever deleting evidence you were obligated to keep. Blur them, and you are one disposition job or one un-released hold away from a very bad day.

---

How does your team draw the line between retention and legal hold — and who owns each? I’d like to hear how other insurance and M365 teams have structured it. Leave a comment below.

This article reflects general industry practice and is not legal advice. Confirm preservation and retention obligations with your legal and compliance teams.