{"id":13253,"date":"2026-11-11T11:21:40","date_gmt":"2026-11-11T11:21:40","guid":{"rendered":"https:\/\/gtclocks.com\/?post_type=insights&p=13253"},"modified":"2026-11-11T15:11:32","modified_gmt":"2026-11-11T15:11:32","slug":"what-hospital-wage-lawsuits-show-about-timekeeping","status":"publish","type":"insights","link":"https:\/\/gtclocks.com\/en-gb\/insights\/what-hospital-wage-lawsuits-show-about-timekeeping\/","title":{"rendered":"What Hospital Wage Lawsuits Reveal About Timekeeping"},"content":{"rendered":"\n
\n
\n
\n

Most conversations about hospital workforce systems start with scheduling, staffing ratios or the HCM platform itself – the timeclock on the wall by the staff entrance rarely gets a mention until something goes wrong with it. That comes as no surprise since punching in and out takes a second and often becomes second nature. Yet when hourly healthcare workers take their employer to court over pay, the argument almost always comes back to that second: when the employee arrived, when they left, and whether the break the system recorded was a break they took.<\/p>\n

Over the last two years, a run of US hospital settlements and verdicts has put timekeeping practices under a level of scrutiny that HR, payroll and IT teams in health systems would do well to look at closely.<\/p>\n

Rounding and Meal Breaks Keep Ending Up in Court<\/span><\/h2>\n

The largest case is Bennett v. Providence Health & Services in Washington State. In April 2024, a jury found that Providence’s 15-minute rounding policy and its handling of second meal breaks on shifts over 10 hours had underpaid more than 33,000 hourly employees. Once damages were doubled for willfulness and interest was added, the judgment came to more than $229 million. <\/p>\n

A state appeals court upheld it in October 2025, and the Washington Supreme Court agreed in April 2026 to hear Providence’s further appeal, so the final figure is still open.<\/p>\n

Smaller cases follow a similar pattern. In North Carolina, Mission Health (part of HCA Healthcare) agreed to a $1.56 million settlement with hourly workers in its state facilities over claims of time rounding and automatic meal-break deductions, while maintaining that staff were paid correctly. Onslow Memorial Hospital, also in North Carolina, reached a $75,000 settlement with 32 overnight maternity staff who said 30 minutes was deducted every shift for meal breaks they often could not take because they had to stay on the unit.<\/p>\n

None of this means rounding or automatic deductions are illegal in themselves. Under the Fair Labor Standards Act, an unpaid meal period is allowed when the employee is fully relieved of duty, and automatic deductions can be lawful as long as there is a reliable way to pay people when a break is missed or interrupted. The difficulty in a hospital is that breaks are interrupted all the time, by a patient who deteriorates or a colleague who calls in sick, and a policy is only as good as the record that sits behind it.<\/p>\n

A Workforce That Never Stands Still<\/h2>\n

The timekeeping record also has to keep up with a workforce that changes constantly. According to the 2026 NSI National Health Care Retention & RN Staffing Report, which surveyed 527 hospitals in 40 states, staff RN turnover rose to 17.6% in 2025. Around 324,000 acute care RNs left their positions during the year and hospitals hired roughly 378,000. NSI puts the average cost of losing one bedside RN at $60,090.<\/p>\n

For the people running time and attendance, that turnover has a practical side. Every new hire has to be in the HCM system, assigned to the right cost center and able to punch on day one at whichever site they report to, and every leaver has to come off every clock they could use. Across a health system with dozens of facilities, that is a great deal of employee data moving between the HCM platform and the hardware, and gaps in that flow tend to surface as missed punches, manual edits and timecard corrections that payroll has to chase.<\/p>\n

The Cost of Recording Hours After The Fact<\/h2>\n

It\u2019s not to say that without a dedicated capture point, records don\u2019t get made \u2013 they do. But the problem is\u00a0how<\/em>.<\/p>\n

Maybe a supervisor enters the hours for their team worked, or maybe it\u2019s the employees themselves completing a timesheet at the end of each week. While both methods show a number of worked hours, neither are defensible records made at the time, by the person who worked the hours.<\/p>\n

And that distinction can turn an overlooked operational process into a legal risk. Under the FLSA, the duty to keep accurate records of hours worked sits with the employer. Where those records are inaccurate or incomplete, an employee who can show unpaid work took place and give a reasonable estimate of their hours may shift the burden onto the employer to prove otherwise. Where entries have been edited, the audit trail showing who changed a record and why can matter as much as the timecard itself. A supervisor\u2019s recollection entered on a Friday leaves the employer poorly placed on both counts.<\/p>\n

But that\u2019s a worst-case scenario \u2013 there\u2019s a real day-to-day cost that appears in HR administration. Payroll teams spend the days before each payroll cycle chasing missing punches and correcting obvious errors, and managers spend time re-keying data that could have arrived automatically.<\/p>\n

What a Health System Should Expect From its Timeclocks<\/h2>\n

The HCM platform holds the pay rules, the rounding policy and the break logic, but the timeclock is where those rules meet the employee. A well-integrated clock can apply them at the point of punch, for example by stopping someone clocking in too early for their shift or by asking them to confirm whether they took their break before they clock out. It also captures the raw evidence that payroll and, if it ever comes to it, a court will rely on, which is why a few hardware and integration questions make a real difference.<\/p>\n