1. HRMS with Workforce Analytics
  2. Features
  3. Hiring
Feature · Hiring

Hiring

Follow a planned seat through requisition, application, interview and offer.

OverviewOpen requisitions
HRMS with Workforce Analytics · Hiring

Open requisitions

Job requisitions

New
Requisition numberPositionDepartmentLocationHeadcountStatus
JR-79176PST-9624DPR-120LCT-15036Open
JR-16650PST-9979DPR-110LCT-12019Open
JR-35221PST-2807DPR-110LCT-1404Open
JR-85294PST-9670DPR-110LCT-13010Open
JR-73283PST-7867DPR-110LCT-11037Open
6 of 6 records
PST-9624Job requisitions · JR-79176
Open
DepartmentDPR-120
LocationLCT-150
Headcount36
Example screen with sample data

What you can do

Connect hiring activity to the workforce plan

A position states the planned seat and its department, location, job title and headcount. A job requisition refers to that position, hiring manager and recruiter. It also records requested headcount, target start date, salary range and status. Those records give a useful frame for the hiring numbers later discussed in a workforce review.

Recruiter manages candidates, applications, interviews, requisitions and offers. Hiring Manager manages requisitions and interview scorecards, and reads candidate and offer context. A candidate can apply to more than one requisition; the application is the pipeline record for one pairing. Keep the application stage separate from the requisition status and the offer status.

How the work is organized

  • Opening. Link the requisition to the position and hiring owner.
  • Candidate. Use an application to follow the person through screening and interviews.
  • Offer. Record compensation, start date and the offer’s own decision status.

The requisition can move from Draft through pending approval, Approved and Open, then to Filled or another recorded outcome. An application has stages from Applied through interview, offer, hired, rejected or withdrawn. An interview records the scheduled time, interviewer, status, rating, recommendation and feedback. An offer holds the candidate, position, compensation and accepted or rejected outcome.

What to agree during setup

Decide how a requisition’s requested headcount relates to the position’s planned capacity. Establish who may approve an opening or offer, and how compensation outside the pay grade is handled. Agree when an accepted offer becomes an employee record and what evidence confirms the actual start. These choices matter because an accepted offer and a current employee are different facts at different points in time.

Candidate records include contact information and a do-not-contact flag. Respect that flag when planning outreach. If career-site intake, interview calendars or e-sign are needed, connect those systems and decide which one owns each event. The local application, interview and offer records remain the review context for the hiring team.

Check the handoff on an actual case

Take an open requisition for a planned position. Link a candidate application, record the interview recommendation and prepare an offer with the agreed start date. Check the application and offer statuses separately. When the person actually joins, create or update the employee and hire history with the effective date. Then compare the hiring event with the next workforce snapshot. The requisition’s target start date and the employee’s hire date answer different questions.

What your team sees

  • Open requisitions — Open hiring requests with position, department and capacity context.
  • Requisition pipeline — Requests grouped by status and target date.

Follow the work through

Use Employee movement when an accepted hire becomes an effective workforce event.

What it keeps track of

Data model
Positions
Seat-level org entries. A Position is what an Employee fills.
Job requisitions
Approved positions opened to recruiting.
Candidates
Person pool in the ATS - may apply to multiple requisitions.
Applications
A candidate applying to a requisition - the ATS pipeline record.
Interviews
Scheduled interviews against an application with scorecard capture.
Offers
Offer letter, approval chain, and e-sign state.
Employees
The central person record. Every transaction in the suite ties back to Employees.
Employment history
Every lifecycle event: hire, promotion, transfer, comp change, manager change, leave-of-absence, termination.

Who uses it

Permissions
Recruiter
Manages the pipeline.
Hiring Manager
Owns the requisition and interview context.
HR Business Partner
(HRBP) maintains the resulting employee and position records.

Set up HRMS with Workforce Analytics your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started