Key takeaways
- Separate request, approval, build, and verification time.
- Record the first successful login, not only the ticket closure.
- Fix the stage with the longest repeatable wait.
Question and scope
This study asks where time is spent between an approved access request and the new hire's first successful login. It separates request submission, manager approval, security or system build, and user verification. The scope is one onboarding cohort and one defined set of systems. The result describes that cohort and is not a benchmark for other employers.
The unit is one access request for one system. If a request covers several systems, record each system separately when the approval or build path differs. Include requests that were corrected or resubmitted, and keep the original segment. Exclude test accounts, and record the exclusion reason. Report the number of requests and the number of systems separately.
| Record | Evidence of completion | Common gap | Use |
|---|---|---|---|
| Owner field | Named person or mapped role | Shared inbox only | Reassign |
| Source | Document identifier and version | Folder link only | Request source |
| Next action | Action and due date | Status only | Clarify |
| Review | Reviewer and date | No acceptance | Escalate |
Method and evidence standard
Define the start and end event for each stage before extracting data. The request starts when the approved form is submitted, not when someone first mentions it. Approval ends when the named approver records a decision. Build ends when the account exists and the required group is assigned. Verification ends when the new hire successfully signs in and confirms the expected access.
Use system timestamps where possible and mark estimates separately. If a ticket was closed before the new hire could sign in, record the gap between closure and first login. Sample across systems, roles, and start dates. Two reviewers should compare a small set of timelines and resolve differences in stage boundaries. The study measures elapsed time, not the quality of the access decision.
Measures, findings, and interpretation
Report the median and range for each stage, the share of requests with a missing timestamp, and the time from ticket closure to first login. Show the result by system and role. A long approval wait is different from a long build wait, and the report should keep them separate. Include the number of requests that required a resubmission and the reason.
Inspect the requests behind the longest waits before assigning a cause. A cluster in one system may reflect a manual build step, while a cluster in approval may reflect an unclear approver list. A cluster of closed tickets without a login may mean the verification step is not owned. The study cannot show whether the access granted was appropriate, and it should not be used to rank individual technicians.
Limitations and practical next step
The timestamps reflect the ticket system and may not capture work done in chat or a direct system console. The study also cannot observe the new hire's availability or the urgency of the role. A stable median can still hide a small group of requests that waited far longer. Report the tail and the missing data with the central measure.
Choose one stage for a bounded improvement, such as a named approver backup, a standard build checklist, or a first-login verification step. Record the owner and the start date, then recheck the same stage with the next cohort. Keep the before-and-after sample. The most useful result is a specific control to test, not a general claim that provisioning is fast or slow.
Sources and methodology
A bounded documentary review of onboarding records for a defined hiring cohort. The study compares the written record with an explicit evidence standard and reports local findings only. Public guidance frames the questions but does not validate a local process or supply a performance conclusion.
- U.S. Office of Personnel Management — Training and Development current.
- U.S. Small Business Administration — Hire and manage employees current.
- NIST Cybersecurity Framework 2.0 current.
- U.S. Equal Employment Opportunity Commission current.
Source count: 4. Last verification date: November 5, 2026.
Questions about the findings
What is the unit of analysis?
A stage-level method for locating delays between an access request and a new hire's first productive login. The unit and the review point are defined before sampling.
Does this study measure individual performance?
No. It tests whether the written record meets the stated evidence standard. The finding is a local readiness signal and does not rank people or prove a legal or performance outcome.
Put the finding to work
Review the full research library, compare cluster coverage inside Onboarding Operations, and pair these findings with our VA candidate screening support.
