When a dispute becomes reasonably foreseeable, ordinary deletion and cleanup routines may become risky. A legal hold is not simply an email marked urgent. It is an instruction tied to people, systems, records, and continuing preservation. An administrative or legal assistant can coordinate the evidence trail, but counsel must define scope and decide when the duty begins and ends.
The decision this research supports
The business is deciding what coordination can be delegated after counsel authorizes a hold. The assistant may maintain custodian lists, distribute approved notices, track acknowledgments, schedule reminders, collect system-owner confirmations, and preserve an audit trail. Counsel retains trigger, scope, privilege, search terms, collection method, sanctions analysis, and release decisions.
Federal Rule of Civil Procedure 37(e) addresses electronically stored information that should have been preserved in anticipation or conduct of litigation and is lost because reasonable steps were not taken. The Advisory Committee notes emphasize reasonableness and recognize that perfection is often impossible. The operational inference is to document proportionate, repeatable steps rather than promise that no byte can ever be lost.
Rule 26 frames discovery around relevance and proportionality. That does not authorize an assistant to narrow a hold. It means counsel should communicate a usable scope so custodians and system owners can act. Ambiguity should be escalated and recorded, not resolved through improvised deletion exceptions.
Create a controlled matter record
Assign a stable matter identifier and record counsel owner, business owner, date authorized, notice version, scope summary, custodians, systems, preservation actions, open questions, and status. Restrict access because the record may reveal disputes, strategy, or personal information. The general project tracker is rarely the right location.
Use version control for every notice and update. Preserve the exact approved text, distribution list, send time, delivery result, acknowledgment, and follow-up. If counsel changes scope, issue a new version and identify what changed rather than silently editing the original.
Separate administrative status from legal conclusions. Fields such as “notice delivered,” “acknowledgment pending,” and “system owner confirmed” are observable. Fields such as “preservation complete” or “custodian not relevant” require an authorized decision and should name the decision maker.
Build the custodian and system map
Start with counsel’s list and verify current contact information, employment status, manager, location, and known systems. Ask system owners about mail, chat, shared drives, local devices, mobile applications, archives, backups, and third-party platforms. The assistant records responses; counsel decides whether a source is within scope.
Pay special attention to departing staff and role changes. Offboarding can trigger mailbox deletion, device reassignment, and license removal. Link the hold workflow to HR and IT change notices so counsel can act before routine deletion occurs. Do not tell HR to delay an employment decision; route the preservation risk.
A system map should record owner, retention behavior, export capability, legal-hold feature, vendor contact, and last confirmation. Avoid copying sensitive content into the map. The map is a routing tool, not a shadow evidence repository.
Distribute notices without altering counsel’s instruction
Send only the approved notice through the approved channel. Do not paraphrase scope in reminder emails, answer substantive questions, or reassure a custodian that a source is excluded. Route questions to counsel and record that the question was raised without copying privileged advice into a broad log.
Track delivery failures, out-of-office responses, acknowledgments, and nonresponses. Use a reminder cadence authorized by counsel and escalate persistent nonresponse to the named owner. A checked box is not proof of comprehension, but it is evidence that the instruction reached the custodian and prompted a response.
Provide accessible alternatives and a confidential contact path. A custodian may need language, disability, or technology support. The assistant can coordinate the accommodation without exposing the matter to people who do not need to know.
Track preservation actions at the source
For each system, record the authorized preservation action, actor, time, scope reference, result, and verification evidence. Examples include applying a mailbox hold, suspending deletion, preserving a device, or exporting a defined dataset. The assistant should not perform a technical action outside approved access.
Preserve native logs and confirmations rather than screenshots alone when the platform offers them. Hashes, export manifests, and immutable storage may be appropriate when technical owners direct them. The assistant can reconcile counts and filenames but should not claim forensic integrity without the required expertise.
When a vendor controls data, record the request, contractual reference, recipient, ticket number, response, and any limitations. Escalate expiring retention windows and inaccessible accounts immediately. Silence is not confirmation.
Monitor changes for the life of the hold
A hold is continuing. Schedule periodic custodian attestations and system-owner checks at a frequency counsel selects. Trigger an out-of-cycle review for departure, leave, device replacement, migration, acquisition, or a material scope update.
Maintain an exception queue for failed delivery, refusal, uncertain source ownership, unavailable exports, deleted accounts, and preservation limits. Age the queue and identify the decision owner. Do not close an item because the responsible person is busy.
If potentially relevant information may have been lost, preserve the facts and notify counsel promptly. Do not investigate blame, reconstruct records, or change ordinary logs unless instructed. Early, faithful reporting is more useful than an optimistic status.
Release only on documented authorization
Counsel decides when a hold or part of it ends. The assistant can prepare the custodian and system list for review, but must not release a hold because a case appears inactive or a calendar deadline passed. Retention and privacy policies resume only after authorized release.
Issue a versioned release notice, track delivery, and record technical release actions. Some records may remain subject to another hold or ordinary retention requirement. System owners should confirm the disposition rule before deletion resumes.
Close the administrative record with the authorization, notices, acknowledgment summary, exception resolution, system confirmations, and lessons learned. Limit retention of the coordination file according to counsel’s instruction.
Pilot the workflow before a real emergency
Create templates for the matter record, custodian table, notice log, system map, exception queue, and release checklist. Review them with counsel, IT, HR, and records owners. A tabletop exercise using a fictional matter will reveal missing contacts and deletion windows.
Train the assistant on the bright lines: never decide scope, never edit approved legal language, never copy matter details into general tools, never promise completeness, and never release without written authorization. Provide named escalation contacts and alternates.
After the exercise, correct routing gaps and test access restrictions. The niche conclusion is that coordination is delegable when legal judgment stays visibly with counsel and system actions stay with authorized owners.
Methodology and limitations
This review translates public guidance into an administrative workflow. It is not legal advice, does not determine which law applies to a particular organization, and does not replace advice from the business owner, counsel, security lead, privacy lead, or another qualified specialist. The cited sources were checked on October 22, 2026. Requirements, agency interpretations, and technology can change, so the owner should schedule a review rather than treating this article as a permanent rulebook.
The method is a structured reading of primary government sources followed by a task analysis: identify the decision owner, inputs, permitted assistant actions, stop conditions, evidence, and review sample. It does not measure outcomes at AssistantStaffing or promise that a control will prevent every error. The conclusions are operational inferences from the cited guidance, clearly separated from the source facts.
A small organization may combine roles, but it should not erase independent review. When one person prepares and executes a task, another authorized person should review a risk-based sample or every high-risk exception. Record the reviewer, date, evidence considered, and correction. That modest trail makes the workflow testable without inventing a bureaucracy that the team cannot maintain.
Sources
- Federal Rules of Civil Procedure, Rule 26 - Legal Information Institute, Cornell Law School. Checked October 22, 2026.
- Federal Rules of Civil Procedure, Rule 37 - Legal Information Institute, Cornell Law School. Checked October 22, 2026.
- Records Management Guidance for Litigation Holds - National Archives and Records Administration. Checked October 22, 2026.
Next step
Review AssistantStaffing's executive assistant roles and the related analysis of retention disposition evidence. Bring the current process and a redacted example to a free role consultation so scope, access, and review boundaries can be defined before delegation.
