YENRA GUEST WI-FI ACCEPTANCE CHECKLIST
Guide: https://yenra.com/wi-fi-management-software/
Prepared September 8, 2026. Copy into a text editor and fill in actual results.

PURPOSE AND PREREQUISITES
Use before opening a guest network and after significant changes. Tests must be
authorized by the network owner and use designated test devices and harmless
test services. Do not probe guests' devices or disrupt payment equipment.
Have the network administrator confirm the gateway, switch and access-point
rules. This checklist does not establish legal or payment-system compliance.

Venue/date/time zone:
Responsible administrator:
Configuration/firmware versions:
Expected simultaneous active guests:
Intended guest tasks and occupied areas:
Expected peak period:
Test devices and operating systems:
Private test resource (first verify from an authorized staff device):
Applicable IPv4/IPv6 paths:

RECORD PASS, FAIL OR NOT APPLICABLE WITH A REASON FOR EACH CHECK
1. Fresh device joins through the intended password/voucher/portal process.
   Expected: accessible instructions, correct authorization and usable internet.
   Actual / evidence / owner:
2. Session expiry and rejoining work as documented.
   Expected: clear expiry behavior and a supported way to regain access.
   Actual / evidence / owner:
3. Guest internet works while the designated private resource is unreachable.
   Expected: configured isolation plus observed separation. Failed ping alone
   is insufficient; first verify the resource works from the authorized network.
   Actual / evidence / owner:
4. Two authorized guest test clients are isolated as intended.
   Repeat on the same AP, different APs, and wired guest ports if present.
   Test applicable IPv4 and IPv6 paths with administrator-approved methods.
   Actual / evidence / owner:
5. Representative simultaneous guest use works throughout occupied areas.
   Expected: agreed browsing/call tasks succeed while staff tasks remain usable.
   Task mix, locations, observed interruptions / owner:
6. Documented controller, portal or internet outage behavior is understood.
   Use an agreed maintenance window for any disruptive test.
   Expected: known failure messages, recovery steps and responsible support.
   Documentation / actual test / owner:
7. Administration is recoverable and limited to authorized roles.
   Expected: named owner, supported MFA where available, secure backup and
   known license/support renewal responsibilities.
   Actual / evidence / owner:
8. Guest data collection has a documented purpose and retention/access plan.
   Expected: only necessary identifiers and staff access appropriate to duties.
   Actual / evidence / owner:

CAPACITY NOTE -- FICTIONAL EXAMPLE
20 active guests x 5 Mbps per-client download cap = 100 Mbps permitted demand.
If the available internet download capacity is 60 Mbps, all clients cannot
receive their full cap simultaneously. A cap is not a reserved share. Check
upload demand, wireless airtime and staff traffic separately.

RELEASE DECISION
Blocking failures and corrective actions:
Retest date/results:
Accepted scope and remaining limitations:
Administrator sign-off record:
Next triggers: firmware, AP, portal, guest policy or service-plan changes.