Skip to main content

Local Government WiFi procurement checklist: public WiFi, staff 802.1X and filtering across municipal buildings

Use this checklist to write a local government WiFi RFP that you can score: four separated networks, staff access tied to your identity provider, certificates on government-owned devices, filtering on every public site and plain-English ward reports. You will also know which evidence to request from bidders and which eight tests to run before go-live.

By James KeanPublished
📖 14 min read3,145 words3 worked examples12 key definitions

Local Government WiFi procurement checklist: public WiFi, staff 802.1X and filtering across municipal buildings

A city or county council WiFi RFP should specify four networks. Residents and visitors get public WiFi with an accessible fair-use sign-in. Staff connect over IEEE 802.1X tied to your identity provider. Council-owned devices use certificates, and building systems sit on isolated networks. Every public network is filtered, and council members receive plain-English reports by site and district.

Which networks does a council WiFi RFP need to cover?

Most local government WiFi grew one building at a time. The result is often one network carrying residents, staff, and CCTV together. The RFP is your chance to separate it by who connects and what they need.

Four networks cover city halls, libraries, recreation centers, and maintenance yards.

Network Who uses it How they join Filtering Typical sites
Public WiFi Residents and visitors Captive portal sign-in with fair-use terms Full public policy, including standard blocklists Libraries, city hall reception, recreation centers, community centers
Staff WiFi Employees, council members, contractors on council accounts IEEE 802.1X with identity provider credentials Malware and phishing, plus your acceptable use categories Every staffed building
Council-owned devices Laptops, cell phones, and tablets issued by the council EAP-TLS certificate installed by MDM Staff policy Every building, including maintenance yards
Building and operational systems CCTV, door entry, building management, kiosks, yard telematics iPSK, one key per device or group Allow-list to required destinations only Maintenance yards, mechanical rooms, libraries

Three terms recur through this guide:

  • Captive portal: the sign-in page a visitor completes before the network passes traffic.
  • VLAN (virtual local area network): keeps each network's traffic apart on shared switches and access points.
  • IEEE 802.1X: the standard for authenticating a device before it gets network access.

Write one isolation clause into the RFP. Public traffic must never reach staff or operational VLANs.

Some buildings host partners, such as a health clinic inside a community center. Keep partner traffic on its own network under the partner's controls. Our GP surgery WiFi providers checklist: patient access, clinical networks and DSPT evidence covers the clinical side. The Healthcare page covers wider healthcare settings.

What should a council have in place before going to tender?

Vendors design and price from what you give them. Gaps in the specification become contract amendments later. Prepare seven things before the solicitation goes out.

  1. A site register. List every building with its access point count, model, and broadband link. Note who owns the hardware and when vendor support ends.
  2. Your identity provider. Name it: Microsoft Entra ID, Okta or Google Workspace. Confirm that HR changes reach it the same day, because staff WiFi will follow it.
  3. A device inventory. Count city-owned laptops, cell phones, and tablets. State how each group is managed today.
  4. A filtering policy. Agree public and staff categories with your Chief Information Security Officer (CISO) and department heads.
  5. A data protection impact assessment (DPIA). The public sign-in processes personal data under the CCPA/CPRA. The FTC and state attorneys general describe a DPIA as good practice for any major project involving personal data.
  6. An accessibility owner. Treat the sign-in page as city web content under the ADA and Section 508 accessibility regulations.
  7. Leadership reporting needs. Ask the relevant committee what it wants each month, before suppliers propose dashboards.

City WiFi procurement started after February 24, 2025 falls under updated federal and state procurement guidelines. Write each requirement below as a criterion you can score, not an aspiration. For the controls that surround these networks, see Securing a business network: A practical guide for 2026.

How should the tender specify each city network?

Public WiFi with a fair-use sign-in

City public WiFi exists to give residents and visitors fair access. It is not there to collect data. Write the sign-in requirement around that purpose.

Ask for:

  • Fair-use limits set per site. These cover session length, per-device bandwidth and a daily allowance. A library and a community recreation center need different limits.
  • Terms of use. Visitors accept them at first sign-in and again when they change.
  • A no-email route. People with no email address or cell phone need a terms-only click-through.
  • Conscious-choice opt-ins. Newsletter consent is separate, un-checked and optional.
  • Minimal data. The DPIA records a stated retention period and deletion on request.
  • WCAG 2.2 level AA conformance. The ADA and Section 508 regulations set WCAG 2.1 AA as the legal floor. Federal government monitoring has tested against 2.2 since October 2024.
  • Language options that match your residents.

