Power is one of the first things people think about when planning a temporary site. It is also one of the most frequently underestimated. In particular, it is easy to overlook during the creative stages of a project, where the focus is on how something will look and feel rather than on whether it — or the things around it — will need power to work at all. By the time that question surfaces, the load it represents is already real, and it has to be found somewhere in the network.

Many people picture temporary power as little more than a generator connected to a few cables. The reality is considerably more involved. Power distribution means designing a complete electrical network capable of safely supplying every operational requirement across the site — with the protection, circuit breakers and safe separation that a proper network demands, not just a cable run from a generator to a load.

Everything draws on the same network

Almost everything on a modern site depends on that network. Lighting. Production systems. Broadcast facilities. Temporary offices. Catering operations. Welfare compounds. Security infrastructure. Cooling systems. Water pumps. Communications equipment. Every connected asset places a demand on the network, and understanding those demands is where power planning genuinely begins. Before any equipment is installed, planners need to understand what loads will exist, where they will sit, and how they will actually operate through the event.

Those operating patterns matter as much as the raw numbers. Some systems draw power continuously. Others create short, sharp demand spikes that the network has to absorb without affecting everything else. Some equipment is mission-critical and needs redundancy built in behind it. Other equipment can tolerate a brief interruption without consequence. These differences shape how the network is designed, how it is divided up and how much headroom is held in reserve — a load schedule is a description of behaviour, not just a total.

Not all power is equal: separating the networks

One of the most important decisions in temporary power is recognising that not all loads should share the same supply. The instinct is to size a single generator big enough for the total and connect everything to it. In practice, the better approach is often to run separate generator sources and distribution networks for different types of load — and, just as importantly, to keep them apart.

The clearest example is the split between technical, or "clean", power and motor and HVAC, or "dirty", power. Sensitive equipment — audio, lighting control, broadcast, IT and communications — needs a stable, clean supply, with voltage and frequency held within tight limits. Motor-driven and inductive loads, by contrast, behave badly on the network. Air-conditioning units, chillers, pumps, compressors and lifts draw a large inrush of current when they start, and cause voltage dips, spikes and harmonic distortion as they run. Put those two families of load on the same generator and every time a large motor or HVAC unit kicks in, the disturbance ripples straight through to the sensitive equipment — audio glitches, flickering lighting, dropped signals, and in the worst cases equipment that faults or resets at exactly the wrong moment.

Separating them removes that problem at the source. A dedicated technical supply protects the sensitive systems that cannot tolerate a dirty waveform, while motor and HVAC loads sit on their own network sized to absorb their starting currents and fluctuations without affecting anything else. On larger sites this may mean genuinely independent generator sources rather than simply separate circuits from one machine, so that the disturbance from a starting chiller never reaches the broadcast compound. It also makes each network easier to size, protect, monitor and maintain, because the loads on it behave in a predictable, similar way. Deciding early which loads are clean, which are dirty, and how they will be kept apart is one of the quiet foundations of a power design that stays stable under real operating conditions.

Power planning shapes the whole site

Distribution planning does not happen in isolation from the rest of the site; it actively shapes it. Generator compounds need access for fuel deliveries, which has to be planned into the layout rather than discovered later. Cable routes must avoid operational conflicts, pedestrian areas and vehicle movements.

Electrical equipment requires safe separation from public areas. And infrastructure teams need physical space to install, maintain and troubleshoot the network once it is live. For all these reasons, power planning becomes closely bound up with overlay planning, logistics and operations — it is one of the systems that the site layout has to be designed around, not over.

Redundancy and the systems that can't just stop

Redundancy deserves particular attention, because some systems simply cannot switch off if a generator fails. Broadcast facilities, security systems, emergency lighting and other critical operational infrastructure may need backup solutions capable of maintaining continuity right through the event, without a visible break. Designing that resilience in — deciding what must never go dark, and providing the standby capacity and switching to guarantee it — is a large part of what separates a robust power design from one that merely works on a good day.

Local conditions influence the design just as strongly. Power distribution is heavily shaped by local regulations, safety requirements and the environment itself. Extreme temperatures, dust, moisture and difficult site terrain all affect how equipment is installed and which equipment is appropriate in the first place — considerations that come to the fore in demanding settings such as GCC projects, where heat and dust are constant factors rather than occasional ones.

Safe, reliable, manageable power

Through all of this, the objective is not simply to provide power. It is to provide power that is safe, reliable and manageable — a network that can be monitored, maintained and adjusted as the site evolves, rather than one that merely energises a set of loads and hopes for the best.

When power distribution is designed correctly, nobody notices it. Equipment works. Operations continue. Guests enjoy the event. The electrical network quietly does its job in the background, which is exactly how it should be.

