Build Legal Hold Compliance Report

Skill: Convert hold-system data into a custodian compliance and escalation report

Region: United States Category: Legal / eDiscovery Does: Takes an export from a legal-hold management system (or a custodian tracking spreadsheet) and produces a hold compliance report — per-custodian acknowledgment status, overdue and escalation queues, and a defensible audit trail demonstrating reasonable preservation steps. Authority: FRCP 37(e) (reasonable steps to preserve) · Zubulake duty-to-monitor · Exterro / Relativity Legal Hold / ZL Unified Archive platform schemas

A hold is only defensible if it is monitored and enforced — issuing a notice and never tracking acknowledgments is the failure pattern that draws FRCP 37(e) sanctions. This report turns hold-system data into the audit trail counsel needs to answer a spoliation challenge and to manage follow-up. It complements generate-legal-hold-notice (issuing) and build-custodian-esi-source-map (scoping).

When this applies

• Ongoing management of an active legal hold: tracking who has acknowledged, who is overdue, and who needs escalation.
• Preparing evidence of reasonable preservation steps in response to a spoliation motion or court inquiry.

Input data required

Report structure (per custodian + summary)

custodian, role, department, employment_status,
notice_sent_date, acknowledged (Y/N), acknowledgment_date,
days_since_notice, days_overdue, reminder_count, last_reminder_date,
data_source_count, system_hold_applied (Y/N),
escalation_flag, status (compliant | overdue | escalate | departed-at-risk)

Summary:
  total custodians, % acknowledged, # overdue, # in escalation,
  # departed without preserved data, oldest-overdue age

Build rules

• Compute acknowledgment aging: days_overdue = today − notice_sent_date − grace_period. Flag any custodian past the grace period as overdue, and past a second threshold (or N reminders) as escalate.
• Acknowledgment ≠ preservation: track whether a central system hold (Purview/Vault/archive) is applied per custodian — a custodian who never acknowledged but whose mailbox is on an in-place hold is lower-risk than an acknowledged custodian with no system hold. Surface both.
• Departed employees are a priority risk: flag custodians who left the organization; verify their data was preserved/collected before offboarding deletion, and mark "departed-at-risk" if not confirmed.
• Escalation queue: produce a prioritized list (overdue longest, key custodians, departed-at-risk) for counsel follow-up; record each reminder and escalation for the audit trail.
• Keep it timestamped and versioned — the report's value in a spoliation fight is showing continuous monitoring over time, not a single snapshot.

Worked example (summary + exceptions)

Matter 2025-014 (hold issued 2025-03-01, ACTIVE) — 12 custodians, grace 5 business days
Summary: 10/12 acknowledged (83%); 2 overdue; 1 in escalation; 1 departed-at-risk
Exceptions:
  R. Roe      overdue 9 days, 2 reminders → ESCALATE (system hold applied, so data preserved)
  T. Smith    not acknowledged, DEPARTED 2025-04-15 → DEPARTED-AT-RISK: confirm mailbox was
              collected before the 30-day offboarding purge — verify with IT immediately
  K. Patel    overdue 3 days, 1 reminder → monitor (within escalation window)

Validation checklist

• Every in-scope custodian from the hold roster present; matter and hold status (active/released) shown
• Acknowledgment aging computed; overdue and escalation thresholds applied consistently
• System-hold status tracked alongside acknowledgment (preservation ≠ acknowledgment)
• Departed employees flagged; data-preservation/collection confirmed before offboarding deletion
• Prioritized escalation queue produced for counsel follow-up
• Reminders and escalations recorded; report timestamped/versioned for the audit trail
• Released custodians (if hold partially released) reflected with release dates
• Reconciles to the hold notice roster (generate-legal-hold-notice) and ESI source map

Last updated: 2026-05-31 — confirm grace-period and escalation thresholds with counsel; the report supports a reasonable-steps showing under FRCP 37(e) but does not itself satisfy the preservation duty. Verify hold-system export fields against your platform (Exterro/Relativity/ZL/Purview).