People
Onboarding and checklists
One engine for joining, leaving and moving, with templates that resolve to the most specific match.
Onboarding, offboarding and transitions all run on one engine. A template resolves most-specific-first — position, then entity, then country and region, then a generic fallback — using the same rule as leave policy.
Tasks are copied when a checklist starts
Editing a template must not rewrite a checklist somebody is halfway through. Deleting a template that has already started one deactivates it instead, so the record of which version of onboarding a person went through survives.
Who can see a checklist
A checklist names documents to collect and carries notes against them, so it is treated as personal data — with one addition the other personal data does not have: a task assignee can see the checklist. Setting up a laptop goes to IT, and gating that on an HR role would put HR in the middle of every step.
- The subject of the checklist, any task assignee, HR viewers and administrators, and a line manager for their own reports.
- Starting a checklist is HR-administrator only.
- Completing a task is authorised by assignment, not by role.
- An unassigned task is HR-only rather than open to anyone who can see the checklist — an unresolved assignment must not let somebody tick off their own right-to-work check.
Tasks that require evidence
A task can require a document of a given type before it can be completed, and the document is re-verified against both the organisation and the person. A compliance task that can be ticked with nothing behind it records nothing.