Who is legally liable when an automated retention rule deletes a record that should have been kept?

Automation does not transfer accountability

A common misconception is that when software deletes a record automatically, the system or its rule “made the decision.” Legally, that framing rarely holds. Retention and disposition obligations attach to the organization that owns the records, not to the tool that executes a rule. An automated workflow is simply carrying out a policy that people designed, approved, and configured. If that policy or its implementation was wrong, the organization remains answerable for the loss.

So the practical answer is: liability flows to the record-owning organization, and within it, to the roles that govern recordkeeping — typically leadership, the records or information-governance program, and legal counsel. The vendor or the algorithm is almost never the liable party for the underlying records obligation.

How responsibility is usually distributed

Several roles can share exposure depending on what went wrong:

• The organization bears the primary legal duty to retain records under applicable laws, regulations, and schedules.
• Records and IG staff are responsible for accurate retention rules, classification, and disposition approval.
• Legal/compliance must ensure litigation holds and regulatory requirements override automated disposition.
• IT is responsible for configuring and testing automation so it behaves as the policy intends.

A breakdown in any of these — a miscoded rule, a missing hold, an untested schedule — is an organizational failure, not a machine’s.

Why holds and schedules matter most

Most improper deletions trace back to two gaps: a record was on a retention schedule that was too short or misapplied, or a legal hold was not enforced against the automated process. When litigation, audit, or investigation is reasonably anticipated, the duty to preserve overrides routine disposition. Failure to suspend automated deletion in that situation can expose the organization to spoliation findings, sanctions, or regulatory penalties.

Reducing the risk

• Validate retention rules against authoritative schedules before activating automation.
• Build legal-hold enforcement that blocks automated deletion.
• Keep audit logs of every automated disposition action.
• Require human review for high-value or permanent records.

For deeper context on managing automated systems and digital recordkeeping, see electronic records.

The bottom line: automation executes decisions, but people and organizations own them — and own the liability when those decisions delete what the law required them to keep.