It's 6:47 a.m. on a Tuesday in July. You're in your truck, stopped for coffee, halfway to the site. Your phone buzzes. It's your best framer. His back gave out last night. He's not coming in.

You have a concrete pour at 8.

You drink your coffee cold and start running through names.

That's what an unplanned absence in peak season looks like. Not just an HR problem — a hit to a day that was already full. And depending on how you handle it, it costs you an hour or the whole week.

What it actually costs

The missing worker is the tip of the iceberg. Underneath, there's a cascade.

The rest of the crew has to absorb. Not just his tasks — the stress, the reshuffling, the fast decisions. If you call someone in last minute, you probably owe them a premium. If you push the pour to tomorrow, the concrete is already ordered. If you run the site short-handed, you lose momentum and your deadline slips.

Then there's the paperwork. He was scheduled for seven hours today. How do you record that? Unpaid absence? Personal day? He's got vacation time banked — does he want to use it? If you work that out on the side of the road at 6:47 a.m., you've got a decent chance of getting it wrong.

The problem with how most shops handle it

In most construction companies, leave and absences are still managed through texts, calls, and handwritten notes on the office calendar. That works. Until July.

In peak season, you might have four active sites, two foremen making their own calls without looping you in, and an office manager trying to reconcile everything on the 25th. That's when you find out one guy took two unplanned days since April, another took a verbally approved week in June, and nobody kept a clean record.

Result: that month's payroll is approximate. Leave balances are fuzzy. And if anyone disputes an amount, you're digging through May texts looking for proof.

What changes when you add a bit of structure

You don't need an HR department. You need a record that stays current without you thinking about it.

In practice, that means three things.

Track absences in the same place as hours. When he doesn't clock in on a Tuesday, you see it. You don't have to call the foreman to find out if he was on site — you already know.

Tag each absence with a category. Unpaid absence, vacation, personal day. Ten seconds to classify when it happens. Thirty minutes to reconstruct it two weeks later if you didn't.

Let payroll reflect reality automatically. If he's on unpaid absence Tuesday, his hours for the week are short and his paycheque adjusts without you recalculating by hand. That's where you get real time back.

Heuro brings timesheet tracking and absence logging into the same workflow. When the office manager validates hours at month-end, the absences are already there, classified, and payroll is right. No catch-up corrections.

How to plan for peak season before it starts

You can't prevent every unplanned absence. But you can reduce the chaos around them.

Do a vacation sweep in May. Ask everyone which two or three weeks they have in mind. You don't have to approve everything — but you'll know what's coming. That stops you from finding out on July 14th that three workers are off the same week.

Have a plan B on every site. A foreman who can reassign two hours of work if someone is missing. A short list of available subcontractors or on-call workers. Write it down somewhere — it doesn't help anyone if it only exists in your head.

Log absences as they happen. Not in a batch on the 25th. Every time someone misses a shift, note it then and there — what, when, why. Two minutes in the moment. If you don't do it on the spot, you lose the details. And the details matter at month-end.

Remind your crew about their leave balances in spring. If your workers have banked vacation time, flag it in March or April. Some will want to take it all at once in July. Better to know that in April than to deal with it on the 10th of July.

The real difficulty is peak season itself

When sites are running flat-out, everyone is moving. You don't have time to update a spreadsheet. You don't have time to check whether he has banked vacation days. You just need the concrete poured.

That's exactly when mistakes happen. An absence coded wrong in payroll. A vacation balance running down without anyone noticing. An office manager catching everything in September because nobody tracked it in July.

An 18-employee contractor in the Montérégie region solved this by connecting timesheet entry directly to payroll. He went from 8 hours to 45 minutes of monthly paperwork — not just reports, but the full administrative load. Absences included.

If your current system has you catching up after the fact, now is a good time to see if there's a better way. Take 20 minutes with us.

Key takeaways

An unplanned absence in peak season triggers a cascade: reshuffling, premiums, delays, and payroll to fix later
Managing absences by text and handwritten notes breaks down the moment the season gets busy
Centralizing hours and absences in the same place eliminates the end-of-month reconciliation scramble
A vacation sweep in May isn't bureaucracy — it's planning
What you don't document in July, you'll be searching for in September