The 45-Minute Drive That's Quietly Wrecking Your Safety Record

Nobody books housing 45 minutes from a job site on purpose. It just happens.

The nearby properties were already booked. The ones within twenty minutes were too expensive. Someone found a block rate at a hotel off the interstate, ran the math, and it looked fine on paper. Forty-five minutes isn't bad — people commute that far to regular jobs all the time.

Except a construction crew isn't driving to a regular job. They're driving to a twelve-hour shift that starts at six in the morning and ends after the sun goes down, on tired legs, with the kind of physical demands most white-collar commuters will never experience. And they're doing that drive twice a day, five or six days a week, for eight to fourteen weeks straight.

Forty-five minutes each way stops being a commute somewhere around week three. It becomes a second shift — one your crew works without pay, without rest, and without anyone counting it on the schedule. And that second shift is where safety quietly starts to erode.

How Commute Creep Actually Happens

Nobody on your team is trying to book bad housing. Commute creep is usually a series of small, reasonable-looking decisions that compound.

The job site location gets confirmed. Someone starts sourcing housing. The closest options are full or overpriced. A property twenty minutes out looks great, but only has half the rooms you need. So you take what you can get — eight rooms at the twenty-minute property, twelve rooms at the forty-minute property, and you figure it evens out.

Then the project extends. More crew comes in. The only availability left is at a property fifty minutes away. The original plan of "most of the crew is close" becomes "most of the crew is far." Nobody flagged it because each individual booking decision made sense in the moment.

This is how a crew ends up averaging forty-five minutes each way by week four of a project that started with a plan for twenty. And because it happened gradually, nobody is treating it like the problem it actually is.

The Fatigue Math the Schedule Doesn't Show

Let's run some honest numbers.

A crew member on a standard 10-hour shift, with a 45-minute commute each way, is really looking at an 11.5-hour workday — minimum. Add gearing up, safety briefings, lunch, and the actual time it takes to get in and out of a vehicle, and you're closer to twelve and a half hours of active time away from their bed.

Subtract that from 24 hours. You've got 11.5 hours left for everything else — dinner, a shower, unwinding enough to fall asleep, actual sleep, waking up, getting dressed, and getting back in the truck.

Sleep research is pretty clear on this: adults need seven to nine hours to function well. If your crew is getting six or less, they're running a sleep deficit. Multi-week sleep deficits compound. By week three, someone getting six hours of sleep a night is operating at roughly the cognitive level of someone who has had a couple of drinks. By week six, it's worse.

And that's for a crew member with no kids, no stress, and a housing situation that actually lets them sleep. Add a noisy hotel hallway, a truck yard outside the window, or a roommate on a different shift, and the sleep budget gets even tighter.

The commute isn't just eating their personal time. It's eating the recovery window their body needs to be safe the next day.

Why Safety Risk Doesn't Show Up in Week One

Here's the tricky part about fatigue-driven safety risk: it's almost invisible at the start of a project.

In week one, everyone is fresh. The commute feels manageable. The crew is dialed in. Safety performance looks strong. This is where a lot of project managers conclude that the housing decision was fine, because nothing bad is happening. And for a short project, they'd be right.

But fatigue is a slow burn. Week one looks fine. Week three, you notice the crew is a little quieter during the morning briefing. Week five, there's a near-miss that gets chalked up to bad luck. Week seven, someone cuts a corner on a fall-protection setup because they're five minutes behind and exhausted. Week nine, there's an incident.

Incident reports rarely trace back to the commute. They get attributed to the direct cause — a missed step, a tool mishandled, a distraction. But the underlying condition that made the mistake more likely is often the same: a crew that has been running a sleep deficit for a month and a half because housing was forty-five minutes from the gate.

This is what "fatigue-related safety exposure" actually means in the field. It doesn't look like people falling asleep at their stations. It looks like mental margins getting thinner. Reaction times slowing by fractions of a second. Judgment calls getting sloppier. Communication getting quieter. The kind of stuff that doesn't cause an incident on any given day, but makes one more likely every day, across hundreds of days of crew-hours.

The Drive Home Is the Other Half of the Problem

Most conversations about commute and safety focus on the morning — getting to site. But the bigger risk is often the drive home.

Think about when incidents tend to happen on highways. Late afternoon and early evening, when people are tired, distracted, and driving familiar routes on autopilot. Now put your exhausted crew on that road, after a full shift, in pickup trucks or crew vehicles, with another forty-five minutes between them and a hot shower.

Vehicle incidents are the leading cause of fatality in construction, and they happen disproportionately on the commute. Long drives after long shifts stack the risk. You're not just taking on jobsite incident risk — you're taking on highway incident risk, and that one can end a life without anyone ever setting foot on the project.

When a crew lives close to the site, the drive home is a buffer. When they live far, it's another hazard.

What "Close" Should Actually Mean

There's no magic number, but there's a reasonable benchmark worth holding to.

Most operations leaders who have thought carefully about this land somewhere around fifteen to twenty minutes as the target, with thirty minutes as the upper edge of acceptable. Past thirty minutes, you start losing meaningful recovery time, and past forty-five, you're actively burning into sleep debt over the course of a multi-week deployment.

This isn't about making housing a perk. It's about recognizing that a construction worker's body treats a long daily commute the same way it treats overtime — as added load. And load without recovery is how people get hurt.

The companies that take this seriously build commute distance into their housing decision criteria up front. It's not the only factor, but it's a filter — properties beyond a certain radius don't make the list at all, unless there's a documented reason and a mitigation plan.

That kind of constraint feels limiting in the moment. It feels a lot less limiting than a safety incident.

What Changes When You Treat Distance as a Safety Variable

When housing proximity becomes part of the safety conversation instead of the budget conversation, a few things shift.

Sourcing starts earlier, because you know short notice usually means a worse commute. Properties get evaluated on drive time as a hard criterion, not just a nice-to-have. Project extensions trigger a housing review, because the commute plan that worked for six weeks might not work for twelve. Safety officers get a voice in housing decisions — not because they're trying to take over procurement, but because they're the ones who understand what compound fatigue does to a crew.

And across the project, small things get better. The morning briefings land harder. The afternoon productivity holds steadier. The near-miss logs look cleaner. And the EMR — the thing your insurance premium is priced on — doesn't take the hit that a distant, tired crew eventually delivers.

This isn't about making housing more expensive. It's about recognizing that a cheaper property forty-five minutes out may be the most expensive line item on your project, if it ends in an incident.

Your Next Move

Commute creep is one of those things that's hard to see until you know to look for it. Once you do, it's everywhere — and the fix starts at the front end of the housing decision, not the back end.

We put together a short read on exactly this: the Commute & Safety Risk Planning Guide. It walks through how to assess proximity against fatigue exposure, where the real thresholds are, and how to build commute distance into your housing decisions before a project kicks off instead of after.

It's built for project managers, safety leads, and operations teams who'd rather catch this in planning than in an incident report.