Legal holds in agency systems: issuing, scoping, and releasing

Reference article · 6 min read

A legal hold, sometimes called a litigation hold or preservation notice, is an instruction to stop the routine deletion of records that may be relevant to a dispute, investigation, or claim. For a government agency the duty to preserve generally begins when litigation is reasonably anticipated, which is usually earlier than the day a complaint is served. A tort claim notice, a demand letter, a subpoena, or an internal report of a serious incident can each start the clock.

The process is mostly administrative, but it depends on technical execution across systems the legal office does not administer. Gaps appear at the seams: a chat platform nobody listed, a separated employee's mailbox purged on the standard schedule, video that aged out of a vendor-hosted cloud, a retention rule that kept running because it lived in a different console. Federal procedural rules address the loss of electronically stored information that should have been preserved, and many states have adopted comparable provisions, but the specifics vary by jurisdiction and by matter type. Confirm yours with agency counsel and your state records authority.

Recognizing the trigger and issuing the notice

One office should own hold issuance so notices are consistent and traceable. In most agencies that is the agency attorney, or the records officer acting on counsel's direction. IT should never be the deciding authority on scope, and should never apply or lift a hold on a verbal request alone.

• Define the trigger list. Tort claim notices, preservation letters, subpoenas, personnel and EEO complaints, use-of-force or serious incident reports, audits, and inspector general referrals.
• Write the notice in plain terms. State the matter, the subject, the date range, the categories of records, what custodians must stop doing, and who to contact with questions.
• Keep holds distinct from public records requests. A records request is a disclosure obligation; a hold is a preservation obligation. They often arrive together and are handled by different workflows.

Scoping custodians, systems, and date ranges

Scope fails in both directions. Too narrow and relevant material disappears on schedule. Too broad and the agency freezes so much data that review becomes unaffordable and the hold is never released.

• Custodians. Begin with decision makers, then add assistants, supervisors, and recipients of the key communications. Include separated employees and contractors.
• Systems, not just mailboxes. Email, chat, shared drives, collaboration sites, case and permitting systems, HR, CAD and records management, video, GIS, ticketing, and voicemail.
• Non-custodial sources. Databases, logs, and shared repositories that no individual thinks of as theirs.
• Dates. Set a start date tied to the underlying events and leave the end open until counsel closes it.

Applying the hold where the data actually lives

Most cloud productivity suites support an in-place hold that preserves content without moving it or telling the user. Use that mechanism where it exists rather than asking staff to drag messages into folders.

• Email. Apply the platform's in-place hold to the custodian's mailbox, including archive and recoverable items, so deletions are captured but the user keeps working normally.
• Chat. Confirm whether your tenant retains chat at all, whether private and direct messages are covered, and whether edits and deletions are recoverable. Ephemeral or unretained chat is a common blind spot.
• File shares and collaboration sites. Hold at the site or library level when individual files cannot be reliably identified, and account for version history.
• Vendor-hosted applications. Body camera, case management, and permitting platforms often have their own retention engines. Ask the vendor in writing how a hold is applied, whether it survives records purges, and whether it is auditable.
• Endpoints and local storage. Identify laptops, removable media, and personal cloud storage used for agency work, and consider imaging where the material exists nowhere else.

Suspending deletion without breaking retention elsewhere

A hold is an exception, not a replacement for your retention schedule. Records outside the hold should continue to age and be destroyed on schedule, because stopping everything creates its own liability and cost. Document which rules were suspended, for which containers, and under whose authority. Verify after the change that disposition jobs still run for unaffected series. Also check automated cleanup that lives outside the records system: mailbox size policies, backup rotation, log truncation, and account deprovisioning scripts that delete data when an employee separates.

Tracking acknowledgements, reminders, and personal devices

Send the notice in a way that produces a record, and require custodians to acknowledge receipt. Keep a running list of who was notified, who acknowledged, and when. Reissue reminders periodically and whenever the scope changes, and notify new custodians as the matter develops.

Personal devices are harder. Agency work conducted on a personal phone or personal email account can be subject to preservation and to public records law in many states. Address it before a dispute: adopt a policy that defines what is permitted, instruct custodians in the notice to preserve responsive material on personal accounts, and route collection through counsel rather than IT so privacy boundaries are respected.

Releasing the hold

Release is the step agencies routinely forget. Holds accumulate, storage grows, and records that should have been destroyed years ago remain discoverable. Only counsel should authorize release, and only after the matter and any appeal period are closed.

1. Confirm in writing that the matter is closed and no related matter depends on the same records.
2. Remove the hold in each system and verify it cleared, including vendor-hosted applications.
3. Notify custodians that the hold is lifted and normal practices resume.
4. Restart suspended disposition rules and confirm the next cycle runs.
5. Record the release date and authorization in the matter file.

Review open holds on a recurring schedule, at least annually, with counsel and the records officer together.

What to ask vendors and put in contracts

When you buy or renew any system that stores records, ask for specifics rather than assurances: how a legal hold is applied and by whom, whether it overrides automated deletion, whether deleted items remain recoverable while a hold is active, what audit evidence the system produces, and how data is exported in a defensible format. For contracts, require preservation on written notice, notice to the agency before any bulk deletion, export of agency data in usable form at no additional charge, and cooperation with discovery at defined rates. Ask whether subcontractors and backups are covered, and how long data persists after termination.

HQT is a technology and software company working in state and local government systems, including the cloud collaboration, records, and public safety platforms where preservation controls have to be configured, tested, and audited.

Frequently asked questions