Purple Access runs Guest WiFi sign-in across every city building from a single pane of glass. Ask every bidder to demonstrate each fair-use control live at clarification stage.

A library service may want consented sign-ups to feed its events newsletter. 8 smart integration ideas to connect guest WiFi and CRM shows how that works.

Staff access that follows joiners, movers and leavers

On WiFi, IEEE 802.1X makes each device authenticate before it receives an address. A RADIUS server is the authentication service that checks the credential and returns the network policy.

Tie the staff network to your identity provider. Joiners, movers and leavers (JML) then run through a process you already operate.

  • Joiner: HR creates the account, and WiFi works on day one with no ticket.
  • Mover: a group change moves the person to a new VLAN or policy. An affordable housing officer who moves to finance gets finance access, not both.
  • Leaver: disabling the account ends network access. Nobody changes a shared key.

Ask the RFP for:

  • Named integrations with Microsoft Entra ID, Okta and Google Workspace.
  • A maximum time from account disable to network refusal. Write it into the contract.
  • SCIM or an equivalent directory sync. SCIM (System for Cross-domain Identity Management) is the standard for syncing accounts between systems.
  • SAML single sign-on for the admin console. SAML (Security Assertion Markup Language) means your engineers and supplier staff use named accounts.
  • Time-bound accounts for contractors and agency staff, expiring automatically.
  • A separate group for council members, with a policy you set.

Purple Access builds Identity-Based Networks on cloud RADIUS. Staff access follows the identity provider, not a password pinned to a bulletin board.

Government-owned laptops and cell phones without a shared password

A shared password on government devices fails twice. You cannot revoke it for one person, and every leaver walks out knowing it.

Certificates fix both problems. EAP-TLS (Extensible Authentication Protocol with Transport Layer Security) authenticates a device with a certificate instead of a password. Each device holds its own certificate, so you revoke one without touching the rest. Pair it with WPA3-Enterprise wherever your access points and devices support it.

Purple MDM enrolls government-owned laptops and cell phones and installs the certificate and WiFi profile. The device joins the staff network automatically, with nothing to type. If someone loses a cell phone, revoke its certificate and it stops connecting.

Many local governments still run PEAP-MSCHAPv2, a password-based method with known weaknesses. PEAP-MSCHAPv2: Why It Is Still Common, Why It Is Risky, and How to Move On explains the migration path.

Method Credential Removing one leaver Standard Suits
Shared WPA2-PSK One password for everyone Change the password on every device IEEE 802.11i Nothing on a government staff network
PEAP-MSCHAPv2 Account name and password Disable the account IEEE 802.1X Legacy environments during migration only
EAP-TLS Per-device certificate Revoke the device certificate IEEE 802.1X, IETF RFC 5216 Government-owned laptops and cell phones
iPSK Unique key per device or group Delete that key Vendor implementations on WPA2-Personal CCTV, door entry, kiosks, telematics

Building systems and depots

Depots and leisure plant rooms are full of devices that cannot do 802.1X. Typical examples are CCTV, door entry, building management controllers and self-service library kiosks.

Use iPSK (identity pre-shared key), where every device or group gets its own key on one network name. Put each group on its own VLAN. Allow it to reach only the destinations it needs. A compromised camera then cannot reach the staff network.

Filtering on every public government network

Local governments must consider filtering on IT that the public can use to ensure public safety and compliance with CIPA guidelines. An unfiltered public network is hard to defend at scrutiny.

Specify filtering on every public network at every site. Make no exception for small buildings. Ask for:

  • Child sexual abuse content blocked using recognized domain and URL blocklists.
  • Harmful and extremist content blocked in line with your security policy.
  • Adult content blocked on all public networks.
  • Malware and phishing protection on public and staff networks.
  • A stated method for encrypted DNS, which can bypass basic DNS filters.
  • An unblock request route with a response time. Library visitors researching health or legal topics should not be overblocked.
  • Reports by category and site, never by named individual.

Ask bidders whether their content filtering meets recognized public safety standards for filtering pornography and explicit content.

