Who is legally liable when a company can't produce records a court asks for?
When a company cannot produce records a court has ordered, liability generally falls on the organization itself — but responsibility can extend to specific people inside and around it. There is rarely a single “guilty party.” Instead, courts ask who had a duty to preserve the records, who failed to meet it, and whether that failure was negligent or deliberate.
The organization bears primary responsibility
A company is a legal person, and it is the party to the lawsuit. When relevant records cannot be produced, the company is the one that faces consequences — regardless of which employee actually deleted a file or let a system auto-purge it. The duty to preserve attaches to the entity, so the entity answers for the gap.
This destruction or loss of evidence that should have been preserved is called spoliation. Once litigation, an investigation, or an audit is reasonably anticipated, routine destruction of potentially relevant records must stop. Failing to suspend it is what creates exposure.
Who else can be on the hook
Depending on the facts and jurisdiction, liability or sanctions can also reach:
- Officers and executives who knew of the duty and ignored it, or who directed the destruction.
- Custodians and IT staff who deleted records, or who failed to suspend automated deletion after being told to preserve.
- Attorneys, who have professional and ethical obligations to ensure their client preserves and produces relevant evidence; counsel can face their own sanctions.
What the consequences look like
Courts have broad discretion. Sanctions range from monetary penalties and fee-shifting, to an adverse-inference instruction (the jury may assume the missing evidence was unfavorable), to — in egregious cases — dismissal or default judgment. Intent matters: accidental loss despite reasonable efforts is treated very differently from deliberate destruction.
How organizations avoid it
The protection is a reliable preservation process. When litigation is reasonably anticipated, the organization should issue a litigation hold, identify the relevant custodians and systems, suspend automated deletion for those records, and document everything. A defensible records program — clear retention schedules consistently followed, paired with a dependable hold mechanism — is the best evidence that any gap was honest, not misconduct.
For more on the principles behind these duties, see the fundamentals topic hub.
Sources & further reading
Authoritative government and non-profit references.
- The Sedona Conference publications — The Sedona Conference
How to cite this page
APA
RM University Editorial. (2026). Who is legally liable when a company can't produce records a court asks for?. Records Management University. https://www.recordsmgmt.org/questions/who-is-liable-when-a-company-cannot-produce-records-in-court/
MLA
RM University Editorial. "Who is legally liable when a company can't produce records a court asks for?." Records Management University, 16 June 2026, www.recordsmgmt.org/questions/who-is-liable-when-a-company-cannot-produce-records-in-court/.
Related questions
- An employee left and had work records saved only on their personal phone or laptop — how do we recover them?
- Are the outputs of generative AI tools like ChatGPT and Copilot considered records that have to be retained?
- Can a company use a single global retention schedule across multiple countries or do different national laws force separate ones?
- Can an employee be personally fined or fired for deleting records they were supposed to keep?
- Can blockchain make records tamper-proof, and does an immutable ledger satisfy recordkeeping and retention requirements?