Assess.one Employee Offboarding Workflow vs EmpCloud Emp-Exit

Assess.one Employee Offboarding Workflow is a web template for managing employee departures after resignation or termination. It covers intake, approvals, handover, final payroll inputs, property return, access removal, exit interviews, notifications, and completion checks. The route depends on the case: resignations go to manager approval, while terminations go directly to employee notification; some resignation cases can involve HR review and legal escalation. Roles are assigned to HR, line managers, payroll, IT, and legal stakeholders. Case records include status tracking, timelines, and dashboard views. A mandatory access-removal task asks IT to confirm removal of accounts, software licences, and physical site access. Steps, routing, role assignments, and notification triggers can be customised without code. The Free plan allows 100 operations per month and one team member. Starter costs $49 a month, billed $588 per year; one operation means one record created against a workflow, regardless of its number of steps.

EmpCloud Emp-Exit is an employee offboarding module for handling resignations, terminations, retirements, and contract endings. Teams can configure notice periods and route clearance sign-offs through departments such as IT, Finance, HR, Admin, and managers. Full and final settlement calculations cover pending salary, leave encashment, gratuity, deductions, and notice recovery, with manual adjustments and approval; EMP Payroll is an optional source of salary data. Employees can submit resignations, check exit status and checklist items, complete interviews, and submit an exit NPS survey. Other described workflows include asset returns, knowledge transfer, PDF exit letters, background verification, an opt-in alumni directory, and rehire. Analytics include 0–100 flight-risk scoring, risk-factor analysis, department heatmaps, attrition trends, and exit data. Six branded email templates can be previewed and customized, with delivery logging. OAuth2/OIDC authentication is through EMP Cloud, which must be running. The project documents an OpenAPI 3.0 specification at /api/docs. Quick-start prerequisites include Docker Compose, Node.js 20+, pnpm 9+, MySQL 8+, and Redis 7+. The repository states an AGPL-3.0 license.