5:28 AM, a Tuesday in March. Your phone rings on the nightstand.

It's Daniel, the foreman in Saint-Hyacinthe. Temperatures dropped to minus seven overnight, the frost warning extends to 10 AM. The concrete pour scheduled for 7 AM is cancelled for this morning. Three of your guys are already in their trucks. Another has been on site since 5:15 — he wanted to check the formwork before the others arrived.

You stare at the ceiling for a second. Then you call Daniel back.

Weather is part of the trade. Everyone knows it. But every time it happens, you face the same question: what do I do with the guys who already left? Is it a paid day, a half-day, nothing? And the rest of the week — how do I reorganize without losing what we had planned?

Those answers, if you have no protocol, you improvise. Improvising is expensive — in time, in payroll errors, and in difficult conversations at 6 AM on a frozen site.

What weather changes in payroll

That's where people get it wrong most often.

A weather stoppage isn't just a day that gets erased. Under Quebec's construction framework, the rules on what is owed vary depending on the concrete situation: was the employee already on site? On his way? Notified the day before?

An employee who drove 40 minutes to arrive at 5:30 AM and leaves at 6 AM because conditions are impossible — that gets documented differently than an employee notified by text the night before. The distinction plays out at the departure time, the stoppage time, and where the employee was when the decision was made. It's in the rules of the sectoral regime covering your employees, and it depends on the site.

What you document that morning — or what you don't — will dictate what shows up on the next paycheque.

The three situations that cause the most trouble

The employee already on site. He showed up. He made the drive. Depending on how long he waited and what his sectoral regime provides, he may be entitled to a minimum number of hours. The rule needs to be known in advance — not decided in the corner of a truck at 6 AM in the cold.

The employee en route. He got the call while driving. He turned around. Does travel time count? The answer depends on the regime that applies to this site. It needs to be documented — not reconstructed three Fridays later when the office manager is preparing payroll.

The employee not officially notified. He saw the weather forecast the night before, assumed the site was closed, didn't show up. You may have an unauthorized absence situation depending on what was communicated, by whom, and when. Without a trace, that's going to be hard to sort out.

These three situations come back every winter. What changes is whether you have a protocol or whether you start from scratch with every weather advisory.

The lost day that becomes a broken week

A weather stoppage is rarely just one day.

It's the pour pushed back 48 hours. The electrical crew that was supposed to start Friday waits for the slab to be ready. The client wants to know if the delivery date still holds. And you need to redistribute people — to another site if there is one, or send everyone home and absorb it into margins.

To do this, you need to know where you stand on each active site: how many hours worked this week, who is available, which tasks can move forward indoors. Without this visibility, you do it from memory. And memory, at 6 AM in March, is a limited resource.

Having the protocol before the sky decides

Not during. Before.

A decision tree, in writing. Who declares the stoppage? Before what time do guys need to be notified so they don't have to make the trip? If the notice comes too late, who calls whom, in what order? A one-page document, shared with all foremen, updated every fall before the cold season. It resolves most of the friction before it even appears.

A clock-in that captures the real time. Not a timesheet filled out Friday from memory. A clock-in done from the phone at the moment the employee arrives on site — or from his truck when he gets the stoppage call. The time is there, timestamped, without having to call anyone Monday to reconstruct who was where at what time.

A default redistribution plan. If you have multiple sites, which one can absorb extra people indoors? What kind of work can move forward when concrete is blocked? Having this reflex thought through in advance is the difference between a half-day recovered and a full day lost to margins.

When the data is already there

The 18-employee contractor in Montérégie we follow in our case study regularly handles this kind of situation with three concurrent sites. When a day goes sideways, it's the clarity of the information — who was on which site, at what time — that lets him redistribute without anything falling through the cracks. His office manager doesn't spend Monday reconstructing. The data is there.

If you want to see what this changes for managing these situations without an administrative crisis, take twenty minutes with us.

Key takeaways

A weather stoppage creates three different situations depending on where the employee was when the stoppage was declared — each is paid differently under the applicable sectoral regime
Without real-time timestamping, your office manager reconstructs everything from memory days later, with the errors that come with it
A clear protocol — who decides, who notifies, before what time — prevents improvising at 6 AM below minus seven
A redistribution plan thought out in advance turns a lost day into a half-day recovered
The real cost of a weather stoppage is rarely the day itself — it's everything that shifts in the week that follows