First-run pass rate
How many acceptance checks pass on the first attempt — a measure of design quality and deployment discipline.
The test phase
Pre-Opening Acceptance & Failover Testing
A network is only as good as the last time you proved it works. Before go-live, we run a documented acceptance test — segmentation holds, WAN failover lands inside the target window, redundancy is live, and monitoring is reporting — so the event doesn't become the first real test of the design.
Prove it before go-live, not during the event
Most catastrophic event-network failures aren't exotic — they're untested assumptions that surface at the worst possible moment. The acceptance test converts assumptions into evidence while there's still time to fix anything, and produces a documented record that the network was verified before a single attendee walked in.
Our goal is zero severity-one incidents caused by untested failover. Every critical path that’s supposed to recover is exercised on purpose — before it has to recover for real.
The acceptance checklist
A consistent, documented set of checks run before go-live on every deployment.
- Segmentation verification — payments, production, registration, attendee, contractor, and management zones are isolated and can't reach each other except where intended
- WAN failover within the target window — connectivity fails over to redundant links inside the agreed recovery time
- Critical-system redundancy live — payments, registration, encoders, and production have their wired-first paths and backups confirmed
- Monitoring reporting — the NOC is receiving telemetry and alerts from every monitored segment and link
- Wired-first paths confirmed — the systems that can't depend on Wi-Fi are on cable and verified
- Documented sign-off — results recorded so there's evidence the network was proven before go-live
How the test runs
Structured, repeatable, and completed before go-live — never improvised mid-event.
Verify segmentation
Confirm each zone is isolated and that payment and production traffic cannot be reached from attendee or contractor segments.
Exercise failover
Deliberately fail primary connectivity and confirm critical paths recover onto redundant links inside the target window.
Confirm redundancy & monitoring
Validate that critical-system backups are live and that the NOC is receiving telemetry and alerts.
Document & sign off
Record results, resolve any failed check before go-live, and capture a documented sign-off for the post-event report.
What we track
The acceptance test isn't a one-off — its results are measured deployment over deployment.
Failover within window
Whether WAN failover lands inside the agreed recovery target every time it's exercised.
Untested-failover sev-1s
The number we drive to zero: severity-one incidents during an event caused by a failover path that was never tested.
What testing covers — and the boundary
Acceptance testing verifies the network and transport layer LGL operates: segmentation, redundancy, failover, and monitoring. It does not validate the applications that ride on it — the systems you run, such as payments and registration, remain the responsibility of their vendors, defined in the data-responsibility and segmentation boundary on every engagement. Where the venue permits dual-WAN we test true link failover; where only an approved single underlay is available, we test the defined failover plan for that design.
Go live on a proven network
Start with a Risk Assessment to scope a deployment with documented pre-opening acceptance and failover testing — before any non-refundable spend.