It is a question asked on almost every large-scale project, usually early and usually more than once. How many toilets does the site need? It sounds like it should have a tidy answer — a figure to write on a plan and move on from. In practice it is one of the hardest questions to answer with a single number, because no two sites are the same and no two audiences behave in quite the same way.

Attendance provides a starting point, but it does not provide the complete answer. The correct provision depends on who will use the facilities, how long they will remain on site and how demand will rise and fall across the hours, days or weeks of operation. A workforce compound supporting fifty contractors has very different requirements from a festival welcoming five thousand guests. A twelve-hour public event creates a different usage pattern from a two-hour sporting fixture. A parade route behaves differently from an exhibition hall, and a site serving food and drink will see markedly different demand from one that does not.

Local regulations, municipal requirements and applicable event guidance must always be considered, and they set the floor that any plan has to clear. But calculating the minimum number of units is only the beginning of the work, not the end of it. The regulatory figure tells you what you cannot go below. It does not tell you whether the site will actually work.

The real question is behaviour

The harder and more interesting challenge is understanding how people behave and how the event itself shapes that behaviour. People do not distribute themselves evenly across a site. Popular areas create concentrated demand, particularly during scheduled breaks, intervals and the period immediately after an event finishes, when a large proportion of the audience decides to do the same thing at the same time. Facilities in quieter corners may sit largely unused while a block near the main draw develops a queue long enough to become a talking point.

This is precisely why distribution matters as much as total quantity. A site can hold more than enough units on paper and still fail its users if those units are in the wrong places. Facilities have to be positioned where people will naturally need them: easy to find, within a reasonable walking distance, and reachable without forcing anyone to cross a vehicle route, a service road or a restricted operational area to get there. Good welfare provision is as much a question of siting and pedestrian flow as it is of numbers, and it has to be planned alongside the wider overlay rather than dropped in once everything else is fixed.

If you cannot service it, it does not work

There is a second audience for every toilet block that guests never see, and it is the servicing operation. Cleaning teams need regular, repeatable access throughout the event. Water supplies have to be replenished and waste tanks monitored and emptied, often on a tight cycle during peak periods. Service vehicles frequently need to approach facilities without moving through crowds, which means the route in and out has to be considered at the same time as the position itself.

A block that looks perfectly placed from the guest's point of view can be almost impossible to maintain if nobody has thought about how a tanker or a cleaning team will reach it once the site is full. When servicing is designed in from the start — clear access, sensible vehicle routing, waste and water logistics that match the operating pattern — the facilities stay clean, stocked and open. When it is an afterthought, they fail at exactly the moment they are needed most.

The right mix, not just the right total

Different users also need different facilities, and lumping them together rarely serves anyone well. Accessible toilets must be provided in suitable, genuinely usable locations rather than grouped somewhere convenient for the plan but inconvenient for the people who rely on them. Family facilities, workforce toilets, guest provision, VIP facilities and units for contractors working overnight may all form part of a wider welfare strategy, each with its own placement and servicing logic.

The balance of cubicles and urinals should reflect the expected audience and the way it will use the site, rather than a default assumption. And the unit itself is only part of the experience. Handwashing, lighting, clear signage, adequate queuing space and weather protection all contribute to whether a facility actually works when someone reaches it. A toilet block that is technically present but poorly lit, badly signed or exposed to the weather is not really doing its job.

Planning for the peak, and for reality

The average number of users across a full day can be quietly misleading. What matters operationally is not the average — it is what happens when several hundred people decide to use the facilities within the same short window, at the interval or as the site empties. A good plan anticipates those pinch points and provides capacity, distribution and servicing arrangements capable of absorbing them without a queue becoming the story of the day.

Contingency matters just as much. Units can be taken out of service unexpectedly. Attendance can run higher than forecast. One part of the site can become far busier than anyone predicted once the event is live and the crowd finds its own preferences. A strategy built only around the theoretical minimum leaves almost no room for any of this. Building in a margin — spare units, flexible servicing, a plan that can flex when reality does — is what separates a provision that copes from one that comes apart under pressure.

The mark of a good plan

The better plan, then, is not necessarily the one with the greatest number of units. It is the one that provides the right mix of facilities, in the right locations, supported by a cleaning and servicing operation that can actually keep them running throughout the event. Numbers alone never tell the full story; behaviour, distribution, access and contingency are what make the difference on the day.

Most guests will never think about how many toilets were ordered, where they were placed or how they were serviced. They should not have to. They simply expect to find one, clean and open, when they need it. Meeting that expectation quietly, at scale, across an entire site, is the real measure of a welfare plan that works.

Most people think fencing exists simply to keep people out.

While security is undoubtedly one of its primary functions, temporary fencing plays a far broader role in the success of an event, construction project or temporary site. From the moment installation begins, fencing helps establish how a site will operate, creating structure, supporting logistics and enabling teams to work safely and efficiently.

