Onboarding Checklists and Documents
Checklist behavior
The monolith stores generic onboarding tasks. Employee and task name are required; category defaults to Joining and status defaults to Pending. Owner, due date, and notes are optional. Authorized administrators can create, update, list, and delete these records. No task template, allowed category catalog, status transition rules, dependencies, completion percentage, reminders, approval, or direct link to Recruitment onboarding was found. This is Foundation functionality.
The Recruitment onboarding screen displays Offer accepted, Documents submitted, Bank details, KYC complete, and User created indicators. Documents submitted is only a checkbox whose outcome is appended to notes. Bank and KYC indicators are computed from current form values. They do not query or enforce the generic task store.
Document collection
| Evidence | Implemented behavior | Limitation |
|---|---|---|
| Candidate documents | Recruitment stores uploaded document references and content through its Document gateway | No onboarding-required document catalog |
| Employee document references | Employee stores document type, name, storage reference, content type, size, pending verification status, and optional expiry | Employee aggregate does not own binary storage |
| UI checkbox | HR can record “submitted” or “pending” in onboarding notes | Not proof of upload or verification |
| Monolith KYC/bank input | Stored on monolith completion | Extracted completion ignores those compatibility fields |
Identity, educational, employment, tax, and other mandatory document classifications Require confirmation. No review/approve/reject verification command was found for the Employee reference, whose initial status remains Pending.
Ownership and safety
Recruitment owns candidate document references; Employee owns employee profile references; Document Service owns storage operations where integrated. Documentation and support evidence must not contain document contents, storage keys, personal numbers, account data, or candidate/employee identifiers.
Source References
Models/OnboardingTask.csControllers/HrOperationsController.csModels/CandidateDocument.csmicroservices/src/recruitment-service/Application/Commands/CandidateCommands.csmicroservices/src/employee-service/Domain/Employees/Employee.csUI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentOnboardingPage.tsx
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly