Evidence Preservation and Litigation Holds

Scope and warning#

This roadmap explains preservation in general terms. Whether and when to send a preservation demand is a strategic decision best made with counsel, because the demand itself announces a dispute.

The factual situation this roadmap addresses#

The following situation is invented for illustration. A former dental assistant at a county juvenile facility expects a dispute over unpaid wages. Her text messages with a scheduler are on an old phone she plans to trade in, and she remembers that the facility's door-access logs show the hours she worked.

Governing law#

• California spoliation remedies must be analyzed in their procedural setting. Cedars-Sinai Medical Center v. Superior Court (1998) 18 Cal.4th 1 declined a stand-alone intentional first-party spoliation tort where the alleged loss was or reasonably should have been discovered before the underlying decision on the merits. Temple Community Hospital v. Superior Court (1999) 20 Cal.4th 464 rejected a separate tort for intentional third-party spoliation. Neither holding eliminates otherwise applicable statutory duties or evidentiary/discovery remedies. (Grade: Settled holdings; remedy, timing and later case treatment require application-specific review.)
• Federal Rule 37(e) requires a sequence of findings for lost ESI: the information should have been preserved in anticipation or conduct of litigation; a party did not take reasonable preservation steps; and it cannot be restored or replaced through additional discovery. Only then may a court order measures no greater than necessary to cure proven prejudice under subdivision (e)(1), or, upon a finding of intent to deprive, use the severe measures identified in (e)(2). Rule 37(e) addresses ESI, not every missing paper or physical item; it does not create the underlying preservation duty. (Grade: Settled rule text; application fact-specific.)
• Patient access is important but not unlimited. HIPAA generally gives individuals access to their protected health information in designated record sets, subject to specified exceptions (45 C.F.R. §§ 164.501, 164.524). California Health & Safety Code § 123110 supplies a related state-law access route. Neither authority should be characterized as an automatic right to every back-end EHR audit, security log or protected peer-review file; whether a record is included in a designated record set or otherwise accessible must be assessed separately. (Grade: Settled federal access scope; California text and record-specific application require authentication.)
• Other people's medical information is protected by California law (Cal. Civ. Code § 56 et seq. (Confidentiality of Medical Information Act)) and, depending on the source, federal law. (Grade: Settled.)
• Peer review. Evidence Code § 1157 protects specified proceedings and records of qualifying peer-review and medical-staff committees from discovery, subject to the statute's definitions and exceptions (Cal. Evid. Code § 1157). It is a protection from discovery, not a general evidentiary privilege, and it should not be assumed to cover every mortality review, quality file, utilisation review, medical-staff record or internal clinical investigation. (Grade: Settled as to the statute; scope fact-specific.)

Preservation is different from collecting everything

Preservation means taking reasonable steps to keep potentially relevant information from being lost, overwritten or materially altered once a preservation duty applies. It does not mean that a person may take records they have no lawful right to possess. A former employee, clinician, detainee, family member, county, contractor and lawyer can each face different access rules even when the same information may ultimately be relevant.

That distinction is especially important in healthcare. Patient charts, other patients' information, peer-review material, personnel data and proprietary systems can carry confidentiality or access restrictions. A preservation request can identify categories that should be retained without demanding that an unauthorized person copy them onto a personal device.

When preservation becomes important

Federal and California courts can impose evidentiary or procedural consequences when relevant evidence is destroyed after litigation is reasonably foreseeable, but the exact trigger and remedy are context-dependent. A prudent preservation review should begin when concrete facts make litigation reasonably foreseeable, which may precede a filed complaint. An agency charge, demand, serious incident or lawyer involvement can be important context, but none creates an automatic universal hold over every employee, patient or system; reasonably relevant sources, control, foreseeability and governing forum must be assessed.

