On a well-run site, nobody thinks about fuel. Generators keep running. Lighting towers come on when they are needed. Vehicles, plant and support equipment stay operational. Fuel deliveries happen quietly in the background, and the project simply continues without interruption. That is exactly how it should be — invisible, uneventful and taken entirely for granted.

Fuel only becomes a conversation when something goes wrong. A generator stops. Lighting is lost. Equipment falls silent. Teams start calling one another to find out when the next tanker is due. And by that point the problem is no longer simply a lack of fuel — it has become an operational disruption reaching across multiple parts of the site at once. That is the nature of fuel: it underpins so many systems that when it fails, it rarely fails quietly.

It is rarely a forgotten order

Major sites almost never run out because somebody forgot to place an order. It happens for subtler reasons. Demand was underestimated. Consumption crept up as the site grew. Operating hours changed. A scheduled delivery was delayed. Access restrictions, traffic conditions and shifting site activity can all interfere with what looked, on paper, like a perfectly straightforward supply plan. The order was never really the risky part; everything around it was.

This is why fuel management is best understood as an exercise in planning and monitoring rather than procurement. Experienced teams track consumption across individual assets, not just the total volume delivered to site. They know which equipment is using the most fuel, how that consumption changes as the project moves through its phases, and — crucially — how long the critical systems can keep running if the next delivery does not arrive when it should. That last figure, the buffer, is what turns a delayed tanker from a crisis into a non-event.

Distance sharpens the risk

All of this matters more the further a site sits from its supply. On remote projects, fuel may have to travel a considerable distance before it even reaches the site, and a replacement delivery is not always available at short notice. In that setting a single delayed tanker can knock out power, lighting, transport and several other systems simultaneously, because they all draw on the same source. The margin for error shrinks exactly where the consequences of getting it wrong are greatest.

The delivery process itself has to be coordinated with real care. Tanker access must stay available even as the site fills up and changes shape. Refuelling has to happen without disrupting live activity around it. Storage and transfer arrangements must be managed safely, with environmental protection, spill-response procedures and accurate consumption records all treated as part of the same operation rather than optional extras. Fuel is not just a commodity to be delivered; it is a hazard to be handled properly every time it moves.

A plan that moves with the site

A fuel plan cannot be set once and left alone, because the thing it is planning for keeps changing. Additional equipment arrives. Generator loads increase. Operating hours are extended into the evening. Weather shifts consumption in ways the early estimates never captured. The assumptions made at the planning stage have to be checked, repeatedly, against what is actually happening on the ground — otherwise the plan slowly drifts out of step with reality until the gap catches someone out.

Contingency is the other half of the discipline. The useful question is never simply "have we ordered enough fuel?" It is "can the site keep operating if demand rises unexpectedly, or the next delivery is late?" Planning for the smooth case is easy. Planning for the awkward one — building in the buffer, the backup arrangement, the visibility to see a shortfall coming — is what separates a supply that holds from one that fails at the worst possible moment.

The best fuel strategy is boring

The strongest fuel-management strategies are, in the end, remarkably uneventful. Fuel arrives before it is needed. Levels stay healthy. Consumption remains visible. Critical systems keep running, and nobody pays the process much attention at all.

Because nobody notices the fuel — until it runs out.

The project approaches opening day. Deadlines are advancing. Contractors are moving across the site. Installations are nearing completion, and the operations team is preparing to receive its first guests. Everything visible is coming together.

But hidden deep within the project folders, an overlooked force is waiting. Drawings. Permits. Inspection records. Meeting minutes.

The paperwork is about to strike back.

Overly dramatic? Perhaps slightly. Nobody has ever walked onto a project site and announced that they cannot wait to read the day's documentation. People get excited about opening days, major installations, big deliveries and visible milestones — the things you can photograph. Documentation sits quietly in the background, attracting very little attention and even less affection.

Until something goes sideways.

Then, quite suddenly, everyone wants to know exactly what was agreed, approved, inspected, tested, changed or communicated. Which drawing was issued? Who approved the change? Was the equipment inspected? What did the method statement require? Was the contractor informed? Where is the record? The questions arrive all at once, and they all have the same shape: show me the paperwork.

The least glamorous, most valuable thing on site

Documentation may be one of the least glamorous parts of project delivery, but it is also one of the most valuable. Drawings, risk assessments, method statements, inspection records, permits, meeting minutes, delivery records and maintenance logs together form the memory of the project — the record of how it was planned, delivered and operated. Take that record away and all you have left is what people happen to remember, which on a large, fast-moving site is never enough.

Its purpose is not simply administrative, and treating it as box-ticking is where projects get into trouble. Good documentation exists so that people can make informed decisions. Contractors can confirm access and installation requirements. Infrastructure teams can verify procedures. Operations teams can understand where their responsibilities begin and end. Health and safety teams can review the controls agreed for the work. Everyone works from the same information rather than from their own version of it.

Why it matters more as a project grows

This shared record becomes more important the larger a project gets. A big site may involve dozens of contractors and hundreds of workers, with plans changing rapidly as the build develops. Information moves fast, and in that environment things drift. Verbal instructions become distorted as they pass from person to person. Assumptions multiply. And yesterday's drawing stays open on someone's laptop long after a revised version has been issued — which is precisely how two teams end up building to two different plans without either of them realising.

Documentation is what holds that together, but only if it is accurate, current and accessible. Those three words are doing a lot of work. A perfectly written document buried in the wrong folder is of almost no use. So is an inspection record nobody can find, or a drawing without a clear revision number that leaves people guessing whether they are looking at the latest version. Effective document control is not about producing more paper; it is about making sure the right people can find the right information at the moment they actually need it.

The time it quietly saves

