Tuesday morning, 7:12 AM. Your employee is in the doorway of the site office, his paycheque stub folded in two in his hand. He doesn't look angry. Not yet. But he has that look — the guy who's been turning the problem over in his head since the night before and is determined to understand.

"Pierre, I have the same hours as last week, but the travel premium isn't there."

You look at your office manager. She pulls out the timesheets. Someone switched trucks on Thursday without noting it. She didn't connect the site to the distance. Twenty minutes to sort it out, a correction on the next pay. Pierre goes back to work. He's fine. But he's going to watch his next stub like a hawk.

And that's just the error you know about.

What it costs directly

The correction itself — everyone knows what that looks like: find the gap, calculate the shortfall, issue the adjustment. But how much time did your office manager spend tracking down the right timesheet? Calling the foreman to confirm which truck left that Thursday? Checking whether other employees took the same route?

In practice, a simple correction pulls 30 minutes to an hour, once you include the whole chain. Multiply by the number of corrections you had last year. The total is rarely pleasant to look at.

And that's not counting the errors in the other direction — the ones nobody ever notices. A rate misapplied, a premium that shouldn't have been paid but was because the site conditions were misconfigured. Those ones disappear into labour costs, into margins, into the impossibility of understanding why a project came in over budget.

What it costs outside the books

That's where it hurts most.

Pierre is going to look at his next stub much more carefully. And if it happens again, he'll start talking about it in the truck. Not out of malice — just because it's natural to talk about what bothers you at work.

Employees who audit their own pay aren't a sign that something is generally wrong. They're a sign that something already went wrong. Trust, once dented, rebuilds slowly — one paycheque at a time.

And it affects morale in a way that's hard to measure. A guy who knows his pay will be right shows up differently than a guy who has to check. It's not dramatic. It's subtle. But over a season, you feel it.

Where errors actually come from

The cause is almost never bad faith. It's the chain.

An employee fills out his timesheet Friday evening, from memory, for the last five days. He notes the hours. The premiums — travel, remote site, elevation — he puts them in if he thinks of them. Your office manager transcribes that into Excel, interprets what's ambiguous, applies the rates she knows. If the rate table changed in spring and nobody told her, she keeps using the old one.

At one employee and one site, it holds together reasonably well. At 18 employees and three sites with different conditions — one residential, one institutional-commercial, one remote — the margin of error compounds at every step. And the problem is you can't see it. You see the error three weeks later when Pierre shows up in the doorway with his stub folded in two.

What you can change without turning everything upside down

There are habits that reduce exposure, even without changing tools.

Lock in the conditions for each site from the start. Sector, applicable premiums, distance, accommodation or not. A shared sheet with your office manager and your foremen. When an employee starts on that site, everyone knows what applies — no need to reconstruct it at month-end from memory.

Validate timesheets before end of week, not after. A look on Thursday evening takes ten minutes. An error caught Thursday gets corrected before payroll. An error caught the day after pay day is a conversation, a correction, and an employee who loses a bit of trust.

Check your rate table every spring and fall. Rates change under Quebec's sectoral construction framework. Set a reminder. Otherwise you risk running six months with the right numbers at the wrong date — and corrections always come at the wrong time.

These three habits don't eliminate all errors. But they eliminate the most common ones.

When the system does the math for you

The real way out of the cycle is to remove the steps that depend on human memory.

That's the principle behind Heuro: when an employee clocks his hours from his phone, directly on site, the conditions are already configured. The sector is known. The distance is calculated. The premium applies or doesn't, based on what was decided once when the site was set up. Your office manager isn't redoing the calculation — she's checking exceptions and validating.

The 18-employee contractor in Montérégie we describe in our case study has had zero post-submission corrections since adopting this approach. Not because his team is perfect. Because the system no longer asks everyone to hold everything in their head at once.

If you want to see what it changes for your team, sign up for early access — or take twenty minutes with us if you'd rather talk it through first.

Key takeaways

A payroll correction typically costs 30 minutes to an hour, once the full chain is included
The real cost is the trust the employee loses — and that rebuilds slowly, one paycheque at a time
Errors almost always come from a chain that depends on human memory at every step
Locking in site conditions, validating early in the week, keeping rates current: that's already a lot
The real way out is taking the calculations out of people's heads and putting them in the system