Case details from HRMorning; public case record: Andrew Larkin, Esq., Administrator of the Estate of Magnolia Walsh v. Total Quality Logistics, LLC, et al., Case No. A2300752, Hamilton County, Ohio (verdict March 18, 2026). General guidance only, not legal advice.

A Hamilton County, Ohio jury returned a $25 million verdict on March 18, 2026, assigning 90% fault to the employer (about $22.5 million), in a pregnancy remote-work accommodation case where the request spent weeks in the leave queue with no documented feasibility review (per HRMorning; WLWT court docs).

This verdict is not a remote-work story. It is a case ownership failure. The request landed in the leave queue. Nobody was accountable for the accommodation decision, the record had no timestamps (per case reporting), and there was no written rationale for why leave was the answer instead of a short-term remote arrangement. That empty record is where someone else’s attorney builds the timeline.

In the reported facts, Chelsea Walsh had a high-risk pregnancy in 2021 and her physicians recommended modified bed rest and remote work. TQL did not approve remote work initially, directed her toward leave, and approved work from home only after outside intervention, on the same day Walsh delivered prematurely at 20 weeks and 6 days. Magnolia Walsh did not survive (per HRMorning; WLWT court docs). TQL has said it disagrees with the verdict and how facts were characterized at trial, and is evaluating legal options including a possible appeal (per HRMorning; WLWT court docs).

These events happened in 2021, two years before the Pregnant Workers Fairness Act (PWFA) took effect June 27, 2023. Under the PWFA, any employer with 15 or more employees must evaluate whether a reasonable accommodation exists before directing an employee to leave. Requiring leave when a reasonable accommodation, such as remote work or a modified schedule, could keep the employee working without undue hardship is the core violation (EEOC PWFA overview). Ohio independently prohibits pregnancy discrimination and requires equal treatment of employees affected by pregnancy-related conditions. Pregnancy alone does not create an ADA disability, but pregnancy-related impairments, such as conditions requiring physician-ordered activity restrictions, may independently qualify. When a request arrives with a physician’s restriction, consider whether a parallel ADA analysis is also warranted alongside the PWFA review.

Decide before routing pregnancy accommodation to leave

The failure starts before anyone picks up the phone. Someone routes a restriction to the leave administrator before documenting whether the employee could keep working with a change. Title VII, as amended by the Pregnancy Discrimination Act, requires women affected by pregnancy-related conditions to be treated the same as others similar in their ability to work. Run these three checks before leave gets coded as the only option.

Build one owned intake record in your HRIS

The first record we pull in any accommodation dispute is the intake ticket. An email thread and a leave packet give you no Owner field and no timestamps. Those two data points decide most accommodation cases. One of the first checks we run is whether the HRIS case owner field is populated on day one, because shared inboxes create “everybody saw it, nobody owned it.”

Run a 72-hour pregnancy accommodation clock

We use a 72-hour internal clock because the handoffs that kill accommodation cases are the ones that sit for a week while two people think the other one is handling it. By the end of hour 72, the request has one named owner, the restriction is written in plain English in the case file, and the next step has a due date. That is the minimum to show you treated the request as a priority. (Note: The 72-hour timeline below is an internal operational best practice, not a statutory deadline.)

What a pregnancy accommodation workflow includes

Most employers we work with do not have a bad policy. They have a bad handoff. If your HRIS report shows blank owner fields or missing decision dates, here is what we build to close those gaps. We build the intake-to-decision path so the case has one named owner, a timestamped record, and a written rationale from the first form to the final pay-status change.

• Accommodation intake workflow and HRIS configuration: Standardized intake form with auto-numbered case ID, named-owner field, and 72-hour response calendar built into your HR Cloud case module so every accommodation has a timestamped, auditable record.
• Manager escalation playbook: Written path showing front-line managers when to route a request, which questions they answer, and what not to decide without HR review. So managers know the three things they answer and the one thing they do not decide without HR in the loop.
• Essential-functions review and JD library: Role-level job description audit so your team pulls a current, dated version the day a clinical restriction arrives, not two weeks later when the case is already in dispute.
• Payroll and benefits coordination checklist: Change-log template tied to the case record so payroll status fields and benefits elections stay synchronized if leave begins, changes, or ends mid-accommodation.

For the compliance workflow side, compliance support and HR Cloud case documentation connect most directly to the controls in this article. Contact VertiSource HR to request the pregnancy accommodation intake template. It includes the case ID structure, owner field, and 72-hour escalation calendar.

Ryan Joyce

Vice President of Client Partnerships, VertiSource HR

Ryan writes on HR operations, compliance workflows, and the systems employers rely on to document training, policies, and workplace controls.