Discovery
We collect the event date, location, attendance, devices, zones, site plan, structures, power and support requirements.
Planning and delivery
The process separates assumptions from confirmed requirements, so the network can be designed, priced and supported properly.
The full process
We collect the event date, location, attendance, devices, zones, site plan, structures, power and support requirements.
We choose the backhaul, distribution method, access point locations, network separation, resilience and equipment allowance.
The proposal defines what is covered, what the organiser must provide, access times, change control, support and payment terms.
Equipment is installed, tested and monitored. Live support and teardown follow the agreed event schedule.
Stage one
“Wi-Fi across the event” is not a usable scope. The starting point is a location list: bars, trader rows, entrances, production areas, ticketing, medical, staff compounds and any guest areas. Each location should then identify the devices that need service and the structure they sit inside or beside.
For outdoor events, we also confirm power, approved mounting methods, cable routes, vehicle routes, public areas and line-of-sight restrictions.
Backhaul brings internet to the event. Distribution moves it around the event. A site may use Starlink, mobile data, fixed broadband or several connections, but still need point-to-point links, switches and access points to reach distant operational zones.
A small market with ten traders has a different risk profile from a multi-day festival with several bars and production networks. We scale backup connections, spare equipment, monitoring and engineer coverage around the commercial and operational impact of downtime.
Moving a bar, adding a campsite or changing which areas need service can alter the network design. The proposal records the plan and assumptions used. Later changes can then be reviewed as variations rather than quietly absorbed into an increasingly unreliable scope.
Testing should include the actual coverage zones, expected device types, network separation and backhaul behaviour. Where practical, critical card terminals, tills, scanners or production devices should be checked before the event opens.
Request a connectivity plan
It does not need to be final, but mark every area that currently needs connectivity.