AI Audit Exchange
Go back

Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

Legal Hold vs Retention Period: The Difference That Matters

What is hold vs retention?

On AI Audit Exchange, retention_months and legal_hold are independent fields of a room, both printed in its manifest. Retention is the ordinary lifespan setting, bounded by plan limits (12 months free; 120 months paid). Legal hold is a boolean preservation state: while true, deletion of the room is blocked on every path. Neither control substitutes for the other.

Two controls, two threats

Every preservation failure is one of two kinds: a record dies too young on an ordinary schedule nobody reviewed, or a record dies during an extraordinary circumstance when it was needed most. Retention guards the first failure; hold guards the second. The controls differ in every property that matters — retention is a duration, hold is a state; retention is set at creation and close-out, hold is set at the moment a circumstance arises; retention expires by calendar, hold ends by decision. A system offering only one control would force you to misuse it for the other threat, and the misuse patterns are so predictable they have names in records management: the eternal hold (everything frozen forever, nothing schedulable) and the confident clock (a long retention trusted to protect a room mid-dispute, which it cannot).

What retention does and does not do

Retention does: give every room a deliberate lifespan matched to its purpose — rehearsals short, engagement records long; make that lifespan visible in every manifest export; and let a shelf of rooms be reviewed as cohorts with staggered clocks. Retention does not: block a deletion that someone with the power initiates for other reasons, respond to events, or know that a dispute began last Tuesday. It is a calendar, and calendars are gloriously indifferent to circumstances. Set it thoughtfully — up to 10 years where the record horizon demands — and then stop asking it to be a guard. Schedules schedule; guards guard.

What a hold does and does not do

A hold does: block all deletion of the held room, on every path, including the owner's, for exactly as long as it stands; record itself in the manifest as a visible fact (legal_hold: true) for every future reader; and convert preservation from a human memory task into a system state. A hold does not: extend or replace the retention schedule, judge the underlying matter, notify anyone, or release itself when the matter closes — release is a decision someone must take, ideally on counsel's advice, with the retention setting re-checked in the same sitting. A hold is a brake pedal, not a route planner.

The classic confusions, priced

Confusion one: 'The room is retained for 10 years, so we are safe in the dispute.' The clock says the room would ordinarily live; it does not prevent deletion during the dispute's chaos — a migration, a tidy-up, an account change. Only the hold blocks deletion. Confusion two: 'The room is on hold, so retention is handled.' The hold ends when the matter ends; if the retention underneath is 12 months default, the release itself starts a short countdown on a record that needed a decade. Confusion three: 'Put everything on hold forever, safest.' A shelf that cannot delete anything cannot be managed, reviewed or honestly certified; holds without matters attached become noise that hides the holds that matter. Each confusion is cheap to avoid and expensive to meet.

Operating both controls in one rhythm

The rhythm is simple enough to print on a card. At room creation: set retention for the room's honest purpose. At close-out: verify retention — the completeness view's step — and export the manifest showing it. On any dispute, investigation or regulator question touching a room: place the hold the same day, note it in the thread, add the room to the held-rooms list with an owner and a reason. On the matter's closure, on counsel's advice: release the hold, re-check retention in the same sitting, note both acts. Annually: review the shelf — every room's retention and every hold's continued justification read off current manifests. Two controls, five habits, no heroics.

How the pair reads in the manifest

The manifest prints the pair together — retention_months and legal_hold in the room block — and together they tell the room's whole preservation story in two values. retention 120, hold false: a long-lived record under ordinary schedule. retention 12, hold true: a short-scheduled room currently untouchable — a combination that should prompt exactly one question ('what matter, and what happens at release?'). retention 120, hold true: a long record inside a live circumstance. retention 12, hold false on a completed engagement: the default accident, waiting to be caught by review. Learn to read the pair at a glance and every manifest becomes a one-second preservation audit. The export ritual is covered in exporting the manifest.

Five actions to take

  1. Name the threat before touching a control: schedule risk → retention; circumstance risk → hold.
  2. Set retention for every room's honest purpose — up to 10 years for engagement records on paid plans.
  3. Place holds the day a dispute, investigation or regulator question touches a room; never rely on retention to do a hold's job.
  4. Release holds only on advice, and re-check the room's retention setting in the same sitting.
  5. Read retention_months and legal_hold together on every manifest — the pair is the room's preservation story.

Worked example

A fictional health-services firm, Vista Clara Health Partners, closes an SB 1119 room of 69 artifacts with retention set at 120 months and no hold — correct for an undisputed record. Eight months later, a dispute arises over decisions from that period. The general counsel places a legal hold the same afternoon and confirms the new manifest reads retention_months 120, legal_hold true: schedule and circumstance each handled by their own control.

Contrast the near-miss in the same firm's history: an older CPPA room had closed at the 12-month default with no hold. When its dispute began, two acts had to happen in the right order under pressure — lengthen retention, then place the hold — either of which, forgotten, would have left the record exposed by clock or by deletion. The firm's SOP now separates the acts by season: retention decided calmly at close-out, holds decided promptly at circumstance. The distinction, once seen, runs itself.

Frequently asked questions

Can a legal hold substitute for setting long retention?

No. The hold ends when the underlying matter ends. If the retention underneath is short, release starts a countdown. Set the schedule for the record's true horizon and use holds for circumstances.

Does long retention protect a room during a dispute?

Not by itself. Retention is a schedule, not a block. Only a hold blocks deletion — including the owner path — while the circumstance lasts.

Should all completed rooms be placed on hold as a precaution?

No. Holds belong to rooms touched by a present circumstance. Blanket holds make the held list meaningless and the shelf unmanageable. Long retention is the precaution; hold is the response.

Where can I see both settings?

In the room and in every manifest export: retention_months and legal_hold are printed in the room block beside regime and period.

Who releases a hold?

The organisation, ordinarily on counsel's advice when the matter has closed — and the release sitting should re-verify retention, because the clock governs from that moment.

Keep reading

All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: How to Set Retention on an Evidence Room · Next: What Happens When Audit Evidence Is Deleted Early

California AI Audit Timeline: 2028–2029, Year by Year · SB 813 / AB 1405 and the AI Auditor Registry, Explained · Who Needs a California AI Audit? Working Out Your Position