IT Onboarding

Manage New Hire Access Request Aging

An access queue that shows which new hire requests are pending, who owns them, and what the start date risk is.

By OnboardingEmployees editorial team | | 2 min read

OnboardingEmployees guide to new hire access request aging
On this page
  1. Record the Request at Submission
  2. Track the Approval Separately
  3. Age the Request Against the Start Date
  4. Assign an Owner at Each Stage
  5. Verify Before the Start Date
  6. Handle the Common Situations
  7. Review the Queue Weekly
  8. Related reading

Access requests are the most common onboarding bottleneck. The ticket is submitted, the start date is close, and nobody can say whether the account will be ready. The new hire arrives, the manager improvises, and the first day is spent waiting.

An aging view turns the queue into a schedule.

Record the Request at Submission

For each request, record the new hire, the role, the systems requested, the requested start date, the requester, and the approval. Link the role profile that defines the access.

Do not accept a request that says "standard access" without the profile.

Track the Approval Separately

Approval and provisioning are different steps. Record the approver, the approval date, and any condition. A ticket that is waiting for approval is not waiting for IT.

This distinction prevents the queue from blaming the wrong team.

Age the Request Against the Start Date

Calculate the days remaining before the start date and flag requests inside the agreed lead time. A request submitted two days before the start is a different risk from one submitted two weeks earlier.

Sort the queue by start date, then by age.

Assign an Owner at Each Stage

Record the owner for approval, provisioning, and verification. When the request moves between teams, the owner changes and the handoff is recorded.

An unowned request is the one that fails.

Verify Before the Start Date

Confirm that the account works, the required groups are present, and the new hire can sign in. Record the verification and the person who performed it.

A provisioned account is not a verified account.

Handle the Common Situations

The manager requests access after the start date. Record the request, the reason, and the interim arrangement. Do not grant broad access to save time.

The approval is delayed. Escalate to the approver's manager using the agreed path and record the escalation.

The role profile is missing. Record the gap and route it to the role owner. Provisioning without a profile creates excess access.

The new hire starts late. Update the start date and reschedule the provisioning. Do not leave an active account waiting.

Review the Queue Weekly

Look at requests inside the lead time, requests without an owner, and requests that missed verification. The weekly review is the control that keeps the first day predictable.

For identity and access context, see the National Institute of Standards and Technology.

Continue building the workflow

Related support: New hire first week check in, Onboarding document retention. The NIST Official program context for onboarding administration..