Onboarding flow
- 01Create templates
Make reusable task lists for a department, designation, location, category or employment type.
- 02Start employee onboarding
Choose accepted offer, employee and template; enter planned/actual joining dates and owner.
- 03Complete generated tasks
Assign responsible person, due date, status, evidence and remarks. Track overall completion.
- 04Issue assets
Record each item/asset, serial number, condition and expected return date with acknowledgement.
Modules and child rows
Set optional applicability filters and Default Completion Days. Template Tasks contain name, category, responsibility rule, due-day offset, mandatory/evidence settings and dependency serial number.
Links offer, employee and template. Status progresses PLANNED → IN_PROGRESS → COMPLETED; use CANCELLED for abandoned onboarding. Child Onboarding Tasks hold actual assignee, due/completion information and evidence.
Record employee, item/asset identity, serial number, issue/return dates and condition. Status ISSUED means custody remains with the employee; RETURNED, LOST or DAMAGED closes/qualifies that custody.
Good practice
- Keep a small number of reusable templates rather than duplicating one per employee.
- Use evidence for compliance-critical tasks such as signed policies or identity verification.
- Enter asset condition both at issue and return.
- Do not mark onboarding complete while mandatory tasks remain open.