Employee With Diabetes Offered to Work a Longer Shift in Exchange for Extra Breaks to Check His Blood Sugar — His Employer Refused and Fired Him

Photo credit: AI-generated image created using ChatGPT. Illustrative only.

It’s one of those workplace requests that sounds simple until a timeclock system gets involved: an employee with diabetes asked for a little more break time during his shift so he could check his blood sugar and recover when he had an episode. He even offered to stay longer to make up the minutes. The employer said no, and the job ended anyway.

That’s the core of a new lawsuit the U.S. Equal Employment Opportunity Commission announced against Alight Solutions, an employee benefits administrator headquartered in Lincolnshire, Illinois. The agency’s allegations are laid out in the original post, and they paint a picture of a company treating medically necessary breaks as a performance problem—and then using its monitoring tools to justify a termination.

He asked for extra time to manage diabetes—and offered to make it up

In the EEOC’s telling, the employee needed additional breaks during his shift for two reasons: to monitor his blood sugar and to recover from diabetic episodes when they happened. This isn’t framed as a want or a convenience. It’s the basic routine many people with diabetes rely on to stay safe and functional at work.

What made the request even more straightforward, at least on paper, was the employee’s proposed trade. The lawsuit says he was willing to work a longer shift to make up for the extra break time. In other words, he wasn’t asking to be paid for doing less work. He was asking for flexibility in how that time was structured.

The EEOC alleges Alight Solutions refused anyway. The accommodation—the extra breaks—never materialized, and the dispute didn’t stay contained to a simple “yes” or “no.”

When the tracking system became the boss

A big part of the complaint centers on how the company tracked employees. The EEOC says Alight used electronic attendance monitoring systems to track employee activity, and those systems did not appropriately account for the additional breaks the employee needed.

This is where the story gets especially tense, because it’s not just a manager making a bad call in the moment. When monitoring software is treated as the official record, a medically necessary break can start to look like time theft, disengagement, or noncompliance—depending on how the system is configured.

According to the EEOC, instead of adjusting the tracking approach so the employee wasn’t unfairly penalized for disability-related breaks, Alight terminated him. The agency’s message is clear: if your systems aren’t built to recognize legitimate accommodations, they can turn into an automated punishment machine.

The firing is the escalation the ADA is supposed to prevent

The lawsuit claims the termination wasn’t separate from the accommodation request—it was part of the same chain of events. The EEOC alleges Alight fired the employee because of his disability, after refusing to provide reasonable accommodation for diabetes.

The legal framework the agency points to is the Americans with Disabilities Act. In the press release, the EEOC emphasizes that employers must accommodate disabled employees when doing so is not an undue hardship. It also notes that the ADA prohibits employers from discharging an employee because of a disability or because the employee requested an accommodation.

Acting EEOC General Counsel Catherine Eschbach’s statement is blunt about what the agency believes should have happened: “Allowing a diabetic employee a small amount of additional break time to manage his condition, and ensuring the company’s tracking systems did not unfairly penalize him for those breaks, falls within the ADA’s core protections.” She also warned that disability protections don’t fade just because workplaces adopt new technology.

From HR problem to federal lawsuit

The EEOC says it filed suit in federal court after trying to resolve the matter first. The case is titled EEOC v. Alight Solutions, LLC, Case No. 1:26-cv-06361, and it was filed in the U.S. District Court for the Northern District of Illinois, Eastern Division.

Before that filing, the agency says it attempted to reach a pre-litigation settlement through its administrative conciliation process. That’s the “let’s see if this can be fixed without court” stage, where employers sometimes agree to policy changes or monetary relief without admitting wrongdoing.

This one didn’t end there. The lawsuit suggests the EEOC believes the breakdown wasn’t a minor misunderstanding—it was a refusal to accommodate, compounded by systems that kept scoring the employee as if he had no medical needs at all.

What people tend to focus on in cases like this

Even without public comments attached to the press release, the pattern in disputes like this is familiar. People zero in on documentation and whether the employer put its decisions in writing—especially when accommodations are requested and denied.

Another common focus is the role of “neutral” tools like attendance software. Plenty of workers have learned the hard way that a system can be neutral in design but harsh in practice, especially when it can’t distinguish between an avoidable pause and a medically necessary one.

And then there’s the practical workplace question that often gets overlooked: if the employee offered to work longer to cover the break time, what was the real barrier? Was it rigid scheduling, a policy that refuses any deviation, or a culture that treats accommodation requests like a challenge to authority? The EEOC’s suit is essentially arguing that whatever the barrier was, it didn’t justify what happened next.

For Alight, the case now plays out in federal court, under the spotlight of a federal agency that’s explicitly warning employers not to let technology quietly erase disability protections. For the worker at the center of it, the allegation is simple and heavy at the same time: he tried to manage a chronic condition at work, proposed a compromise, and lost his job instead.