Thursday. 5:40 PM. Your office manager is sitting in front of eight timesheets from the Boucherville site, and one of them says Marco worked 10 hours on Tuesday.

She knows Marco left at noon.

She pulls out the absence log. Nothing. Calls the foreman. Voicemail. Leaves a message, goes back to the other sheets. Two have a site code she doesn't recognize — a digit missing, or maybe the wrong format. Those can wait.

The coffee on her desk has been cold for an hour.

This isn't a bad day at work. This is a normal Thursday.

The errors you can see

The easy ones first: the guy who logged 12 hours on a day that got rained out at 1 PM. The hours are in the site diary — if you have one. Or in the foreman's phone, if you think to call before Friday evening.

Then there are the duplicates. The same employee on two sites on the same day. It happens more than you'd think — a mid-week transfer that didn't get communicated, a timesheet filled out in advance, a copy-paste in Excel that went sideways. You notice because the hours don't balance.

And the undocumented absences. An employee who missed Monday but still submitted Monday's hours — because he'd already pre-filled the same template from last week, and nobody thought to clear the line.

A good office manager catches all of this. It costs her time — but she catches it.

The errors you can't see

That's where it actually costs money.

An employee switches tasks mid-week — framing on Thursday, concrete work on Friday. He notes his hours, not his trade. Your office manager applies his usual classification. If both trades carry the same rate, it goes through. If they don't, you've got a problem you may never find.

Premiums work the same way. A site 55 km from the employee's home — the travel premium applies. Except he didn't write it on his sheet. Your office manager doesn't know exactly where he lives. And nobody told her the site conditions changed in June when the contractor shifted territory.

And then there are the rate tables. Quebec's sectoral construction framework updates its schedules on fixed dates. If your office manager is still working from last season's version, the math is technically correct — just with the wrong numbers.

None of these errors are obvious at first glance. They hide in labour costs, in job margins, in the projects that come back over budget for no apparent reason.

Why this happens so often

Short answer: the chain is too long.

The employee fills out his timesheet Friday evening. From memory. For five days. He's not cutting corners — he's doing his best with what he remembers. Your office manager retypes it into Excel, interprets the illegible codes, fills in what's missing with what she knows. She's doing her best too.

But between the jobsite and the paycheque, the information has changed hands three or four times. Every handoff is a chance for error. And errors compound.

The problem isn't the people. It's the system.

What you can change this week

You don't need to overhaul everything to cut your exposure.

Lock in the conditions for each site from the start. Sector, applicable premiums, trades on site, travel distance. A simple sheet — paper or digital — that your office manager and foremen both have. When an employee starts on that site, there's nothing left to guess.

Validate timesheets mid-week, not just at the end. A quick scan Wednesday evening catches errors while people are still on site and memories are fresh. Waiting until Friday means asking everyone to recall a five-day-old detail correctly.

Flag anomalies the moment you see them. A two-hour discrepancy, an unfamiliar site code — if you leave it to handle later, it gets buried in the pile. Five seconds of noting it now saves twenty minutes of searching tomorrow.

These three habits don't fix everything. But they catch most problems before they reach payroll.

When the system does the checking for you

The real error reduction comes from removing the steps that live in people's memory.

That's what Heuro is built around: employees clock in from their phones, directly on site. Trade, site, applicable premiums — all pre-configured. Nothing to guess, nothing to interpret, nothing to retype.

Your office manager sees the anomalies — double-time, absences — and validates. She's not reconstructing reality from scraps of paper.

The Montérégie contractor in our case study hasn't had a single post-submission correction since switching to this approach. 18 employees, three active sites. The system runs the numbers — she checks the exceptions.

If you want to see what that would look like for your team, let's talk.

Key takeaways

Visible errors — wrong hours, wrong site — cost correction time
Invisible errors — missing premiums, wrong trade codes, stale rate tables — cost money and margins
The cause is almost never bad faith: it's a chain with too many manual handoffs
Locking in site conditions, validating mid-week, noting anomalies immediately: three habits that change a lot
The real fix is removing the retyping and letting the system handle what it can