Skip to main content

Offboarding and Checklist Model

Summary​

Offboarding is implemented in the monolith HR Operations boundary. It records exit requests and decisions, permits rollback in supported states, and performs a manual access-revoke operation after the last working day.

Audience​

Developers, QA, support, security reviewers, and solution architects.

Exit state flow​

The controller applies tenant, permission, service, and workforce relationship checks around operations. An approval produces a notification event through the monolith notification path. Processing disables associated access/workforce records and completes the exit request.

Checklist and task representation​

OnboardingTask is a generic monolith task record. The extracted Recruitment onboarding aggregate tracks lifecycle status but does not own an enforced multi-domain checklist. No offboarding checklist aggregate, task dependency graph, mandatory-clearance engine, or automatic task generation was found.

Persistence and audit​

Exit requests and their audit log are stored in the monolith application database and participate in tenant query filtering. The audit record is application evidence of actions; it is not documentation of regulatory retention, immutability, or external audit certification.

Requires confirmation​

  • The exact rollback states and operational approval policy expected by each tenant.
  • Whether access revoke must wait for asset, payroll, knowledge-transfer, or other clearance evidence.
  • Recovery handling when only some user/labor updates succeed.
  • Whether completed exit data has a mandated retention or archival schedule.

Source References​

  • Controllers/HrOperationsController.cs
  • Models/ExitRequest.cs
  • Models/ExitRequestAuditLog.cs
  • Models/OnboardingTask.cs
  • Data/AppDbContext.cs

See Also​

Keywords​

  • Exit request
  • Access revoke
  • Checklist boundary

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Review cycle: Quarterly