Note: This article is for general informational purposes only and is not legal advice. Employers, employees, and managers dealing with wage-and-hour disputes should consult qualified employment counsel before making decisions that could turn a workplace headache into a courtroom fireworks show.
Introduction: The FLSA Retaliation Net Just Got Wider
The Ninth Circuit has again reminded employers that retaliation law is not a game of legal hide-and-seek. In Hollis v. R&R Restaurants, Inc., the court expanded how the Fair Labor Standards Act retaliation provision can apply when a worker complains about wage-and-hour violations and then loses a work opportunity connected to the same business network.
The headline is simple but powerful: under the FLSA, the alleged retaliator does not always have to be the worker’s direct employer. The worker also does not necessarily need to be employed by the retaliating entity at the exact moment the adverse action happens. That may sound like a tiny procedural tweak, but in employment law, tiny tweaks often arrive wearing steel-toed boots.
The decision matters for employers, managers, business owners, staffing agencies, franchised operations, entertainment venues, restaurants, gig-style workplaces, and any organization where workers move between related entities. It also matters for employees who fear that speaking up about unpaid wages, misclassification, overtime, or minimum wage issues could quietly shut doors elsewhere.
What Happened in Hollis v. R&R Restaurants?
The case involved Zoe Hollis, a dancer who sued a Portland venue known as Sassy’s. The lawsuit alleged that dancers had been misclassified as independent contractors and denied protections tied to wages and hours under the Fair Labor Standards Act. After Hollis filed the lawsuit, a person connected to both Sassy’s and another venue, Dante’s, canceled Hollis’s scheduled performance at Dante’s.
That cancellation became the center of the retaliation claim. The lower court granted summary judgment against Hollis on the theory that she was not employed by Dante’s when the performance was canceled. In other words, the district court treated the employment relationship with the second venue as the key gatekeeper.
The Ninth Circuit disagreed. The appellate court held that the relevant employment relationship was not necessarily between Hollis and Dante’s. Instead, the court focused on the underlying alleged employment relationship between Hollis and Sassy’s, the business involved in the wage-and-hour complaint. The case was sent back for further proceedings.
The Core Legal Issue: Who Can Be Liable for FLSA Retaliation?
The Fair Labor Standards Act prohibits retaliation against employees who file complaints, participate in proceedings, testify, or otherwise assert rights under the statute. The anti-retaliation provision is designed to keep workers from being punished for raising wage-and-hour concerns.
The key phrase is that the FLSA makes it unlawful for “any person” to discharge or discriminate against an employee because the employee engaged in protected activity. That phrase carries real weight. It does not say only “the direct employer.” It does not politely whisper, “Only the company name printed on the paycheck.” It says “any person,” and the Ninth Circuit treated those words as meaningful.
The court also relied on the FLSA’s broad definition of “employer,” which includes persons acting directly or indirectly in the interest of an employer in relation to an employee. In practical terms, owners, managers, executives, lawyers, related businesses, and other individuals may face scrutiny if they take action that appears designed to punish or deter FLSA-protected activity.
Why the Ninth Circuit’s Decision Expands Retaliation Scope
The Ninth Circuit did not say that every lost opportunity automatically becomes an FLSA retaliation case. That would be a legal piñata party, and courts are not quite that festive. Instead, the court clarified that retaliation liability can reach beyond the simplest employer-versus-employee scenario.
1. The Retaliator Need Not Be the Direct Employer
The decision confirms that a retaliation defendant does not always need to be the actual employer that allegedly violated wage-and-hour laws. If a person acts directly or indirectly in the interest of the employer, and the action is connected to the employee’s protected complaint, liability may be possible.
That point is especially important for companies with layered ownership, shared managers, sister companies, franchises, contractors, and related business entities. A business cannot safely assume that retaliation becomes legal simply because it happens through a different corporate doorway.
2. The Worker Need Not Be Currently Employed by the Retaliating Entity
The court also rejected the idea that the worker must be employed by the retaliating entity at the time of the adverse action. In the Hollis case, the worker’s relationship with Sassy’s mattered even though the canceled opportunity involved Dante’s.
This is a big deal. Retaliation often happens after a worker complains, leaves, files a lawsuit, joins a collective action, or becomes known as “the person who asked where the overtime money went.” The law would be much weaker if employers or managers could wait until the worker was outside the building and then start closing doors.
3. Time-Barred Wage Claims Do Not Automatically Kill Retaliation Claims
The Ninth Circuit also made clear that the underlying wage-and-hour claims do not necessarily have to succeed for a retaliation claim to move forward. A worker can engage in protected activity by filing or pursuing a complaint, even if the wage claim later faces procedural problems such as a statute-of-limitations issue.
That distinction matters because retaliation law protects the act of asserting rights. If employees had to win the underlying wage case before being protected from retaliation, the protection would arrive late, tired, and carrying a tiny umbrella in a thunderstorm.
How This Fits With Earlier FLSA Retaliation Cases
The Hollis decision did not appear out of nowhere. It builds on a broader legal trend in which courts interpret the FLSA’s retaliation language in light of the statute’s remedial purpose.
In Kasten v. Saint-Gobain Performance Plastics Corp., the U.S. Supreme Court held that oral complaints can qualify as protected activity under the FLSA if they are clear enough to give fair notice that the employee is asserting statutory rights. That case helped prevent employers from dodging liability by arguing that only written complaints count.
The Ninth Circuit has also taken a broad view in cases involving internal complaints and managerial employees. In Rosenfield v. GlobalTranz Enterprises, Inc., the court focused on whether the employer had fair notice that the worker was asserting FLSA rights. The lesson is not that every workplace grumble becomes protected activity. The lesson is that substance matters more than labels.
The Ninth Circuit’s earlier decision in Arias v. Raimondo also plays a key role. There, the court allowed an FLSA retaliation claim against an employer’s attorney who allegedly acted against a worker because of wage-and-hour litigation. Hollis extends that logic into a related-business setting, reinforcing the idea that the anti-retaliation provision can reach individuals who act in the employer’s interest.
What Counts as Protected Activity Under the FLSA?
Protected activity under the Fair Labor Standards Act may include filing a lawsuit, making a wage complaint, cooperating with a Department of Labor investigation, testifying in an FLSA proceeding, or raising concerns about minimum wage, overtime, misclassification, or unpaid work.
The complaint does not always need to be dressed in formal legal language. Workers do not have to say, “Pursuant to 29 U.S.C. section 215(a)(3), I hereby activate my statutory protection shield.” That would be memorable, but it is not required. The communication generally must be clear enough that a reasonable employer understands the worker is asserting FLSA-related rights.
For example, an employee who says, “I think we are not being paid overtime correctly,” may be engaging in protected activity. A worker who asks, “Why are we clocking out and still cleaning for 20 minutes?” may also be raising a wage-and-hour issue. Context matters, and employers should train managers not to treat such comments as personal attacks or invitations to retaliate.
What Counts as Retaliation?
Retaliation under the FLSA can include termination, demotion, reduced hours, blacklisting, threats, refusal to rehire, loss of assignments, canceled opportunities, intimidation, or other actions that would discourage a reasonable worker from asserting wage rights.
In Hollis, the alleged retaliation involved canceling a scheduled performance and barring future work at another venue. That fact pattern is important because it shows that retaliation is not limited to the classic “you’re fired” scene. Sometimes retaliation looks less dramatic: fewer shifts, colder emails, mysteriously vanishing opportunities, or being told that a lawsuit has made things “complicated.” In employment law, “complicated” can be the smoke alarm.
Why Employers Should Care
For employers, the decision raises the compliance stakes. Businesses operating within the Ninth Circuit should assume that FLSA retaliation exposure may extend to owners, managers, related entities, and individuals who influence future work opportunities.
This does not mean employers cannot make legitimate business decisions after a worker complains. They can still discipline employees for documented misconduct, end contracts for lawful reasons, enforce neutral policies, and protect business operations. But the reason must be real, consistent, documented, and unrelated to protected wage-and-hour activity.
The dangerous zone appears when a decision-maker says or implies that the worker’s complaint, lawsuit, cooperation, or wage demand caused the negative action. That is where a routine business decision can start glowing like a neon sign that says, “Exhibit A.”
Practical Compliance Lessons for Businesses
Train Managers Before Trouble Starts
Managers should know that wage complaints are protected activity. They should not threaten, mock, isolate, reduce hours, cancel assignments, or discuss punishing workers who raise pay concerns. Even casual comments can become evidence later.
Keep Related Entities Separate in Practice
If two businesses share owners, managers, scheduling systems, payroll support, or operational control, retaliation risks may cross entity lines. Corporate separateness on paper is helpful, but courts may look at actual conduct. A beautifully organized corporate chart will not save a company if everyone behaves like the businesses are one big group chat.
Document Legitimate Reasons
If a worker who recently complained about wages later loses hours, assignments, or opportunities, documentation becomes critical. Employers should be able to show non-retaliatory reasons supported by records, timing, policy, and consistency.
Do Not Treat Legal Risk as a Retaliation Excuse
One of the most important lessons from Hollis is that businesses cannot justify retaliatory conduct by saying they were only trying to reduce legal exposure. If the “risk management” strategy is to punish the person who complained, it is not risk management. It is risk production, with garnish.
Practical Lessons for Employees
Employees should understand that the FLSA protects workers who assert wage-and-hour rights. If a worker complains about unpaid overtime, minimum wage violations, off-the-clock work, tip issues, or misclassification and then experiences a negative action, the timing and facts may matter.
Workers should keep records of complaints, schedules, messages, pay stubs, assignment changes, and communications from managers. Documentation can help show whether a negative action was connected to protected activity. It is also wise to write clearly and professionally when raising wage concerns. A calm message that says, “I believe our overtime pay may not comply with the FLSA, and I would like this reviewed,” is much easier to evaluate than an angry midnight text written like a raccoon found the keyboard.
Specific Examples of FLSA Retaliation Risks
Consider a restaurant employee who tells a manager that workers are being asked to clock out before cleaning. Two days later, the employee’s shifts disappear, while less experienced employees receive the same hours. That may raise retaliation concerns.
Consider a delivery worker classified as an independent contractor who joins a wage lawsuit. A manager connected to another related delivery brand then blocks the worker from future routes. Under the reasoning of Hollis, the company should not assume the second entity is automatically insulated from scrutiny.
Consider an HR manager who repeatedly warns leadership that overtime practices are unlawful and is then terminated after escalating the issue. Depending on the facts, that conduct may qualify as protected activity if the employer had fair notice that the manager was asserting employee rights under the FLSA.
These examples all share the same theme: retaliation law looks at the connection between protected activity and adverse action. The more direct the timing, the clearer the statements, and the weaker the employer’s explanation, the more dangerous the situation becomes.
Why the Decision Matters in the Modern Workplace
Modern work is rarely simple. Workers may be assigned through apps, contractors, staffing agencies, parent companies, franchise systems, subcontractors, and related businesses. A worker may not know which entity controls scheduling, pay, discipline, or future assignments.
The Ninth Circuit’s broader approach recognizes that retaliation can travel through these modern structures. If the law only protected workers from retaliation by the exact entity on a paycheck, businesses could create gaps large enough to drive a payroll truck through.
Hollis makes that harder. The decision tells employers that courts may look beyond formal labels and ask who acted, why they acted, whose interests they served, and whether the action would discourage a reasonable worker from asserting FLSA rights.
Experience-Based Insights: What This Looks Like in Real Workplaces
In real workplace disputes, retaliation rarely arrives wearing a name tag that says “Hello, I am illegal retaliation.” It usually shows up as scheduling changes, awkward silence, canceled opportunities, delayed responses, sudden criticism, or a manager saying, “It is just not a good fit anymore.” That is why the Hollis decision feels so practical. It speaks to how retaliation often works outside a textbook.
Many wage-and-hour conflicts begin with small questions. Someone asks why overtime is missing. Someone notices that prep time is unpaid. Someone wonders why a contractor works like an employee but receives none of the protections. At first, management may treat the question as annoying but manageable. Then the worker files a complaint, contacts an attorney, joins a lawsuit, or cooperates with an investigation. Suddenly, the worker becomes “difficult.” That word is one of the oldest characters in the employment-law drama.
From a compliance perspective, the most common mistake is emotional decision-making. A manager feels betrayed by a lawsuit or embarrassed by a wage complaint and reacts too quickly. The reaction may be framed as protecting the business, but if the protected activity is the real reason for the decision, the label will not help. Calling retaliation “business judgment” does not make it safe, just as calling a burnt sandwich “artisan charcoal toast” does not make it lunch.
Another common experience is confusion inside related companies. One business receives the complaint, but another business controls future opportunities. Owners may assume that the second company can quietly cut ties because it is technically separate. Hollis warns against that assumption. When the same individuals influence both businesses, and the adverse action is tied to the original wage complaint, the separation may not be enough to defeat a retaliation claim.
Workers also experience uncertainty. They may wonder whether they are protected if they are labeled independent contractors, former employees, temporary workers, or performers. Hollis does not answer every classification question, but it reinforces that labels are not the end of the analysis. Courts often look at economic reality, control, dependence, and the actual working relationship.
The best real-world lesson is simple: slow down. Employers should pause before changing a complaining worker’s schedule, assignments, contracts, or access to future work. Ask whether the same decision would have happened without the wage complaint. Review documents. Involve HR or counsel. Use consistent criteria. Keep the tone professional.
Employees should also be careful and organized. Save records, communicate clearly, avoid exaggeration, and focus on facts. A strong retaliation concern becomes easier to evaluate when the timeline is clean: complaint made, decision-maker informed, adverse action taken, explanation given. Facts are the seatbelts of employment disputes. Nobody gets excited about them until the crash begins.
Ultimately, Hollis is a reminder that anti-retaliation law protects more than a paycheck. It protects the ability to speak up without being quietly pushed out of future opportunities. For businesses, the decision is a warning to treat wage complaints with discipline instead of defensiveness. For workers, it is a reminder that retaliation can be challenged even when it travels through indirect channels.
Conclusion
The Ninth Circuit’s decision in Hollis v. R&R Restaurants, Inc. expands the practical reach of Fair Labor Standards Act retaliation protection. The court emphasized that an alleged retaliator does not always need to be the worker’s direct employer and that retaliation may occur through indirect actions connected to protected wage-and-hour activity.
For employers, the message is blunt: do not punish workers for asserting FLSA rights, even indirectly, even through a related business, and even when the complaint creates legal discomfort. For employees, the decision strengthens the idea that wage complaints, lawsuits, and protected participation should not cost them future work opportunities.
In plain English, the FLSA retaliation provision has teeth, and the Ninth Circuit just reminded everyone that those teeth are not decorative.