For electronically stored information, Rule 37(e) begins only after evidence that should have been retained was lost through inadequate reasonable steps and cannot be restored or replaced in further discovery. Prejudice permits only curative measures no greater than necessary under (e)(1); intent to deprive is required for (e)(2) adverse-presumption, adverse-inference, dismissal or default measures. The rule neither creates the preservation duty nor decides whether an individual was authorized to collect documents. Paper/physical evidence and discovery-order violations call for different standards. Leon v. IDX Systems Corp., 464 F.3d 951 (9th Cir. 2006), predates the December 1, 2015 Rule 37(e) revision and should not be used to lower its modern ESI intent requirement. (Grade: Settled as to current rule text; precise sanction pathway fact-specific.)

The Ninth Circuit has also recognized courts' authority to address spoliation in appropriate circumstances. At the same time, California's Cedars-Sinai Medical Center v. Superior Court rejected a separate tort claim for intentional spoliation by a party when traditional litigation remedies are available. That does not make destruction harmless; it changes the form of the remedy.

What a litigation hold should identify

A useful hold is concrete enough that custodians know what to keep. It ordinarily identifies:

• the subject matter and relevant date range;
• known custodians and departments;
• email and messaging accounts;
• EHR/chart data and audit trails;
• scheduling and staffing systems;
• HRIS/personnel/payroll systems;
• grievance, incident and quality databases;
• policies and historical versions;
• contracts, amendments and performance reports;
• call logs, video and other systems with automatic deletion cycles;
• relevant local files, network drives, cloud workspaces and mobile-device data;
• routine deletion, overwriting or recycling processes that may need suspension.

A hold should be updated when new custodians or data sources are identified. A one-time email sent to a generic mailbox is not the same thing as a functioning preservation process.

Native files, metadata and audit trails

Printing a record can preserve what is visible while losing information about how the record was created, modified, routed or accessed. When lawful and practicable, preserve native electronic information or ensure the responsible organization preserves it. Examples include email headers, document metadata, EHR audit trails, scheduling-system histories, electronic grievance timestamps and policy version histories.

Do not alter a native file merely to make it easier to review. Work from a copy. Keep the original acquisition date and source. If a screenshot is necessary, record what application or webpage it came from, the date, and enough context to identify the record later.

A preservation request is not discovery

A preservation letter asks that information not be destroyed. It does not itself compel production. Public-record statutes, medical-record access laws, personnel-record statutes, subpoenas and formal civil discovery are separate mechanisms with separate limits. Conflating preservation with production can produce overbroad demands or create the mistaken impression that a recipient must immediately turn over material that may be privileged or confidential.

Similarly, an organization can preserve information it later contends is privileged, peer-review protected, irrelevant or outside the permissible scope of discovery. Preservation does not waive those objections.

Build a data-source map

For complex contractor/county matters, preserve the difference between custodian and system owner. A physician may send an email, but the email system may be administered by a corporate affiliate. A jail nurse may enter a chart note, while the county or contractor controls the EHR contract. A staffing report may be generated by a scheduling vendor but retained by another entity. The data-source map should therefore identify:

1. what the information is;
2. who created or used it;
3. which entity controls the system;
4. ordinary retention/overwrite cycle if known;
5. whether a hold was issued;
6. whether a copy has been lawfully obtained;
7. any privilege/confidentiality issue.

This becomes particularly important where CFMG, Wellpath-branded operations, county departments and third-party vendors appear in the same factual record. An administrator, author, legal owner, custodian, contract party and entity legally able to obtain a record may be different. Product branding, a shared domain or a bankruptcy notice does not alone establish that any named entity controls a specific source for litigation purposes; document the contract, retention administrator, migration history or testimony supporting each proposed link.

Elements of the claim#

Not applicable; preservation supports every claim. Three questions organise it: what already exists in the person's own hands; what exists only in others' hands; and how quickly each may disappear.

Potentially relevant defendants#

Not determined here. Preservation requests are addressed to whoever holds the records, which may differ from whoever is responsible (Roadmaps 003 and 004).

Administrative prerequisites#

