There is a predictable moment in project planning meetings when accommodation comes up. It's typically near the end. The budget is largely set, the team is confirmed, the site is ready, and someone asks, almost as an afterthought, where everyone is staying.
The assumption behind the question is that accommodation is an admin task. Something to sort quickly so the meeting can move on. Any decent option within range of the site will do, and the real differences between one and another come down to price.
It's a reasonable assumption. It's also, fairly consistently, the wrong one.
What the nightly rate doesn't capture
Take a construction team: ten people, eight weeks, working away from their home city on a project running to a tight programme. Two accommodation options are on the table. Option A costs £15 per person per night less than Option B. Over eight weeks, that is a saving of roughly £8,400. At face value, Option A is the obvious choice.
Except Option A is 45 minutes from the site by public transport. Option B is a 12-minute walk. Option A is hotel rooms with no cooking facilities. Option B is self-contained apartments. Option A has a checkout policy that creates a problem on the one Sunday morning the team needs to be on site by 7 am. Option B doesn't.
The £8,400 doesn't disappear from the project. It moves. Some of it becomes transport costs. Some becomes lost time at the margins of each working day. Some of it becomes a resignation in week five from someone who has spent eight weeks in a hotel corridor and decided that the next project will be with a different employer. The cost of replacing that person — recruiting, onboarding, the weeks before they reach full productivity — is not captured on the accommodation invoice. But it is real, and it is traceable back to that original decision.
Where the costs go when nobody's looking
The reason accommodation decisions so rarely get examined after the fact is that the costs distribute. They land on different budget lines, different teams, and different points in the project lifecycle. Fatigue shows up in rework data. Turnover shows up in HR. Transport costs get absorbed into the general logistics figure. No single person is looking at the total, which means no single person is asking whether it could have been avoided.
Organisations that have started asking that question tend to find the same things. Workers who are housed well, with space, privacy, a kitchen, and a commute that doesn't eat an hour of their day, arrive in better condition. They stay on projects longer. They're easier to bring back for the next one. These are not marginal differences over the life of a programme.
The pattern holds across sectors. NHS trusts deploying temporary clinical staff see it. Insurance firms sending loss adjusters into the field for three or four weeks at a time see it. Companies managing staff relocations see it. The operational context changes; the underlying cause and effect doesn't.
Why this is a planning decision, not a procurement one
The shift that changes outcomes is treating accommodation as a decision that belongs in project planning, not in the week before mobilisation.
Companies that approach it this way tend to have figured out a few things. They know which providers can actually flex around project timelines because timelines move, and a provider with rigid checkout terms becomes an operational problem the moment the programme shifts. They know the difference between accommodation that works for a two-day business trip and accommodation that works for a ten-week deployment. And they've built workforce housing into their employer proposition, because the labour market for skilled project workers is competitive, and what it's like to work away from home is part of what experienced workers weigh when they're deciding where to take their next job.
The UK construction industry has a sustained skills shortage. The NHS faces similar pressure. The organisations that retain experienced workers across multiple projects tend to be the ones that treat working away from home as something they actively manage, not something they leave to chance.
What good looks like in practice
A self-contained apartment with a kitchen is meaningfully different from a hotel room with a kettle. Not because of aesthetics but because of what it makes possible. Someone spending six weeks in a city can cook, can vary their meals, and can have something resembling a normal evening after a long day on site. That affects how they perform the following morning. It affects whether they come back for the next project.
Proximity matters more than most accommodation briefs acknowledge. A 10-minute walk to site and a 40-minute commute are not logistically equivalent, even when the cost difference appears modest.
Flexibility at both ends of the stay matters. The ability to extend a booking quickly when projects overrun and to add rooms when teams grow is operationally valuable. Building that flexibility into an accommodation arrangement in advance is straightforward. Scrambling for it at short notice is expensive and disruptive.
And consistency matters, perhaps most of all. When workers know that project accommodation with a given employer is reliable, not luxurious, just functional, well-located, and properly managed, that becomes part of what they associate with working for that organisation. It is part of the offer.
The practical question
Most organisations don't change how they approach accommodation because of an argument. They change when they can see clearly that the current approach is costing them something they'd rather keep.
If you're running projects with workers deployed away from home, the cost is probably there. It's showing up somewhere — in turnover, in performance, in the friction of last-minute bookings that could have been planned for. The question is whether it's being measured against the thing that caused it.
We work with project managers, HR teams, and operations leads across the UK who have started treating accommodation as the business decision it is. If you'd like to talk through what that looks like for your next project, get in touch.
