Spoliation of Electronic Evidence: How Lost Data Becomes a Sanctions Risk for Texas Businesses (2026)

Spoliation is the destruction, alteration, or failure to preserve evidence that a party should have kept for pending or reasonably anticipated litigation. In Texas state court, the Texas Supreme Court's decision in Brookshire Bros. v. Aldridge set the framework: a duty to preserve arises when a party knows, or reasonably should know, that there is a substantial chance a claim will be filed and that evidence in its possession will be material. In federal court, Rule 37(e) governs lost electronically stored information (ESI). The details differ, but the practical message is the same for your firm: the duty can start well before a complaint is served, and courts look at what you actually did to preserve data. This article is general information, not legal advice, so confirm specifics with your counsel.

Most spoliation we see in Houston-area businesses is accidental. Normal IT operations quietly destroy data while everyone is focused on the dispute. The usual culprits include:

• Automated retention and deletion rules in Microsoft 365 that purge mail, Teams chats, and OneDrive files on schedule.
• Device refresh and reimaging when a departing employee's laptop goes back into the spare pool.
• Mobile phones and text messages that sit outside any company system, especially on personal devices.
• Disappearing-message apps and personal messaging used for business conversations.
• Backup rotation that overwrites the only copy of a mailbox or file share.
• Account deprovisioning that deletes a former employee's mailbox license and its contents after 30 days.

Each of these is a normal, defensible practice until a duty to preserve attaches. After that moment, the same routine can become a sanctions problem.

Under federal Rule 37(e), a court asks whether ESI that should have been preserved was lost because a party failed to take reasonable steps, and whether it can be restored or replaced. If the loss prejudiced the other side, the court can order measures no greater than necessary to cure that harm. Harsher penalties, such as an adverse-inference instruction or dismissal, require a finding that the party acted with intent to deprive. Texas courts similarly weigh the culpability of the spoliating party and the prejudice to the opponent before choosing a remedy. For an SMB, the takeaway is that documented, reasonable effort is your best protection. A written hold, a dated IT action log, and a clear record of what was suspended carry real weight when a judge asks what you did.

You do not need an enterprise legal department to be defensible. You need a repeatable process that connects your counsel, your leadership, and your IT provider. A workable sequence looks like this:

1. Name a trigger owner. Decide who tells IT, in writing, when a demand letter, subpoena, agency inquiry, or credible threat of suit arrives.
2. Issue a written legal hold to the relevant custodians and to IT, describing the matter, the date range, and the data types to keep.
3. Suspend auto-deletion for those custodians. Our step-by-step guide to a litigation hold in Microsoft 365 shows how to place mailboxes, OneDrive, and Teams content on hold.
4. Freeze device and account changes. Pull departing employees' laptops and phones from the reimage queue and stop mailbox deletion.
5. Capture mobile and collaboration data. Texts, Teams chats, and Slack channels are routinely requested; see how they are handled in eDiscovery for Teams and Slack data.
6. Log everything. Record who did what and when, so you can show reasonable steps later.
7. Re-send and release. Remind custodians periodically and release the hold only when counsel confirms the matter is closed.

A sensible retention schedule reduces spoliation risk and cost at the same time. When you keep only what you need, there is less to preserve and review, and routine deletion under a documented, consistently applied policy is generally easier to defend than ad hoc cleanups. Pair a written schedule with the ability to override it instantly when a hold is issued. Our data retention guide for Texas businesses covers how to set schedules by record type, and the economics of keeping the volume of ESI manageable are explored in our post on controlling eDiscovery costs. Newer data sources matter too: AI assistants now generate content that may be discoverable, as discussed in eDiscovery and Copilot AI content.

This week, ask one question: if we received a demand letter this afternoon, could IT freeze the right mailboxes, chats, and devices within a day? If the answer is no or maybe, start by writing a one-page hold procedure, confirming which Microsoft 365 retention settings are active, and checking that your offboarding process does not auto-delete accounts. LayerLogix helps Texas SMBs and law firms put this in place through our eDiscovery and content search services and Microsoft 365 managed services. If you are a firm advising clients, see our overview of IT support for Houston law firms and our eDiscovery guide for Microsoft 365.

• Managed IT services in Houston
• Managed IT services in Cypress
• Managed IT services in Sugar Land