HR Briefing

Labor Law & Compliance

Sixth Circuit sides with employer in exemption dispute over 18-hour days

The Sixth Circuit ruled an employee who worked 18-hour days was exempt from overtime under the FLSA computer employee exemption, affirming summary judgment for Cincinnati Bell.

IC-Turned-W-2 Employee Sues for OT Pay: Why Court Backed Employer
IC-Turned-W-2 Employee Sues for OT Pay: Why Court Backed EmployerMonoar_CGI_Artist / pixabay

Daniel Okafor

· 3 min read

A federal appeals court has ruled that an employee who sometimes worked 18-hour days was not owed overtime because his duties fit the FLSA computer employee exemption. The Sixth Circuit affirmed summary judgment for Cincinnati Bell Telephone Co. in Bennink v. Cincinnati Bell Telephone Co., decided October 29, 2026.

The ruling touches two employer obligations at once: how companies classify pay in offer letters, and how they document whether technology roles meet the duties test for exemption. Cincinnati Bell cleared both hurdles. Many employers do not.

How the case began

Loren Bennink worked with Cincinnati Bell for several years through an outside vendor before joining the company directly as a W-2 employee in May 2016. His offer letter listed pay of $75 an hour and placed him in a job class the company treated as exempt under the Fair Labor Standards Act (FLSA), the federal law governing minimum wage and overtime. The letter stated it was not a contract.

Cincinnati Bell paid Bennink $3,000 a week — the equivalent of $75 per hour for 40 hours — regardless of how many hours he actually worked. Bennink said his workload eventually grew beyond what one person could handle, at times requiring 18-hour workdays. He resigned and sued for overtime covering hours beyond 40 per workweek.

What does the exemption require?

Under the FLSA, the computer employee exemption has two parts: a pay threshold and a duties test. A qualifying computer employee must earn at least $684 a week on a salary basis, or $27.63 an hour if paid hourly.

The parties disputed whether Bennink was paid hourly or salaried. Both sides agreed his pay exceeded the hourly threshold, so the Sixth Circuit focused entirely on his job duties.

To qualify, Cincinnati Bell had to show that Bennink's main responsibility involved work such as designing, developing or documenting computer systems or programs to meet user needs or technical specifications.

Why did the employer win?

Bennink argued that the phone system he worked on was not a computer system, and that his documentation amounted to little more than flowcharts. He cited his lack of formal computer training and his reliance on colleagues for actual programming.

The court was not persuaded. The interactive voice response system (the automated phone menu technology that routes callers) was a computer system, the panel reasoned, and Bennink helped design, develop and document it by mapping call flows and determining how it should meet user needs.

Three counterarguments failed in turn:

  • His project-management work did not disqualify the exemption.
  • His reliance on others for programming did not change the analysis.
  • His lack of formal training was irrelevant — the exemption requires no particular degree, education or job title.

The Sixth Circuit affirmed summary judgment for Cincinnati Bell, holding that Bennink qualified for the exemption and was not entitled to overtime pay.

The offer-letter lesson

The court also rejected Bennink's contract claim. He argued the $75 hourly rate in his offer letter created an agreement to pay him for every hour worked. The panel disagreed — the stated rate did not establish such a promise, particularly where the letter disclaimed contractual status.

That is the quiet second victory in the decision. An hourly figure in an offer letter is often read by employees as a per-hour payment commitment. Cincinnati Bell's letter said, in effect, the opposite, and the disclaimer held up in federal court.

For HR teams, the comparison is instructive: the exemption survived not because of Bennink's job title or credentials, but because the record showed his primary work involved designing and documenting a system that met user needs. Titles did not save the employer. Evidence of duties did.

Employers with computer-adjacent roles — telephony, infrastructure, business-systems support — can expect plaintiffs' counsel to keep testing the boundaries of this exemption, and documentation of actual daily duties, not labels, will decide the next case.

Source: hrmorning.com

Share this article:

More from Daniel Okafor

Daniel Okafor

Show full bio

Senior reporter covering technology and product news in Recruiting and talent acquisition, learning and development at HR Briefing.

295 articles

© 2026 HR Briefing. All rights reserved.