Auto-Deletion and a Product-Liability Hold at Precision Parts
At Precision Parts Inc., email is automatically deleted after 60 days and employees may keep local .pst files. A product-liability suit involving brake calipers was filed 11 days ago. Outside counsel sent a hold notice to 12 named engineers and the CEO, but not to the 34-member engineering distribution list, the plant quality manager, or a contract metallurgist. The plant manager deleted his .pst file after the notice because 'it was mostly junk.' Backup tapes are recycled every 28 days; the next re-use is in 6 days. A draft failure-analysis report sits on a shared drive with 90-day versioning. A 2019 retention schedule says engineering project files are kept 7 years. The company has 3,000 employees. The legal department asks the records manager to 'make sure we are covered.'
1. What immediate preservation actions should the records manager take, and what is the reasoning behind each?
Read the worked answer
The trigger is the filed lawsuit plus counsel's hold notice, so preservation must become irreversible and broader than the 12 names. First, suspend the 60-day auto-delete for all engineering, quality, plant, procurement, and executive accounts likely to hold caliper records; waiting for a perfect custodian list will destroy evidence. Second, stop the 28-day tape recycling immediately and segregate tapes covering the caliper program and relevant custodians; do not restore everything, but preserve the tapes so counsel can decide. Third, preserve the plant manager's device and any remnants of the deleted .pst through a defensible forensic process, and document the deletion. Fourth, place the shared drive and its 90-day version history under hold so the draft report and prior versions are not overwritten. Fifth, reissue the hold to the engineering distribution list, the quality manager, and the contract metallurgist, and ask counsel about former employees and suppliers. Document each action with date, custodian, source, and chain of custody. The principle is that deleted and recycled data cannot be restored by later good intentions.
2. How should the records manager evaluate whether the legal hold scope is adequate?
Read the worked answer
The 12-name list is too narrow because it defines custodians by title rather than by role in design, testing, supplier approval, manufacturing, and failure analysis. A defensible scope starts with the claims and relevant time period, then identifies people who created, received, approved, or investigated caliper records. That includes design engineers, the test lab, quality assurance, procurement, plant management, field service, and the contract metallurgist. It also includes non-custodial sources: shared drives, quality systems, email distribution lists, and backups. The 34-member distribution list may include peripheral recipients, so counsel should decide whether to hold all members or use a targeted questionnaire to identify relevant knowledge. The records manager should build a custodian-by-data-source matrix, interview key custodians, and update the matrix as new sources emerge. Scope is iterative and should be documented. Over-preservation can be narrowed later; under-preservation after notice creates spoliation risk.
3. What should be done about the plant manager's deletion, and what controls should follow?
Read the worked answer
The deletion after notice is a serious spoliation risk. The records manager should immediately notify counsel, preserve the device and any logs or backup remnants, and avoid independent cleanup that could overwrite evidence. Counsel may require a forensic examination and may decide whether disclosure is needed. The organization should document the timeline: when the hold was issued, what the manager understood, when he deleted the file, and what was recovered. Remediation should address root causes, not just the individual: auto-deletion must be suspended automatically for all hold custodians; hold notices should require acknowledgment; local .pst files should be restricted or centrally captured; and hold compliance should be monitored. Training alone is insufficient. The records manager should not assume backups will save the day, because the 28-day recycling means some data may already be gone. Document corrective actions to show good-faith remediation.