Hired means the record exists.
Accepting an offer creates the employee, the payroll profile, the journey and the mandatory learning. Nobody imports a CSV on Monday.
Part of Employee Management
The first day is ready. The last day is not an argument.
Two journeys on the same record. An accepted offer raises the welcome checklist for HR, IT and the hiring manager. A recorded separation raises the leaver checklist, queues access revocations, and calculates the settlement with the working shown.
- An accepted offer in Recruit creates the employee record and the welcome journey. Nobody retypes what the candidate already gave.
- HR, IT and the hiring manager each hold their own tasks, with status visible before she arrives.
- Probation reviews are dated from her first day and already sit on the calendar.
- A recorded separation raises the leaver checklist and queues access revocations while there is still time.
- The final settlement shows its working: pro rata pay, unused leave and recoveries, not a calculator argument.
Priya NairProduct Designer · joins MondayJourney startedDay 1 · Monday, 24 August
August 202624
10:00 welcome session, video
Welcome journey
- Laptop reserved, IT
- Buddy introduced, manager
- Policies to read, Priya
- Benefits enrolment, People
Probation review
22 NovNinety days from her first day, already on the calendarThe problem
Day one is chaos. The last day is worse.
Day one arrives regardless.
The contract is unsigned, the right to work check is half done, and nobody notices until the new joiner is sitting there waiting to be given a laptop.
Access that outlives people.
Weeks after a leaver’s last day, their accounts still work. Every forgotten revocation is a security finding waiting to be written.
The settlement argument.
Final pay, unused leave, deductions and recoveries computed on a calculator, disputed by the leaver, and defended with no working.
How Onboarding & Offboarding fixes it
What Onboarding & Offboarding does on the connected record.
Onboarding journeys with owners: task checklists for HR, IT and the hiring manager, each with status and progress visible
Hired means ready: an accepted offer in Recruit creates the employee record and the onboarding checklist automatically
Probation watched properly: probation end dates and reviews surface before they are due, never after
The leaver checklist raises itself: the moment a separation is recorded, knowledge transfer, equipment return, access and final pay tasks are created and tracked to done
Access revocation queued: revocation requests for every system are raised when the separation starts, not remembered afterwards
Exit interviews captured: scheduled, recorded and themed, and a separation can carry a regrettable loss judgement that attrition analytics reads once it is set
Final settlement with the working shown: pro rata pay, leave payout and recoveries calculated with a full trace anyone can check
Immediate dismissal, same stack: last day today, notice at zero, access revoked and login off. There is no parallel firing path
A real workflow
The first day and the last, step by step.
- The offer becomes a record.Acceptance in Recruit creates the employee record and raises the onboarding checklist automatically, so nobody retypes what the candidate already provided.
- Day one is prepared, not improvised.HR, IT and the hiring manager each hold their own tasks with visible status, so the laptop, the documents and the first week plan are ready before arrival.
- The journey continues past week one.Probation end dates and reviews surface ahead of time, so the follow up happens on schedule rather than by apology.
- A separation raises the exit chain.The moment it is recorded, knowledge transfer, equipment return and access revocation tasks are created and tracked to done, while there is still time to act on them.
- The settlement shows its working.Pro rata pay, unused leave payout and recoveries are calculated with a full trace anyone can check, and the exit interview is captured with its themes, so why people leave is written down while it is still fresh.
One record. Nothing entered twice.
Onboarding & Offboarding does not live on an island.
Arrivals and exits run through the same record: Recruit hands a hire straight into onboarding, offboarding raises asset returns and access revocations automatically, and the final settlement reads pay and leave from the ledger rather than a calculator.
Why teams switch
The first day and the last already have owners.
A separation raises the work.
Knowledge transfer, equipment return, access and final pay are created when the leaving date is recorded, not remembered afterwards.
The settlement shows its working.
Pro rata pay, unused leave and recoveries are calculated with a trace. Dual control means two different signed-in people. There is no service-role approve shortcut.
Probation starts itself.
A person on a probation status gets a journey from the record. Reviews are dated from the first day. Nobody presses Start, and a forgotten date is not the process.
Already connected
Recruit hands over. Payroll and Assets already know.
Journeys are checklists with owners and due dates. A coloured badge is not the work. Probation starts itself when the status says so. Notice cards show the real milestones, not a fake local tick list.
- HR, IT and the hiring manager each hold their own tasks. Status is visible before day one, not after the person is waiting.
- Access revocation is queued when the separation starts. Forgotten accounts are a security finding the product is built to prevent.
- Immediate dismissal is the same stack with last day today and notice at zero. PILON can be none.
- An exit interview can be booked as a real calendar meeting. A regrettable loss judgement is what attrition analytics reads, once it is set.
Who it is for
The people who actually run the first week and the last.
Recruiter
The person who sent the offer.
Nora watches accept create the record. The seat on Organo is the same hire. She does not retype Priya into People.
Hiring manager
The person who meets them on day one.
The welcome and the first check-in are already tasks. He is not building a week from a doc.
IT
The person with the laptop list.
Issue is on the journey. A resignation lists what is still out. Access revoke is queued, not hoped.
Finance
The person who signs the settlement.
Muiz cannot be the only signature. The working is on the page. A calculator argument is not the process.
Keep reading
How arrivals and exits should run.
Questions people actually ask.
When does the employee record appear?
When the candidate accepts the offer. Day 1 cascade creates the record, payroll profile, journey, mandatory learning and Flow work. The start date can still be in the future.
Do I start probation by hand?
No. A person on a probation status gets a journey from the record. The start button was removed on purpose. Health reads the real check-in milestones.
Who can approve a final settlement?
Two different signed-in people. Dual control is not a service-role shortcut, and the person who gave the first signature cannot give the second.
Is immediate dismissal a different product?
No. It is the same termination stack with last day today and notice at zero. Access revoke and login off run the same day.
Included with Employee ManagementOnboarding & Offboarding ships inside Employee Management at $5 per employee / mo · payroll included, with connected Organo included at no extra charge.Compare pricing →
More of Employee Management
The rest of the record.
Ready for onboarding & offboarding
that lives on one record?
Onboarding & Offboarding arrives as part of Employee Management, connected to the same record every other module reads. Nothing to sync, nothing entered twice.
← Back to Employee Management