1. Booking too late (price spikes, limited stock)

• What goes wrong: Mobilisation creeps up, dates shift, and accommodation becomes a last-minute scramble. Prices jump, quality drops, and teams end up split across multiple properties far from site.
  
  
• Impact: Higher cost, longer commutes, more admin, and tired crews.
  
  
• Fix: Pencil options early, even if dates are still firming. Use rolling holds, staged arrivals, and a simple “go/no-go” check two weeks out.

Example 

A civils team of 8 waits until the Friday before a Monday start. City event week means hotel rates spike and parking is scarce. A week earlier, a two-property set-up near site would have been cheaper and far easier.

2. Pricing per room instead of per property (higher cost per person)

• What goes wrong: Applying a hotel mindset to a team stay. Paying five nightly room rates adds up fast.
  
  
• Impact: Inflated per-person cost, higher spend on meals and laundry.
  
  
• Fix: Compare per-property weekly or monthly rates with the same number of bed spaces. Look for twin rooms and shared homes, not five separate hotel rooms.

Example 

5 workers, 4 weeks. Five hotel rooms at £X per night vs a 3-bed + 2-bed property at £Y per week. The property set-up usually wins on total cost and comfort.

3. Ignoring parking, bed layouts and laundry (hurts productivity)

• What goes wrong: Listings hide details. No van parking, not enough separate beds, or no laundry after muddy shifts.
  
  
• Impact: Missed starts, tired teams, extra spend on parking and laundrette runs.
  
  
• Fix: 
  • Standardise a worker-ready spec in every brief
  • Van parking or on-street tolerance
  • Twin beds where possible (not doubles)
  • Laundry on site
  • Kitchen with proper fridge/freezer
  • Reliable Wi-Fi (speed matters for site updates)
  • Early/late access as needed
  • Heating and drying space for kit
    

Example

Night-shift crew arrives to permit-only streets and a single washer in a basement laundrette. Next day starts late. A simple parking + laundry tick-list would have avoided it.

4. Using consumer platforms for team stays (no PO, no reporting)

• What goes wrong: Consumer platforms look quick, but they are set up for solo or leisure travel. Payments are card-first, invoices vary by host, and there’s no project-level reporting.
  
  
• Impact: Finance ends up with five different receipts, card statements to reconcile, and no clean view by site or cost code. Support is host-dependent.
  
  
• Fix: Use a business provider that supports invoices, POs, consolidated statements and changes mid-stay.

Example

Two sites running in parallel. Consumer bookings produce eight separate receipts across two cards. Finance spends hours matching costs. A single supplier with one monthly statement would have solved it.

5. No flexibility built in (date/guest changes, extensions)

• What goes wrong: Projects shift, bookings don’t. Fixed hotel policies mean cancellations, rebookings, and lost nights.
  
  
• Impact: Fees, admin, and gaps where people have nowhere to sleep.
  
  
• Fix: Agree change-friendly terms up front - guest swaps, phased check-ins, extension options, and clear cut-offs for chargeable changes.

Example

The concrete pour slips by three days. Flexible terms allow a simple extension and two guest swaps by email. No rebook. No fuss.

6. Not centralising bookings (multiple suppliers, no visibility)

• What goes wrong: Each site “sorts their own.” Good intentions, messy results: varied standards, duplicate work, and no joined-up view.
  
  
• Impact: Supplier sprawl, poor leverage on rates, and little control on policy or spend.
  
  
• Fix: One preferred process, one supplier (or a short list), one PO per project, and standard reports. Sites still get what they need — but within a clear framework.

Example 

Five regional projects each book locally. Head office can’t see who is where or what it costs. A centralised flow cuts the admin by half and gives live visibility.

7. Weak location planning (long commutes, late arrivals)

• What goes wrong: Chasing the cheapest nightly rate miles from site.
  
  
• Impact: Lost time, overtime, and late starts. A “cheap” stay becomes expensive once travel and fatigue are included.
  
  
• Fix: Optimise for door-to-site time. Balance rate with distance, traffic patterns, and shift timings. Sometimes paying a little more to be closer saves a lot.

Example 

A team saves £15 per night by staying 35 minutes away. Over a month of early starts, the travel time costs more than the saving.

