Key takeaways
- Measure readiness against the systems the role actually needs.
- Separate a provisioning failure from an identity recovery failure.
- Track time to restore access, not only the number of tickets.
Research question and decision use
The audit asks what share of new hires can access every required system at the start of their first scheduled shift, and how long failures take to resolve. The unit is one new hire and the role's required system list. The result guides provisioning and service desk staffing, not an individual employee's performance.
| Stage | Evidence | Failure mode | Use |
|---|---|---|---|
| Intake | Dated source and owner | Missing record | Route for review |
| Handoff | Named recipient and time | Unconfirmed receipt | Recheck |
| Closure | Completion evidence | Status only | Keep open |
Population and eligibility
Eligible new hires started during the window and had a documented system list from the role profile. Record the role, location, start time, provisioning source, and service desk queue. Exclude hires whose start date moved, but keep a count of schedule changes that affected readiness.
Sampling protocol
Include every new hire in a small cohort, or sample by role family and start week for a larger population. Add all hires with a severity one ticket. Record the seed and the replacement rule, and do not exclude a failed hire because the cause is already known.
Evidence dictionary
Fields include required system, account creation time, first successful sign-in, MFA enrollment, ticket open time, first response, resolution time, workaround, and employee confirmation. A missing timestamp is a finding. The analysis should not infer a sign-in from an account creation event.
Classification rubric
Rate readiness complete, partial, blocked, or unknown. Complete means every required system was accessible at the start time. Partial means a non-critical system was missing or a workaround was in place. Blocked means a required system was unavailable with no workaround.
Reviewer calibration
Calibrate on a hire with email but no time clock, a hire with a working loaner but no badge, and a hire whose manager confirmed a temporary exception. Reviewers should agree on whether the role list or the actual access determines the rating.
Analysis plan
Report readiness by role family, location, and provisioning source. Show median and upper-quartile resolution time for failures, with counts by severity. A high readiness rate can coexist with slow resolution for the few who fail, so present both.
Sensitivity and exception analysis
Recompute excluding hires whose start date changed and excluding roles with a known system migration. Compare results when a workaround counts as ready. If the conclusion changes, describe the operational condition rather than labeling the cohort.
Privacy and role boundaries
Access records can reveal role, location, and system use. Use a restricted extract, aggregate before sharing, and suppress small cells. Do not include employee names or exact sign-in times in a published table.
Limitations
The audit observes access at one point in time and cannot prove that the employee could perform every task. A system may be technically available but misconfigured for the role. The method also depends on an accurate required-system list, which may itself be out of date.
Replication package
Retain the role system lists, provisioning export, ticket timestamps, severity rules, and readiness ratings. A later cycle should reproduce the readiness rate and the resolution distribution from the package.
Conclusion
The useful output is a readiness report by role and system, with the top failure causes and the owner of each fix. A single overall percentage is less actionable than a short list of systems that repeatedly miss the start time.
Sources and methodology
A bounded review of onboarding records with a frozen population, evidence rules, reviewer calibration, and explicit limitations.
- NIST SP 800-63B digital identity guidance current.
- NIST Cybersecurity Framework current.
- CISA Secure Our World current.
- SHRM onboarding toolkit current.
- DOL new hire reporting current.
- NARA records management current.
- Plain Language Guidelines current.
- W3C WCAG 2.2 current.
- FTC data security guidance current.
- BLS Employer Costs for Employee Compensation current.
Source count: 10. Last verification date: October 27, 2026.
Questions about the findings
What is the unit of analysis?
One onboarding record followed from its triggering event to a verified disposition.
Does this establish causation?
No. The design is descriptive and limited to the retained administrative record.
How is missing evidence handled?
It remains a visible finding rather than being inferred or excluded.
Put the finding to work
Review the full research library, compare cluster coverage inside Onboarding And Retention Research, and pair these findings with our VA candidate screening support.