XOPS

The Platform  /  Domains  /  Employee

Employee Lifecycle.
Hire to retire.

HR knows the employment event. Identity knows access. Devices, software, communications, workplace, and finance each know a piece of the employee. XOPS continuously reconciles those signals into the Employee Position, then coordinates every transition as one governed outcome.

5

Lifecycle phases

8

Governed outcome patterns

Weeks

To first production Outcome

The core primitive

Every system knows
part of the employee.

HR knows employment status. Identity knows access. Endpoint systems know devices. Software systems know entitlements. Workplace systems know location and badges. Each holds a fragment of the employee’s operational reality.

XOPS reconciles those fragments into the Employee Position.

The Employee Position is the continuously reconciled state of role, employment type, manager, identity, access, devices, software, location, policy, and lifecycle obligations. It gives XOPS the context required to determine and execute the correct outcome.

The lifecycle, end to end

Five phases.
One coordinated lifecycle.

Every employee, every transition, every event: coordinated across HR, identity, devices, software, comms, workplace, and finance, reconciled into one Employee Position.

1

Pre-employment

Pre-staged identity, HR data validation, long-lead device pre-order, day-1 cascade scheduling.

2

Onboarding

IDP activation, role-based provisioning, device, software, comms, workplace cascade, compliance training.

3

Active · moves & changes

Role change, manager change, location change, contractor extension, contractor → FTE conversion, elevated access.

4

Leave of absence

Leave registration, access suspension, periodic check-in, return-from-leave reactivation, escalation paths.

5

Offboarding

Voluntary, involuntary, manager delegation, asset recovery, identity archive, retention compliance.

Governed outcome patterns

Eight governed outcome patterns.
Every employee transition.

These are not fixed workflows. Each outcome pattern uses the current Employee Position to determine the right actions, ordering, policy, and exception path across HR, identity, devices, software, communications, workplace, payroll, and finance. Every transition follows a governed, auditable path. Every action is reversible.

Onboarding

P2 · day 1

FTE Onboarding

Pre-staged identity, role-based provisioning bundle, device delivery, comms, workplace, training enrollment, complete by start time.

Onboarding

P2 · bounded

Contractor Onboarding

Time-boxed identity, contract-end-aware access, vendor management coordination, contractor-tier device + software bundle.

Onboarding

P3 · cohort

Intern Onboarding

Cohort-aware provisioning, scoped access, mentor pairing, term-limited entitlements, end-of-program offboarding scheduled.

Offboarding

P2 · scheduled

Voluntary Offboarding

Notice-period coordination, knowledge transfer scheduling, asset recovery, manager delegation, comms continuity, identity archive on last day.

Offboarding

P1 · immediate

Involuntary Offboarding

Coordinated immediate revocation across identity, devices, software, comms, workplace. Asset recovery initiated. Preservation policy where required.

Move

P2 · cross-system

Role Change

Entitlement upgrade or right-sizing, manager and team reassignment, software bundle adjustment, comms updates, training assignments.

Move

P3 · cross-region

Location Change

Multi-site badge access, regional device standards, local comms config, payroll routing, workplace assignment, time-zone-aware calendars.

Leave

Scheduled

Leave of Absence

Access suspension, comms auto-reply, manager delegation, payroll continuity, periodic check-in, clean reactivation on return.

When scale meets the seam

Two hundred new hires.
Twelve countries. One Monday morning.

A quarterly hiring wave finalizes Friday afternoon. Two hundred new employees across twelve countries start Monday. Every one of them needs HR, identity, device, software, comms, workplace, and training to land before 9am local. Without coordination, that’s a four-day fire drill.

Without coordination

Half of them couldn’t log in until Thursday.

  • Friday: HR finalizes 200 new hires. ITSM team drafts a queue of 200 onboarding tickets. Operators in three regions divide the work.
  • Monday: Some hires can log in, some can’t. Some have laptops, some don’t. Different time zones are at different stages. Help desks across three regions are flooded.
  • Wednesday: Most are online. A few are still missing software entitlements, badge access, or local comms config. Managers escalating daily.
  • Thursday: everyone is finally productive. The new hires’ first impression of the company is a fire drill.

With XOPS

Two hundred employees ready to work by 9am local.

  • Friday: HR finalizes the cohort. XOPS reconciles employment type, role, country, manager, location, device standards, policy, and required entitlements into an Employee Position for each hire. Two hundred Onboarding Outcomes fire in parallel, each based on the employee’s actual Position.
  • Friday evening → Sunday: Devices ship to local addresses. Identity provisioned in correct order. Software entitlements applied by role. Badges pre-configured for the right office. Comms and calendars staged.
  • Monday 8am London: 47 European hires log in. By 9am local in each subsequent timezone, the rest of the cohort follows. Every account, badge, device, app, ready.
  • Manager dashboard shows 200/200 productive. Help desks see no surge. The new hires don’t notice. That’s the point.

One HR signal. Two hundred onboarding Outcomes coordinated in real time.
Zero broken Mondays.

What changes in production

Operational impact,
measured where it matters.

Representative outcomes observed across Fortune 500 deployments. Your numbers will vary. And we’ll measure them with you.

Day 1

Productive on start time, every region

85%

JML auto-completion rate

Real time

Cross-domain coordination on every event

~70%

Reduction in JML ticket volume

100%

Access recertification compliance

Single

Workforce-wide operational view

In production today

Running employee lifecycle
across the Fortune 500.

Customer outcome · Cencora

Fortune 15 · Pharmaceutical

From per-team JML to one coordinated workforce.

Cencora processes thousands of employee transitions every month: joiners across pharma research, supply chain, and corporate; offboarders, role changes, leaves, returns. Before XOPS, each transition surfaced as a multi-team ticket scramble. XOPS now reconciles every employee event into a single Position and treats it as one governed Outcome. Onboarding cohorts arrive ready. Departures don’t leave gaps. Role changes coordinate across HR, IT, comms, and workplace from one signal.

Thousands

Employee transitions per month

Day 1

Onboarding cohorts ready by start time

Real time

Cross-domain JML coordination

“The new hire orientation deck used to include ‘tickets to expect this week.’ We removed that slide. Now the onboarding email says ‘your laptop is on your desk.’ And it is.”

VP of People Operations · Fortune 100 Pharmaceutical

1.4M+

Employees under coordinated lifecycle

39

Countries deployed

Weeks

Typical time to first production Outcome

See it coordinate in your estate. In days, not quarters.

Pick one domain. Connect the systems. Run a real Outcome end-to-end before the next steering meeting.