Skip to content

Solutions / Use case

Employee lifecycle automation, from offer accepted to last day.

Every hire, move and exit runs across the ATS, HRIS, payroll, identity and IT. When they don't talk, new hires wait for access, payroll gets fixed by hand and leavers keep their logins. Tray.ai connects every handoff, so HR and IT run by exception.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.

Jump to the stages
One new hire moving through onboarding: offer accepted in Greenhouse, worker created in Workday, account activated in Okta, mailbox ready in Google Workspace, laptop enrolled in Intune, joined the team channel in Slack, and ready for day one, recorded back in Workday.

The short answer

What is employee lifecycle automation?

Employee lifecycle automation keeps every system in step with a person's job, from accepted offer to last day: the hire record, accounts and access, equipment, payroll, the org chart, required training, role changes and offboarding. It runs across the ATS, HRIS, payroll, identity and IT systems, and most problems happen in the handoff between two of them rather than inside any one.

  1. 1 Offer to HRIS
  2. 2 Accounts and access
  3. 3 Laptop and devices
  4. 4 Pay and benefits
  5. 5 Org chart
  6. 6 Training
  7. 7 Role change
  8. 8 Offboard
to fully onboard a new hire at a fintech leader
10 days → 4–5 min
a month saved on provisioning at Auctane
50 hrs
a month of HR time recovered at a leading social network, on Greenhouse to BambooHR alone
~10 hrs
contractors onboarded in Peddle's first 90 days
106

The employee lifecycle, stage by stage

Eight stages from offer to exit, each with what breaks and a how-to guide for building it.

  1. 1

    Offer to hire record

    The accepted offer becomes the worker record in the HRIS, with start date, role, manager and pay.

    Where it breaks: The offer is retyped into the HRIS, and the start date is a week out.

  2. 2

    Accounts and access before day one

    Identity, email and the apps the role needs are ready before the start date.

    Where it breaks: The first morning is spent waiting on IT tickets for logins.

  3. 3

    Equipment

    A laptop is ordered, set up and shipped to arrive before day one, and tracked to the person who has it.

    Where it breaks: The laptop turns up after the start date, or arrives without the company's settings on it.

  4. 4

    Payroll and benefits

    Pay, tax and benefits details reach payroll before the first pay run, and every change after it.

    Where it breaks: A new hire misses the first payroll and has to be paid by hand.

  5. 5

    Org chart and approvals

    Manager, team and cost centre flow from the HRIS to every system that routes approvals or reports by team.

    Where it breaks: Expense approvals still go to a manager who left two months ago.

  6. 6

    Training and compliance

    Required courses are assigned by role and location, and completions go back to the HRIS.

    Where it breaks: The auditor asks who finished security training, and nobody can say.

  7. 7

    Role changes and transfers

    A promotion or transfer adds what the new role needs and removes what the old role had.

    Where it breaks: Someone moves from finance to sales and can still post journals in the ERP.

  8. 8

    Offboarding

    On the leave date, access goes everywhere, work is handed over and the laptop comes back.

    Where it breaks: Someone who left in March still has access to the CRM.

Three ways to connect the systems

  • Built-in HRIS integrations and SCIM. Quick where they exist, but each covers one app and often only some of the fields. At a leading social network, BambooHR’s own Greenhouse integration filled about 7 of 30 to 40 onboarding fields, and many of the apps people use every day don’t support SCIM at all.
  • Custom scripts. Full control, and your team owns every fix, every API change and every new app for as long as they run.
  • An integration platform. Every handoff in one place, with the same error handling, logging and access control, and apps without SCIM reached through their own API. This is Tray.ai: HR and IT build the workflows, and IT governs them.

The Tray.ai platform behind it

Tray.ai is the enterprise orchestration platform for data and AI. These are the parts of it that run employee lifecycle.

Employee lifecycle metrics

What HR and IT teams measure, and which stage each number depends on.

