These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Security Services HRMS
- Features
- Joining and leaving
Joining and leaving
Give a hire or leaver a dated checklist, assign tasks and keep employment events connected to the employee.
OverviewPeople on leave×
Security Services HRMS · Joining and leaving
New
People on leave
Employees
| Employee ID | Full name | Department | Manager | Status | |
|---|---|---|---|---|---|
| EI-623 | Full 341 | DPR-110 | On Leave | ||
| EI-172 | Full 562 | DPR-130 | On Leave | ||
| EI-376 | Full 872 | DPR-150 | On Leave | ||
| EI-738 | Full 574 | DPR-140 | On Leave | ||
| EI-613 | Full 809 | DPR-120 | On Leave |
6 of 6 records
EI-623Employees · EMP-75680
On LeaveFull nameFull 341
DepartmentDPR-110
What you can do
Make the handoff visible
An accepted offer is the point where recruiting hands responsibility to HR and the receiving team. An onboarding checklist belongs to one employee and identifies the type of handoff, its start date, target completion and overall status. Individual tasks carry a title, category, due date, assigned employee, status and evidence. That separation lets HR see whether a checklist is progressing while each person sees the work they own.
How the work is organized
- Checklist. Choose Onboarding, Offboarding, Transfer or Rehire for the employee and set dates that match the actual change.
- Tasks. Assign IT, Facilities, Payroll, HR, Compliance, Manager, Buddy, Training or Self-Serve work to named employees.
- History. Keep a dated employment event for the hire, transfer or termination so the personnel record explains the change.
What to agree during setup
Start with a small checklist template that reflects the handoffs your team really performs. Agree which category owns account setup, pay-calendar placement and any mandatory learning assignment. A due date should be early enough to expose a blocker before the employee starts. Define what evidence is required to mark each task Completed, and who may mark an item Skipped. A blocked task should stay visible until the responsible person resolves it.
For a departure, decide when to open the Offboarding checklist, who verifies final pay and who records the termination event. The employee’s status and termination date must agree with the history. An employee leaving one role for another may need a Transfer checklist instead of a new-hire checklist. Keep the prior history available to the HR Business Partner.
Check the handoff on an actual case
A candidate accepts an offer for an open operations position. HR Business Partner confirms the employee’s legal entity, start date, manager and position. Create an Onboarding checklist for that employee with a target completion. Assign payroll preparation to an employee who can check the pay calendar, and a training task to the person preparing the required course enrollment. Assigned people report progress to Admin, who moves tasks from Pending to In Progress and then Completed as work is confirmed. Admin reviews the checklist total and unresolved blockers before the start date. Record the Hire employment event with its effective date.
If the worker later transfers to a different department, record the from and to positions in employment history and open a Transfer checklist for any access or training changes. For a leaver, use Offboarding, preserve the task evidence and let Payroll Admin review pay records for the final applicable period. Do not use a completed checklist as the sole proof that the employment status changed.
What your team sees
- Joining tasks — Due work by category, assigned person and blocked status.
- Active employees — Workers whose joining handoff has reached the live people record.
Follow the work through
What it keeps track of
Data model- Onboarding checklists
- Per-hire or per-separation container of onboarding and offboarding tasks.
- Onboarding tasks
- Individual tasks that fan out to IT, Facilities, Payroll, HR, Manager and the new hire.
- Employees
- Central person record for every worker; all suite transactions tie back to Employees.
- Employment history
- Every lifecycle event: hire, promotion, transfer, comp change, manager change, leave of absence, termination.
- Offers
- Offer letter, approval chain and e-signature state.
Who uses it
Permissions- HR Business Partner
- Owns the employee handoff.
- Admin
- Maintains checklists, assigned tasks and access.
- Employee
- Completes assigned work after access is granted.
- L&D Admin
- Handles learning records.
- Payroll Admin
- Reviews payroll preparation.
Set up Security Services HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.