Well-planned fencing is one of the first pieces of infrastructure installed on many projects because it provides the framework around which everything else can be organised.

Defining How A Site Functions

Temporary fencing creates more than a perimeter. It defines how an entire site functions.

Clear boundaries help separate operational areas, establish secure work zones and ensure that different activities can take place safely alongside one another. Whether creating production compounds, logistics yards, welfare areas or restricted technical zones, fencing gives every part of a site a clearly defined purpose.

As additional infrastructure is installed, those boundaries become increasingly important. Temporary cabins, storage compounds, welfare facilities, utilities and production offices all rely on secure, controlled environments to operate effectively.

Rather than acting as a standalone product, fencing becomes one component of the wider event overlay that allows complex sites to function.

Supporting Safe Site Establishment

During the build phase, temporary fencing provides immediate structure for contractors, suppliers and delivery teams.

Clearly defined work areas reduce confusion, helping contractors understand where they can and cannot operate. Vehicle routes remain protected, pedestrian movements can be controlled and deliveries can be directed to designated unloading points without disrupting other activities.

For large-scale events, multiple contractors are often working simultaneously across different parts of the site. Fencing allows these activities to be safely separated, reducing unnecessary interaction between vehicles, plant and pedestrians while improving overall site management.

As the project evolves, fence lines may also be adjusted to reflect changing operational requirements, with compounds expanding or contracting as installation progresses.

More Than Security During Live Operations

Once an event opens, fencing continues to play an essential operational role.

It helps manage pedestrian movement, supports queue systems, protects back-of-house infrastructure and controls access to restricted areas. The same fencing installed during the build phase may be reconfigured throughout the project lifecycle to support changing operational needs.

Depending on the event, temporary fencing can help create:

• Secure production and broadcast compounds.
• Accreditation and staff-only areas.
• Vehicle exclusion zones.
• Service corridors.
• VIP and hospitality access routes.
• Queue management systems.
• Emergency access routes.
• Public and contractor separation.

By creating clear physical boundaries, site operators can manage movement more effectively while supporting both safety and security objectives.

Choosing The Right Fencing Solution

Not every project requires the same type of temporary fencing.

A workforce compound has very different operational requirements from a city-centre public event. Likewise, a sporting venue, music festival or government event may each require different levels of security, privacy and access control.

Common temporary fencing solutions include:

• Heras fencing, providing secure perimeter protection for construction sites, event compounds and temporary operational areas.
• Branded fencing panels, which combine security with event presentation, allowing organisers and sponsors to reinforce branding while maintaining controlled boundaries.
• Shade netting and screening, improving privacy, reducing visual impact and concealing operational areas from public view.
• Pedestrian barrier systems, used alongside temporary fencing to guide visitor movement and create safe circulation routes.
• High-security perimeter solutions, where enhanced access control and additional security measures are required for government, infrastructure or sensitive public events.

Selecting the correct solution depends on the site's operational requirements, expected footfall, security objectives and overall event overlay strategy.

Supporting Security And Crowd Management

Temporary fencing is also an important part of wider security planning.

Rather than relying solely on security personnel, effective fencing creates physical boundaries that naturally influence behaviour and reduce opportunities for unauthorised access.

Clearly defined entry points allow accreditation teams and security staff to manage access more efficiently, while secure perimeter fencing helps protect valuable equipment, temporary buildings and operational infrastructure.

When integrated with vehicle management plans, temporary barriers, access gates and security operations, fencing contributes to a coordinated site management strategy that balances safety with operational efficiency.

Temporary Boundaries That Adapt

One of the greatest advantages of temporary fencing is its flexibility.

Unlike permanent infrastructure, fencing can be installed, relocated and removed as project requirements change. As sites develop, compounds expand, operational areas move and public spaces open, fencing layouts can be adapted to support each stage of the project.

This flexibility makes temporary fencing suitable for projects ranging from short-duration public events to complex multi-week site establishments involving phased installation and dismantling.

Careful planning ensures that every fence line continues to support the evolving operational needs of the site throughout its lifecycle.

The Infrastructure People Only Notice When It's Missing

The interesting thing about fencing is that most people only notice it when something goes wrong.  A missing section.  An unsecured gate.  An undefined boundary.

The consequences become apparent almost immediately.

Without clear perimeter control, vehicle routes become harder to manage, restricted areas become vulnerable to unauthorised access and operational teams lose the structure that allows a busy site to function efficiently.

That is because fencing is far more than a physical barrier.

It is a critical element of temporary infrastructure that supports safety, security, logistics and operational planning from the first day of installation through to final dismantling.

When designed as part of a wider event overlay strategy, temporary fencing helps create environments that are safe, manageable and efficient to operate—allowing every other element of the site to perform as intended.

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.

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.

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.