None for keeping one's own records. Requests for personnel files, wage records, signed instruments and medical records follow statutory procedures (Cal. Lab. Code § 1198.5; Cal. Lab. Code § 226, subd. (b); Cal. Lab. Code § 432; Cal. Health & Saf. Code § 123110).

Limitation periods#

None stated here; see the deadlines roadmap.

Evidence#

Records to obtain#

Use the routes in the table above. Keep originals untouched and work from copies. Record when each request was made and when each response arrived (Roadmap 006).

Preservation checklist by evidence family

What not to do

Do not delete unfavorable material because it appears damaging. Do not edit a contemporaneous note to “clarify” it without preserving the original. Do not ask a coworker to forward confidential patient records to a personal account. Do not use another person's credentials to enter a system. Do not secretly remove original paper files. And do not assume that because a record might be discoverable later, it is lawful to take it now.

The preservation goal is defensibility: the important information still exists, its source is known, its integrity can be explained, and the method used to retain or request it did not itself create a new problem.

Favorable and adverse facts#

Favorable facts

• Records kept from the time of the events, with dates intact.
• Written requests made early, with proof of delivery.

Adverse facts

• Deleted messages or replaced devices.
• Records obtained outside lawful channels, which may create separate legal or professional problems.

Likely defenses#

A party disputing spoliation may show that litigation was not reasonably foreseeable, the particular record was not relevant or under its control, the requested source never existed, routine deletion occurred before any duty, reasonable steps were taken, or the content was restored or replaced from another custodian. A federal Rule 37(e)(1) remedy also requires prejudice; the severe (e)(2) remedies require intent to deprive. In California proceedings, the scope of a requested discovery sanction depends on the statutory/discovery pathway, including the routine good-faith ESI provisions in Code of Civil Procedure §§ 2023.030(f) and 2031.300(d), which expressly do not alter preservation obligations. None of these arguments authorizes intentional destruction once preservation is required.

Causation#

This page does not decide the causation of any underlying employment, patient-care or contract claim. For evidence-loss relief, a separate showing about the missing item, its relationship to disputed issues and applicable prejudice or intent standard may be essential. Missing evidence is not a substitute for proof of the underlying wrong.

Preservation requests should be specific enough to act on

A useful preservation communication identifies the dispute, date range, principal custodians and data categories without attempting to argue the whole case. For example, “preserve all versions of the referral policy in force from January through June, referral-queue data, audit histories, and communications concerning the identified referral” is more operational than “preserve everything related to bad medical care.” Specificity helps the recipient identify systems and automatic-deletion functions while avoiding needless capture of unrelated sensitive material.

For organizations, preservation is a process rather than a letter. Reasonable steps may include identifying custodians, suspending automatic deletion where necessary, preserving cloud and mobile sources, documenting collection, and following up when personnel leave or systems change. For individuals, reasonable preservation may be as simple as retaining lawfully possessed originals/native files, avoiding deletion, exporting an account before closure where lawful, and recording source information.

Ephemeral and short-retention systems deserve early attention

Some evidence can disappear on routine schedules long before formal discovery begins: CCTV, access logs, message platforms, call recordings, temporary audit views, web dashboards and contractor portals. If those sources could matter, identify them early and preserve through lawful requests. Do not assume that an organization acted wrongfully merely because a routine system overwrote data before any preservation duty arose; the timing and foreseeability questions matter.

Departing employees and account closures

Employment separation can trigger deletion, reassignment or archival of email, messaging accounts, shared drives and device data. A preservation plan should identify the account and relevant date range before closure. It should not encourage a departing worker to download restricted records. The organization controlling the system can preserve a defensible copy while maintaining confidentiality and access controls.

Medical records have change histories

Clinical records can include corrections, late entries, addenda, result timestamps, order histories and audit trails. A printed chart may not reveal all of them. When the timing or authorship of an entry matters, preserve or request the relevant audit information rather than assuming the face of a PDF tells the whole history. The same caution applies to electronic medication administration and referral systems.

Chain of custody is mostly good recordkeeping