Purple Shield applies filtering on both public and staff networks, so one tender line covers both.

Reports stakeholders can read

Local officials do not need an analytics console. They need one page per district each month. That page answers three questions: is it used, is it working, and is it safe?

Specify:

  • Usage: sessions and unique devices per site and district, month on month.
  • Peak hours by site, to inform opening times and staffing.
  • Uptime per site against the contract SLA.
  • Filtering events by category, as counts.
  • No personal data in any member report.
  • CSV export for public records requests and audit.

WiFi Analytics reports on visits and connection patterns across every site. Ask each bidder for a sample district report at tender stage, then score it.

Rollout across sites

Purple is hardware-agnostic and runs as a cloud overlay. It works on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. Keep access points that are still in vendor support. Why your next WiFi upgrade doesn't need new hardware sets out the case.

Ask the tender for:

  • A four-site pilot: city hall, your busiest library, a community center and a depot.
  • Waves grouped by building type, so each wave reuses one tested configuration.
  • A parallel run of old and new staff networks, with a published sunset date.
  • Out-of-hours cutover at libraries and community centers.
  • A named vendor project lead, with per-site acceptance sign-off before the next wave.

RFP requirements at a glance

Requirement What to ask the vendor Evidence to request
Public sign-in accessibility Conformance to the ADA and Section 508 Recent independent accessibility audit
Fair-use controls Per-site session, bandwidth and daily limits Live demonstration at clarification
Joiners, movers, leavers Microsoft Entra ID, Okta, Google Workspace integration and disable-to-refusal time Leaver test on a demo account
Government-owned devices EAP-TLS certificates installed by MDM Enrollment of one laptop and one phone
Building systems iPSK on segregated VLANs Configuration walkthrough
Filtering CIPA compliance, content filtering categories, encrypted DNS handling Category list and test results
Citizen reporting Monthly district reports with no personal data Sample district report
Hardware Named supported vendors Published vendor list
Security assurance ISO 27001 and Cyber Essentials Current certificates
Availability Platform uptime SLA Contract SLA figure

Got questions about your specific setup?

Our team works with venue operators, IT managers, and network engineers across 80,000 venues. Book a 20-minute call and we will show you how others like you solved it.

How do you test city WiFi before go-live?

Run these tests at every pilot site, then sample them in each wave. Write the pass criteria into the contract.

  1. Leaver test. Disable a test account. The device must be refused within the contracted time.
  2. Mover test. Change the account's group. The device must land on the new VLAN.
  3. Lost device test. Revoke a phone's certificate. The phone must fail to reconnect.
  4. Isolation test. From the public network, try to reach a staff file server. The attempt must fail.
  5. Filtering test. Use vendor test addresses for each category. Repeat with encrypted DNS turned on.
  6. Accessibility test. Complete sign-in with NVDA, JAWS, VoiceOver, keyboard only and 200% zoom.
  7. Fair-use test. Exceed the daily allowance on a test device. The limit must apply.
  8. Report test. Generate a district report. Confirm it contains no personal data.

What goes wrong with city WiFi, and how do you fix it?

Leavers keep access because HR updates late

The network can only follow the identity provider. If HR disables accounts a week late, so does WiFi. Fix the HR-to-identity feed first, then hold the vendor to the disable-to-refusal time.

Staff use public WiFi to avoid signing in

Staff do this when the staff network is harder to join than the public one. Certificate-based access removes the friction, because enrolled devices connect automatically. Tell staff that city business stays on the staff network.

Encrypted DNS bypasses the filter

Modern browsers can send DNS requests over HTTPS, which skips basic DNS filters. Ask the vendor how they handle it, and include it in the filtering test.

Libraries report overblocking

Health, sexual health and legal advice pages sometimes fall into blocked categories. Publish the unblock route at the library desk. Review requests within the contracted response time.

Certificates expire on a batch of laptops

Devices enrolled on the same day often expire on the same day. Require MDM renewal well before expiration, plus an expiration report each month.

Building systems end up on the staff network

This usually happens when a contractor installs a device and needs it working that afternoon. Make iPSK onboarding part of your facilities contracts, with a named contact who issues keys.

The sign-in page fails people using assistive technology

Image CAPTCHAs, unlabeled fields and timeouts lock people out. Test with screen readers before go-live, not after a complaint.

