A legal hold in a DAM works like a legal hold anywhere else \u2014 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.<\/p>
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 \u2014 if the loss was intentional \u2014 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.<\/p>
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 \u2014 not the asset’s normal owner \u2014 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.<\/p>","protected":false},"excerpt":{"rendered":"
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.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"What is a legal hold in a DAM context?","answer":"A directive triggered by anticipated or actual litigation, an investigation, or an audit that overrides normal deletion or expiration rules for a specific, named set of assets."},{"question":"What does amended FRCP Rule 37(e) require once a duty to preserve attaches?","answer":"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."},{"question":"Does Rule 37(e) offer any protection for automated deletion?","answer":"Yes, a safe harbor for information lost through the routine, good-faith operation of an electronic system \u2014 but that protection depends on the system being configured correctly, including a hold-override."},{"question":"What kinds of DAM assets typically become relevant to litigation?","answer":"Dated campaign materials, product imagery, and marketing claims are routinely responsive in advertising, IP, and employment disputes."},{"question":"What's the failure pattern legal hold in a DAM is meant to prevent?","answer":"A routine automated retention or cleanup job deleting an asset days after it became relevant to a dispute, because the workflow had no hold-override mechanism."},{"question":"Who should be able to release a legal hold?","answer":"Legal or compliance staff, not the asset's normal owner \u2014 release authority stays separate from day-to-day asset management."}],"checked_date":"2026-08-07","sources":[{"statement":"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.","source_name":"Duke Judicature \u2014 analysis of amended FRCP Rule 37(e)","url":"https:\/\/judicature.duke.edu\/articles\/amended-rule-37e-whats-new-and-whats-next-in-spoliation\/","checked":"2026-08-07"}],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"","seo_description":"","noindex":false,"related":[2410,2555,2548,2554,2552,2549],"definition":"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":"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 \u2014 dated campaign materials, product imagery, marketing claims \u2014 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.","example_rows":[{"field":"Trigger","values":"Litigation notice, regulatory inquiry, IP dispute over a campaign asset"},{"field":"DAM behavior","values":"Suspends scheduled deletion\/expiration; freezes metadata and version history; logs all access"},{"field":"Release","values":"Hold lifted only by legal\/compliance sign-off, not by the asset owner"}],"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 \u2014 exactly the failure pattern the current federal rule on spoliation sanctions is built around.","deep_link":""},"silo":[24],"class_list":["post-2585","glossary","type-glossary","status-publish","hentry","silo-glossary"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2585","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/types\/glossary"}],"version-history":[{"count":3,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2585\/revisions"}],"predecessor-version":[{"id":3553,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2585\/revisions\/3553"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=2585"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=2585"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}