Legal Services Offshore blog

Build a litigation hold acknowledgment log that records each custodian response

A custodian acknowledgment log that ties every response to a hold version, a reminder date, and a named owner while the lawyer keeps the preservation decision.

Build a litigation hold acknowledgment log that records each custodian response editorial illustration
Defined workflowAttorney review gatesPractical escalation

Key takeaways

A litigation hold is only useful when the firm can show that each custodian received it and answered. The acknowledgment log records the custodian, the hold version, the date sent, the date answered, and the person who followed up. A hold that was emailed but never acknowledged is an open question rather than a completed step. The log turns that question into a visible item with an owner.

The log should point to the hold notice itself instead of summarizing it. Custodians may receive different instructions for different data sources, so the notice version matters. Record the version identifier and the scope covered by that version. A later reader should be able to match the acknowledgment to the exact instruction the custodian received.

A reminder is part of the process and not evidence of a problem. Write the reminder date and the channel used before the first follow-up is sent. If the custodian does not answer, the log should show the next escalation step and who owns it. Silence should never be recorded as agreement.

Close the hold with a release note when the matter ends or the hold is lifted. The release should name the custodian, the date, and the authority for the change. Keep the original acknowledgment in the record even after the release. The history is what shows the firm acted in sequence.

Name the custodians before the hold goes out

Build the custodian list from the matter file, the interviews already recorded, and the key documents that identify authors and recipients. Write the basis for each name so the list does not look arbitrary. A person named only because a colleague remembered them is a weak entry. The support worker can compile the list and cite the source for each name.

Separate people who hold potentially relevant material from people who are only witnesses. A witness may need an interview later but does not need a hold instruction today. Record the category beside each name and the reason for it. The responsible lawyer confirms which category applies before the notice is sent.

Include former employees, contractors, and third parties who may still hold firm data. Their contact details are often missing from the current directory, so record the last known address and the source. A departed custodian needs a different delivery plan. The log should show that the difference was considered.

Assign one named owner for each custodian before the notice goes out. The owner confirms delivery, records the response, and sends reminders. A list with no individual owner tends to stall at the first unanswered message. Record the owner and the date the assignment was made.

Record the acknowledgment as a dated event

Record the notice version, the send date, the channel, and the address used for each custodian. These fields let a reviewer compare what was sent with what the custodian says they received. A forwarded notice is not the same event as a direct send. Keep the original message with the log entry.

Capture the acknowledgment date and the method the custodian used to answer. A reply email, a signed form, and a verbal confirmation are different evidence with different weight. Record the method in plain words rather than a code. Attach the reply or a contemporaneous note to the entry.

Distinguish an acknowledgment of receipt from a confirmation that the custodian will preserve the material. Some replies say only that the message arrived. Record any qualification the custodian added, such as a question about a device or an account. The lawyer decides whether the response is sufficient.

When a custodian answers by phone, write a short note with the date, the time, and the person who took the call. Send a written confirmation the same day so the record matches the conversation. Record the confirmation in the log. A verbal answer with no written trace is difficult to rely on later.

Separate a reminder from an escalation

Set the reminder interval in advance and have the responsible lawyer approve it. A fixed interval prevents the team from either chasing too often or waiting too long. Record the interval in the log instructions rather than in a personal calendar. The rule should be short enough to apply without a meeting.

Log each reminder with its date and channel, and note whether the message changed. Repeating the same reminder without a new detail rarely produces a response. A second reminder can restate the deadline and offer help with a technical question. Record what was different about each attempt.

Escalate when the interval passes with no answer, and name the person who receives the escalation. The escalation should go to the lawyer who owns the matter rather than to a wider group. Record the decision that follows, including a decision to wait. A documented decision is better than an undocumented silence.

Treat non-response as an exception in the log instead of an assumed compliance. The exception should carry a follow-up date and an owner. Review open exceptions at the weekly check so they do not disappear. A hold program is measured by the questions it can still answer.

Handle a custodian who leaves or changes role

Record the departure date and the person who takes over the custodian role. A new custodian needs the same notice and the same acknowledgment as the original. Update the log without deleting the earlier entry. The history should show both people and the handover date.

Confirm what happens to the departed custodian's accounts and devices before access is removed. The data may need to be preserved even when the account is closed. Record the instruction and the person who carried it out. Account closure and record preservation are separate decisions.

Ask the new custodian to confirm the material they hold, not only that they received the notice. A role change can mean the new person holds different files. Record the confirmation and any gap the person identifies. The lawyer decides whether the gap needs a further step.

Keep the departed custodian on the list until the lawyer approves removal. Removing a name early can hide an unresolved question. Record the approval and the date. The log should show why the name was removed and who decided.

Close the hold with a release record

Write a release note that names the custodian, the matter, the date, and the authority for lifting the hold. A release without an authority is a gap that a later reviewer will notice. Record the lawyer who approved it and the instruction that was given. The note should be short enough to complete on the day of the decision.

Confirm that routine deletion may resume under the retention schedule after the release. The schedule still governs, and a release does not authorize immediate destruction. Record the retention date that now applies. The records owner confirms the next step.

File the acknowledgment and the release together in the matter record. A reader should see the whole sequence without opening a mailbox. Record the storage location and the date it was filed. The pair is stronger evidence than either document alone.

Report any custodian with an open acknowledgment at matter close. An open item that travels into a closed file tends to be forgotten. Record the exception and the new owner. The closing note should state what remains unresolved.

Review the log at a fixed cadence

Review the open acknowledgments each week and confirm that each has an owner and a next date. Look for entries that were sent but never followed up. A short weekly review catches most gaps before they become preservation problems. Record the reviewer and the date of the check.

Compare the log against the hold register to make sure no matter is missing a custodian list. A register that lists the matter but not the people is only half the record. Record any discrepancy and the person who will resolve it. Do not correct one list without checking the other.

Sample a few entries and confirm that the notice version in the log matches the notice in the file. A version mismatch is easy to create when a hold is updated. Record the result of the sample and any correction. The sample is process evidence, not a performance score.

Review the reminder interval and the escalation path with the lawyer who owns the holds. A path that worked for one matter may not fit another. Record the change and the date it takes effect. The next hold should start with a clearer instruction.

A supervised support lane can maintain the custodian list, send reminders, and keep each acknowledgment with the hold notice while the lawyer decides what must be preserved. case file management support.

Sources

  1. American Bar Association, Model Rules of Professional Conduct

    Used for supervision, confidentiality, competence, and communication boundaries in legal support work.

  2. U.S. Courts, Federal Rules of Civil Procedure

    Used for the litigation, service, and production workflow context that these controls support.

  3. GAO, Standards for Internal Control in the Federal Government

    Used as a general reference for documented ownership, review evidence, and exception handling.

  4. NIST Cybersecurity Framework 2.0

    Used for access control, monitoring, and recovery language around shared legal records.

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.