What does this look like across a municipal estate?

The two worked scenarios below are illustrative, built on typical properties. Every outcome follows directly from the design, not from a vendor survey.

Worked scenario 1: a city council retires its shared staff password

Situation. A local council runs 26 buildings with 1,200 staff. Staff WiFi uses one WPA2 password, changed every six months. Last year 130 people left. Each one kept a working key until the next change.

What was done. The council moved staff WiFi to 802.1X tied to Microsoft Entra ID. It enrolled 900 council laptops and cell phones with Purple MDM onto EAP-TLS. The shared password was retired after a 30-day parallel run.

Outcome.

  • Password changes: down from two a year to zero.
  • Manual device updates: 1,800 a year (900 devices, twice a year) eliminated.
  • Leaver exposure: down from up to six months to the contracted disable-to-refusal time. None of the 130 annual leavers now leaves with a working key.

Worked scenario 2: a county library and recreation service closes its filtering gap

Situation. A county runs 38 libraries and six recreation centers. Filtering covered the libraries but not the recreation sites. The sign-in page failed a keyboard-only test. Officers answered council members' usage questions by hand.

What was done. The county deployed one sign-in across all 44 sites, tested to Section 508 and WCAG 2.2 AA. It applied Purple Shield to all 44 public networks. Each district now receives a scheduled monthly report.

Outcome.

  • Filtering coverage: up from 38 of 44 public networks to 44 of 44.
  • Accessibility: the sign-in now passes keyboard and screen reader tests.
  • Member reporting: ad hoc council member requests replaced by one report per district each month.

What does public sector WiFi cost, and what does it return?

What you pay for

Cost sits in four lines:

  • The platform plan: Connect, Capture or Engage.
  • Add-ons: Purple Shield for filtering and Purple MDM for devices.
  • Hardware, only where access points are out of vendor support.
  • Your internal time for identity integration, device enrollment and staff communications.

Ask every bidder to price per site. You can then add a new building at a known rate.

What you get back

  • No password rotations, and no leaver walking out with a working key.
  • One platform across every building, not a different arrangement per service.
  • Filtering evidence for compliance and scrutiny at every public site.
  • Member reports produced on schedule, not collated by hand.
  • Existing access points kept, so capital goes to buildings that need it.

Proof behind the platform

Purple was founded in 2012 and runs in 80,000+ live venues across more than 90 countries. It handles 500 million users and logins a year. The platform delivers 99.999% uptime, based on Purple's own platform data. Purple is ISO 27001 certified and holds Cyber Essentials and B Corp certification. It is CCPA/CPRA and CCPA compliant.

Frequently asked questions

Can Purple run on the access points our city already owns?

Yes. Purple is hardware-agnostic and runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You keep access points that are still in vendor support and replace only those that are not. A city WiFi tender can then separate the platform decision from the hardware refresh. Each building's replacements can follow their own timetable.

Does city public WiFi need a sign-in page?

Yes. The sign-in page is where visitors accept your terms of use and where fair-use limits apply. It can stay light: a terms-only click-through works for people without an email address. Keep any marketing consent separate and optional. Build the page to the ADA and Section 508 standards so people using screen readers or keyboards can connect unaided.

How does city public WiFi stay compliant with CCPA/CPRA?

Collect only what the service needs, and say why. Record the lawful basis and retention period in a privacy impact assessment. Keep newsletter consent as an unchecked conscious-choice opt-in, and delete data on request. Purple is ISO 27001 certified, holds Cyber Essentials and is GDPR compliant. Member reports should carry counts only, never named individuals.

Can we move staff off a shared password or PEAP-MSCHAPv2 without disruption?

Yes, if you run old and new networks side by side. Enroll city-owned devices with Purple MDM so they receive certificates and join the new staff network automatically. Keep the old network live for a published period and monitor remaining connections, then switch it off. Staff on enrolled devices notice only that they no longer type a password.

What filtering should every city public network apply?

At minimum, block child sexual abuse content using the IWF list. Also block terrorist and extremist content in line with your Prevent policy, adult content, and malware and phishing sites. Apply filtering at every public site, including small community buildings. Ask how the vendor handles encrypted DNS. Set an unblock route with a response time so library research is not overblocked.