Every temporary event project begins with a power plan, and a good one is a genuinely satisfying thing to look at. Load calculations are completed and signed off. Distribution routes are drawn so that every unit draws from the nearest sensible point. Generator locations are agreed, positioned for access, fuelling and acoustic separation from the areas that matter. Cable runs are coordinated with the wider overlay so nothing clashes with pedestrian routes, vehicle movements or the trackway going in the following morning. On paper, everything makes sense. Every load has a home, every run has a purpose, and the numbers balance.

Then somebody walks the site, stops, points to a location on the far side of it, and says the words every infrastructure team has heard a hundred times.

"We need power over there."

No amount of planning seems to prevent this moment. It arrives on almost every project, usually once the site is live and the drawings are already a version or two behind reality. The specifics vary. It might be a catering unit that has been relocated to improve queuing. A temporary office that has quietly grown from a desk into a department. A security position that only became necessary once the traffic management plan was tested against real vehicles. A sponsor activation that was confirmed late and needs to look effortless by gates-open. A welfare facility, a broadcast position, an accreditation point that turned out to be busier than anyone modelled. The request changes shape, but the principle behind it stays remarkably consistent. Power is always needed somewhere that was never part of the original conversation.

This is not, in itself, a problem. Projects evolve. Requirements change as the picture sharpens, new commercial opportunities appear, and operational teams learn things about a site that no drawing could have told them in advance. Movement is a sign that a project is alive and responding to reality rather than clinging to a plan for its own sake. The interesting part is not that the request happens. It is understanding everything that sits behind such a deceptively simple sentence.

Power is rarely just power

To the person making the request, "power over there" is a single item on a to-do list. To the team delivering it, it is a short chain of dependencies that all have to line up. Power requires capacity, and capacity has to exist before it can be handed out — a generator running close to its ceiling has nothing left to give, however keen everyone is to help. It requires distribution: the right cable, correctly rated, routed to the right place through a board that can carry the load safely. It requires protection, both electrical and physical, because a cable across a roadway without ramp or trackway is a trip hazard, a vehicle-damage risk and a failure point all at once. It requires installation by competent people, and it requires maintenance and monitoring for as long as the site is live.

Depending on where "over there" happens to be, it may also require additional fuel planning, a new cable route through an area that was never intended to carry one, or a further distribution point that changes the balance of everything downstream of it. The request itself takes seconds to make. Turning it into a safe, reliable, connected supply can take a great deal of coordination, and often has to happen without disturbing anything already running.

None of this is said to make a simple ask sound difficult. It is said because the gap between the two is exactly where experienced infrastructure teams earn their reputation. Anyone can run a cable. Running one late, into a live site, without compromising capacity, safety or the supplies already in service, is a different discipline entirely.

Planning for the request you know is coming

Because seasoned power teams have heard "over there" so many times, they plan for it long before it is spoken. This is one of the quieter reasons they spend real time during the planning stages talking through future requirements — not because anyone believes every change can be predicted, but precisely because they know change is certain even when its details are not. Flexibility stops being a nice-to-have and becomes part of the strategy itself.

In practice, that flexibility is designed in through a handful of deliberate decisions. Spare capacity is built into generator sizing and distribution so there is genuinely something to give when a new load appears, rather than a plan already stretched to its limit. Utility corridors are protected and kept clear, so that a late cable run has a safe, logical path rather than an improvised one across a busy thoroughfare. Distribution points are positioned to stay accessible, so that connecting a new unit is a matter of reaching the nearest board rather than tracing a supply back to its source. Cable routes are documented as they are installed, so that when a change lands, the team is working from what is actually in the ground rather than from memory.

Individually, none of these choices looks dramatic. Together they are what turn a late request into a straightforward job rather than a scramble. They are the difference between a supply that is added calmly during a quiet hour and one that is chased under pressure while everything else carries on around it. Good overlay infrastructure is not the plan that assumes nothing will change; it is the plan that assumes something will, and leaves room for it.

The part nobody remembers

There is a small and enduring irony in all of this. Nobody remembers the planning conversation where someone insisted on holding back a little spare capacity, or argued for keeping a utility corridor clear even though it was tempting to run something through it. Those decisions disappear into the background the moment they prove useful. What everyone remembers is needing power, getting it, and the site simply working.

And that is exactly as it should be. The entire point of temporary event infrastructure is to support operational requirements as they develop, then to stay quietly out of the way. Back-of-house power, distribution and utilities are successful precisely when they are invisible — when caterers, broadcasters, security teams and welfare providers can do their jobs without ever thinking about where their supply comes from. Infrastructure that draws attention to itself is usually infrastructure that has gone wrong.

So experienced power teams tend to smile when the request finally comes. Not because it surprises them, and not because it is unwelcome. They smile because they knew it was coming. Somewhere on the site. At some point in the build. And, almost without fail, over there.

Infrastructure planning tends to be associated with the big jobs — major festivals, national celebrations, large sporting events, sprawling workforce compounds. Those are the projects that get talked about, and it is easy to assume that careful planning is something reserved for them. The reality is that the same principles apply whether a project serves twenty people or twenty thousand. The scale changes. The thinking does not.

