Coca-Cola says its Women's Forum was "focused on increasing the pool of qualified candidates for promotion. " A federal judge recently ruled that's not enough to end the EEOC's sex discrimination lawsuit. Here are the alleged facts. In September 2024, ...
‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 

Have a Coke and a Title VII claim

Coca-Cola says its Women's Forum was "focused on increasing the pool of qualified candidates for promotion." A federal judge recently ruled that's not enough to end the EEOC's sex discrimination lawsuit.

Here are the alleged facts. In September 2024, Coca-Cola Beverages Northeast held a two-day event at the Mohegan Sun for women. Attendees got regular pay without using PTO, a paid hotel stay, meals, and executive speakers. Men weren't invited. A male production employee says he would have gone if they were.

The court denied Coca-Cola's motion to dismiss. Under Muldrow v. City of St. Louis, a plaintiff needs only "some harm" to a term or condition of employment. Missed networking, paid time off, and a hotel stay plausibly qualify. That's a pleading-stage ruling, not a finding that the Forum was unlawful. 

Nevertheless, this is the EEOC's DEI playbook in action. Its March 2025 technical assistance (non-binding, but a clear signal of where the agency is heading) says limiting affinity group membership by a protected trait, or separating employees by sex for training, can violate Title VII.

Let's say you want to run a women's event but don't want to end up in the EEOC's crosshairs. How do you do so lawfully? Here's what I'd tell a client.

1. Open it to everyone. Call it "welcome to all, centered on women's experiences." The content can address the barriers women face or other issues specific to women. Attendance can't depend on sex.

2. Give everyone the same terms. If attendees get paid time, travel, or meals, every employee who wants to attend gets them. Coca-Cola's exposure rests on three alleged harms: the missed networking and speakers, the paid time off, and the hotel and meals.

3. Separate the event from employment decisions. Don't make attendance a step toward promotion.

In other words, aim the content at women, but open the door to everyone.

The EEOC says he had a case. The calendar says he didn't.

The EEOC found reasonable cause to believe the City of Detroit denied a police officer a reasonable accommodation and forced him to retire.

Why, then, did Plaintiff William Woods lose his federal ADA lawsuit? His EEOC charge was 22 days late.

Woods, a Detroit police officer, worked restricted duty after a back re-injury. In December 2017, the department applied to retire him on non-duty disability. Woods says the department was pushing him out instead of accommodating him. He applied for duty disability instead. On April 5, 2018, the pension board approved his duty disability application at a hearing. Woods then retired on April 30.

He filed his EEOC charge on February 21, 2019, claiming that on April 30 he was suddenly denied his restricted-duty accommodation and involuntarily retired. In January 2023, the EEOC issued its cause finding. That's an agency finding, not a ruling on the merits.

The Sixth Circuit affirmed summary judgment for the City without ever reaching the merits. The claim died on timeliness.

The clock was the whole case. Woods had 300 days to file his EEOC charge. The issue was when that clock started running. He argued it started on his last day of work. The court disagreed. The period starts when the employer makes and communicates a final decision, not when the paycheck stops. Mere continuity of employment doesn't extend it.

Day one was April 5. Day 300 was January 30, 2019. His charge came 22 days too late.

Equitable tolling—a doctrine that allows a court to pause a deadline when someone diligently pursues a claim but an extraordinary circumstance beyond their control prevents them from filing on time—can save a late filing. It didn't save Woods here. He pointed to a brain injury, severe depression, anxiety, and PTSD.

The court said that wasn't enough to show a specific circumstance beyond his control that kept him from filing on time. He also offered no evidence of diligence, which the court called "essentially fatal."

There are three solid lessons here for employers.

1. Nail down the date a decision was communicated. The City won because Woods' own deposition put him in the room on April 5. Develop the record in discovery.

2. Plead timeliness and exhaustion in your answer. Every single time as long as you have a good faith basis to do so.

3. Don't treat a cause finding as the end of the story. The court never reached the merits. It didn't have to.

Deadlines don't care how strong the claim is.

Your employees are using AI. It's just not always the tool you've approved.

Half your workforce may be using AI tools you never approved.

That's not a hunch. A BlackFog survey of 2,000 UK and US employees found that 49% use AI tools their employer hasn't sanctioned. And 60% agreed the security risk is worth it if the tool helps them work faster or hit a deadline.

Even worse, a TrustedTech survey found senior decision-makers were more than twice as likely as the people they manage to use unapproved tools: 65% to 31%. Your policy problem may start in the corner office.

It's called shadow AI. And it's a big problem for businesses. 

Every time someone pastes a customer list, a draft contract, a personnel file, or a client's confidential information into a personal chatbot account, you may have lost control of it. Trade secret protection depends on reasonable efforts to keep information secret. Privilege can be waived by sharing with a third party. And your confidentiality promises to customers and employees don't come with an exception for "it was faster."

Then there's accuracy. AI makes things up. If a manager uses an unvetted tool to screen resumes or draft a performance review, you've created discrimination exposure that nobody is auditing. And if those prompts and outputs live on a personal account, good luck finding them when a litigation hold lands.

So what do you do?

1. Banning AI isn't the answer. Employees will just stop telling you. In the BlackFog survey, 21% figured their employer would turn a blind eye as long as the work got done. Don't prove them right.

