At first glance, planning a site compound can look like a game of Container Tetris. Move one cabin to the left. Rotate another. Slot the toilets into the remaining gap and line the storage units neatly along the fence. Everything fits.

The trouble is that everything fitting does not guarantee that anything functions. A tidy drawing and a working compound are two very different things, and the gap between them is where a lot of daily friction is either designed out or quietly built in.

A small operational headquarters

A site compound is far more than a collection of temporary buildings. On a major project it becomes a small operational headquarters, supporting planning, communication, logistics, welfare, maintenance and decision-making — frequently all at the same time. Hundreds of people may interact with it every single day.

Project managers hold meetings there. Contractors come to collect information and permits. Drivers arrive with deliveries. Suppliers need access, visitors need somewhere to report in, and infrastructure teams need space to store equipment and coordinate their work. The real challenge of compound planning is letting all of these activities happen alongside one another without creating unnecessary friction — because when the compound is congested or confusing, that friction is multiplied across everyone who passes through it.

Location: connected, but out of the way

Location is one of the first decisions, and one of the most consequential. A compound positioned too far from the operation creates long journeys and slower response times, quietly taxing every trip to and from it. Position it too close to the centre of activity, though, and it starts contributing to congestion, noise and conflict between vehicles and pedestrians. The aim is to stay genuinely connected to the project without sitting directly in its way — near enough to be useful, far enough not to be a bottleneck.

Layout is where compounds succeed or fail

The arrangement inside the compound matters every bit as much as where it sits. Offices should be positioned around how teams actually communicate and work together, not just where they happen to slot in. Meeting rooms need to be reachable without routing every visitor through restricted workspaces. Storage areas require practical delivery access rather than a theoretical space on the plan. And welfare facilities should be genuinely convenient for the people using them. Throughout, pedestrian routes, parking, loading areas and emergency access all have to stay clear.

There is also a detail that sounds trivial and absolutely is not: the container doors need to open in useful directions. This is normally discovered shortly after somebody has produced a beautifully symmetrical drawing with half the entrances facing a fence. It is a small thing on paper and a daily nuisance in reality — a neat reminder that a compound has to be planned as a place people move through, not a pattern that looks balanced from above.

The infrastructure behind the boxes

A compound is not just the containers, either. It needs power, lighting, water, wastewater management, internet connectivity, furniture, shade and waste facilities to function as a workplace. Air conditioning and ventilation have to reflect real occupancy and working hours rather than a nominal spec, and the utility routes feeding all of this must be protected from vehicles and the wear of daily activity.

Crucially, these systems have to be considered before the compound goes live — not connected wherever space happens to be left over once the cabins are down. A compound planned around its services works from day one. A compound where the services were an afterthought spends its whole life compensating for it.

A facility that evolves with the project

The best compounds also change as the project moves through its phases. During the build, contractor offices, induction areas and storage tend to dominate. As the project shifts into live operations, meeting spaces, communications and operational control become more important. During the dismantle, storage and logistics activity ramps up again, even as the compound itself gradually disappears. A layout with some flexibility built in can adapt to all of this without the whole operation having to be picked up and relocated each time the emphasis changes.

The strongest compounds are rarely defined by their size. They succeed because they make daily working life easier. People know where to go. Information moves efficiently. Deliveries arrive without blocking the entrance. Facilities work as expected, and teams can concentrate on delivering the project rather than fighting the environment around them.

From the outside, a site compound may still look like a collection of rectangular boxes. The pieces may fit together like Tetris.

The real skill is making sure the people do too.

People often assume that the first thing to arrive on a project site — whether remote or in the middle of town — is the main infrastructure: a generator, a building, or a major piece of equipment. It feels logical. The headline items are what the project is for, so surely they lead.

Usually, they don't.

The first arrivals are almost always much simpler: fencing, containers, toilets, water tanks and temporary offices. These are the essential facilities that create a safe, secure and workable environment for everyone who follows. They are not glamorous, and nobody photographs them turning up, but nothing else can happen until they are in place. The big kit is the reason for the project; the modest first arrivals are the reason the project can start at all.

Starting from nothing

Remote projects show this most clearly, because there is often nothing waiting on site at all. No office. No welfare facilities. No storage. No established operational support of any kind. Before the main project can even begin, the entire environment needed to support it has to be created from scratch — the ground has to be made ready to be worked on.

That process usually starts with a small operational footprint: a site office, basic welfare facilities, secure storage and controlled access. Each element earns its place immediately. Teams need somewhere to coordinate their work. Equipment needs protecting the moment it arrives. And the workforce needs the basic services required to operate safely and effectively, because people cannot be expected to deliver a project with nowhere to shelter, wash, eat or store their tools. Only once these foundations are in place can the wider site genuinely begin to develop.

Building a small settlement

In many ways, establishing a remote project is like building a small settlement. The first facilities exist to support the workforce — and the workforce then builds everything else. It is a deliberate sequence, not a coincidence: you put the people in a position to work, and they extend the site outwards from there.

As activity increases, the site grows around that initial footprint. Temporary power and water systems are introduced. Lighting, vehicle routes and operational compounds are established. Storage and welfare capacity expand to keep pace with the growing number of people on site. What began as an empty location gradually becomes a coordinated, fully functioning working environment — one layer enabling the next, in an order that has been thought through rather than left to chance.

This is the logic behind site establishment, and it holds true almost everywhere. Before major infrastructure can be installed, people need somewhere safe to work, rest, eat and store equipment. Get those fundamentals right and you create the conditions for everything that follows. Get them wrong, or leave them too late, and every later stage inherits the problem — a site that is behind before the main work has even begun.

Where it really begins

Strictly speaking, though, the very first thing to arrive on site is usually none of the above. It is someone carrying a 100-metre tape measure, a bundle of marking flags — and a kettle.

That is where the onsite lifecycle of the project truly begins.