Document Legal Holds on AWS

Targeted preservation, hold tracking, and defensible evidence management — on AWS infrastructure you control.

Targeted Preservation, Hold Tracking, and Defensible Evidence Management — on AWS Infrastructure You Control

When litigation is anticipated, an investigation is underway, or a regulatory proceeding is imminent, organisations have a legal obligation to preserve all documents and records that may be relevant. This obligation — known as legal hold, litigation hold, or preservation order — overrides normal retention schedules and prevents the modification, deletion, or disposition of held documents until the matter is resolved and the hold is released.

Getting legal hold wrong is one of the most expensive document management failures an organisation can face. Failing to preserve relevant documents results in spoliation sanctions — adverse inference instructions, monetary penalties, or the dismissal or default of claims. Over-preserving documents (holding everything "just in case") inflates storage costs, increases eDiscovery review burden, and delays matter resolution. The goal is targeted preservation: hold the right documents, track the hold with full evidence, and release the hold defensibly when the matter concludes.

FormKiQ provides legal hold as a core governance capability — with targeted hold application, concurrent hold management, hold tracking with full audit evidence, and integration with the platform's retention, access control, and search capabilities. Deployed into your own AWS account, the hold infrastructure and hold evidence are in your environment, under your control, and producible to courts, regulators, and opposing counsel.

What Is Legal Hold?

Legal hold is a process that suspends the normal retention and disposition lifecycle for documents that may be relevant to anticipated or active legal proceedings. It operates as an override — regardless of what the retention schedule says, a document under legal hold cannot be modified, deleted, or disposed of until the hold is released.

Concept Definition
Legal hold / litigation hold A directive to preserve documents and records relevant to anticipated or active litigation, investigation, or regulatory proceeding
Preservation obligation The legal duty to preserve relevant evidence once litigation is reasonably anticipated — arising from common law, statute, or regulation depending on jurisdiction
Hold notice A communication to custodians (employees or departments) informing them of the hold, the scope of documents affected, and their preservation obligations
Custodian An individual who possesses, controls, or is responsible for documents subject to a legal hold — typically employees, but also departments, contractors, or systems
Scope The definition of which documents are subject to the hold — by custodian, date range, subject matter, document type, keyword, metadata value, or combination
Release The formal termination of a legal hold when the matter is resolved — documents return to their normal retention lifecycle
Spoliation The destruction or failure to preserve relevant evidence — resulting in sanctions, adverse inferences, or other legal consequences

How Legal Hold Works in FormKiQ

Hold Application

Legal holds in FormKiQ can be applied with targeted scope — broad enough to satisfy preservation obligations, narrow enough to avoid the cost and burden of over-preservation:

Hold Scope What It Preserves When to Use
By custodian All documents associated with specific employees, departments, or roles When the matter involves specific individuals — employment disputes, executive investigations, whistleblower matters
By date range All documents created, modified, or received within a specific date range When the relevant period is defined — contract disputes, regulatory investigation periods, incident windows
By subject matter All documents matching specific keywords, metadata values, or classification criteria When the matter involves a specific topic, project, product, or transaction
By document type All documents of a specific type — contracts, emails, financial records, correspondence When the relevant document category is defined but the custodians or dates are broad
By case or matter All documents within a specific case file or matter collection When FormKiQ is managing the case file directly
Combined scope Any combination of the above — e.g., all emails from three custodians within a 12-month date range containing specific keywords When the matter requires precise scoping to balance preservation with proportionality

Hold Protection

Once a legal hold is applied, FormKiQ enforces preservation automatically:

  • Deletion blocked — held documents cannot be deleted by any user, regardless of role or access level
  • Modification controlled — held documents are protected from content modification; metadata annotations and hold-related tagging are permitted and audit-logged
  • Disposition suspended — held documents are excluded from retention-driven disposition, even if their retention period has expired
  • Storage tier preserved — held documents are not transitioned to storage tiers that would make them inaccessible within required timeframes

Hold Tracking and Audit Trail

Every hold event is recorded in FormKiQ's audit trail with the detail needed for defensible preservation evidence:

Event What's Recorded
Hold application Hold identifier, matter reference, scope definition, applying party, authorisation, timestamp
Scope modification Changes to hold scope — additions, narrowing, or broadening — with reason, authorising party, and timestamp
Hold notice distribution Distribution of hold notices to custodians — delivery confirmation, acknowledgment tracking
Custodian acknowledgment Custodian acknowledgment of hold notice — individual acknowledgment with timestamp and signer identity
Document identification Documents identified as within hold scope — count, classification, and storage location
Access during hold Any access to held documents — who, when, what action, from where
Hold release Hold released — reason, authorising party, matter resolution reference, timestamp
Post-release disposition After hold release, documents returning to normal retention lifecycle — any resulting disposition is separately audit-logged

Concurrent Holds

A single document can be subject to multiple concurrent legal holds — arising from separate matters, separate litigations, or separate regulatory proceedings. FormKiQ manages concurrent holds with clear rules:

  • All holds tracked independently — each hold has its own scope, its own audit trail, and its own release process
  • Last hold standing — a document is protected until the last applicable hold is released; releasing one hold does not expose a document that is still subject to another
  • Independent release — holds are released individually by matter; releasing Hold A does not affect Hold B
  • Merged reporting — reporting can show all holds affecting a specific document, or all documents affected by a specific hold

Legal Hold and the Preservation Lifecycle

Legal hold intersects with other governance processes at multiple points. Understanding these intersections is essential for defensible preservation.

Legal Hold and Retention

