Skip to main content

​
Overview

Use Lifecycle changes (/hr/lifecycle-changes) to coordinate starter, leaver, and mid-year employment changes in one request workflow. Each request creates owner-team tasks for HR, IT, Finance, and the line manager, then tracks progress in a status timeline. The queue table matches the hiring listings pattern: search, kind and status filters, sort, clear status chips, and per-team task progress for HR, IT, and Finance.

​
Create a lifecycle request

People with Manage employee records, and line managers for their direct reports, can create a request from Lifecycle changes in the People sidebar (/hr/lifecycle-changes):
  1. Choose the person
  2. Choose type: Starter, Leaver, or Mid-year change
  3. Confirm the effective date (prefilled from Job start or leaving date when available)
  4. Review department, role, contract, and pay fields (also prefilled from Job where present)
  5. For leavers, add a reason for leaving and optional offboarding options (HR only)
  6. For mid-year changes, capture previous and updated role/pay
  7. Add summary and details for other teams
The request is saved with status Open and default owner-team tasks. Manager-created requests route work to HR, IT, and Finance through those tasks. Automatic archive, holiday adjustment, and onboarding start still require HR manage permission. Lifecycle changes is a People module queue. Starter, leaver, and change requests are not managed from the employee record Overview.

​
Team tasks and ownership

Each request spawns default tasks grouped by owner team:
  • HR: record and policy checks
  • IT: account and access actions
  • Finance: payroll and cost checks
  • Manager: handover and team planning
The queue shows completed/open task counts per HR, IT, and Finance so each team can scan what still needs action. Users with matching permissions can complete tasks from the request detail page. Completing all tasks marks the request as completed.

​
Side effects

Lifecycle changes trigger lightweight operational side effects:
  • Leaver requests register leaver data and start an offboarding checklist run. Access is revoked on the leaving date by a daily job. If you cancel the request before that date, the scheduled archive is cleared and access is not revoked. To change a leaving date, cancel the request and create a new one with the correct date. Already archived profiles stay archived.
  • Starter requests can optionally start an onboarding account-setup run.
  • Mid-year change requests capture context and route work through team tasks without rewriting contracts automatically.
Use Cancel request on the request detail page to stop work. That control sits before Mark completed.

​
Timeline and audit

Every request stores status changes in an auditable timeline, including who changed the status and when it changed. Use this timeline during handovers and payroll cut-off checks. Submitted form fields stay on the request for IT and Finance to review.