For ordinary civil evidence, a practical chain-of-custody log can record: item ID, source, date obtained, person obtaining it, original filename/form, where the original is stored, and any conversion made for review. Hashing may be useful for large electronic productions, but most people gain more from disciplined source records than from technical procedures they cannot later explain.

Preservation can be reciprocal

A claimant should expect their own potentially relevant information to matter too: messages, social-media posts relevant to claimed damages, job-search records, photographs, calendars, medical information placed at issue, and communications about the disputed events. Preservation should not be treated solely as a demand imposed on the opposing side.

Damages and remedies#

Lost evidence may impair proof without independently establishing a damages claim. California Cedars-Sinai and Temple Community decisions reject the specified independent intentional-spoliation torts; evidentiary inferences, discovery sanctions, orders and other statutory or contractual remedies require separate legal predicates. For ESI in federal court, Rule 37(e) supplies the applicable lost-ESI measures, with its restoration/replacement, prejudice and intent limitations. California Code of Civil Procedure §§ 2023.030(f) and 2031.300(d) limit certain sanctions for routine good-faith ESI losses without undoing a preservation duty. Do not present those state provisions as a blanket immunity against all evidence destruction.

Preservation and proportionality are compatible

A litigation hold does not require every byte in an organization to be frozen forever. The task is to identify information that is potentially relevant to the dispute and take reasonable preservation steps. Date ranges, custodians and subject matter can be refined as facts become clearer. Overly broad holds can create cost and confusion; overly narrow holds can miss the system where the decisive record lives.

Preserve policy history, not just the current policy

Web portals and shared drives often display only the latest policy. When a policy/custom or standard-of-care issue depends on an earlier event, the historic version can be critical. Preserve superseded versions, approval records, change logs and the date a replacement became effective. The same principle applies to job descriptions, staffing matrices, organizational charts and contract amendments.

Automated logs can have especially short lives

Audit logs and system logs are sometimes stored separately from the underlying record and may have shorter retention periods. Examples include EHR access history, referral queue transactions, authentication logs and messaging retention. A preservation plan should identify the log as its own data source rather than assuming preservation of the visible record also preserves the audit trail.

Preserve evidence of unavailability too

For PLRA exhaustion, a claimant can sometimes litigate whether an administrative remedy was “available.” Preserve grievance forms, kiosk screenshots, rejection reasons, lockdown notices, language/access problems, disability-access issues, unanswered submissions and instructions provided by staff. The existence of a written grievance policy alone does not resolve what was available in practice; Ross v. Blake frames the federal availability inquiry.

Preservation notices should not make legal admissions unnecessarily

The communication can identify the dispute and categories to preserve without admitting that every requested item exists, is discoverable, belongs to the recipient, or is nonprivileged. Organizations routinely preserve broadly while later litigating relevance and privilege. A claimant likewise can preserve their own material without characterizing every item as favorable.

Revisit the hold at major events

Useful checkpoints include filing an agency charge or government claim, receiving a right-to-sue notice, filing suit, identifying new defendants, learning of a new data system, employee departure, corporate transaction, bankruptcy filing, or a court order changing the case's scope. Update the data map and custodians rather than assuming the first hold remains complete.

Discovery#

Preservation notices may be sent outside litigation, but enforceable production generally requires an applicable access statute, properly issued subpoena, discovery mechanism or court order; specific rules depend on the forum and stage. Counsel should assess sensitive records, privilege and nonparty burden (e.g., Fed. R. Civ. P. 26(b)(1), 26(c), 45). For protected health information in judicial or administrative proceedings, HIPAA permits certain disclosures under 45 C.F.R. § 164.512(e) with a suitable court order or prescribed notice/protective-order assurances; a subpoena alone does not universally authorize unrestricted transfer. Appropriate redaction and protective orders may still be necessary.

Preservation in a multi-entity operation