Scenario What Happens
Hold applied, retention period active Document is protected by both hold and retention — neither can dispose of it
Hold applied, retention period expired Document is protected by the hold despite retention expiry — hold overrides
Hold released, retention period active Document returns to normal retention — retained until retention period expires
Hold released, retention period expired Document becomes immediately eligible for disposition review

Legal Hold and eDiscovery

Legal hold is the preservation phase of the eDiscovery process. FormKiQ supports the downstream eDiscovery stages through:

  • Targeted search — identify and collect documents within the hold scope using full-text and metadata search
  • Collection — compile held documents for review, with deduplication and document-level metadata export
  • Production support — held documents and their metadata exportable via API for transfer to eDiscovery review platforms
  • Chain of custody — the audit trail provides a complete chain of custody from hold application through collection and production

Hold Notice Management

A legal hold is only effective if the people responsible for preserving documents are aware of it. FormKiQ supports hold notice management through its document generation and distribution capabilities:

  • Notice generation — hold notices generated from templates with matter-specific details (matter name, scope description, preservation instructions, custodian obligations)
  • Targeted distribution — notices distributed to identified custodians via the platform, with delivery confirmation
  • Acknowledgment tracking — individual custodian acknowledgment collected via eSignature, with completion dashboards showing who has and hasn't acknowledged
  • Reminder workflows — automated reminders for custodians who haven't acknowledged, with escalation to legal or compliance
  • Notice updates — when hold scope changes, updated notices distributed with the same tracking and acknowledgment workflow
  • Release notices — when the hold is released, release notices distributed to custodians with instructions on any changes to their preservation obligations

Who Uses Document Legal Holds on AWS

Organisation Type Legal Hold Needs Key Drivers
Corporations and enterprises Multi-matter hold management across departments, business units, and jurisdictions; concurrent holds from litigation, regulatory investigations, and internal investigations Litigation risk, regulatory examination, corporate governance
Financial services Client communication holds, trading record holds, regulatory investigation holds SEC/FCA/APRA examination; FINRA arbitration; litigation
Healthcare Patient record holds for malpractice litigation, regulatory investigation, and compliance proceedings Medical malpractice defence, regulatory compliance, HIPAA investigations
Government and public sector Agency record holds for litigation, FOIA/Access to Information proceedings, and regulatory enforcement Sovereign litigation, FOIA compliance, public accountability
Higher education Student record holds for Title IX/misconduct proceedings, employment holds, research compliance holds Employment litigation, student proceedings, research misconduct investigations
Legal and professional services Client matter holds, firm-level litigation holds, professional regulatory holds Client defence, firm risk management, professional regulatory proceedings
Insurance Claims record holds for coverage disputes, subrogation, fraud investigation Claims litigation, regulatory examination, fraud investigation

FormKiQ Editions for Document Legal Holds

Capability Core Essentials Advanced Enterprise
Document Storage (S3) & API
Tagging, Search & Classification
Workflows, Queues & Rulesets
Encryption (KMS — in-transit & at-rest)
Document Control & Versioning
eSignature (hold notice acknowledgment)
Document Generation (hold notices)
Enhanced Full-Text Search (OpenSearch)
AI Processing & Analysis (Bedrock)
Multi-Instance & Multi-Region Licensing
Vendor-Managed & Hybrid Deployment
Compliance Consulting
SupportCommunity2-business-day SLAPrivate Slack + 40 hrs onboarding8-business-hour SLA + strategic support

Getting Started

FormKiQ Core can be deployed to your AWS account in fifteen to twenty minutes. Legal hold capabilities — including hold tracking, disposition override, eSignature acknowledgment, and hold notice generation — are available on FormKiQ Essentials, Advanced, and Enterprise.

Schedule a consultation · Start a Proof-of-Value deployment

Frequently Asked Questions

What is legal hold?

Legal hold is a process that suspends the normal retention and disposition lifecycle for documents relevant to anticipated or active litigation, investigation, or regulatory proceeding. Documents under hold cannot be modified, deleted, or disposed of until the hold is released. The purpose is to preserve potentially relevant evidence and avoid spoliation.

What is the difference between legal hold and litigation hold?

The terms are often used interchangeably. "Litigation hold" specifically refers to holds triggered by anticipated or active litigation. "Legal hold" is broader — encompassing holds for regulatory investigations, internal investigations, government inquiries, and other legal proceedings beyond litigation. FormKiQ supports both under the general legal hold framework.

What happens if we fail to preserve documents under legal hold?

Failure to preserve relevant documents — known as spoliation — can result in serious legal consequences: adverse inference instructions (the court instructs the jury to assume the destroyed documents were unfavourable), monetary sanctions, dismissal of claims, default judgment, or disciplinary action. The specific consequences vary by jurisdiction and the severity of the failure.

Can a single document be under multiple holds?

Yes. FormKiQ supports concurrent holds — a single document can be subject to multiple holds from separate matters. Each hold is tracked independently with its own scope, audit trail, and release process. The document is protected until the last applicable hold is released.

How does legal hold interact with retention schedules?

Legal hold overrides retention schedules. A document under hold cannot be disposed of even if its retention period has expired. When the hold is released, the document returns to its normal retention lifecycle — if the retention period has already expired, the document becomes immediately eligible for disposition review.

How does FormKiQ track hold notices and custodian acknowledgment?

Hold notices are generated from templates and distributed to identified custodians through the platform. Each custodian's acknowledgment is collected via eSignature with timestamp and signer identity. Completion dashboards show acknowledgment status. Automated reminders follow up with custodians who haven't acknowledged. All notice and acknowledgment events are recorded in the audit trail.

Start with FormKiQ Core

The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.

Get Started Free

Deploy FormKiQ Essentials or Advanced

Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.

Explore Options

Plan an Enterprise Rollout

For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.

Book a Call