Spoliation and Missing Evidence
Disposing of records is entirely ordinary until the moment a duty to preserve attaches to them. After that, destruction becomes a separate wrong with its own remedies, and the argument in practice is almost always about exactly when that moment arrived.
The rule in short
Spoliation is the destruction or alteration of evidence after an obligation to preserve it has arisen. The consequences range from an adverse inference through evidential exclusions to determinative sanctions, and they depend on when the duty attached, whether the loss was deliberate and how much prejudice resulted. Routine destruction before the duty arose is generally not spoliation at all.
Organizations destroy records constantly and lawfully. The question in every spoliation argument is when that ordinary activity should have stopped, and the answer is usually earlier than the party doing the destroying believed.
When the duty to preserve attaches
Usually before proceedings. In most systems the obligation arises when a dispute is reasonably anticipated, which can be well before anything is filed.
A demand letter is a clear trigger. Correspondence asserting a claim puts the recipient on notice, and destruction afterwards is difficult to defend.
Internal awareness counts. Where an organization knew of a problem likely to lead to a claim, the duty may have attached without any external communication.
The scope follows the dispute. What must be preserved is material relevant to the anticipated issues, not everything the organization holds.
It covers electronic material. Messages, logs and stored data fall within the duty, and automatic deletion has to be suspended, per preserving a device before it changes.
Third-party holdings may be included. Where a party controls material held by somebody else, the duty can reach it, and notice to that holder becomes necessary as well.
Personal devices are covered. Where work material sits on somebody's own phone or laptop, the duty follows the material rather than the ownership of the device.
It continues. The obligation runs until the matter concludes, and material destroyed midway through is as much a problem as material destroyed at the start.
Routine destruction and where it stops being safe
Retention schedules are legitimate. Disposing of records on a documented timetable is ordinary practice, per records destroyed on schedule.
The policy has to be real. A schedule applied consistently is a defense, and one produced afterwards to justify a particular disposal is not.
Suspension is the key step. Once a duty attaches, the ordinary policy must be suspended for relevant material, and that suspension needs documenting.
Automatic deletion is the usual failure. Systems that delete messages after a period keep running unless somebody switches them off, and nobody remembers to.
Selective application looks bad. A policy followed loosely and then applied strictly to one category of document invites an obvious inference.
Document the decision. A record showing when the hold was imposed, over what material, and who was told is what answers the allegation later.
Review it periodically. Holds that are imposed and never revisited miss material that becomes relevant later, and a periodic check is cheap insurance.
| Circumstance | Usual treatment | Reason |
|---|---|---|
| Routine disposal, no notice | Not spoliation | No duty had attached |
| Deletion after a demand letter | Serious | Duty clearly attached |
| Automatic deletion not suspended | Negligent | Failure to impose a hold |
| Deliberate destruction | Most severe | Intent to defeat a claim |
| Loss disclosed promptly | Mitigated | Candor and reduced prejudice |
The range of consequences
An adverse inference. The mildest common remedy, permitting a conclusion that the destroyed material would have been unhelpful, per adverse inferences.
Exclusion of related evidence. A party who destroyed material may be barred from relying on evidence about the same subject.
Deemed findings. In serious cases a decision-maker may treat a fact as established rather than merely permitting an inference about it.
Costs and financial sanctions. Many systems impose the cost of the resulting dispute on the party responsible for the destruction.
Determinative sanctions. At the extreme end, a claim or a defense may be struck out entirely, which is reserved for deliberate destruction.
Reputational effect. Beyond any formal remedy, a finding of this kind colors how everything else that party says is received afterwards.
A separate claim, sometimes. Some systems recognize destruction of evidence as a wrong in its own right, distinct from any consequence within the proceeding itself.
Almost every spoliation problem is an automatic process that nobody switched off. Message retention, backup overwriting and device replacement all continue destroying material after a duty attaches unless somebody actively stops them, and the instruction to do so is what a party will be asked to produce.
What determines the severity
State of mind. Deliberate destruction to defeat a claim is treated far more seriously than negligence, and negligence more seriously than accident.
Prejudice. How much the loss actually harmed the other party matters, and where the material is available elsewhere the prejudice may be slight.
Whether it was disclosed. A party who reports a loss promptly is in a different position from one whose destruction was discovered by somebody else.
Efforts to restore. Attempts to recover deleted material, even unsuccessful ones, bear on how the conduct is assessed.
The importance of the material. Destruction of the central record is treated differently from the loss of something peripheral.
The party's sophistication. An organization with legal advice and formal systems is held to a higher expectation than an individual acting without either.
Whether substitutes exist. Where the contents can still be established another way, the prejudice is limited and the remedy is usually correspondingly modest.
Practical steps
Impose a hold early. The cost of preserving too much is trivial compared with the cost of a spoliation argument, and the timing is what matters.
Put it in writing. A documented instruction, dated, identifying the material and the recipients, is the evidence that answers the allegation.
Suspend automatic processes. Deletion routines, overwriting backups and device replacement cycles all destroy material without anybody deciding to.
Tell the people who hold material. A hold that never reaches the individuals with the records achieves nothing, and distribution should be recorded.
Disclose losses promptly. Where something has already gone, saying so early is considerably better than the alternative, per explaining a gap honestly.
Do not delete anything after a dispute appears. The rule is simple enough, and the failures are almost always about material that nobody thought was going to count.
Preserve more than seems necessary. The cost of keeping material that turns out to be irrelevant is trivial next to the cost of an argument about something discarded.
Destroying records is ordinary and lawful until a duty to preserve attaches, and in most systems that duty arises when a dispute is reasonably anticipated rather than when proceedings begin.
The argument in these cases is almost always about timing. When the party knew or should have known that a claim was coming determines whether ordinary disposal became something else.
Consequences range from a permitted inference through evidential exclusions to determinative sanctions, and where a case sits on that range depends on state of mind, on prejudice and on candor.
The commonest failure is not deliberate destruction but an automatic process nobody suspended. Retention systems, backup cycles and device replacement continue running until somebody stops them.
The defense is preservation, imposed early, documented in writing, distributed to the people who actually hold material, and accompanied by prompt disclosure of anything already lost.
Points to carry away
- The duty to preserve usually attaches before proceedings begin.
- Routine destruction before that point is not spoliation.
- State of mind determines how severe the consequence is.
- Prejudice to the other party is a separate question.
- Preservation steps taken early are the whole defense.
Questions readers ask
When does the obligation to preserve evidence begin?
In most systems when litigation or a claim is reasonably anticipated, which is commonly well before anything is filed. A demand letter is an obvious trigger, and internal awareness of a serious problem likely to produce a claim can be enough on its own. The practical consequence is that the safe assumption is always the earlier date, because the cost of preserving material that turns out not to be needed is trivial next to the cost of defending an allegation that relevant records were destroyed after the duty attached.
Is routine document destruction a problem?
Not before a duty to preserve arises. Disposing of records on a documented retention schedule, applied consistently, is ordinary practice and is generally a complete answer where the destruction happened before anything was anticipated. It stops being safe the moment the duty attaches, at which point the ordinary policy has to be suspended for relevant material. Two things undermine the defense: a policy that was applied loosely in general, and one that cannot be evidenced because it was written afterwards.
What is the most common way parties fall into this?
Automatic deletion that nobody switched off. Message retention settings, backup rotation, log expiry and device replacement cycles all continue destroying material after a duty has attached, without anybody making a decision to destroy anything. Because no individual chose to delete, the conduct is usually treated as negligent rather than deliberate, which matters for the severity of the consequence but does not avoid it. The instruction suspending those processes is what a party will be asked to produce.
Sources
- Federal Rules of Civil Procedure — Rule 37(e), Failure to Preserve Electronically Stored Informationlaw.cornell.edu
- Legal Information Institute — Spoliation of Evidencelaw.cornell.edu
- Federal Rules of Civil Procedure — Rule 26, Duty to Discloselaw.cornell.edu
- Federal Rules of Evidence — Rule 1004, Admissibility of Other Evidence of Contentlaw.cornell.edu
- Legal Information Institute — Litigation Holdlaw.cornell.edu
- NIST — Guide to Integrating Forensic Techniques into Incident Responsecsrc.nist.gov
True Justice Record is a publication, not a law firm. This article states general rules and cites its sources; it is not advice about any particular case, and the law differs by state and changes over time.
More in When the Proof Does Not Exist
Delay, Memory and What Is Recoverable
Delay affects evidence unevenly. Volatile electronic material is overwritten within weeks, institutional records survive for defined retention periods, and public registers persist for decades. Memory declines continuously while confidence does not, which is why late accounts can be both detailed and unreliable. Knowing the decay rates determines what to secure first.
Preserving Proof Before It Is Needed
Evidence problems are usually created long before anybody anticipates a dispute. Keeping originals, documenting arrangements when they are made, using traceable payments, obtaining records while institutions still hold them and writing brief contemporaneous notes prevent most of the difficulties that later require reconstruction, secondary evidence or explanation.
Evidence Destroyed by Somebody Else
Where an opponent destroyed evidence after a duty to preserve arose, remedies including inferences, exclusions and sanctions become available. Where a third party or an accident destroyed it, the secondary evidence route applies instead. In every case the first task is proving what the material was, that it existed and that it is genuinely gone.