Day-one readiness
Share of new hires with every account and their laptop ready on their first morning.
What moves it Creating accounts from the HRIS record before the start date, instead of from a ticket. How to build employee onboarding provisioning 
Payroll corrections
Pay runs or payslips fixed by hand because the HRIS and payroll disagreed.
What moves it Sending every hire, change and leaver to payroll ahead of the cut-off. How to build an HRIS to payroll sync 
Training completion rate
Share of required training finished by its due date.
What moves it Assigning courses by role and location, and chasing the overdue ones automatically. How to build a training completion sync 
Access kept after a role change
People still holding access from a previous role past its removal date.
What moves it Removing the old role's access on a schedule after every promotion or transfer. How to build a role change access update 
Time to remove access
Hours from the leave date to the last account removed.
What moves it Removing access across every system on the leave date, and checking each one. How to build employee offboarding deprovisioning 
Devices not recovered
Laptops and phones still out with people who have left.
What moves it Tying every device to its person, and starting recovery from the leave date. How to build a device lifecycle sync 

Employee lifecycle connectors

The systems the employee lifecycle runs on, grouped by the seat each one fills. Each links to its connector page.

Recruiting and offers

Where the candidate accepts the offer and signs it.

HRIS

The record of who works here, in which job, for which manager.

Payroll and benefits

Where people are paid and enrolled in benefits.

Identity and access

Where accounts are created, grouped and removed.

Devices and IT service

Where laptops are tracked and IT requests are worked.

Learning and performance

Where required training is assigned and reviews are run.

Finance and sales

Systems that route approvals and ownership by manager and team.

Collaboration

Where new hires are welcomed and exceptions get worked.

Data and reporting

Where headcount, access and training records are reconciled and reported.

Anything not listed connects through the full connector library, or directly through its API.

Teams running employee lifecycle on Tray.ai

“We have automated so much of the onboarding and offboarding process that we're no longer spending valuable time on manual data entry.”

— Ryan Pesta, Corporate IT Manager, Auctane
Read the study

Frequently asked questions

How is this different from the workflows inside our HRIS?

+

HRIS workflows run well inside the HRIS. The work that goes wrong is everywhere else, in identity, devices, payroll, finance and the apps people use every day. Tray.ai treats the HRIS (Workday, BambooHR, SAP SuccessFactors and others) as the record of who works here and carries each change to every system that needs it.

Which systems does Tray.ai connect in the employee lifecycle?

+

Recruiting (Greenhouse, Lever, Workable, DocuSign), HRIS (Workday, BambooHR, SAP SuccessFactors, Personio, UltiPro), payroll and benefits (ADP, Gusto, Paylocity, TriNet, PlanSource), identity (Okta, Azure Active Directory, OneLogin, JumpCloud, Google Workspace), devices and IT service (Microsoft Intune, ServiceNow, Jira Service Desk, FreshService), learning (Docebo, Absorb, Lattice), and the warehouse for reporting (Snowflake, Google BigQuery). Anything without a connector connects through its API.

Can HR or IT build this without engineering?

+

Yes. The HR team at a leading social network built its Greenhouse to BambooHR onboarding with Tray.ai, saves about 10 hours a month, and has each new hire's profile ready up to two weeks before they start. Auctane's small IT team runs onboarding and offboarding on Tray.ai and saves 50 hours a month on provisioning.

Should employee lifecycle sync run in real time or in batches?

+

Both. Hires, leavers and role changes should be acted on as soon as the HRIS records them, so access is ready on the start date and gone on the leave date. A scheduled check then compares the HRIS with each system, because a change that never arrived sends no error and nothing else will notice it.

Where do AI agents fit in the employee lifecycle?

+

In the questions and the exceptions. An HR agent in Slack answers time-off and policy questions and submits requests, and an IT agent works through routine access requests from new starters. Access the role already allows follows the same rules a workflow uses, and anything outside them, or any change to pay, goes to a person for approval.

Do we have to replace our HRIS or identity provider?

+

No. Tray.ai connects the systems you already run and carries the changes between them. The stages above describe what moves between systems, not which ones you use.

Last reviewed 2 October 2026.

See employee lifecycle running on your stack.

Walk through your systems and stages with a Tray.ai expert.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.

Browse the how-to guides