Legal Services Offshore research · legal-support-governance

What share of litigation hold reminders reach the named custodian on time?

A reminder-timing study for litigation holds that separates a delivery failure from a missing acknowledgment and a departed custodian.

Published · 4 sources

What share of litigation hold reminders reach the named custodian on time? research illustration

Research context

This research brief is designed for legal operations planning. Use the findings to ask better workflow questions. Test any proposed process against the firm’s jurisdiction, professional duties, systems, and client commitments. Treat every local result as a starting point for review rather than a universal benchmark.

Question and scope

This study asks what share of litigation hold reminders reach the named custodian within the scheduled window. It treats the reminder as the unit and the custodian record as the evidence. The scope is one firm, one set of active holds, and a fixed reminder period. The result describes that setting and should not be read as a measure of preservation compliance.

The unit is one reminder tied to one custodian and one hold. A reminder is eligible when the schedule names a due date and a recipient. Reminders for custodians who have left are included if the schedule still expects an acknowledgment. Record the inclusion rule before reviewing.

Record whether the hold notice and the reminder use the same custodian list. A reminder sent from an older list can reach the wrong person. Report the list version with the delivery result. The two records should point to the same custodian.

Definitions and evidence standard

Define on-time delivery as a reminder sent to the named custodian on or before the scheduled date through the approved channel. A reminder sent to a manager instead is a different event unless the schedule allows it. A reminder that bounced or went to an inactive address is not delivered. Record the distinction.

Define acknowledgment separately from delivery. A delivered reminder with no response is not acknowledged. Use the reply, the system receipt, or a dated note from the custodian as evidence. If the custodian confirms by phone, record who took the call and when. The study should not treat a delivery log as a response log.

Record whether the reminder was sent by a person or an automated system. An automated reminder may be consistent but easy for the custodian to ignore. A personal reminder may carry more weight but depend on one sender. Report the sender type with the delivery result.

Sampling and measurement

Select holds and reminder cycles from the window and freeze the list before review. Include different custodian roles and different reminder channels. If the firm uses more than one hold system, report each separately. Record the number of reminders and the number of custodians.

Measure the number delivered on time, the number delivered late, the number not delivered, and the number acknowledged. Report the counts by channel and by custodian role. Add the number of reminders sent to a departed custodian. A single on-time rate hides which failure occurred.

If a reminder is sent to a distribution list, record the list name and the owner. A list can hide a departed custodian or a person who should not receive the hold. Report list-based reminders separately from named-recipient reminders. The distinction matters for both delivery and confidentiality.

Findings and interpretation

Present the distribution before suggesting a cause. A cluster of late deliveries in one channel may mean the address list is stale. A cluster of unacknowledged reminders may mean the message is unclear or the custodian is not reading it. A cluster around departed custodians may mean the offboarding step is missing.

Read the reminders behind the largest gaps and compare them with the custodian list. Record whether the address was current, whether the message asked for a reply, and whether a follow-up happened. The pattern should point to a specific control, such as an address check or an escalation rule. Record the source and the date with the entry.

Compare the on-time rate with the number of custodians in each hold. A large hold has more recipients and more chances for a delivery failure. Report the count beside the rate. Do not compare a small hold with a large one as if they carried the same coordination burden.

Compare the on-time rate with the number of reminders in each cycle. A cycle with several reminders has more chances for a late send. Report the count beside the rate. Do not compare a single reminder with a multi-reminder cycle as if they carried the same burden.

Limitations

The study measures the reminder record, not whether the custodian preserved the documents. A delivered and acknowledged reminder does not prove that the hold was followed. It also cannot decide whether the hold scope was adequate. Those questions need a substantive review by the responsible lawyer.

The window may include a system migration or a custodian change that affects delivery. If the reminder schedule changed during the period, the cycles may not be comparable. Record these limits with the result and keep the delivery logs with the method. Record the source and the date with the entry.

If a custodian acknowledges the hold but asks a question, record the question and the answer. An acknowledgment with an open question is not fully resolved. Report the open question separately from the delivery result. Keep the evidence beside the decision in the file.

Practical next step

Choose one repair that matches the most common failure, such as an address check, a clearer acknowledgment request, or a departed-custodian step. Write the change, the owner, and the start date. Define the measure that will show whether it helped, using the same delivery and acknowledgment categories. Test it on the next reminder cycle.

Keep the before and after cycles separate so the comparison is honest. Record the reminders that were excluded and why. Review the result with the lawyer who owns the hold and the person who sends the reminders. If the change does not help, record that result too.

Test the revised reminder with one custodian group before applying it to every hold. A group that uses email may not respond to a system prompt. Record the group and the result. The next cycle can compare the same delivery categories.

Comparing channels

Email, system prompts, and manager meetings may produce different delivery and acknowledgment patterns. Report the count and the rate for each channel, and label small groups as descriptive only. A channel that looks worse may simply be used for custodians who are harder to reach. Record the source and the date with the entry.

If one channel shows a consistent delivery gap, check whether the address list is maintained for that group. If acknowledgment is low, check whether the message asks for a specific reply. Compare the process, not the custodian. The next study can test a channel-specific reminder before changing the whole schedule.

Keep the delivery logs and custodian list in a restricted workspace. Publish only the aggregate counts and the channel categories. If a client asks for the result, describe the method and the control rather than sharing names. Keep the evidence beside the decision in the file.

Keep the delivery logs and custodian list in a restricted workspace. Publish only the aggregate counts and the channel categories. If a client asks for the result, describe the method and the control rather than sharing names. Ask the named owner to confirm the record.

What the evidence does not show

The study does not establish that a late reminder caused a loss of documents or a discovery problem. It also does not measure whether the custodian understood the hold. Those questions need a separate review. Timing is a control observation, not a compliance finding.

Do not use the result to promise a client that every reminder will be acknowledged or that no record will ever be lost. Do not publish custodian names or matter details. Keep the sample size, the definitions, and the review decisions with the result. If the firm needs a legal conclusion, it should ask counsel.

Ask the lawyer whether a missed acknowledgment should trigger a preservation audit. The answer may depend on the custodian and the records. Record the decision rule with the result. Not every missed reminder carries the same risk.

Using the result in a client conversation

A client may ask how the firm manages litigation holds, and the study supports a careful answer. Describe the window, the number of reminders, the delivery and acknowledgment categories, and the control that was added. Do not say that every custodian will respond or that every record will be preserved. Explain that the measure covers the reminder record and that the lawyer reviews the substance.

If the client asks for a commitment, offer a process commitment such as an address check, a clear acknowledgment request, and an escalation rule. Record the commitment and the measure that will show whether it was met. Keep client-specific details out of any public write-up. Record the source and the date with the entry.

Keep the delivery logs and custodian list in a restricted workspace. Publish only the aggregate counts and channel categories. If a client asks for the result, describe the method and the control rather than sharing names. Keep the evidence beside the decision in the file.

Sources and method

Open each source to confirm its scope, publication date, and applicability before relying on it for a legal workflow decision.

  1. U.S. Courts, Federal Rules of Civil Procedure
  2. American Bar Association, Model Rules of Professional Conduct
  3. GAO, Standards for Internal Control in the Federal Government
  4. NIST Cybersecurity Framework 2.0

Related research

Bring the messy task list

We will help turn it into one clear legal support role.

Share the work, tools, hours, and review needs. The next step is a practical staffing scope, not a public rate card.