Geofencing and Known Location Audit

Purpose

Review location controls, device behavior, and evidence used to allow or deny punches.

How to use this checklist

Run this review with a system administrator, payroll/timekeeping owner, operational manager, and reporting or integration owner. Mark each item Pass, Needs Work, or Not Applicable and capture evidence.

Checklist

• [ ] Every active worksite has accurate coordinates and radius
• [ ] Known Places are named consistently and mapped to facilities
• [ ] Mobile GPS permissions and precision requirements are documented
• [ ] Web punching uses approved network or access profile controls
• [ ] Overlapping geofences are identified and resolved
• [ ] Multi-floor and large-campus accuracy has been field-tested
• [ ] Denied punches generate usable support evidence
• [ ] Location changes follow change control and regression testing

Minimum evidence to retain

• Screenshot or export of the applicable configuration.
• Test employee, test date, expected result, and actual result.
• Named owner and due date for every failed item.
• Approval showing the business owner accepted the final result.

Stop and escalate when

A failed control could affect payroll, employee access, compliance, or a closed pay period. Do not use production edits as the first test.