Where several entities share operational systems, a preservation request should not assume that one company possesses every data source. The county may hold custody logs and contract-performance records; a medical contractor may control EHR or staffing information; a payroll/management affiliate may hold employment data; a third-party vendor may host scheduling, messaging or learning systems. Identify likely custodians and system owners separately.

This is also why exact entity naming matters in a hold. A notice addressed only to a brand name can create ambiguity if several legal entities use that brand. Counsel can decide whether to send coordinated notices to multiple entities, but the factual groundwork should identify the legal names supported by the record.

Third-party sources can disappear independently

Outside hospitals, pharmacies, laboratories, staffing agencies, consultants and technology vendors can hold relevant information under their own retention schedules. A party's litigation hold does not automatically preserve every third party's records. Identify those sources early so counsel can evaluate appropriate preservation or record-request steps.

Privacy obligations continue during preservation

A preservation duty does not suspend HIPAA, CMIA, employment confidentiality, protective orders or professional duties. Organizations can preserve restricted information while controlling access. Individuals should avoid placing sensitive records into ordinary personal cloud accounts or forwarding them to unnecessary recipients. Security is part of preservation because a breached or altered record creates its own evidentiary and privacy problem.

Peer-review protection does not equal deletion permission

California Evidence Code § 1157 may shield qualifying peer-review committee proceedings and records from discovery; it does not automatically apply to every incident report or quality-improvement document. A lawful preservation plan should address possible § 1157 material without disclosing it or treating discoverability as settled. Discovery protection and retention duties are distinct; counsel should verify committee status, statutory exceptions and whether separately created source records are covered before claiming protection.

Preserve the fact of a hold and its implementation

Organizations commonly document when a hold was issued, to whom, which systems were covered, reminders, departures of custodians and collection steps. Those records can later demonstrate reasonable preservation efforts. Claimants should likewise preserve copies of preservation requests sent and delivery confirmation.

CFMG/Wellpath-specific relevance#

Relevant sources may sit with a professional corporation, management company, county, Wellpath debtor, successor or technology vendor. An inherited reference to the Wellpath bankruptcy Bar Date Notice (Dkt. 776, Jan. 2, 2025, implementing Dkt. 491, Dec. 18, 2024) is a document-identification lead, not verified proof of any named entity's present custody, legal control, successor liability or retention policy. Those propositions require contracts, system records, corporate documents and/or testimony; see Roadmap 004. The cited bankruptcy docket document was not independently authenticated in this editing pass.

Primary authorities#

Related roadmaps#

Chronology; finding counsel; correct defendant. Additional roadmaps are in development.

Companion worksheet (print-ready)#

Print-ready companion worksheets are in development.

Preservation end-state

A defensible preservation file should be able to answer: What categories were identified? Who controlled them? When was preservation requested or initiated? What automatic-deletion risks existed? What was actually collected or retained? What remains inaccessible? What confidentiality/privilege limits apply? If a category is later shown to be missing, those records allow counsel and the court to evaluate what happened rather than reconstructing preservation from memory.

The objective is not perfect preservation of every possible item. It is a reasonable, documented process proportionate to the dispute, with special attention to sources that are uniquely important or likely to disappear.

Preserve lawful source provenance, not unauthorized copies

A general preservation index should identify where each relevant category of record may lawfully be requested, not direct someone to retrieve records beyond their access rights. Patient information, peer-review materials, attorney communications and confidential employer systems may be restricted. A source inventory can document the known custodian and preservation concern without reproducing protected material on the public website. This also prevents a preservation request from being confused with authorization to bypass privacy, workplace or court rules.

Anticipated records and legitimate access restrictions

A preservation inventory may identify records that exist within an organization without asserting that a reader has a right to obtain or retain them. Audit logs, peer-review records, personnel files and medical records each have separate access rules. The index should record likely custodians, known retention practices and lawful methods of preservation or later production, while making clear that the public website will not receive protected material.

What this page cannot do#

It cannot say what any particular person must preserve, whether any record was lawfully obtained, or whether to send a preservation demand.