When Your Employer Cuts Your Digital Access: Retaliation, Spoliation, and the Modern Workplace Record

The shape of workplace records has changed dramatically over the past decade. The traditional employment record (personnel file, payroll records, performance reviews stored in HR) still exists, but it is now a small fraction of the documentary record an employer or employee may need in litigation. The real record lives in Slack channels, Google Drive folders, Microsoft Teams conversations, Salesforce activity logs, Asana task histories, project management notes, calendar invitations, video conference recordings, and industry-specific tools like Hudl (for athletic coaches), Epic (for healthcare), Veeva (for life sciences), and dozens of others. When an employer revokes an employee's access to those tools after the employee has engaged in protected activity, the revocation often serves two simultaneous functions: it constitutes potential retaliation under federal and state employment statutes, and it positions the employer to control or destroy the evidence that would prove or disprove the employee's claims. This article walks through the legal frameworks that govern both functions, with practical attention to what employees and their counsel should preserve when access is at risk.

The Evolving Workplace Record

A decade ago, a workplace harassment investigation might have produced fifteen emails and a personnel file. Today, the same investigation might involve hundreds of Slack messages across multiple channels, a Google Drive history showing edits to shared documents, calendar metadata showing when meetings occurred and who attended, Zoom recordings of those meetings, Asana task assignments revealing workflow patterns, and industry-specific records that may be central to the case. For an athletic coach, the Hudl video library and scouting data may be the documentary backbone of a year of work. For a salesperson, Salesforce records show every customer contact, every opportunity stage change, every commission-eligible event. For a healthcare provider, Epic charting records show every patient interaction.

The implication is that workplace evidence is now distributed across many systems, much of it controlled exclusively by the employer. When the employee leaves the company (voluntarily, involuntarily, or even temporarily through suspension or administrative leave), access to those systems often terminates immediately. The employer's IT department deactivates accounts, recovers devices, and disables access tokens. Whatever evidence existed in those systems is now under the employer's exclusive control. The employee who has not preserved copies in advance is now dependent on the employer's good faith and on civil discovery procedures to recover what may have been days or years of their own work product.

The Duty to Preserve

Federal and Ohio law impose a duty to preserve evidence whenever litigation is reasonably foreseeable. The duty arises before the lawsuit is filed, before a litigation hold notice is sent, and often before the employer has been served with any formal demand. The Sixth Circuit has consistently held that the duty arises when the employer knows or reasonably should know that the evidence may be relevant to anticipated litigation (Beaven v. U.S. Dept. of Justice, 622 F.3d 540 (6th Cir. 2010)). For employment cases, the duty often arises with the first complaint of discrimination, harassment, retaliation, or unpaid wages, regardless of whether litigation is explicitly threatened.

The duty extends to electronically stored information (ESI), including the contents of workplace SaaS tools. Federal Rule of Civil Procedure 37(e) governs sanctions for failure to preserve ESI. The rule distinguishes between negligent loss (which can result in measures to cure the prejudice, including specific evidentiary inferences) and intentional destruction with intent to deprive the other party of the evidence (which can result in adverse inference instructions to the jury, dismissal of claims, or default judgment). Ohio recognizes spoliation of evidence as a separate cause of action under Smith v. Howard Johnson Co., 67 Ohio St.3d 28 (1993), with elements including pending or probable litigation, knowledge by the spoliator, willful destruction, and disruption of the case.

Title VII and R.C. 4112 Retaliation Framework

Title VII and R.C. 4112 prohibit retaliation against employees who engage in protected activity. The Supreme Court in Burlington Northern & Santa Fe Railway v. White, 548 U.S. 53 (2006), held that the standard for an actionable adverse action in the retaliation context is whether the action would "have dissuaded a reasonable worker from making or supporting a charge of discrimination." The standard is broader than the materially adverse action standard for substantive discrimination claims and reaches actions that affect terms and conditions of employment less directly.

Revocation of digital access to systems the employee needs to perform their job, to maintain professional relationships, or to demonstrate the value of their work product can satisfy the Burlington Northern standard in appropriate cases. The revocation often affects compensation indirectly (a salesperson cut off from Salesforce cannot demonstrate the pipeline supporting a quarterly bonus), professional standing (a coach cut off from Hudl loses access to recruiting tape and game film), or the ability to defend against subsequent allegations (an employee facing performance allegations cannot access the email or message history that would document their actual performance). Where the revocation occurs in the temporal window immediately after protected activity, the retaliation inference is often strong.

ADA Retaliation

The ADA includes a separate retaliation provision (42 U.S.C. Section 12203) that prohibits retaliation against individuals who have opposed unlawful practices or participated in ADA proceedings. The Burlington Northern materially-adverse-action standard applies in the ADA context as well (Rorrer v. City of Stow, 743 F.3d 1025 (6th Cir. 2014)). Where the employee has requested an accommodation or filed an ADA complaint and the employer responds by removing the digital tools that enabled the accommodation or that document the employee's performance, the ADA retaliation framework can apply alongside the Title VII or R.C. 4112 framework.

FLSA Retaliation and the Records Problem

The FLSA prohibits retaliation against employees who file wage-and-hour complaints. The unique feature of FLSA cases is that the records the employee needs to prove their claim (time records, project assignments, communications about work hours) are typically controlled by the employer. Where the employer revokes the employee's access to those systems shortly after the wage complaint, the employee loses the ability to prove the unpaid hours. The interaction between the retaliation prohibition and the underlying records problem makes digital access revocation in FLSA cases particularly problematic from the employer's perspective.

Title IX Retaliation in the Education Context

