Custodian Interviews and Data Mapping for Litigation

When an organization reasonably anticipates litigation, two early activities determine whether its discovery effort will be defensible: identifying the people who hold relevant information, and mapping where that information actually lives. Custodian interviews answer the human question of who knows and who created relevant material, while data mapping answers the systems question of which repositories, applications, and devices store it. Done well, the two reinforce each other—interviews surface systems the IT inventory missed, and the data map gives interviewers concrete repositories to ask about. Done poorly, or not at all, they leave gaps that surface later as spoliation accusations, sanctions exposure, or expensive re-collections.

These activities sit at the front of the discovery lifecycle, immediately after a duty to preserve attaches and a legal hold is issued. They translate a broad obligation to preserve potentially relevant electronically stored information (ESI) into a specific, documented plan: named custodians, identified data sources, defined date ranges, and reasoned decisions about scope. The goal is not to collect everything, but to make proportional, well-reasoned choices and to be able to explain those choices to a court, an opposing party, or an auditor long after the fact.

Why Custodian Interviews Matter

A custodian is any individual who possesses, controls, or has knowledge of information relevant to a matter. Identifying the right custodians is foundational because almost every downstream decision—what to preserve, what to collect, what to search—flows from that list. The interview is the structured conversation that confirms a person’s relevance and, just as importantly, develops the factual picture of how they work.

Effective interviews go beyond “Are you involved in this matter?” They explore how the custodian communicates (email, chat platforms, text messages, voicemail), where they save documents (network drives, cloud storage, local folders, personal devices), what applications they use for their role, and whether they collaborate with shared mailboxes, distribution lists, or departing colleagues whose data may have been reassigned. Interviewers should ask about date ranges, project code names, key counterparties, and informal terminology, because that vocabulary later shapes search terms and reveals sources a generic inventory would never capture—a side database, a personal note-taking app, a recorded meeting archive.

Interviews must be documented. A contemporaneous record of who was interviewed, when, by whom, and what sources they identified becomes essential evidence of a reasonable, good-faith effort if the adequacy of preservation is ever challenged.

Data Mapping: Knowing Where Information Lives

A data map is an inventory of an organization’s information assets: the systems and repositories where ESI resides, who owns and administers each one, what kinds of records it holds, how long data is retained, and how it can be preserved and collected. Where custodian interviews are people-centric, data mapping is systems-centric, and a mature program maintains a baseline map continuously rather than rebuilding it under deadline pressure for every new matter.

A useful data map typically captures:

• Repositories and applications — email systems, file shares, collaboration and messaging platforms, line-of-business databases, content and records management systems, and cloud services.
• Ownership and administration — the business owner and the technical administrator who can actually export or hold the data.
• Retention and disposition — how long each source keeps data, including auto-deletion rules, mailbox quotas, and ephemeral-messaging settings that can quietly destroy relevant ESI.
• Backup and archival behavior — whether backups are accessible, their rotation cycle, and whether they constitute the only copy of certain records.
• Accessibility — whether data is reasonably accessible or sits on legacy or backup media that may be costly or burdensome to restore.

This last point ties directly to proportionality. The Federal Rules of Civil Procedure frame discovery in terms of relevance and proportionality and recognize that some ESI is not reasonably accessible because of undue burden or cost. A data map lets counsel make and substantiate those arguments with facts rather than assertions.

How the Two Work Together

Custodian interviews and data mapping are iterative, not sequential. Interviews validate and enrich the map—custodians routinely name a shared drive, a chat channel, or a personal device that no inventory listed. The map, in turn, prompts sharper interview questions: if the map shows the marketing team uses a particular collaboration platform, the interviewer can confirm whether the custodian used it for the matter at hand. Each pass narrows uncertainty and tightens the defensible scope of preservation and collection.

This interplay also exposes the riskiest sources early: auto-deleting messaging tools, departed-employee accounts pending deletion, and bring-your-own-device arrangements. Catching these before data is lost is the difference between a manageable preservation effort and a spoliation crisis.

Defensibility and the Records Foundation

The legal standard is reasonableness and good faith, not perfection. Courts and authoritative guidance—such as the principles developed by The Sedona Conference—consistently reward parties who can show a thoughtful, documented, proportional process even when some data ultimately proves unavailable. Maintaining a written methodology, interview notes, the data map itself, and a clear chain of custody for collected material is what transforms activity into demonstrable defensibility.

Crucially, all of this is far easier in an organization with strong underlying records management. A current records inventory, an enforced retention schedule, and consistent classification mean the data map is mostly built before litigation arises, and that routine disposition has already reduced the volume of stale, low-value data. Sound recordkeeping practices—reflected in NARA guidance and in standards like ISO 15489—are not separate from e-discovery readiness; they are its precondition. Organizations that treat information governance as ongoing discipline find that custodian interviews and data mapping become confirmation exercises rather than emergency excavations.

For broader context on how these activities fit the discovery lifecycle, see the e-discovery topic hub.