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.