Back to Case Studies
Advertising Notice: This case study is a hypothetical illustration for informational purposes only. It does not describe an actual client matter, does not report past results, and does not predict similar outcomes. Every matter turns on its own facts, timing, documents, and law. Prior results do not guarantee a similar outcome.
Case StudieseDiscovery

When Auto-Delete Erased the Case: Preserving Chat Data After a Demand Letter (Hypothetical)

A hypothetical Jacksonville design-build firm let workplace-chat auto-deletion and a wiped company phone destroy months of the most relevant messages before counsel was engaged. A 30-year attorney shows how prompt suspension, metadata-preserving collection, reconstruction from the other side of each thread, and a sworn declaration defeated a spoliation motion.

5 min read
Jonathan D. Woods, Esq.

Jonathan D. Woods, Esq.

Licensed in Florida and Illinois. Jacksonville, Florida. FL Bar #0145017 | IL Bar #6230549.

Reviewed for accuracy by Jonathan D. Woods, Esq..

Florida-specific. Information is general and not legal advice.

Hypothetical scenario: Renée owns a Jacksonville design-build firm. A former project manager sent a demand letter claiming he was shorted roughly $28,000 in commissions on three finished jobs. The entire relationship — scope changes, price approvals, and an offhand promise about a bonus — had played out in text messages and the company's workplace chat workspace. Renée forwarded the letter to her insurer, told her office manager to "pull the messages," and kept the business running.

Two problems were already in motion. The chat workspace was on a plan set to purge messages older than ninety days, and nobody had changed it. The project manager's company phone had been wiped and reissued to his replacement the week he left. By the time Renée brought in counsel three months later, a large block of the most relevant messages was simply gone — and opposing counsel had begun drafting a spoliation motion arguing the destruction was deliberate.

How the hypothetical response was framed

  1. Counsel fixed the date the duty to preserve attached — the day the demand letter arrived — and immediately suspended the chat workspace's auto-deletion in writing with the platform administrator, stopping any further loss.
  2. Every remaining custodian's phone and account was preserved: forensic images of the devices still in the company's control, and a metadata-preserving export of the surviving chat channels and direct messages.
  3. The reissued phone was traced; the carrier and device had no recoverable data, and that dead end was documented rather than glossed over.
  4. Counsel reconstructed the missing period from the other side of each conversation — messages still on the phones of employees who had texted with the project manager — recovering much of what the purge had removed.
  5. The loss, its cause (a pre-existing routine retention setting), the date of remediation, and everything preserved were documented in a sworn declaration.

Why that mattered

In the hypothetical, the sworn record reframed the fight. Instead of "Renée destroyed evidence," the court saw a routine retention policy, a clear moment the duty attached, prompt suspension once counsel was engaged, and a good-faith reconstruction of what was lost. Florida courts distinguish between routine, good-faith operation of a retention system and the failure to stop it once preservation was required; the declaration put the firm on the right side of that line, and the adverse-inference request was denied.

The structural takeaway is that the damage was done in the first ninety days, by a setting no one chose with litigation in mind. The cheapest moment to preserve modern messaging data is the day the demand letter lands — by suspending auto-deletion and imaging the phones before anyone is reissued a device — not months later, after the routine has quietly done its work.

Florida legal updates by email

Subscribe for practical updates on Florida business law, estate planning, HOA disputes, and firm news. Double opt-in required.