Google Found a Legal Escape Hatch for Joint-Employer Rulings

Google has perfected a legal escape hatch for contractor-heavy staffing models: refuse to bargain, appeal the joint-employer finding, then terminate the vendor contract mid-litigation to render the case moot. Workers get a union but no job. Employers get a replicable playbook to avoid liability. The joint-employer determination you thought was binding precedent? It can be erased.

On April 8, 2026, the NLRB ordered Google to bargain with 120 Accenture Flex workers after finding joint-employer status. It was Google's third such ruling in three years. Google announced it will appeal. Labor attorneys are now watching to see if the company runs the same playbook it used in the YouTube Music case, where it successfully wiped a joint-employer finding from the books by letting a vendor contract expire during the appeal window.

The YouTube Music case: how to erase a ruling

On February 29, 2024, 43 YouTube Music content moderators employed by Cognizant were told during a livestreamed Austin City Council meeting that their jobs were being terminated. They had voted 41-0 to join the Alphabet Workers Union. The NLRB had found Google was their joint employer and ordered the company to bargain. Google refused and appealed. Then Google's contract with Cognizant expired; the work moved offshore under a new contract. Google maintained it was Cognizant's decision.

Fourteen months later, on April 22, 2025, the D.C. Circuit vacated the NLRB's joint-employer order as moot. No contract, no case. But the court didn't just dismiss the bargaining order. It vacated the underlying joint-employer finding entirely. That means Google didn't just avoid the duty to bargain. It erased binding precedent that could have been used against it in future cases.

The union's lawyer, Karla Campbell, had warned the court this would create a "litigation tactic" for employers. The court acknowledged the concern but ruled it had no legal alternative. Every one of the 43 workers remains terminated. Google now has zero enforceable NLRB joint-employer findings on the books.

The mechanism: why mootness beats the duty to bargain

Here's what HR consultants miss when they tell clients "once the NLRB finds joint-employer status, you're locked in." They're assuming the finding survives long enough to matter. But appellate review for NLRB unfair labor practice cases takes 18 months or more. Vendor contracts in tech, logistics, and customer service typically run 12 to 24 months. If you control the vendor relationship and the contract expires before the appeal concludes, you can moot the case. And if the case is moot, the finding gets vacated.

This isn't a loophole. It's a feature of federal civil procedure. Courts won't issue advisory opinions on contracts that no longer exist. The incentive structure is clear: delay works if you can outlast the timeline. And if you're a company that employs roughly half your workforce as temps, vendors, and contractors (as Google does, per internal sources), you have the contract-renewal leverage to run the clock.

What the Accenture case tests

The new Accenture Flex case involves 120 remote workers who were certified by the NLRB in November 2023. The NLRB ruled in April 2026 that Google violated the National Labor Relations Act by refusing to bargain with the Alphabet Workers Union. Google announced it will appeal. The Accenture contract terms are not public, but labor attorneys are now calculating renewal windows and appeal timelines to see if Google can moot this case the same way it did the Cognizant one.

If Google lets the Accenture contract expire before the appeal resolves, the 120 workers will face the same outcome as the YouTube Music 43: terminated, with a union victory that exists only on paper. The joint-employer finding will be vacated. No precedent, no liability, no bargaining table.

The concession: courts can't force phantom contracts

The D.C. Circuit didn't want to create this escape hatch. It acknowledged that its ruling handed employers a tactic to evade NLRA obligations. But courts can't order parties to maintain contracts that have ended, and they can't issue rulings on employment relationships that no longer exist. The NLRB could, in theory, seek damages or reinstatement for the terminated workers, but that requires proving the contract termination was pretextual retaliation, not a legitimate business decision. When the work is moved to a new vendor or offshore, that's a hard case to win.

Google's position has been consistent: it's the vendor's decision to end the contract, not ours. The workers are Cognizant's employees or Accenture's employees, not Google's. If the vendor can't staff the contract or the business needs change, the contract ends. The fact that this happens during a pending joint-employer appeal is, from Google's perspective, just timing.

What this means if you run a contractor-heavy operation

If you're solving for joint-employer liability risk, you're solving for the wrong variable. The risk isn't the finding; it's whether you're stuck with it. Google has shown that joint-employer determinations are escapable if you control the vendor contract and can outlast the appellate clock. That means your legal team needs to map vendor contract terms (length, renewal windows, termination-for-convenience clauses) against NLRB appeal timelines. It also means that workers who win union elections at contractor shops may be voting themselves out of a job, and unions will need to start demanding contract-continuation clauses as part of their organizing strategy.

The conventional wisdom that "refusing to bargain just delays the inevitable" ignores that delay itself can be the strategy. Vendor contracts cycle faster than appellate courts move. If you can moot the case, you don't just avoid bargaining. You erase the precedent.

This is the kind of endgame FiringAgents.ai is built to help managers think through: the hard conversations that happen when a contract ends and workers need answers you're not allowed to give yet.