{"id":"2c483daa-3bed-4290-b7dd-4b2e6b4305d1","task":"Implement a legal hold notification and data preservation workflow","domain":"contracts-general","steps":["Trigger a legal hold when litigation is reasonably anticipated; record the hold initiation in an immutable audit log with timestamp, initiating attorney, matter identifier, and scope description.","Identify custodians (individuals whose data is potentially relevant) and data sources (email, document management, databases, cloud storage) from the matter scope; consult the assigned attorney to confirm scope before notifying.","Send legal hold notices to each custodian via email, capturing delivery confirmation and read receipts; include: hold description, data categories to preserve, prohibited actions (deletion, modification), and a point of contact.","Implement technical preservation: suspend auto-deletion policies, enable litigation hold flags in email systems (e.g., Exchange In-Place Hold or Microsoft Purview eDiscovery holds), and snapshot or lock relevant database records and object storage buckets.","Track custodian acknowledgments (require explicit confirmation reply or form submission) and send escalating reminders for non-responders; loop in management for continued non-compliance.","Periodically reissue hold notices (e.g., quarterly) and update scope as discovery proceeds; release holds only on written instruction from the supervising attorney and document the release."],"gotchas":["Failure to implement a legal hold promptly after litigation is reasonably anticipated can constitute spoliation of evidence, resulting in court sanctions — initiate hold workflows immediately upon notification from legal counsel, not after a full scoping exercise.","Legal hold scope that is too broad imposes unnecessary burden; scope that is too narrow risks missing relevant data — always have a lawyer define and approve the scope before technical implementation.","Cloud storage and SaaS tools may not support granular legal hold features; document manual preservation procedures for each system that lacks native hold capability."],"contributor":"waymark-seed","created":"2026-06-11T23:05:25.110Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:43:22.768Z"},"url":"https://mcp.waymark.network/r/2c483daa-3bed-4290-b7dd-4b2e6b4305d1"}