The Real Cost of Overtime: What School Districts Are Saying

When we talk about time tracking in schools, it's easy to focus on the technology. But the real story isn't about clocks or software. It's about what happens when overtime goes untracked, unverified, or worse, falsified.

These aren't hypothetical problems. They're the stories that Business Managers, CFOs, and Technology Directors tell us when they explain why they needed to change. And now, with new IRS reporting requirements for overtime under the One Big Beautiful Bill Act, these problems have become compliance risks.

Why Overtime Tracking Suddenly Got More Complicated

Retroactively starting January 1, 2025, eligible employees can deduct up to $12,500 in qualified overtime pay from their federal income taxes ($25,000 if married, filing jointly). That sounds like good news for staff. But for districts, it creates a significant new burden: you now need to track, isolate, and report the FLSA-mandated premium portion of overtime separately on W-2s.

For 2025, the IRS is providing transition relief. Districts won't be penalized for incomplete reporting. But that grace period ends with the 2026 tax year, when full compliance becomes mandatory. By the time you generate 2026 W-2s, your payroll system needs to be able to answer a question most districts have never had to ask: for every employee, in every pay period, how much of their overtime pay was the half-time premium required under the Fair Labor Standards Act?

If your current time tracking process can't produce that answer cleanly and defensibly, 2026 isn't a year to relax. It's the year to fix it. Because the districts that wait until January of 2027 will be scrambling to reconstruct data they should have been capturing all along.

The customer stories below aren't just about overtime problems. They're about districts that needed better time tracking before the new IRS requirements existed. Now those requirements make the problems these districts faced not just costly, but potentially non-compliant.

 For more on the new overtime reporting requirements and what they mean for K-12 districts, see No Tax on Overtime: What K-12 Leaders Need to Know and What "Qualified Overtime" Actually Means for District Payroll.

When Trust Isn't Enough (And Now Can't Be)

Amy Tomalavage, Business Manager at Blue Mountain School District in Pennsylvania, remembers the conversation she had to have six months before we spoke:

"I hate paper timesheets. Because this was maybe six months ago, we had to fire somebody because they were falsifying their timesheets by 4 hours every day. 4 hours of overtime every day."

Four hours. Every single day. That's an employee collecting overtime pay for an entire second shift they never worked, and doing it for long enough that the financial impact went from a budget line item to a termination meeting.

Paper timesheets required trust because there was no other option. They handed someone a form, and they believed what they wrote. Blue Mountain learned what that trust was actually worth: falsified time, fraudulent overtime, and a firing that could have been prevented if verification had been built into the process from the start.

That was before the new IRS requirements. Now consider this: if the district were still running on paper timesheets today, they wouldn't just be paying for fraudulent overtime. They'd be reporting it to the IRS as qualified overtime compensation, certifying data they couldn't verify. The employee would receive a W-2 showing overtime they didn't work, and the district would be on record as having paid it.

After switching to Touchpoint SmartClocks, every clock-in became tied to a verified employee at a physical device. Falsified time isn't just harder now. It's structurally impossible. The accountability Blue Mountain needed stopped depending on whether someone was honest and started depending on whether they were physically present.

When the IRS starts requiring defensible overtime records for 2026, districts like Blue Mountain will have them.

The Manual Labor Behind Overtime Tracking (And the New Precision It Requires)

Even when the time is accurate, overtime tracking creates its own administrative burden. Daniel Cazares, Director of Technology at Lumberton ISD in Texas, describes the process his district used to run:

"It's a real time saver on not having paperwork. We used to use timesheets, and they'd have to turn all those in, and somebody would have to key in what the hours, especially overtime or whatever. Now that they're able to go into their portal and see how many hours they have and how much time they have over."

This is the hidden cost of paper systems: someone has to turn data written on paper into data a payroll system can use. Every hour. Every employee. Every pay period. Overtime hours are particularly tedious because they require verification, rate calculations, and approval workflows that paper can't encode.

The work doesn't add value. It just makes payroll possible. And while someone is keying in overtime hours from last week's timesheets, employees are calling to ask how much time they've accrued because they have no way to see it themselves.

But here's the part that matters now: manual data entry doesn't just create administrative burden. It creates opportunities for error in the exact data element the IRS will be scrutinizing. When someone keys in "8 hours overtime" from a paper timesheet, your payroll system sees that as total overtime pay. It doesn't know that only the half-time premium qualifies for the new deduction. That calculation has to happen somewhere, and if your time collection process can't feed your payroll system clean data about which hours were worked, when, and under what job code, you're adding estimation and reconstruction to an already manual process.

