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
- Recruiting and rehire
Recruiting and rehire
Preserve prior employment context for a later return.
OverviewOpen requisitions×
HRMS with Exit Management · Recruiting and rehire
New
Open requisitions
Job requisitions
Approved3
PST-6688JR-95658
PST-7416JR-60235
PST-5808JR-29938
Add
Open3
PST-9861JR-24552
PST-3558JR-31062
PST-4322JR-38782
Add
What you can do
Use the existing person history
Employees can be marked Rehireable after termination. Employment history has both Termination and Rehire event values. Recruiting records connect Candidates, Applications, job requisitions and Offers to the hiring process. The earlier employee event remains useful context when a former worker is considered for a new role.
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 may mark someone Rehireable and which hiring steps still apply. Recruiting should use the approved requisition and offer records for a new position. Confirm whether the person record is reused and how prior termination history is preserved before entering a rehire 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
Take a former employee who applies for an open role. Recruiter reviews the application and offer against the requisition. HR Business Partner checks the old employee status and history. When the hire is accepted, the team records the new effective event while retaining the prior termination and checklist history.
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
- Open requisitions — Review approved and open roles before a former employee returns to the hiring pipeline.
- Employment changes — 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- 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.
- Candidates
- Person pool in the applicant tracking system.
- Applications
- A candidate applying to a requisition; the recruiting pipeline record.
- Job requisitions
- Approved positions opened to recruiting.
- Offers
- Offer letter, approval chain and e-signature state.
Who uses it
Permissions- Recruiter
- Manages the hiring pipeline.
- Hiring Manager
- Views applications and interviews.
- HR Business Partner
- Manages employee history.
- Admin
- Controls 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.