How long does a city council-wide WiFi rollout take?

Plan a pilot plus waves, not a single cutover. Pilot four representative sites first: city hall, your busiest library, a community center, and a public works depot. Then roll out by building type. Because Purple runs on existing access points, identity and device onboarding work sets the pace, not hardware deliveries. Require per-site sign-off before each wave starts.

What should council members see in a WiFi report?

Council members should see one page per district each month. It shows sessions, unique devices, peak hours, uptime against the contract SLA, and filtering events by category. No personal data appears in member reports. Ask every bidder for a sample district report at tender stage and score it. A report council members cannot read simply generates manual requests instead.

Key Definitions

IEEE 802.1X

The IEEE standard for port-based network access control. It carries EAP between the device, the access point and an authentication server, so a device must authenticate before it receives network access.

The basis of municipal Staff WiFi. Specifying 802.1X lets network access follow the identity provider, so joiners, movers and leavers are handled by a process HR already runs.

RADIUS

Remote Authentication Dial-In User Service, the IETF protocol an 802.1X authenticator uses to send credentials to an authentication server, which accepts or rejects them and returns the network policy, such as a VLAN assignment.

Purple Access runs on cloud RADIUS. It is the service that refuses a disabled account and places a moved employee on the right VLAN, so its disable-to-refusal time belongs in the contract.

EAP-TLS

Extensible Authentication Protocol with Transport Layer Security, defined in IETF RFC 5216. The device and server authenticate each other with certificates, so no password is exchanged.

The method for government-owned laptops and cell phones. Each device holds its own certificate, so you revoke one lost phone without touching the rest of the deployment.

PEAP-MSCHAPv2

Protected EAP wrapping Microsoft's MS-CHAPv2 challenge-response, a password-based 802.1X method that relies on account name and password inside a TLS tunnel and has known weaknesses.

Common in legacy housing developments. The RFP should treat it as a migration-only method, with a parallel run and a published sunset date.

iPSK (identity pre-shared key)

A vendor implementation on WPA2-Personal that gives each device or group its own pre-shared key on a single network name, with the key mapped to a VLAN or policy.

Used for CCTV, door entry, building management controllers, kiosks and depot telematics that cannot do 802.1X. Deleting one key removes one device without disturbing others.

VLAN (virtual local area network)

A logical network defined by IEEE 802.1Q tagging that keeps each network's traffic apart on shared switches and access points.

The isolation clause in the proposal depends on VLANs. The isolation test at go-live checks that the public network cannot reach a staff file server.

Captive portal

The sign-in page a visitor completes before the network passes traffic, where terms of use are accepted and fair-use limits are applied.

The public face of municipal WiFi. It is municipal web content, so it must meet accessibility regulations and offer a terms-only route for people without an email address.

SCIM

System for Cross-domain Identity Management, the IETF standard (RFC 7643 schema, RFC 7644 protocol) for provisioning and deprovisioning accounts between an identity provider and other systems.

Ask for SCIM or an equivalent directory sync so account changes in Microsoft Entra ID, Okta or Google Workspace reach the WiFi platform without manual steps.

SAML

Security Assertion Markup Language, the OASIS standard (SAML 2.0) for exchanging authentication assertions between an identity provider and a service to deliver single sign-on.

Specify SAML single sign-on for the admin console so municipal engineers and vendor staff use named accounts rather than shared logins.

WCAG 2.2 level AA

The W3C Web Content Accessibility Guidelines version 2.2 at conformance level AA. The ADA and Section 508 set accessibility compliance standards.

Specify 2.2 AA for the public sign-in page, since federal accessibility monitoring tests against 2.2. Request a recent independent audit as evidence.

DPIA (data protection impact assessment)

An assessment of the risks a processing activity poses to individuals under CCPA/CPRA. The FTC and state attorneys general describe it as good practice for any major project involving personal data.

The public sign-in processes personal data, so the DPIA records the lawful basis, a stated retention period and deletion on request before the RFP is issued.

Acceptable use policy (AUP) filtering

The requirement for public authorities to implement content filtering and security safeguards to prevent public networks from being used for illegal or harmful material.

Federal and state guidelines expect municipalities to consider filtering on IT the public can use, which is why the RFP requires filtering at every public site.

Worked Examples