Title IX prohibits retaliation against employees of educational institutions who participate in Title IX proceedings or otherwise oppose practices unlawful under Title IX. The Sixth Circuit applied this framework in Doe v. Mercy Catholic Medical Center and related cases. For coaches, faculty, and educational employees who file Title IX complaints and then face revocation of digital access (to Hudl, to learning management systems, to faculty intranets, to library databases that contain the employee's research), the access revocation often serves as both retaliation and pre-emptive evidence control. The Hudl pattern is particularly stark in athletic departments: a coach who has built years of scouting tape, recruiting materials, and game film loses immediate access to the work product that defines their professional value, and the institution gains exclusive control over the records that would document the coach's actual performance.

Spoliation Sanctions Under FRCP 37(e)

FRCP 37(e), as amended in 2015, governs sanctions for failure to preserve ESI. The rule distinguishes two categories. Where ESI is lost due to negligence and cannot be restored, the court may "order measures no greater than necessary to cure the prejudice" (Rule 37(e)(1)). Where the loss is due to "intent to deprive another party of the information's use in the litigation" (Rule 37(e)(2)), the court may presume the lost information was unfavorable, instruct the jury that it may or must presume so, or dismiss the action or enter default judgment.

The intent prong is often the analytical battleground. Where the employer revoked digital access shortly after a protected complaint and the access revocation resulted in loss or alteration of evidence, the inference of intent can be strong. Where the employer issued a formal litigation hold immediately upon revoking access, took steps to preserve the contents of the systems before access was cut, and maintained those records throughout the litigation, the intent inference is weaker. The employer's preservation conduct matters significantly. Employers who revoke access without first preserving the contents face substantially greater Rule 37(e) exposure than employers who preserve carefully.

State-Law Spoliation Claims

Ohio recognizes spoliation of evidence as an independent tort under Smith v. Howard Johnson Co., 67 Ohio St.3d 28 (1993). The elements are: (1) pending or probable litigation involving the plaintiff; (2) knowledge by the spoliator that the litigation is pending or probable; (3) willful destruction of evidence designed to disrupt the plaintiff's case; (4) actual disruption of the plaintiff's case; and (5) damages proximately caused by the willful destruction. The tort applies to both first-party defendants (the employer in an employment case) and third parties who destroy evidence relevant to litigation.

The Ohio spoliation tort offers a separate remedy from the procedural sanctions available under FRCP 37(e). Where the procedural sanctions provide adverse inferences and other in-litigation consequences, the tort claim provides an independent damages remedy. Both can be pursued in appropriate cases.

The Tools That Recur

The specific digital tools that come up in employment cases vary by industry but follow recognizable patterns:

• Communication systems. Email (Gmail, Outlook), workplace chat (Slack, Teams), video conferencing (Zoom, Google Meet). These systems contain the day-to-day communications that document the workplace context surrounding the dispute.
• File and document systems. Google Workspace (Drive, Docs, Sheets), Microsoft 365 (OneDrive, SharePoint), Dropbox. These systems contain work product, draft documents, version histories, and the documentary backbone of much workplace litigation.
• Project and task management. Asana, Jira, Trello, Monday.com, Notion. These systems show task assignments, workflow patterns, project ownership, and the day-to-day operational record.
• CRM and sales tools. Salesforce, HubSpot, Microsoft Dynamics. For sales employees, these systems document every customer interaction, every opportunity stage change, and every commission-eligible event.
• Industry-specific tools. Hudl (athletics), Epic (healthcare), Veeva (life sciences), AutoCAD (architecture and engineering), MyCase (legal). These systems are often the documentary heart of the employee's professional output in the relevant field.
• HR systems. Workday, BambooHR, ADP. These systems contain performance reviews, compensation history, leave records, and the formal HR record.

For any employment dispute where digital evidence may matter, the analysis should identify which of these systems contained relevant information, whether access has been revoked, what preservation steps were taken, and what evidence may have been lost.

The Practical Reality

For employees who have engaged in protected activity and reasonably anticipate adverse employer response, several practical steps preserve options:

• Document the complaint context contemporaneously. Save copies of the complaint, the response, and any communications about the complaint to personal storage (email forwarded to personal account, screen captures, document downloads where permitted). Do this before any access revocation occurs.
• Identify the systems that contain relevant work product. For each system the employee uses regularly, note what the system contains and what the employee would lose if access were revoked.
• Preserve work product where lawful. Some employer policies prohibit downloading or copying of confidential information; others permit personal copies for legitimate purposes. The employee should know their employer's policies and act within them. Where lawful, contemporaneous copies of the employee's own work product preserve evidence in case access is later revoked.
• Issue preservation demands through counsel where appropriate. A formal preservation letter to the employer (often sent immediately after the protected activity or as soon as termination is anticipated) establishes the duty to preserve as a matter of record and reduces the employer's later ability to claim ignorance of the preservation obligation. The letter should identify the specific systems and types of records that must be preserved, not just generic categories.
• Document access revocations in real time. If access to specific systems is revoked, document the date, time, and method of revocation, and identify the specific records that the employee can no longer reach. This documentation often becomes important evidence in subsequent spoliation analysis.

The Bottom Line

Workplace records have moved from filing cabinets to cloud-based SaaS platforms, and the employment dispute now turns on documentary evidence that the employer controls more completely than ever before. When an employer revokes an employee's digital access after the employee engages in protected activity, two distinct legal frameworks apply: the retaliation prohibitions under Title VII, R.C. 4112, the ADA, the FLSA, Title IX, and other statutes, and the preservation and spoliation rules under FRCP 37(e) and Ohio common law. Employees facing access revocation should preserve work product contemporaneously where lawful, document the revocation, and engage counsel early so that preservation demands can be issued to the employer before evidence is lost. The framework rewards employees who anticipate the issue and document early; it punishes employees who learn about it only after the evidence is gone.