Employee Offboarding Workflow

How is this workflow audited for compliance and regulatory purposes?

Every action taken within the Employee Offboarding Workflow on assess.one is recorded in a tamper-evident audit log, capturing who completed each step, when, and any decisions or notes entered. This includes all approval outcomes, status changes, and notifications, providing a complete chain of custody for each offboarding record. HR and compliance teams can retrieve this audit trail at any time directly within the platform, supporting internal reviews, labour law compliance, and external audits without requiring additional tooling.

Who has access to offboarding records and how are permissions controlled?

Access to offboarding records is governed by role-based permissions configured directly within assess.one. Administrators can define which roles — such as HR Business Partner, Line Manager, Payroll, or IT — can view, edit, or action specific steps, ensuring that sensitive information such as termination details or final payroll inputs is only visible to authorised personnel. This granular permission model supports the principle of least privilege and reduces the risk of unauthorised disclosure during a sensitive process.

How does this workflow integrate with our existing HR and IT systems?

assess.one supports integrations with email and collaboration tools such as Slack, which are configured directly within the platform — no third-party development work or external implementation project is required. Notifications to stakeholders, managers, and IT teams can be automated at key workflow stages, such as when System & Site Access Removal is triggered or when the offboarding record is created. For deeper HRIS or identity management integrations, your assess.one administrator can configure the relevant connection settings within the platform.

How long does it take to implement this offboarding workflow?

Publishing the Employee Offboarding Workflow on assess.one takes minutes, not weeks. The template is ready to use immediately upon publication, and your team can begin running live offboarding processes straight away. There is no software installation, no external implementation project, and no dependency on a development team — customisation of steps, roles, and approval logic is handled entirely within the platform.

How can we customise the workflow to reflect our organisation's specific offboarding policies?

All workflow steps, routing logic, role assignments, and notification triggers are fully customisable within assess.one without writing any code. Organisations can adjust the conditional routing — for example, modifying the criteria that escalate a resignation query to legal review — add organisation-specific steps such as GDPR data handling or benefits cessation, and tailor notification content to align with internal communications standards. Changes are applied directly in the platform and take effect immediately upon republication.

What happens at the Manager Approval of Resignation step and what are the possible outcomes?

At the Manager Approval of Resignation step, the assigned line manager is prompted to review and formally approve or query the resignation submission. The workflow then routes based on the outcome: an approved resignation advances the process to stakeholder notifications and the active offboarding steps, while a queried resignation routes to HR Review for further assessment. From HR Review, the workflow can further branch to close the record if the resignation is withdrawn, or escalate to legal if required — ensuring every scenario is handled through a governed, documented path.

How is the System & Site Access Removal step enforced to prevent security gaps?

The System & Site Access Removal step is a mandatory, sequenced stage within the workflow that must be completed and verified before the offboarding record can progress to Completion Verification. The assigned IT or security role receives a structured task with clear accountability, and the step cannot be bypassed or skipped by other participants. This enforcement mechanism ensures that access revocation is consistently executed for every departing employee, reducing the risk of unauthorised system access following departure.

How are payroll and HR teams coordinated during the offboarding process?

The Final Payroll Inputs step is a dedicated, role-assigned stage that routes directly to the payroll team at the appropriate point in the offboarding sequence, after handover tasks have been addressed. Payroll personnel receive a structured notification and task within assess.one, ensuring that final pay calculations, accrued leave, and deductions are captured in a documented, auditable step rather than through informal communication. This coordination reduces the risk of payroll errors and ensures that the finance function has a clear record of all inputs provided for each departing employee.

Can this workflow handle both voluntary resignations and involuntary terminations within the same process?

Yes — the workflow includes a Route by Offboarding Type step that directs the process along the appropriate path depending on whether the departure is a resignation or a termination. Voluntary resignations follow a path that includes manager approval and, where necessary, HR review and legal escalation, while terminations route directly to employee notification and stakeholder communications. This conditional logic ensures that the correct governance steps are applied to each departure type without requiring separate workflows to be maintained.

What compliance considerations are addressed by the Exit Interview and Completion Verification steps?

The Exit Interview step provides a structured, documented opportunity to capture the departing employee's feedback, which supports obligations around fair treatment, grievance identification, and continuous improvement in people practices. Completion Verification serves as the formal closure gate for the entire offboarding record, confirming that all preceding steps — including access removal, property return, and payroll finalisation — have been completed before the case is closed. Together, these steps create a defensible, end-to-end record that demonstrates procedural compliance and due diligence in the event of a post-departure dispute or regulatory inquiry.