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.