A Legal Hold Was Applied to the Wrong Prospect Record: Correct Preservation Without Deleting Evidence

A hold on the wrong prospect is still evidence about what happened in the outreach system. Treat the correction as a recorded change: identify the wrong subject. Preserve the original scope and audit history. Obtain authority, then apply the valid scope to the correct subject.

For U.S. federal civil litigation, Federal Rule of Civil Procedure 37 addresses lost electronically stored information that should have been preserved when reasonable preservation steps were not taken. That rule does not create a universal workflow for every business, but it makes a simple point practical: do not solve a scope mistake by making the evidence disappear.

• Pause routine deletion or cleanup for the affected record while the correction is assessed.
• Record the matter ID; wrong prospect ID; correct subject ID; hold ID; actor; timestamps; systems; and affected data locations.
• Keep the original hold notice, acknowledgement status, change history alongside exports and correction approval.

How can the team prove the hold was attached to the wrong subject?

Start with identifiers, not names alone. Compare the matter's approved preservation scope with the prospect record that received the hold. Capture the CRM record ID and LinkedIn outreach profile or campaign reference where available. Also capture the email address, account or company association, and timestamps that show when the hold was applied.

The proof should show both sides of the mismatch. One side identifies the valid subject and matter. The other identifies the wrong prospect and the exact hold action. Do not overwrite the wrong record to make it resemble the right one.

What evidence must remain preserved during correction?

Preserve evidence of the error and evidence of the correction. That includes the original hold configuration; the affected prospect record as it existed at review; the notice and acknowledgement trail; relevant system logs; exports made under the hold; and the approval that changed the scope.

Keep the content locations and criteria explicit. Microsoft explains that an eDiscovery hold can preserve content in specified locations, with an all-content or query-based scope, and that preservation continues until the location is removed from the hold or the hold is deleted. Its product guidance also says a new hold can take up to 24 hours to take effect. Microsoft's hold guidance applies to its eDiscovery environment, so use it as system-specific documentation, not as a rule for every outreach stack.

For outreach records, the preserved set may include CRM notes; connection-request history; messages; campaign settings; reply-routing records; exports; and linked collaboration messages. Preserve only what the authorized scope requires. Do not broaden a correction into an unsupervised collection exercise.

• Original hold ID, scope, creation time, editor, and status.
• Wrong prospect record snapshot and durable identifiers.
• Valid subject evidence and approved preservation scope.
• Notices, acknowledgements, exceptions, and escalations.
• Release approval, corrected-hold approval, and validation results.

Who can authorize the release and corrected scope?

The person who spotted the mistake should not quietly release it alone. Route the decision to the role or person with authority under the matter's legal-hold policy, such as the matter owner or legal reviewer, or a records owner or delegated eDiscovery administrator acting on documented approval.

Separate approval from execution. The reviewer approves release of the wrong scope and application of the correct scope. The system administrator implements those decisions and records the result. The outreach operator confirms which prospect record and outreach locations were affected, but should not guess the legal scope.

If Slack holds relevant outreach coordination, verify the preservation path before changing anything. Slack says its Discovery API is available to Org Owners on Enterprise plans for eDiscovery, archiving, and data-loss-prevention uses, with third-party applications able to collect messages and files. Slack's Discovery API guide describes that platform path, not a substitute for matter-specific authorization.

How should the team close the correction?

Close only after the correction register shows that the wrong scope was reviewed; the required evidence remains available; the valid subject has the approved hold; and the responsible reviewer has signed off. Record any system delay before relying on a new hold as active.

Run a final location check against the correction register. For systems with messaging records, preserve associated metadata and attachments where the approved scope requires them. The U.S. National Archives notes that electronic-message management can require capture of messages together with their metadata and attachments in a form that supports authenticity and availability. Its July 29, 2015 bulletin is guidance for U.S. federal agencies, but the recordkeeping principle is useful when designing a business workflow.

Keep the correction register with the matter record. It gives the team a repeatable account of what was wrong; what stayed preserved; who approved the release; and how the valid scope was applied.

• Reviewer confirms the wrong-subject evidence remains preserved.
• Administrator confirms the invalid scope was released only after approval.
• Administrator confirms the valid scope is active in the intended locations.
• Outreach owner confirms subject identifiers and affected records.
• Register contains dated approvals and the final verification result.