From requisition to first day, on one record.
From requisition to first day on one record — so nobody re-types a new joiner into a second system.
The most expensive part of recruitment is not the sourcing. It is the handover: a candidate becomes an employee and someone re-enters their details into a different system, usually incompletely, usually the week payroll closes. PiPO HRIS Recruitment & Onboarding keeps the chain intact — the requisition that authorised the role, the candidate who filled it, and the employee record that results, are the same thread.
The chain, end to end
Each stage writes to the same thread, which is why the employee record on day one is complete rather than a placeholder.
Requisition
- Role, unit and site
- Approval by the structure
- Budget and headcount position
Pipeline
- Applications and screening
- Interview stages and notes
- Candidate communication history
Offer
- Offer approval chain
- Terms recorded against the candidate
- Acceptance captured
Onboarding
- Employee record created from the candidate
- Documents and identifiers collected
- First-day checklist by role
What changes
Common questions
Yes. The employee record is created from the candidate record, so the details collected during hiring are not re-entered.
Yes. The approval chain follows the organisation structure configured in Core HR.
Casual engagement runs through the casual register rather than a full recruitment pipeline, because the process is genuinely different. Both end up on the same platform.
Ready to see Recruitment & Onboarding in action?
Tell us how your workforce operates and we will tailor the conversation around what you actually need to improve.