---
name: new-hire-access-readiness
description: Maps a new hire's role and department to required access, equipment, training, and policy acknowledgements, then identifies dependencies and unassigned tasks. Use for onboarding readiness, access preparation, equipment planning, or manager handoff.
license: Apache-2.0
metadata:
  adlass.categories: "hr-people/onboarding-offboarding"
  adlass.industries: ""
  adlass.tags: "new-hire,access-readiness,equipment,onboarding-dependencies"
  adlass.adaptation: "reference-doc"
  adlass.source: "n8n:14221, n8n:15689"
  adlass.version: "1"
---

# New-hire access readiness

## Purpose

Translate a new hire’s role, department, location, and start date into a traceable readiness matrix for accounts, equipment, training, and required acknowledgements.

## Scope

Assess employee ID, role, department, manager, start date, location, employment type, access catalogue, role-to-system matrix, equipment inventory, training catalogue, policy acknowledgements, dependency status, owner, and due date.

**Excluded:** creating accounts, granting access, purchasing equipment, contacting people, and approving exceptions.

## Data basis

- HR new-hire records and start-date fields.
- Role-to-access matrix, application catalogue, equipment inventory, training catalogue, and policy register.
- Existing onboarding tasks, dependency rules, and ownership matrix.

## Result

A readiness sheet with requirement, system or item, required level, task owner, dependency, due date, status, evidence, and gap reason, plus a start-readiness memo.

## Quality criteria

- Every required access, item, course, and acknowledgement for the mapped role has one row.
- Due dates are calculated from start date and documented lead-time rules.
- No access is marked ready without a source status or evidence.
- Conflicting role mappings and missing owners are explicit.

## Instructions

Use the role matrix as the authority and intersect it with employment type, department, location, and start-date rules. Distinguish required, conditional, and not-applicable requirements. Treat least privilege as the default when levels conflict. A dependency blocks readiness when its prerequisite is incomplete or ownerless.

Apply start-date offsets in calendar units defined by the onboarding policy, and retain the calculated date alongside the source start date. Separate technical provisioning from manager-owned training and acknowledgement tasks. A blocked requirement should identify the first incomplete predecessor.

## Adapt before use

- Add role-to-system, equipment, training, policy, dependency, and ownership matrices.
- Map HR fields and define lead times, status values, and required evidence.
- Set rules for contractors, locations, privileged access, and exception escalation.