Onboarding, mobility, role changes, exits and sensitive cases coordinated across HR, line managers, IT and facilities — every event with its effective date and its defined tasks, each with a recorded confirmation from the authorized owner or the system agreed for it.
01 · The problem
An onboarding, a transfer, a change of line manager or an exit sets off work at the same time in HR, the requesting team, IT, facilities and — depending on the case — security, finance or legal. Each area knows its own part and none of them sees the whole: which task was left without an owner, who has already confirmed theirs, and what is still missing for the event to be complete.
The event is coordinated with whatever is at hand: a Microsoft Excel spreadsheet holding the onboarding checklist, emails to IT and facilities asking for access and equipment, and Microsoft SharePoint folders where the signed paperwork ends up. Each piece does a useful job, and none of them records which task was left without an owner, who confirmed each access grant, and on what evidence the event was called complete.
The cost shows up later: access granted too late, equipment nobody collected, a signature that surfaces in a review, a role change recorded a month after the fact. In sensitive cases, coordinating by email also stops being an efficiency problem and becomes a confidentiality one.
The event is not late for lack of tasks: it is late because none of those checklists can show, on a given date, that the event is complete and on what evidence.
02 · The solution
Every onboarding, move, role change or exit opens as an event with its effective date, the person, the legal entity, the site, the role and the responsible line manager. Those details determine the tasks that belong to it: paperwork and signatures, approvals, granting or revoking access, handing over or recovering equipment, induction and the update to the HR record.
Role, legal entity, site, line manager, the applications associated with the position and the rules for each event type are already defined and approved in the Operational Graph; that is where the task list for the event comes from. BPMflow supports the workflow — tasks, assignment, deadlines, approvals and evidence — so the event is built from the organization's own context instead of a checklist rewritten by hand every time.
HR Shared Services — Negotiated Offboarding remains the dedicated workflow for agreed separations, with its documents, its signatures and its payroll and legal approvals; Employee Lifecycle Operations coordinates the rest of the lifecycle and routes negotiated exits to that workflow. Governed documentation comes from Document Governance & Evidence, and the context of applications and devices from Live IT Inventory.
03 · Capabilities
Events sit in a single queue, with type, effective date, legal entity, owner and open item visible at a glance. Max answers questions about the event within the authorized context: it explains which task is missing, shows the evidence on record and points to whoever has to confirm it.
Opens an onboarding, transfer, role-change, manager-change or offboarding event — raised by the business or triggered by the agreed date — with its effective date stated.
Tasks are assembled from role, legal entity, site, working arrangement and the rules that apply: paperwork, approvals, access, assigned equipment, induction and structure changes.
HR, the line manager, IT, facilities and security all work on the same event, each with their own part, their own deadline and a named owner visible to the relevant participants.
An event that requires confidentiality limits who takes part and who can see the evidence, without leaving the case file or falling back to email.
When the effective date changes, the scheduled tasks are reviewed: which ones are brought forward, which are pushed back and which no longer apply.
Each task record identifies who confirmed it or which system reported completion; the event keeps its paperwork, its approvals and its open items visible to authorized participants.
04 · Roles
Opens the event and supplies the context for the role.
What they see
The status of their request, what information is missing and who holds the next task.
What they do
Raises the onboarding, the transfer or the role change, supplies the context and confirms their own part.
Coordinates the event and owns its case file.
What they see
The event queue by type, effective date, legal entity, site and open item, with the paperwork attached.
What they do
Reviews the request, sends it back with a specific request for what is missing, coordinates the teams involved and records the outcome in the HR system where that is the authorized source for the event.
Delivers and confirms access and equipment.
What they see
The tasks in their area with the person, the role, the site, the effective date and the committed deadline.
What they do
Provisions access and prepares devices and assigned equipment; revokes access and recovers equipment at exit, and confirms each handover or return with its evidence.
Approves what policy requires and signs the event off as complete.
What they see
The approvals pending at their level, with the supporting evidence and the tasks still unconfirmed.
What they do
Approves, sends the event back with a specific request, or closes it once all of its tasks are confirmed.
05 · Implementation
Implementation starts with the event that is hardest to close today: the minimum context for that workflow — roles, legal entities, sites and the rules that apply — is enough, without requiring an architecture project up front.
1 · Agree on the event and its closure
Which events are included in the initial scope, which tasks belong to each one, who confirms each task, and what counts as a complete event.
2 · Capture the operating context and connect source systems
Role, legal entity, site, line manager and reporting structure come from the HR system of record, and the document repository is connected where it is the authorized source for the case file.
3 · Test the workflow and hand it over
The workflow is tested on events from the current period; tasks, deadlines and the audience for sensitive cases are then refined, and the client team takes over day-to-day operation.
A new hire is due to start on the 1st: the position has been approved, IT has prepared the access and facilities has reserved the laptop. Four days out, the effective date moves two weeks later. The event is rescheduled — access is re-dated to the new start, induction is rebooked, the HR start date is updated, the equipment handover stays open with its owner — and whatever was already confirmed keeps its evidence and the identity of whoever confirmed it. An illustrative example of the workflow, not an existing deployment.
06 · Typical scenarios
Several legal entities and sites, in-house and external workers, line managers spread across the business and dates that move: situations that come up often when the employee lifecycle crosses several teams.
An employee lifecycle event is finished when every task has been confirmed by its authorized owner or by the system agreed for that task, and the outcome carries the confirmation defined for the case; where the HR system is the authorized source, its record is added to the case file. The practical way in is to start with one event type — an onboarding or a transfer — and extend from there.
Employee Lifecycle Operations is an EAFlow cross-industry solution on the Operational Graph, supported by BPMflow's automation capabilities. HR Shared Services — Negotiated Offboarding remains the dedicated workflow for agreed separations. The examples on this page are illustrative.