2. Provide approve AI tools to use. Give people a sanctioned tool with real data protections, including a contract that keeps your inputs out of the vendor's training. People go rogue when the approved option is nothing at all.

3. Write a short, plain-English policy. Which tools are approved. What information never goes in. Which uses need a human to check the output. If it reads like a vendor contract, nobody will read it.

4. Train people. A Lenovo survey of 6,000 employees found 31% of AI users get no employer training. You can't enforce a rule nobody explained.

5. Hold leaders to the same standard. Then enforce it consistently, and update your handbook and confidentiality agreements so they actually mention AI. If you monitor for unapproved tools, say so in writing.

You won't stop employees from using AI. That horse has left the barn. You can, however, decide whether you're holding the reins.

WIRTW #818 (the 'late-night call' edition)

As a parent, when your daughter is overseas and your cell phone rings at 3:00 a.m., it's either a spam call or something has gone wrong. Two weeks ago, it was very much the latter.

It was Norah, calling from an airport in Romania, too sick to board her plane back to France. She needed my advice on what she should do.

By the end of the morning she'd been to an ER, gotten two bags of IV fluids, and rebooked her flight for the next day. My contribution was telling her to grab an air sickness bag and tough it out. I'm glad she ignored my advice and found a doctor instead.

But here's what I keep coming back to. She called me.

Every parent dreads the 3 a.m. phone call. I get it. But we have it backwards. That call means your kid, thousands of miles from home and in the middle of a mess, thought of you. It means they believe you'll pick up, stay calm, and help figure it out. That belief gets built over years, in a thousand small moments, long before the middle of the night.

The call to worry about is the one that never comes. 

You can hear Norah tell the whole story, along with the rest of her recent European travels, on this week's Norah and Dad Show, available on Apple Podcasts, Spotify, YouTube, Amazon Music, Overcast, in your browser, and everywhere else you get your podcasts.


Here's what I read this week.

Jensen Huang Broke an Unspoken Rule That Most Companies, and Their HR, Choose to Ignore — Evil HR Lady

When Does an Angry Response to a Discrimination Complaint Become Retaliation? — The Employer Handbook Blog

OWBPA mishap supports age bias claim, plaintiff says — Employment & Labor Insider

Home health company settles EEOC allegations it abided by clients' race-based preferences — HR Dive

Research: The Risks of Rewarding Top Employees with Better Schedules — Harvard Business Review

SpaceX must face sex-bias claims after appeals court rejects arbitration request — Reuters

Kylie Jenner Sued by Housekeeper Who Says Mogul's Dog Bit Her — Rolling Stone

Fired Employee Sues the Ethereum Foundation and Vitalik Buterin — Unchained

A CEO gave his employees Fridays off. Three years later, revenue is up about 160% — Fortune

Amazon worker fired over parking lot speeding loses all five claims — HCA Magazine

Trump administration proposes stricter work-search rules for unemployment benefits — CNBC

Fearing AI disruption, white-collar workers are quitting their jobs — The Guardian

Your employee's AI chat history is the new smoking gun

"Don't bring anything from [Dorsia] to Rumor. No code, no docs, no playbooks, no contact lists."

That's what an AI assistant allegedly told a senior engineer weeks before he left for a competitor. Bring "any architectural patterns, customer insights, or pricing intel," it allegedly added, and "you're toast."

He asked on his employer's account. The employer alleges he ignored the advice and did the exact opposite.

Dorsia, a members-only hospitality platform, sued Rumor Group and its new CTO, Chris Mathew, yesterday. The complaint alleges Mathew used a Claude account Dorsia paid for to ask how exposed he was under his contract, what he could take to Rumor, and how to avoid getting caught. 

Dorsia further alleges Rumor denied that Mathew had disclosed any Dorsia confidential information, then reversed course, placed him on leave, and announced it would terminate him, after Dorsia confronted it with his own AI prompts.

These are allegations, and Mathew and Rumor haven't answered. But the complaint is built on his own time-stamped prompts, from an account the company owned.

Not every employer can pull those chats. Many AI plans, especially personal and lower-tier business plans, give admins no view into employee conversations. Often only enterprise tiers offer audit logs or compliance exports. So what do you do if you're not on one, and how do you position your company for a case like this?

1. Check your plan today. Find out whether admins can see chats, export them, or search them. Don't learn the answer the day a key employee resigns.

2. Own the account. Buy a tier with admin access, tie it to work email, and ban personal accounts for work.

3. Require it in your policy. State that AI use for work is subject to review, that employees must preserve work-related chats, and that they must export and hand them over on request or on departure.

4. See around the chats. Web filters, browser logs, and data-loss tools show which AI sites people use, when, and what they upload. Company laptops can be forensically imaged.

5. Don't log in as the employee if you don't own the account. Using someone's password to read an account you don't control can create Stored Communications Act and computer-access problems. Ask for an export, or get it through forensics or discovery.

6. Act at resignation. When someone with access to code, pricing, or customers gives notice, image the device and request the export before accounts shut down. Then call counsel before you read anything.

Every litigator wants the smoking gun in the other side's own words. An employee's AI chats may be exactly that, but only if you can get to them before they disappear.

© Jon Hyman. You're receiving this email because you've signed up to receive updates from us.

If you'd prefer not to receive updates, you can unsubscribe.