Good documentation also saves a great deal of time, even though the saving is rarely visible. The correct drawing prevents hours of confusion on site. A clear method statement heads off the same discussion being had three times. An inspection record confirms in seconds that work has already been checked, rather than sending someone back to check it again. Properly recorded meeting decisions stop the same argument returning every few days, because the answer is written down and dated rather than relitigated from memory.

The trouble is that all of this success is invisible. Nobody celebrates the information that was easy to find. Nobody tells the story of the drawing that quietly prevented an installation error, or the maintenance record that helped resolve a fault the night before opening. Documentation only becomes noticeable when it is missing — and at that point it tends to return as the most powerful force in the room, capable of stopping work, opening questions and consuming a day that nobody had spare.

Records that earn their place

The strongest project teams understand this, and it shapes how they work. They do not create documents simply because somebody requested them or because a folder needs filling. They create and maintain reliable records because those records help the project operate safely, consistently and efficiently — because good document control is a delivery tool, not a filing exercise. The paperwork is there to be used, not admired.

So the documentation may spend most of the project sitting quietly in the background, unloved and unread, doing nothing to draw attention to itself.

But when the questions begin, may the correct revision be with you.

Temporary infrastructure is one of those things people only notice when it stops working. Guests arrive at a festival and simply expect lighting, toilets, drinking water, food concessions, pathways, communications and power to function. Teams arrive on site expecting welfare facilities, offices, storage areas and operational compounds to be ready and waiting. Suppliers need access routes and loading areas. Security teams require controlled entrances and reliable communications. None of it registers as "infrastructure" to the people relying on it — it simply registers as things working.

Making all of that happen requires a great deal of infrastructure, and the defining challenge is time. On temporary sites, everything has to be designed, installed, operated and then removed within a relatively short window. Temporary infrastructure therefore has to perform like a permanent environment while being built around temporary conditions, changing requirements and strict programme constraints. It must feel settled and reliable to everyone using it, even though it was assembled at speed and will be gone within weeks.

Far more than generators and fencing

It is easy to picture temporary infrastructure as a generator and a run of fencing, but that barely scratches the surface. Power distribution, water supply, wastewater, lighting, temporary offices, workforce facilities, communications, access control, roads, barriers, waste management and security all form part of the same infrastructure network. Together they are the essential systems that allow a site to operate safely and efficiently.

The crucial point is that each element depends on the others. A generator without fuel planning is not a power solution. A toilet block without a water supply or a means of removing wastewater is not a welfare solution. A road without traffic management is not a transport solution. Treated in isolation, each piece is just equipment. It only becomes infrastructure when it is connected to everything around it. This is why the most effective infrastructure is planned as one joined-up system — aligned with the site layout, the construction programme, the operational requirements and the eventual removal — rather than procured as a set of separate packages that happen to share a site.

Planning the systems, not just the kit

Power planning illustrates the point well, because it involves far more than choosing a generator. Load requirements, distribution routes, cable protection, fuel storage, refuelling access and backup arrangements all have to be considered together, and a weakness in any one of them undermines the rest. Water and wastewater systems demand the same joined-up thinking, particularly where there is little or no access to permanent utilities and everything has to be brought in and taken away.

Logistics follows the same logic. Access roads, loading zones and vehicle routes need to work during construction while also supporting the live event — two quite different demands placed on the same ground at different stages. Infrastructure is at its most effective when these individual requirements are planned alongside one another from the outset, rather than solved one package at a time and stitched together afterwards.

When a site becomes a temporary city

Some events operate at a scale where the site effectively becomes a temporary city. Large festivals, major sporting events and big programmes can require workforce villages, production compounds, catering facilities, offices, storage and welfare areas serving hundreds or even thousands of people. At that point the infrastructure is not supporting the event so much as making an entire short-lived settlement habitable and functional.

This becomes particularly demanding in remote environments — remote GCC projects among them — where established utilities may simply not exist. Power, water, wastewater, fuel, communications, waste removal and access may all have to be created or brought to site from scratch. There is no grid to plug into and no mains to connect, so the infrastructure has to provide everything.

Environmental conditions shape the approach as much as scale does. Heat, dust, wind, ground conditions and long distances all affect equipment performance, logistics and maintenance. Infrastructure planning therefore has to consider not only how systems are installed, but how they will be serviced and maintained through the life of the project, and how they will eventually be removed. A system that cannot be reliably serviced in the conditions it sits in is a problem waiting to happen.

Designed around how the site actually operates

Good infrastructure is designed around how a site will genuinely be used, not around a tidy drawing. Vehicle movements, deliveries, workforce shifts, emergency access and pedestrian flows all influence where roads, compounds, utilities and support facilities should sit. Get that relationship right and the site feels effortless to move through; get it wrong and people spend their days working around the infrastructure instead of being served by it.

Phasing matters just as much as position. Infrastructure is frequently installed while other construction activity is still under way, which means access, power and welfare facilities may need to come online at different stages rather than all at once. Because the packages depend on one another, a delay to a single infrastructure element can quickly ripple out and affect the wider programme. Sequencing is not an administrative detail — it is part of the design.

The strongest plans also account for what happens when something goes wrong. Critical systems may need monitoring, maintenance regimes or contingency arrangements to keep disruption to a minimum if a fault develops. The objective is never to install the greatest possible quantity of infrastructure. It is to provide exactly what the project needs to operate reliably, with enough resilience built in to absorb the inevitable surprises.

The mark of getting it right

When infrastructure is designed correctly, it becomes almost invisible. Guests experience the event. Operational teams focus on delivery rather than firefighting. Suppliers work efficiently because the access, power and facilities they depend on are simply there. Nobody has cause to think about the network holding it all up, which is exactly as it should be.

That is ultimately the purpose of temporary infrastructure: not to be seen, but to create the conditions that allow everything else to happen.

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.