Cross-Domain Patterns That Signal Legal Risk

Risk appears in the sequence

Separate events become a legal pattern when they are seen together.

Cross-domain patterns that signal legal risk rarely announce themselves in a single complaint. They show up as separate events — a comp claim, a leave request, a safety report, a performance write-up — that only look dangerous when you see them together.

Retaliation rarely announces itself. It appears as a series of separate decisions that add up when the full sequence is visible.

Five patterns worth seeing early

Protected activity. Then a shift. Then adverse action.

The Sudden Discipline

An employee files a workers’ comp claim, returns to modified duty, then receives a write-up for an old issue. Across multiple employees, the timing stops looking coincidental and starts signaling retaliation.

Claim → return → old discipline

The Accommodation Breakdown

An ADA accommodation is approved but never fully implemented. When multiple employees experience the same failure and later complain or leave, the issue is systemic—not isolated.

Approval → manager resistance → complaint

The Leave-to-Termination Pipeline

An employee returns from FMLA leave to a changed schedule, reassigned work, and eventual termination. A higher post-leave termination rate reveals interference that one case cannot.

Leave → changed conditions → termination

The Safety Complaint Silence

A documented hazard goes unresolved while the reporting employee loses hours, is reassigned, or receives unrelated discipline. Repetition across reports signals OSHA retaliation risk.

Report → no correction → adverse action

The Concentrated Manager

When complaints, comp claims, accommodation requests, and terminations cluster under one manager—and protected employees leave at a dramatically higher rate—the concentration itself becomes the signal.

Multiple domains → one manager → abnormal rate

Why fragmented systems miss it

Every event looks ordinary in its own system.

The sudden-discipline pattern lives between workers’ comp and performance documentation. The leave-to-termination pattern requires FMLA dates and later employment actions. The concentrated-manager pattern spans terminations, complaints, accommodations, and safety reports.

These questions require a single view across domains. When the data is scattered, the sequence disappears.

The “should have known” standard

Documentation is not the same as a compliance program.

If the data exists and the pattern is present, monitoring is what turns records into controls.

The DOJ Compliance Program Guidance asks whether organizations monitor compliance risks, analyze data to identify patterns, and maintain controls that detect violations. Cross-domain correlation is what makes those answers real.

What the data should answer

Four questions that turn scattered records into an early-warning system.

Workers’ comp

How often does adverse action follow return to work—and which managers have unusual rates?

FMLA

How often are employees terminated within 12 months of leave, compared with the baseline?

Safety

Which complaints produce corrective action, and which reporters face adverse action within 90 days?

Across domains

Which employees have multiple protected activities, and what happened after each one?

If these questions can be answered because the data is analyzed together, there is a compliance program. If they cannot, there is only hope—and hope is not a control.

Retaliation doesn’t usually look like, “We fired you because you filed a workers’ comp claim.” It looks like a series of separate decisions that, when you see them together, add up to retaliation.

Pattern 1: The Sudden Discipline

Employee files a workers’ comp claim. Six weeks later, returns to modified duty. Two weeks after return, gets written up for a mistake that happened three months ago. Nobody mentioned it at the time. One write-up? Could be coincidental. Three employees who filed comp claims all getting written up for old issues shortly after returning? That’s a pattern of retaliation. And that pattern is actionable liability.

Pattern 2: The Accommodation Breakdown

Employee requests an ADA accommodation. HR approves it. Manager is supposed to implement it. Three weeks later, the accommodation either wasn’t implemented or was implemented half-heartedly. Manager says it’s “too disruptive.” Employee files an EEOC complaint. If five employees with documented accommodations all experienced implementation failures, and three of them eventually filed complaints or quit, that’s a compliance failure across the board — not isolated incidents.

Pattern 3: The Leave-to-Termination Pipeline

Employee requests FMLA leave, takes it, returns. Things are different. Schedule changed. Manager seems cold. A project got reassigned. It feels like they’re being pushed out. Within 90 days of return, terminated. One case? Could be legitimate. But if 20% of employees who take FMLA leave are terminated within a year, and the general termination rate is 10%, you have a pattern. And that pattern is FMLA interference.

Pattern 4: The Safety Complaint Silence

Employee reports a safety hazard. It’s documented. The hazard is serious. But nothing happens. The hazard isn’t fixed. Meanwhile, that employee is reassigned. Their hours are cut. They get written up for unrelated issues. Multiple safety complaints, none of which get addressed, all followed by adverse action against the reporter? That’s a pattern of retaliation against safety reporters. That’s OSHA liability.

Pattern 5: The Concentrated Manager

Over 18 months, one manager has: five employees file safety complaints, four workers’ comp claims, three ADA accommodations requested, six employees terminated. Every employee who filed any kind of complaint or protected activity got terminated within 12 months. The general termination rate in the company is 8%. For this manager, it’s 40%. That’s a manager who retaliates against complaints. And that’s a company liability, because now you know about it.

Why These Patterns Are Invisible in Fragmented Systems

Each of these patterns requires looking across multiple systems. The sudden discipline pattern requires correlating workers’ comp claims with performance documentation — two different systems. The leave-to-termination pattern requires tracking FMLA approvals, leave taken, return dates, and subsequent employment actions. The concentrated manager pattern requires pulling termination data, complaint data, accommodation requests, and safety reports and analyzing them by manager. These questions require a single view across domains. They’re invisible when data is scattered.

The Legal Standard for “Should Have Known”

If you have access to data, and the pattern is there, but you’re not looking for it, that’s negligence. The DOJ Compliance Program Guidance specifically asks: do you monitor for compliance risks? Do you analyze data to identify patterns? Do you have controls in place to detect violations? If you’re not correlating data across systems, the answer to all three is no. You have documentation. You don’t have a program.

What You Should Be Asking

On workers’ comp: How many employees who file comp claims get adverse action within 90 days of return? Is that rate different from employees who don’t file claims? Which managers have the highest rate of adverse action against returning employees?

On FMLA: How many employees who take FMLA leave get terminated within 12 months? Are there managers or departments with unusual rates?

On safety: How many safety complaints result in corrective action? How many employees who file safety complaints get adverse action within 90 days?

Across domains: Are there employees with multiple types of protected activity? Did those employees get adverse action? If you can answer these questions because you analyze your data, you have a compliance program. If you can’t — you don’t have a program. You have hope. And hope isn’t a compliance program.