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.
Feature · Onboarding and offboarding
Example screen with sample data
Onboarding and offboarding
Assign joining and leaving work with named employees, evidence and payroll handoffs.
OverviewOffer approval inbox×
HRMS · Onboarding and offboarding
New
Offer approval inbox
Approval conditions
| Offer number | Candidate | Position | Base salary | Currency | Start date | |
|---|---|---|---|---|---|---|
| OFF-80820 | CND-5469 | PST-8797 | 760 | USD | 07 Oct | |
| OFF-46435 | CND-3635 | PST-5045 | 480 | CAD | 24 Oct | |
| OFF-32358 | CND-2232 | PST-9216 | 30 | INR | 15 Oct | |
| OFF-22150 | CND-7463 | PST-1965 | 650 | SGD | 27 Oct | |
| OFF-12915 | CND-3920 | PST-3139 | 240 | GBP | 05 Oct |
6 of 6 records
CND-5469Offers · OFF-80820
USDPositionPST-8797
Base salary760
Start date07 Oct
StatusPending approval
What you can do
Give each joining or leaving task an owner
An accepted hire needs a clear route from agreed terms to the first day. A checklist identifies the employee and joining cycle. Its tasks carry the individual assignment, due date, status and evidence. The same structure supports onboarding, offboarding, transfer and rehire, with the checklist type identifying the work being coordinated.
Joining work comes from a role-based template after employee provisioning. Separation creates an offboarding checklist for access revocation, equipment return, final pay and statutory closures. HR Business Partner (HRBP) coordinates employee events while task owners follow their assigned handoffs through the relevant systems and retain the outcome.
How the work is organized
- Employee provisioning. The accepted offer supplies the start date, salary and currency. The position supplies organizational references, and its location supplies the country. Check these links before using the employee record for joining work.
- Task progress. Categories distinguish IT, Facilities, Payroll, HR, Compliance, Manager, Buddy, Training and Selfserve work. Pending, In progress, Blocked, Completed and Skipped express different outcomes. Completion dates and evidence help the coordinator review what actually happened.
- Checklist closure. The checklist carries completed and total task counts with recorded progress. The completion workflow responds to task and checklist changes. Review first-day employee activation and the Hire history event alongside checklist progress. Mandatory learning assignment belongs to the learning workflow.
What to agree during setup
Choose a joining template and a separation template for the pilot. Define the evidence each owner supplies and the next action when a task is blocked. Configure access to assigned tasks and test it with the ordinary accounts of the people doing the work.
Keep learning ownership explicit so onboarding does not repeat mandatory course assignments. For a separation, agree the payroll handoff and connect the final-pay task to the intended run. Assign an owner for identity-provider results and equipment confirmation. The coordinator needs a clear way to inspect those confirmations beside the task.
Check the handoff on an actual case
Accept a pilot offer and inspect the employee record before reviewing the checklist. Compare the department, position, location and hire date with the accepted terms. Complete an assigned task with evidence and inspect the parent checklist’s recorded progress. Leave another task Blocked and ask its owner to explain what must happen next.
Next rehearse a departure. Apply the employee’s termination through the lifecycle route and inspect the history event and offboarding checklist. Find the final-pay task and its linked run. Keep the access-revocation task unresolved until the identity provider confirms the result. Ask HR Business Partner (HRBP) and Payroll Admin to explain the remaining work using the same employee context.
What your team sees
- Onboarding work — Review joining and leaving checklists, target completion dates and recorded progress.
- Effective employee changes — Connect a hire or separation to its dated lifecycle event.
Follow the work through
Use accepted offer to onboarding for joining and employee changes and separation for departures.
What it keeps track of
Data model- Onboarding checklists
- The per-hire or per-separation container of tasks.
- Onboarding tasks
- Individual tasks that fan out to IT, Facilities, Payroll, Manager and the new hire.
- Employees
- The central person record that every transaction in the suite ties back to.
- Offers
- Offer letter, approval chain and e-sign state.
- Positions
- Seat-level org entries that employees fill.
- Locations
- Physical and remote work locations with country and tax jurisdiction.
- Employment history
- Every lifecycle event: hire, promotion, transfer, comp change, manager change, leave of absence, termination.
- Payroll runs
- A scheduled execution of payroll for a calendar and period.
- Course enrollments
- Employee enrollment in a course - the LMS transaction record.
Who uses it
Permissions- HR Business Partner
- (HRBP), CHRO / VP People, Payroll Admin, Employee.
- HR Business Partner
- (HRBP) coordinates through scoped actions; CHRO / VP People has oversight.
- Payroll Admin
- Prepares final pay.
- Employee
- Receives only the tasks and information made available within the agreed scope.
Set up HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.