When Lumberton deployed Touchpoint SmartClocks, the hours captured at the device became the hours in their time and attendance system. Employees could view their own time immediately. The manual keying process that had defined payroll work simply disappeared, not because someone got faster at data entry, but because the data entry stopped being necessary.

More importantly, the data going into the payroll system was now tied to verified punches at physical devices, with job codes and timestamps that could support the kind of granular overtime reporting the IRS will require. That's not something you can retrofit onto manually keyed timesheets.

Another Director of Technology in Texas (whose district preferrs to remain unnamed) described the same challenge this way:

"It's a real time saver on not having paperwork. We used to use timesheets, and they'd have to turn all those in, and somebody would have to key in the hours, especially overtime."

The phrase "especially overtime" does a lot of work in that sentence. Overtime isn't just more data entry. It's higher-stakes data entry. Get regular hours wrong and someone's paycheck is slightly off. Get overtime wrong and you're either underpaying people who are legally entitled to time-and-a-half or overpaying based on fabricated hours.

And now, get overtime reporting wrong on a W-2 and you're certifying inaccurate data to the IRS while creating confusion for employees trying to claim a deduction they may or may not actually qualify for. There's no margin for error, which means every overtime entry has to be verified before it's entered, and every overtime hour needs to be trackable back to the punch that created it.

The Overtime You're Already Paying For (And Now Have to Document)

Doug Culler, Director of Technology at Shenandoah County Public Schools in Virginia, was watching overtime costs climb and knew something was wrong:

"We have paid out an incredible amount of overtime this year. With the SmartClock, it's a more accurate reflection of hours that people are actually working."

The problem wasn't overtime itself. Schools legitimately need staff to work beyond their contracted hours during busy periods. The problem was that Shenandoah County couldn't tell whether the overtime being paid out matched the overtime actually worked.

Paper submissions and manual processing made it nearly impossible to catch discrepancies in real time. By the time payroll ran, the money was already budgeted and allocated. If someone rounded their hours up by fifteen minutes every day, that might be invisible in any single pay period but would compound into paid overtime that was never actually worked.

Doug's observation, "a more accurate reflection of hours that people are actually working," is careful language. It means Shenandoah County was paying for overtime based on time that was close enough to correct to likely slide by in the past, rather than verified as correct.

That was always a budget problem. Now it's also a compliance problem. The new IRS requirements don't just ask how much overtime you paid. They ask how much qualified overtime you paid, which means you need to know exactly which hours were worked over 40 in a workweek, by which employees, under which FLSA classification. "Close to correct" isn't good enough when you're certifying data on a federal tax form.

After deploying SmartClocks, actual hours worked replaced estimated or self-reported time. Overtime costs are accurately reflected, and the finance team (who had been spending significant time processing payroll every period) have reclaimed that time for higher-value work.

Just as importantly, the data foundation for IRS reporting was in place. Every overtime hour was tied to a verified punch, a specific employee, and a timestamp that could prove when the work actually happened. That's not something you can reconstruct from paper after the fact.

What Changes When Overtime Tracking Becomes Compliance

The pattern across these stories is consistent: overtime wasn't being tracked precisely because the systems in place couldn't track it precisely. Paper timesheets required trust but couldn't verify. Manual data entry required labor but couldn't scale. Self-reported hours required honesty but couldn't enforce it.

The result was overtime costs that were unknowable (Shenandoah County), overtime processing that consumed administrative time (Lumberton ISD), and overtime fraud that went undetected until it became a termination case (Blue Mountain).

Those problems were expensive. Now they're also compliance risks.

Time tracking tools don't eliminate overtime. But they do make overtime visible, verifiable, and accurate, which means districts can finally manage it instead of just paying for it. And when the IRS starts asking questions about your overtime data in 2026, you'll need records that can answer them.

The quotes in this article come from real conversations with school Business and Technology leaders who faced these problems directly. Their stories aren't primarily endorsements of a product. They're descriptions of what actually happened when they switched from systems that relied on trust to systems that enforced accountability.

If your district is still running on paper timesheets, manual data entry, or trust-based overtime reporting, these aren't cautionary tales. They're previews. And with new IRS requirements taking effect, the window to fix these problems before they become compliance failures is closing.

 For a complete guide to overtime readiness, including a self-assessment quiz, compliance checklist, and resources for payroll and IT teams, visit the Overtime Ready for 2026 resource page.