Skip to content
WLOCAuthorized iOS location testing

Authorized check-in radius QA for attendance products you maintain

How can an organization audit employee check-in rules in a test environment?

After an attendance-policy change, administrators need to confirm radius, shifts, field approvals, correction requests, and exception check-ins from the…

Solution

Solution

The admin's workflow: prepare office, radius-edge, field, and blocked points in a test environment. A test employee account can audit whether mobile prompts and backend attendance records match the written policy. Review mobile prompts, attendance records, and WLOC diagnostics together before applying policy changes broadly.

Problem

Problem

After an attendance-policy change, administrators need to confirm radius, shifts, field approvals, correction requests, and exception check-ins from the employee side. Backend settings alone do not reveal confusing prompts or missing actions. Compare the written radius sentence with the employee prompt; this paperwork rehearsal is not an HR bypass and does not mark anyone present.

Use WLOC in 3 steps

Use WLOC in 3 steps

  1. Map the office and field-policy points.

    Save in-office, radius-edge, approved field site, and blocked check-in locations according to the policy.

  2. Run the full rule with a test employee.

    Check clock-in, clock-out, late arrival, field approval, correction entry, and exception copy.

  3. Compare employee UI with backend records.

    Review mobile prompts, attendance records, and WLOC diagnostics together before applying policy changes broadly.

Important boundary

Important boundary

WLOC is not a jailbreak. The current testing Profile includes a certificate and a VPN tunnel, and it does not require a separate third-party VPN client. Saving a target, Gateway acceptance, or a submitted Restore does not mean the target app adopted the location or that the device is already restored. WLOC does not promise to override every app's permissions, cache, or anti-cheat checks.