HR playbook · AI Employee: Harry

New Hire Onboarding

Employee has SSO, laptop, Slack, calendar access on day 0

The problem

The first 24 hours of a new hire's tenure decide the next 24 months. Every missed account, missing device, or day-1 handbook confusion costs momentum you cannot recover. But onboarding is the messiest cross-team workflow in the company — HRIS fires an event, IT provisions accounts, facilities ships a laptop, finance issues a card, the manager schedules 1:1s, security enrols the device in MDM. Anything that runs by ticket or spreadsheet drifts within a quarter.

At a glance
Trigger
HRIS event (new hire start date)
Approvals
Manager confirms start date if not in HRIS
What it does
Writes to your systems
Systems
Workday · BambooHR · Okta · Google Workspace · Microsoft 365 · Slack · Jamf · DocuSign
How it feels in production

An hour-by-hour walkthrough.

8 weeks before the start date, your HRIS marks the requisition closed and the hire signed. Harry reads the event: name, role, manager, team, location, start date. He resolves the role to a template — which SSO groups, which SaaS licences, which device model, which Day-1 doc pack. The manager gets a Slack DM: "Priya starts March 4. Buddy assigned? Reply here or on the ticket." T-3 days, Harry provisions: Okta account created, SSO groups added, Google Workspace mail alias reserved, Microsoft 365 licence assigned, Slack account invited to team + org channels, Jamf device order confirmed with MDM enrolment scheduled for arrival, DocuSign IP-assignment sent. The manager gets a status card: green ticks where done, amber where waiting on external delivery. Day 0, 9am local: Priya logs in with SSO. The welcome pack lands in her inbox — handbook, benefits, first-week reading, buddy intro. Harry posts in her manager's DM: "Priya is onboarding now. First check-in on the calendar for Day 3." 30/60/90-day check-ins are scheduled. Onboarding stall detection watches for anyone whose Day-3 or Day-7 tasks slip and nudges the manager before it becomes an attrition signal. Day 30, 60, 90: Harry sends the check-in survey, aggregates responses (anonymised where policy demands), and posts the cohort summary to HRBP. Manager gets Priya's individual signals. VIP hires trigger a separate skip-level review path automatically.
How it works

Step by step.

  1. 01

    Read the HRIS payload

    New-hire webhook fires from Workday / BambooHR / HiBob / Rippling / ADP with the requisition data. Harry parses name, email, role, manager, team, location, start date, employment type (FTE / contractor / intern).

    HRIS
  2. 02

    Resolve manager and team

    Look up the manager's identity in the Context Graph, resolve the team's default onboarding template (which SSO groups, which SaaS licences, which device SKU), check for VIP flag which routes through a separate skip-level review path.

    Context Graph
  3. 03

    Provision identity and SSO groups

    Create the Okta / Microsoft Entra ID user, add to SSO groups per the role template, reserve mail alias in Google Workspace or Microsoft 365, assign licences. All writes idempotent — a re-run of the playbook on a race condition doesn't double-provision.

    Okta · Google Workspace · Microsoft 365
  4. 04

    Assign device via MDM

    Trigger the device order through your procurement API (CDW, Apple Business Manager, Lenovo direct), schedule Jamf / Intune / Kandji auto-enrolment so the laptop is ready to log in the moment it powers on.

    Jamf Pro · Intune · Kandji
  5. 05

    Send welcome pack + Day-1 tasks

    Deliver the handbook, benefits guide, buddy intro, first-week reading, IP-assignment DocuSign envelope. Personalised by role: engineers get repo access + on-call rota, salespeople get territory + comp doc + Gong access.

    Slack · Email · DocuSign · LMS
  6. 06

    Notify manager and buddy

    Manager gets a status card with green/amber/red per provisioning step. Buddy gets a warm intro DM with the first-week meeting scheduled. Both parties know exactly what's ready and what to do next.

    Slack
Systems and wiring

What you connect to make this run.

Workday · BambooHR · HiBob · Rippling · ADP

trigger

Enable webhook on the new-hire event (usually named `worker.hire` or similar). Point to the BeforeQuery HRIS webhook URL. On payload we verify the signature and enqueue the playbook.

Okta · Microsoft Entra ID · Google Workspace

write

Create a service account / app registration with scopes to create users, add to groups, assign licences. Store in Models Studio; every action idempotent by external_id.

Jamf Pro · Intune · Kandji

write

OAuth or API-key credential with scopes to create device records, assign to user, schedule auto-enrolment. MDM does the actual device wipe/setup; we just orchestrate.

Slack

write

Install the BeforeQuery bot in the workspace. Bot posts DMs to manager + buddy, adds new hire to team + org channels per the role template.

DocuSign

write

OAuth token with envelope-create scope. IP-assignment template pre-configured with signer fields; Harry fills the merge fields and sends.

Context Graph

read+write

Every provisioning action writes edges (identity → group, identity → device, identity → manager). Downstream playbooks (offboarding, JIT access, VIP fast-track) read those edges.

What changes

Before and after, honestly.

Time to Day-1 productivity
Before
24-72 hours across manual tickets
After
Ready at 9am on start date
Onboarding-related IT tickets in week 1
Before
4-8 per new hire (missing account, group, licence, device access)
After
0-1 (only genuine edge cases)
Manager time spent on onboarding coordination
Before
~4 hours per hire across chase-ups and status checks
After
~15 minutes reading Harry's status cards
First-90-day attrition warning signal
Before
Discovered at exit interview
After
Flagged in Day-30 or Day-60 check-in aggregate
Frequently asked

Answers about this playbook.

What if the HRIS event fires and the manager isn't identified?

The playbook holds. Harry posts to your HR-ops channel with the requisition data and asks who the manager is. Once resolved (by reply or dashboard), the playbook resumes automatically. Never provisions to a hire without a manager on record.

How does it handle contractors vs. full-time employees?

The role template carries the employment type. Contractors get a scoped-access template (fewer licences, contract-end-date on every group grant so offboarding fires automatically). FTEs get the standard package. Interns get a third variant with mentor assignment.

What if the device order can't ship in time?

Harry detects the delivery slip from the procurement API, posts a status update to the manager, and offers a loaner device via the RMA / loaner playbook. New-hire access still works from the loaner; the primary device swaps in on arrival.

Does the manager need to do anything before Day 0?

Two things: confirm the buddy assignment (Harry asks in Slack; a 3-word reply is enough), and confirm the Day-1 meeting on the calendar (Harry schedules it, manager just accepts). Everything else runs on autopilot with status cards.

Can we customise the welcome pack per team?

Yes. The team template holds a Day-1 doc list; engineering gets repo access + on-call, sales gets territory + comp + Gong, etc. Update the template in Playbook Studio; the change applies to the next hire without touching the playbook.

What happens if a new hire is rehired within a year?

Harry checks the Context Graph for a prior identity with the same email. If found, offers a rehire path that preserves badge number, historical audit trail, and equipment history — while re-issuing new credentials and re-consenting to policies. Prevents both duplicate records and stale-account revivals.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.