Outsourced EmploymentPowered by StealthAgents

Research note

What share of onboarding access requests wait past the start date?

A local method for measuring whether new employees can use the systems their role requires on the first day, and where the queue loses time.

Published

Research note illustration for What share of onboarding access requests wait past the start date?
Table of contents

Question and scope

The question covers access to the systems named in the role's first-week checklist. It includes identity accounts, payroll or HR tools, shared mailboxes, and the ticket queue when those are required for the work. It excludes optional tools that the role can use later. The boundary should match the role brief rather than the full catalog.

An access request is eligible when it was opened before or during the employee's first week and was required for a named task. A request for a tool that no one has defined is out of scope until the role owner confirms the need. Record the request date, the need date, and the role. This keeps the sample tied to a real task.

The review also records whether the manager or the employee could perform the first task on the start date. A login that exists but cannot complete the task is not ready access. Report the task test separately from the account creation. The distinction shows whether the delay is technical or procedural.

Definitions and evidence standard

Define ready access as an active permission that lets the employee complete the first approved task without borrowing another account. A created account with no role assignment is not ready. A role assignment that is too broad is a different problem and should be recorded separately. The definition should be written before the review.

Use the identity record, the system role list, and the first-task test as evidence. The identity record shows when the account was created, while the role list shows what it can do. The task test shows whether the two work together. Record the observer and the time for each piece.

Separate a request that was never opened from a request that was opened but not completed. The first is an intake problem, while the second is a fulfillment problem. Report both counts so the team can see where the queue loses time. Combining them hides the fix.

Sampling and measurement

Freeze the list of new employees and their access requests for the window. Include employees from more than one manager and more than one role family. Record the role checklist version and the systems in scope. A sample drawn only from completed onboardings will miss the people who are still waiting.

Measure the time from the request to ready access, the number of requests that were ready by the start date, and the number still waiting at the end of the first week. Add the number of requests that needed a second attempt. Report the counts by system and by role. A single average hides the system that always lags.

Record the reasons for delay from the request notes, not from memory. Common reasons include a missing manager approval, an identity mismatch, a license wait, and a permission that was assigned to the wrong group. Use a short reason list so the counts are comparable. Keep an unknown category for cases without enough evidence.

Findings and interpretation

Present the readiness rate by system before suggesting a cause. A system with a low rate may have a slow owner, a dependency on identity, or a checklist that asks for access too late. Compare the request date with the start date for the same cases. The gap often explains more than the system name.

Compare employees who started after a weekend or a holiday with those who started midweek. A short window can make a normal process look slow. Report the start-day pattern with the result. The comparison keeps the calendar from being mistaken for a performance problem.

Check whether the employees who waited had a safe first task that did not require the missing system. A team can protect the first day by sequencing work around the delay. Report the workaround and the task that remained blocked. The answer shows whether the delay affected the employee or only the checklist.

Limitations

The review measures access readiness, not whether the employee received adequate training. A ready account can still be unusable if the person does not know the task. It also cannot show whether the permission was appropriate for the role. Those questions need a separate access review.

The role checklist may change during the window, and an employee may have started under an older version. Record the checklist version rather than judging the past with the current list. A missing item under an old checklist may not be a current defect. The reviewer should state which version applied.

A first task may be delayed for reasons unrelated to access, such as a missing supervisor or an unfinished training module. Record those reasons separately. The access result should not absorb every onboarding delay. A clear boundary keeps the measure honest.

Practical next step

Move the access request earlier by tying it to the accepted offer rather than the first day. The request can start with the identity record and the role checklist attached. Set a target ready date before the start date. The owner should confirm the target with the hiring manager.

Assign one access coordinator to track the requests and one granting owner for each system. The coordinator can see the queue, while the owner can change the permission. A shared ticket queue is not enough without a named owner. Review the open requests in a short weekly meeting.

Test the change on the next group of new employees and compare the readiness rate with the baseline. Keep the earlier start if it improves the first-day task. If the delay moves to a different system, fix that dependency next. The goal is a ready employee, not an earlier ticket date.

Sources

References supplied with this research note.

Article source directory
SourcePublisherContext
U.S. Department of Labor, Recordkeepingdol.govPrimary reference supplied with this article.
Internal Revenue Service, Publication 15irs.govPrimary reference supplied with this article.
National Institute of Standards and Technology, Cybersecurity Framework 2.0nist.govPrimary reference supplied with this article.
U.S. Department of Labor, Fair Labor Standards Actdol.govPrimary reference supplied with this article.