What is FIFO accommodation?

FIFO — fly-in fly-out — accommodation houses workers who travel to a remote site, work a fixed rotation, then return home for an equivalent period. It's standard in mining, oil and gas, and remote construction. The defining characteristic for accommodation management is that occupancy is cyclical rather than continuous.

Can two workers share the same bed on opposite rotations?

Yes, and it's common practice — sometimes called hot bedding. It roughly doubles utilisation of the same physical bed. It requires forward-dated allocation with overlap detection, because the failure mode is allocating both workers to the same night when rotations shift.

How do you bill for beds while a worker is off rotation?

It depends on the contract. Held beds are typically billed continuously because the capacity is reserved and cannot be resold. Released beds are billed only for occupied nights. The practical requirement is that the hold-or-release decision is recorded explicitly when the resident departs, and that billing follows that decision rather than being reconciled manually afterwards.

What occupancy rate should a rotational camp target?

Point-in-time occupancy is the wrong measure. Track bed utilisation across a full rotation cycle instead. A camp at 90% peak occupancy may run substantially lower across the full cycle — and that difference is where the commercial opportunity sits.

How is rotational accommodation different from a standard labour camp?

Movement volume and forward planning. A rotational camp processes several times the check-ins and check-outs of a static camp of the same size, and its planning is entirely date-forward rather than current-state. Systems built around a snapshot of today struggle with both.

FIFO & Rotational Workforce Accommodation Management

Most accommodation systems assume a resident checks in, stays a while, and checks out. Rotational workforces break that assumption comprehensively.

On a 28-days-on / 28-days-off rotation, a worker occupies a bed for four weeks, vanishes for four weeks, and returns. Multiply that across a few thousand workers on staggered cycles and the question “how many beds do we need?” stops having an obvious answer.

This article covers what changes when your workforce rotates, and what to look for in a system that can handle it.

Why rotation breaks conventional accommodation management

Occupancy stops being a number

In a static camp, occupancy is straightforward: beds filled divided by beds available. In a rotational camp, that figure is meaningless without a date attached, because it changes structurally every rotation boundary.

What matters instead is occupancy over a cycle — peak occupancy, trough occupancy, and the overlap period when outgoing and incoming crews are both on site. Systems that report a single current occupancy figure give you a snapshot of an oscillating value.

Bed sharing becomes economically necessary

If two workers are on opposite rotations, they can share a bed — one on site while the other is off. The commercial upside is obvious: near-double utilisation of the same physical asset.

The operational risk is equally obvious. Get the rotation dates wrong and two people are allocated to the same bed on the same night — which is exactly what double-allocation prevention exists to stop. Bed sharing therefore depends on disciplined date management: the beds must be genuinely vacated and released between rotations, not merely assumed to be free. If your operation is considering this, talk it through with your provider before designing rotations around it.

Churn volume dwarfs a static camp

A 1,000-bed static camp might process a few hundred movements a month. The same camp on a 28/28 rotation processes over 2,000 — every worker moving out and another moving in, twice per cycle.

At that volume, per-person check-in stops being viable. Bulk operations aren't a convenience, they're the only way the arithmetic works. We cover the mechanics in Mobilising 500 Workers Overnight.

Billing gets genuinely complicated

Does the client pay for the bed while the worker is off rotation?

Both answers are defensible and both appear in real contracts. If the bed is held, the client pays continuously and you cannot resell it. If the bed is released, the client pays only for occupied nights and you can allocate it to someone else — but you must be able to give it back on the return date.

Your system needs to support both — and bill according to the decision actually recorded when each resident departs. Getting this wrong is expensive in both directions: bill for released beds and you'll face disputes; fail to bill for held beds and you're giving away inventory.

What to look for in a system

Forward-dated inventory

The critical capability is knowing availability on a future date, not just today. Rotational planning is entirely forward-looking: you're allocating beds for crews arriving in three weeks against departures that haven't happened yet.

This requires reservations, blocks and maintenance holds to subtract from availability on the dates they apply — not just from a current-state count. Our accommodation management module treats availability as date-aware rather than a single number.

Leave that understands beds

For rotational operations, leave management is not an HR concern that happens elsewhere. Whether a bed is held or released when someone goes off rotation is simultaneously an operational, commercial and billing decision.

The three requirements: the choice is explicit at the point of departure, billing respects it automatically, and return is a guided process rather than a fresh check-in that loses the resident's history.

History that survives churn

With workers cycling through repeatedly, an accommodation record that only shows the current stay is close to useless. You need the full timeline — every stay, every room, every gap — for the same person across months or years.

This matters for more than tidiness. It supports billing disputes, incident investigations, welfare tracking, and the “which room was this worker in last April” question that will eventually be asked.

Reporting built for cycles

Standard occupancy reports assume stability. Rotational operations need:

Occupancy trended across the rotation cycle rather than a point figure
Peak and trough occupancy for capacity planning
Utilisation broken down through property, block, floor and room, exposing areas that sit empty through both rotations
Visibility of confirmed reservations and expected arrivals for the weeks ahead

Reporting and analytics with as-of-date capability is what makes the historical half of this possible — occupancy reconstructed for any past date rather than only today. The forward half comes from reservations and the arrivals planner.

The utilisation question

Here's the commercial heart of it. In a static camp, high occupancy means efficient use. In a rotational camp, high occupancy at peak can coexist with terrible economics if beds sit empty during troughs.

The metric worth tracking is bed utilisation across the full cycle: what proportion of available bed-nights were actually occupied over a complete rotation period, not on a given day.

Operations that measure this usually find something uncomfortable — that a camp reporting 90% occupancy at peak can be running far lower across the cycle, because trough periods are invisible in daily reporting. That gap is either a bed-sharing opportunity or a case for reducing capacity, and you can't see it without cycle-level measurement.

A utilisation heatmap across property, block, floor and room makes the pattern visible: which parts of the estate are genuinely worked hard and which are carried.

Practical starting points

Map your rotation cycles explicitly. Different crews on different cycles is normal. Get them documented before you configure anything, because the cycles determine your peak and trough.

Agree the held-vs-released treatment with each client. Different clients will want different treatment, so settle it in the contract — then make sure the hold-or-release decision is recorded explicitly at each departure, because that recorded choice is what billing follows.

Model bed sharing before committing to it. The utilisation gain is real, but only if rotations are genuinely offset and reliably tracked. Sharing beds on approximate dates creates allocation collisions.

Measure your cycle utilisation first. Before adding capacity, find out what your existing beds do across a full rotation. Many operations discover they have more headroom than they thought.

Clean up who is actually in your accommodation. Rotational workforces accumulate people housed elsewhere — own housing, allowances, client-provided accommodation. If they sit in the resident register unflagged, your peak and trough figures are both wrong, and capacity decisions get made on bad numbers.

FIFO and Rotational Workforce Accommodation: Managing High-Turnover Camps