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.
- HRMS with Exit Management
- Features
- Employment history
Employment history
Keep dated employment changes alongside the current employee state.
OverviewFormer employees×
HRMS with Exit Management · Employment history
New
Former employees
Employees
Terminated3
EI-769Full 553
17 Oct
EI-998Full 128
20 Oct
EI-979Full 863
09 Oct
Add
Rehireable3
EI-112Full 242
05 Oct
EI-397Full 119
08 Oct
EI-620Full 546
16 Oct
Add
What you can do
Record the effective event
Employment history records a lifecycle event with an effective date, reason, prior and new position, prior and new manager and salary values where relevant. Termination is an event type value. HR Business Partner can enter the event, and the linked employee record keeps the current status and termination date.
A departing employee may have a current record, a dated employment change, an exit checklist and a payroll statement. Review the links between those records before treating one status as the whole answer. The manager and HR Business Partner should be able to identify the next owner from the assigned task and its due date.
How the work is organized
- Person. Keep the employee identifier and current manager with the departure record so the work is attached to the right worker.
- Date. Use the effective event date and task due dates to distinguish future work from overdue work.
- Result. Record the status and supporting evidence on the record where the work occurred.
What to agree during setup
Agree who approves a departure decision and who records the dated event. Choose the required reason from the available values: Voluntary, Involuntary, Retirement or Redundancy when one applies. Preserve the effective date and recorded-by employee reference. Changes to pay or position need the same care as the exit event.
For the pilot, choose an employee with a normal departure and one with a change close to the payroll cutoff. Decide who reviews each case and where an exception will be recorded. The team should use the exact same owner for a task in the app and in its operating procedure.
Check the handoff on an actual case
For a person who moved teams and later leaves, inspect both events in order. Check that the termination event belongs to the correct employee and uses the agreed effective date. Compare the employee termination date with the event and the exit checklist. Resolve discrepancies before the final pay review.
Ask the next owner to open the record without relying on a separate message. They should see the relevant employee, dates, current status and who completed or still owns the work. If they cannot make the next decision from those records, improve the task description or review rule before expanding use.
What your team sees
- Employment changes — Open the relevant records and review the current result.
- Former employees — Open the relevant records and review the current result.
Follow the work through
See employee departure, payroll review and implementation for the handoffs around this module.
What it keeps track of
Data model- Employment history
- Every lifecycle event: hire, promotion, transfer, comp change, manager change, leave of absence, termination.
- Employees
- Central person record for every worker; all suite transactions tie back to Employees.
- Positions
- Seat-level org entries that an Employee fills.
Who uses it
Permissions- HR Business Partner
- Records and reviews lifecycle events.
- CHRO / VP People
- Has oversight.
- Admin
- Manages setup.
Set up HRMS with Exit Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.