Monday morning, 7:45 AM. You step out of the truck at the Saint-Lambert site and your phone is already buzzing. It's Martin, your foreman in Boucherville: he's short a formwork carpenter for the morning — can he borrow someone from your crew? You say yes. Martin's problem is solved.

But that guy is going to finish his day in Boucherville and fill out his timesheet Friday evening, from memory, in five minutes at the corner of the table. He'll write his hours. The site — if the pen is still in his hand and he thinks of it. If it's not clear, your office manager will enter what looks logical — probably the site where he works most of the time.

And the labour costs for the Saint-Lambert site will be a little off for that week. Just a little. Not a big deal, once.

Except it happens several times a season. And at the end of the project, when you look at your numbers and costs exceed the estimate, you no longer know whether it's because the project was badly estimated — or because hours have been slipping into the wrong column since day one.

Why hour attribution is the nerve of cost tracking

With one active site, everything goes to the same place. No question to ask.

At two sites, you stay alert. At three or four running in parallel, with crews moving based on urgency, attribution becomes a problem of its own. Every labour hour should land in the right project column, with the right sector and the right conditions. In practice, the snags pile up.

Not out of bad faith. Out of the chain. An employee covering two sites in the same week who checks only one on his sheet. A subcontractor who invoices his hours globally, without breaking them down by project. A foreman who moves resources without notifying the office manager, because he's managing the day, not the accounting.

Each of these snags is mundane. Their cumulative effect, at project close, gives you a picture that no longer matches reality — and on which you can no longer act.

What you lose when costs get mixed up

A site with clean attribution, you can read in real time. If you estimated 1,200 hours for the structure and you're at 900 hours mid-project, you know. If you're trending toward 1,400, you know too. You can adjust before it's too late.

A site where hours accumulate without being clearly tied to the right project, you're flying blind. The information exists — in the sheets, in Excel, in your office manager's head — but it's not organized in a way that gives you a clear picture. You'll know what it cost when it's done. Not before.

And it complicates the next estimate too. If you can't break down what last year's project actually cost by phase and by labour type, you start approximately from scratch on the next one. Estimation errors repeat because the data that would correct them isn't readable.

Three habits that make a real difference, even without changing tools

One unique site code, everywhere. Not "Martin site," "Martin residence," "Martin-Main-Street" depending on who fills in the form. A short name, decided once, used everywhere — timesheets, purchase orders, texts with foremen. Ambiguity slips into data quickly. One word is enough to create it; a standardized code is enough to eliminate it.

A conditions sheet for each active site. Sector, primary occupation, applicable premiums, distance from the meeting point. One page, taped in the foreman's truck or shared on the server. When a guy switches sites mid-week, the sheet tells him what applies there — no need to reconstruct it at month-end from memory.

A weekly look at attributions, not monthly. Ten minutes on Thursday, not on the 14th when pressure builds. An hour mis-attributed on Thursday gets fixed before payroll. Noticed at project close, it no longer changes any of the decisions you could have made along the way.

What it looks like when attribution happens at entry time

The real shift is when attribution is no longer a separate step that someone reconstructs after the fact. It's when it happens at the moment the employee enters his hours.

An employee clocks in from his phone: he picks his site from a closed list, picks his occupation, enters his hours. The rest — the sector, the premiums, the conditions — is already configured on that site. Your office manager doesn't redo the work. She looks at exceptions — duplicates, absences, anything that looks off — and validates.

And you see site costs accumulating in real time. Not a month-end reconstruction. Not an estimate. Yesterday's worked hours, in the right place, available this morning.

The 18-employee contractor in Montérégie manages three active sites with this approach. Zero post-submission corrections since making the switch. Not because his team never makes mistakes — because attribution no longer waits on anyone's memory.

If you want to see what this would look like on your sites, with your crews, take 20 minutes to look at it together.

Key takeaways

When multiple sites run in parallel, every mis-attributed hour distorts the accounting picture for your projects — and you see it only when it's too late to course-correct
The causes are mundane: a guy on two sites, a sub who doesn't itemize, a crew move not communicated to the office manager
A standardized site code, a conditions sheet per site, and a weekly look at attributions already change a lot
The real shift is when the employee attributes his hours to the right site at the moment he enters them — no reconstruction, no ambiguity
You go from "I'll know at project close" to "I know this morning"