A city municipality runs 26 buildings with 1,200 staff on one WPA2 password changed every six months. Last year 130 people left, and each kept a working key until the next change. How should it fix leaver exposure?

The municipality moved Staff WiFi to IEEE 802.1X tied to Microsoft Entra ID, so disabling an account in the identity provider now ends network access. It enrolled 900 municipal laptops and cell phones with Purple MDM onto EAP-TLS, giving each device its own certificate that can be revoked individually. The shared password ran in parallel for 30 days, then was retired. Password changes fell from two a year to zero, and 1,800 manual device updates a year were eliminated. Leaver exposure dropped from up to six months to the contracted disable-to-refusal time, so none of the 130 annual leavers now leaves with a working key.

A county runs 38 libraries and six community centers. Filtering covers the libraries but not the community sites, the sign-in page fails a keyboard-only test, and officers answer council members' usage questions by hand. What should change?

The county deployed one sign-in across all 44 sites and tested it to Section 508 and WCAG 2.2 AA, so the same accessible page serves every building. It applied Purple Shield to all 44 public networks, closing the gap at the community centers with one consistent filtering policy. It also scheduled a monthly report for each district. Filtering coverage rose from 38 of 44 public networks to 44 of 44. The sign-in now passes keyboard and screen reader tests. Ad hoc council requests were replaced by one report per district each month, which carries counts only and no personal data.

A contractor installs a new door entry controller at a facility and needs it working that afternoon, so it ends up on the staff network. How do you stop this recurring?

Building systems should never share the staff network, because a compromised device could then reach staff services. Make iPSK onboarding part of your facilities contracts, with a named contact who issues keys. Each device or group gets its own key on one network name, lands on its own VLAN and is allowed to reach only the destinations it needs. The contractor gets a working connection the same day without touching staff credentials. If the device is later removed or compromised, deleting its key cuts it off without affecting any other system on the site.

Frequently asked questions

Can Purple run on the access points our city or county already owns?

Yes. Purple is hardware-agnostic and runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You keep access points that are still in vendor support and replace only those that are not. A municipal WiFi tender can then separate the platform decision from the hardware refresh. Each building's replacements can follow their own timetable.

Does local government public WiFi need a sign-in page?

Yes. The sign-in page is where visitors accept your terms of use and where fair-use limits apply. It can stay light: a terms-only click-through works for people without an email address. Keep any marketing consent separate and optional. Build the page to Section 508 and WCAG 2.2 AA so people using screen readers or keyboards can connect unaided.

How does local government public WiFi stay compliant with CCPA/CPRA?

Collect only what the service needs, and say why. Record the lawful basis and retention period in a privacy impact assessment. Keep newsletter consent as an unchecked conscious-choice opt-in, and delete data on request. Purple is ISO 27001 certified, holds Cyber Essentials and is CCPA/CPRA compliant. Member reports should carry counts only, never named individuals.

Can we move staff off a shared password or PEAP-MSCHAPv2 without disruption?

Yes, if you run old and new networks side by side. Enroll government-owned devices with Purple MDM so they receive certificates and join the new staff network automatically. Keep the old network live for a published period and monitor remaining connections, then switch it off. Staff on enrolled devices notice only that they no longer type a password.

What filtering should every public network apply?

At minimum, block child sexual abuse content using the IWF list. Also block terrorist and extremist content in line with your security policy, adult content, and malware and phishing sites. Apply filtering at every public site, including small community buildings. Ask how the supplier handles encrypted DNS. Set an unblock route with a response time so library research is not overblocked.

How long does a municipality-wide WiFi rollout take?

Plan a pilot plus waves, not a single cutover. Pilot four representative sites first: city hall, your busiest library, a community recreation center and a facility operations center. Then roll out by building type. Because Purple runs on existing access points, identity and device enrollment work sets the pace, not hardware deliveries. Require per-site sign-off before each wave starts.

What should council members see in a WiFi report?

Council members should see one page per ward each month. It shows sessions, unique devices, peak hours, uptime against the contract SLA and filtering events by category. No personal data appears in member reports. Ask every bidder for a sample ward report at tender stage and score it. A report council members cannot read simply generates manual requests instead.

Got questions about your specific setup?

Our team works with venue operators, IT managers, and network engineers across 80,000 venues. Book a 20-minute call and we will show you how others like you solved it.