8. Poor cancellation/terms (fees and rebooking pain)

• What goes wrong: Terms vary by property, small print bites when plans change.
  
  
• Impact: Unexpected fees and gaps between bookings.
  
  
• Fix: Set standard terms across your bookings - clear cancellation windows, named change allowances, and extension priority. Write it in once; apply it everywhere.

Example 

A client wants to push start by a week. With standardised terms, you move the stay without penalty and secure the same properties.

9. Finance friction (no PO support, no credit terms, split payments)

• What goes wrong: Card-only payments, no PO matching, and random receipts land in inboxes.
  
  
• Impact: Month-end reconciliation pain, weak cashflow visibility, awkward audits.
  
  
• Fix: Request PO support, 30-day terms (subject to approval), consolidated monthly invoices, and spend reports by cost centre or site.

Example 

Three sites, 18 workers, 6 weeks. One invoice per month, matched to a single PO with a breakdown by site, is far easier than dozens of card receipts.

10. No feedback loop (issues repeat on the next site)

• What goes wrong: As soon as handover happens, the team moves to the next job and the same problems repeat.
  
  
• Impact: Recurring noise issues, parking headaches, and bed layout surprises.
  
  
• Fix: Run a two-minute post-stay check - what worked, what didn’t, would we rebook? Build a preferred list and a red-flag list. Share it with procurement and ops.

Example 

The quiet cul-de-sac with twin rooms and driveway parking becomes your go-to. The flat above a bar goes on the never-again list.

11. Not aligning accommodation to shift patterns

• What goes wrong: Day-shift rules applied to night-shift teams. Cleaning shows up at the wrong time. Check-in clashes with sleep.
  
  
• Impact: Tired crews and failed starts.
  
  
• Fix: Specify quiet hours, cleaning slots aligned to shifts, blackout blinds where possible, and flexible check-in/out.

12. Overlooking utilities and hidden add-ons

• What goes wrong: “Great rate” excludes utilities, parking or cleaning, which are added later.
  
  
• Impact: Budget creep and awkward conversations with finance.
  
  
• Fix: Confirm what’s included vs chargeable (utilities, Wi-Fi, parking, periodic cleans) and set a cap or bundle where possible.

When this advice matters most

• Multi-week projects with rotating crews
  
  
• Multi-site programmes where bookings move weekly
  
  
• Peak seasons or event weeks in busy towns
  
  
• Rural or edge-of-town sites where parking and access are critical

Who should own what

• Project / Operations define the brief, location priorities, and shift needs
  
  
• Procurement standardise supplier list, terms and SLAs; manage rate negotiations
  
  
• Finance / AP POs, consolidated invoicing, 30-day terms, month-end reports
  
  
• Site Admin / Office Manager day-to-day changes, guest swaps, access and keys

A simple brief that prevents 80% of problems

Send one email (or form) with:

1. Where & when postcode(s), first check-in, likely end date
   
   
2. How many & how they sleep singles vs twins, number of beds vs bedrooms
   
   
3. Must-haves parking for vans, laundry, Wi-Fi speed, early/late access
   
   
4. Shifts day or night, quiet hours, cleaning timing
   
   
5. Finance PO yes/no, billing contact, any cost caps or code splits

Practical examples (so you can sense-check plans)

Example A – Rolling crews, 6 weeks:

Two 3-bed homes within 10 minutes of site. Twin rooms where possible. Parking on driveways. Weekly clean on Fridays 13:00–15:00 between shifts. Guest swaps allowed with 24-hour notice. One invoice per month, PO-matched, breakdown by site.

Example B – Two sites, one project:

Three properties across two towns, coordinated under one booking. Shared terms and one point of contact. Monthly statement sorted by site code and team lead. Extension options held on a soft-confirm basis

Conclusion

Most booking problems come from treating team accommodation like standard business travel. If you plan early, price per property, standardise a worker-ready spec, and centralise your bookings and billing, you’ll reduce cost per person, cut admin time, and keep crews rested and ready. Clear terms and a simple feedback loop will stop the same issues from following you site to site.

Want a quick sense-check for your next mobilisation? Send us your brief and we’ll reply with options, terms and a clean plan that avoids the usual pitfalls.