Hyperfind and Employee Population Audit

Purpose

Test saved searches so managers act on the right employee population.

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

• [ ] Each operational Hyperfind has a named owner
• [ ] Home, transferred-in, and scheduled-transfer logic is understood
• [ ] Date-sensitive searches use the intended timeframe
• [ ] Inactive and terminated employees are excluded where appropriate
• [ ] Location and labor-category filters use current structure
• [ ] Managers cannot retrieve employees outside authorized scope
• [ ] Results are compared against a known control population
• [ ] Changes to global Hyperfind behavior are regression-tested

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.