Take a simple generator installation. On the face of it, the requirement could not be more straightforward. Power is needed. A generator is delivered. Problem solved.

Except it isn't, not quite. There are still questions to answer, and they are the same questions a large site would ask. Where will the generator be located? How will fuel be replenished? Who is responsible for monitoring it? Can maintenance teams reach it safely? How will the cables be protected? And what happens if it fails? None of these questions disappear simply because the project is small. There are fewer of them, perhaps, and they are easier to answer — but they still have to be answered, and answering them is what turns a delivered generator into a working power solution.

Small projects still go wrong

This is precisely why experienced infrastructure teams take smaller projects seriously rather than treating them as an afterthought. A small site can still run into real operational trouble. A poorly positioned generator can create noise problems for the people working nearby, or for neighbours. An inaccessible fuel delivery route can cause downtime the moment a tanker cannot get to where it needs to be. Unprotected cabling can introduce a safety risk that has nothing to do with how many people are on site. The consequences may affect fewer people, but they still affect whether the project succeeds — and to the twenty people relying on that generator, a failure is total, not minor.

The same logic runs through every other piece of temporary infrastructure. Welfare facilities, temporary offices, site cabins, lighting towers, fencing — each one has to support the environment around it, and each one benefits from a few minutes of proper thought about where it goes, how it is serviced and what it depends on. A cabin with no thought given to access, or a lighting tower aimed at nothing useful, is just as unhelpful on a small site as on a large one. Good planning is what makes sure each element actually does its job.

The commercial case for planning small

There is a straightforward commercial argument here too, and on small projects it is sharper than people expect. Small issues on small projects can consume a wildly disproportionate amount of time. A few hours spent solving an avoidable problem might represent a significant slice of the entire programme when that programme is only a few days long. On a large project, a delay of a few hours disappears into the schedule; on a small one, it can be the difference between finishing on time and not. Simple, proportionate planning up front is almost always cheaper than the disruption it prevents.

None of this means a small project needs the same volume of planning as a major event — that would be its own kind of waste. It means it deserves the same quality of thinking, scaled sensibly to the job. The mindset is what carries across, not the paperwork.

Importance doesn't wait for scale

Large projects will always attract more attention, bigger budgets and more scrutiny. That is fair enough. But smaller projects still deserve the same professional approach, because infrastructure does not suddenly become important once it passes a certain size.

It is important from the moment somebody depends on it.

Water has a habit of becoming important very quickly. At the start of a project, the conversations tend to gather around the visible infrastructure: power, buildings, containers, roads, fencing. Water receives comparatively little attention. It is assumed, rather than planned — right up until somebody needs it. At that point it suddenly reveals itself as one of the most important systems on the entire site.

And it is needed in more ways than people first realise. Drinking water. Toilet facilities. Cleaning operations. Catering. Dust suppression. Animal welfare and cleaning. Landscaping. Many projects lean on water across far more of their operation than the early planning would suggest, which is exactly why a shortfall is felt so widely when it comes.

Deceptively simple

The interesting thing about water infrastructure is how simple it appears. A tank arrives. A tanker delivers water. Problem solved. It is the same trap that catches people out with power and fuel — mistaking the delivery of a thing for the management of a system.

Because somebody still has to calculate the demand in the first place. Somebody has to schedule the deliveries, monitor consumption, manage the storage, coordinate replenishment before levels run low, and plan for the situations where the normal arrangement fails. The tanker itself is only one visible part of a system that is mostly invisible. Get the system right and the tanker looks like the whole answer; get it wrong and the tanker turns up to a problem that started days earlier.

When one missed delivery hits everything at once

This matters most on remote sites, where the margins are thin and there is no mains to fall back on. It is worth drawing the contrast with fuel. A missed fuel delivery may take out a generator — serious, but relatively contained. A missed water delivery can affect entire sections of site infrastructure simultaneously. Toilets stop functioning properly. Cleaning operations become difficult or impossible. Catering is disrupted. Workforce welfare suffers almost immediately, and operational pressure builds fast, because so many different things were all quietly relying on the same supply. Water failures rarely stay small.

This is why experienced infrastructure teams spend real time on water logistics rather than treating it as an incidental. Consumption forecasts, delivery schedules, storage capacity and backup arrangements all work together to create reliability — and each one is a hedge against the day the routine plan meets an unexpected demand or a late tanker. Storage in particular does a lot of quiet work: enough on-site capacity turns a delivery problem into a manageable buffer rather than an immediate crisis.

Normality is the whole point

Guests rarely think about any of this. Neither, in truth, do most of the workforce. They simply expect the facilities to work — the tap to run, the toilet to flush, the catering to open. That expectation is entirely reasonable, and meeting it is precisely the job. The objective of infrastructure is to create normality in environments that are often anything but normal, and water is one of the systems that normality depends on most.

The water tanker may never receive much attention or a word of thanks. That, usually, is the surest sign that the planning behind it worked.

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.