Separate workflows for new headcount and replacement hires
Requisitions, candidates and interview feedback in one pipeline, with a distinct path for replacement hiring because backfilling a leaver is not the same process as adding headcount.
Recruitment
Sample viewRequisition raised
Replacement for a resigning employee
Candidates in pipeline
Four at offer stage
Offer accepted
Handed to onboarding
Configured to your policies and entities, running on the same employee record as every other module.
Separate workflows for new headcount and replacement hires
Approval chain before a role is opened to the market
Stage-wise pipeline with interview scheduling and feedback
Offer generation that hands straight over to onboarding
Hiring managers raise requisitions, finance approves the headcount, recruiters run the pipeline, and interviewers leave structured feedback.
Requisition approvals over email and candidate tracking in a shared sheet.
Recruitment shares the employee record with Onboarding,
A backfill is linked to the employee being replaced and to their exit date, so the approval path, budget check and target joining date all follow from the vacancy rather than from a new-headcount business case.
Yes. Accepting an offer triggers onboarding and creates the employee record from the candidate data already captured, so nothing is re-typed.
Continue through the platform