Reference Glossary
Legal hold (digital asset)
A directive that suspends normal deletion or modification of specific assets and their metadata because they are, or may become, relevant to litigation, investigation, or audit.
Why it matters in a DAM
Once litigation is reasonably anticipated, US federal courts can sanction a party for losing electronically stored information it had a duty to preserve, and DAM assets — dated campaign materials, product imagery, marketing claims — are routinely responsive in advertising, IP, and employment disputes. A DAM's automatic retention or expiration rules have to be overridable per-asset for a legal hold, or the system's own scheduled cleanup becomes the mechanism that destroys evidence.
A worked example
Common mistake
An automated retention or asset expiration workflow runs without a hold-override mechanism, so a routine cleanup job deletes an asset days after it became relevant to a dispute — exactly the failure pattern the current federal rule on spoliation sanctions is built around.
A legal hold in a DAM works like a legal hold anywhere else — it’s a directive, triggered by anticipated or actual litigation, an investigation, or an audit, that overrides normal data lifecycle rules for a specific, named set of records. What’s DAM-specific is what those records typically are: not just documents and emails, but marketing claims, dated campaign creative, product photography, and the metadata and version history attached to them, all of which can be directly responsive in advertising disputes, trademark and copyright claims, or employment litigation involving marketing materials.
Amended Federal Rule of Civil Procedure 37(e) sets the federal standard for what happens when electronically stored information that should have been preserved is lost. It requires that once a duty to preserve attaches, a party takes reasonable steps to preserve relevant evidence; if it fails to and the information can’t be recovered, courts can order remedial measures, and — if the loss was intentional — instruct a jury that the lost material was unfavorable to that party, or dismiss the case outright. The rule does include a safe harbor for information lost through the routine, good-faith operation of an electronic system, but that protection depends on the system having been configured correctly in the first place, which is exactly where a DAM’s automated retention rules become a legal risk if they can’t be paused per-asset.
Practically, a legal hold in a DAM needs to do more than stop deletion: it should also freeze version history and metadata edits on the held assets, log every access to them, and require that only legal or compliance staff — not the asset’s normal owner — can release the hold. Assets under hold also need to survive normal expiration workflows, since a hold and a usage-rights expiration date are separate controls that can both apply to the same asset at once.
Frequently asked
What is a legal hold in a DAM context?
A legal hold is a directive triggered by anticipated or actual litigation, a regulatory investigation, or an audit that suspends normal deletion, expiration, and retention rules for a specific, named set of assets. Instead of applying broadly, it targets exactly the files identified as relevant to the matter, keeping them intact and unaltered until the responsible legal or compliance team formally releases the hold.
What does amended FRCP Rule 37(e) require once a duty to preserve attaches?
A party must take reasonable steps to preserve relevant evidence; if it fails and the information can't be recovered, courts can order remedial measures or, for intentional loss, adverse-inference instructions or dismissal.
Does Rule 37(e) offer any protection for automated deletion?
Yes. Rule 37(e) provides a safe harbor for information lost through the routine, good-faith operation of an electronic system, meaning a DAM's ordinary automated retention or cleanup jobs are not automatically treated as spoliation. That protection isn't automatic, though — it depends on the system being configured correctly, including a working hold-override mechanism that actually suspends deletion for assets placed under an active hold, and on the deletion genuinely being routine and in good faith.
What kinds of DAM assets typically become relevant to litigation?
Dated campaign materials, product imagery, packaging mockups, and marketing claims are routinely responsive in advertising, intellectual-property, and employment disputes. Assets showing when a claim was made public, who created or approved a design, or how a product was represented at a specific point in time often become central evidence — which is why version history and approval metadata, not just the final file, can matter as much as the asset itself.
What's the failure pattern legal hold in a DAM is meant to prevent?
A routine automated retention or cleanup job deleting an asset days after it became relevant to a dispute, simply because the workflow had no hold-override mechanism to stop it. In this pattern, the system isn't malicious — it's just doing what it was built to do, on schedule. But because nobody paused it for the specific assets under hold, the routine deletion itself becomes an act of spoliation, turning an ordinary maintenance task into a legal liability.
Who should be able to release a legal hold?
Legal or compliance staff, not the asset's normal owner, project lead, or day-to-day content manager. Release authority is deliberately kept separate from ordinary asset management so that the person under pressure to free up storage, close out a campaign, or reuse a slot can't also be the one deciding whether the underlying litigation or investigation risk has passed. Only the team tracking the legal matter itself is positioned to know when a hold can safely be lifted.
Sources
- Amended Federal Rule of Civil Procedure 37(e) governs sanctions for failure to preserve electronically stored information once a duty to preserve has attached, while providing safe harbor for information lost through the routine, good-faith operation of an electronic information system. checked 2026-08-07 — Duke Judicature — analysis of amended FRCP Rule 37(e)