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.

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.