Onboarding

Day-One Access Ticket Triage for New Hires

A triage routine for the access problems that appear on an employee's first morning, with clear severity, ownership, and recovery steps.

By OnboardingEmployees editorial team | | 3 min read

Day-One Access Ticket Triage for New Hires
On this page
  1. Define what blocked means
  2. Collect the minimum ticket detail
  3. Use a short severity ladder
  4. Start with identity, then entitlement
  5. Keep a human in the recovery path
  6. Record the workaround
  7. Close with confirmation
  8. A first-morning example
  9. Review the pattern weekly
  10. Sources
  11. Related reading

Published October 27, 2026.

Define what blocked means

A new hire who cannot sign in to email, the HR system, or the time clock is blocked from working. A new hire who cannot open a reporting dashboard is degraded but productive. Write the distinction before the first ticket arrives so the service desk does not treat every access issue as equally urgent.

Collect the minimum ticket detail

Ask for the employee name, start date, role, system, exact error, and whether the person has ever signed in successfully. Do not ask for a password. Attach the ticket to the onboarding record so the pattern can be reviewed later.

Use a short severity ladder

Severity one is no access to a required system with no workaround. Severity two is partial access or a workaround that blocks a key task. Severity three is a convenience issue. The ladder should include a response target and an owner for each level, not just a label.

Start with identity, then entitlement

Many day-one failures are identity problems: the account was created with the wrong name, the MFA device was not enrolled, or the recovery method is missing. Resolve identity before changing permissions. Granting extra access to work around a sign-in problem creates a security issue and hides the real cause.

Keep a human in the recovery path

A new hire who cannot verify identity should speak with a named person, not enter an endless reset loop. Give the service desk a verified callback procedure and a temporary, logged access path. The procedure should be tested before a busy hiring week.

Record the workaround

If the new hire uses a shared mailbox, a loaner laptop, or a temporary account, record the workaround, the owner, and the expiry date. A workaround without an expiry becomes permanent. Review open workarounds at the end of the first week.

Close with confirmation

The ticket closes when the employee confirms access to the required system and the service desk records the fix. Do not close on a password reset alone. A confirmation from the employee or the manager is the evidence that the work is actually done.

A first-morning example

A sales coordinator starts at nine and cannot open the CRM. Email works, so the ticket is severity two. The service desk finds that the role mapping was copied from an old template and the CRM license was never assigned. The fix is recorded, and the onboarding template is corrected for the next sales hire.

Review the pattern weekly

Count day-one tickets by system, role, and root cause. A repeated failure in one system is a provisioning problem, not a run of bad luck. Assign the fix to the team that owns the template or the identity source, and check the next cohort.

  • Blocked versus degraded
  • Severity and owner
  • Identity verification path
  • Workaround expiry
  • Employee confirmation

Sources

  1. NIST SP 800-63B digital identity guidance
  2. CISA Secure Our World
  3. NIST Cybersecurity Framework
  4. SHRM onboarding toolkit

Continue building the workflow

Related support: virtual assistant role brief, virtual assistant onboarding checklist. The U.S. Equal Employment Opportunity Commission explains that employment selection procedures should be job related and consistent with business necessity.