Mobile and Web Punch Access Audit

Purpose

Confirm each access method provides the intended experience without creating policy gaps.

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

• [ ] Supported browsers and mobile versions are documented
• [ ] Access method profiles distinguish mobile, web, and no-access users
• [ ] Punch tiles and quick timestamp are assigned intentionally
• [ ] Device permissions are included in employee instructions
• [ ] Offline, weak-signal, and denied-location behavior is tested
• [ ] Authentication and automatic logout meet security standards
• [ ] Shared-device and kiosk scenarios prevent employee crossover
• [ ] Support can identify the source and device for a disputed punch

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.