Job Requisition

A job requisition — often called a req — is the formal document or workflow that authorizes a company to recruit for a specific position. It captures the role title, department, reporting structure, budgeted compensation range, target start date, and the business justification for the hire. Before a recruiter posts a job or contacts a single candidate, the requisition must exist and, in most organizations, must carry approval signatures from the hiring manager, finance, and HR. The requisition serves as the single source of truth throughout the hiring cycle: it defines the scope of the search, establishes the approved headcount, and provides the data anchor for tracking recruiting metrics from time-to-open through offer acceptance.

Why it matters for recruiting and HR teams

Without a structured requisition process, recruiting operates on informal requests that are easy to misinterpret and hard to audit. A missing or incomplete req creates downstream problems: recruiters start searches for roles that haven't received budget sign-off, compensation bands shift mid-process when finance later weighs in, and headcount plans drift out of sync with actuals. For HR teams, every approved requisition is a documented commitment — it connects workforce planning forecasts to real hiring activity and gives people analytics teams the clean data they need to report on hiring velocity, recruiter capacity, and cost-per-hire. For growing companies where headcount is tightly controlled, the requisition is the enforcement mechanism that keeps hiring aligned with the plan.

How it works

1. Hiring manager submits a requisition form — either directly in the ATS or via an integrated HRIS — specifying the role, level, business justification, and target start date.
2. The req routes through a configured approval chain, typically hitting the hiring manager's direct leader, a finance or budget owner, and an HR business partner.
3. Once all approvals are collected, the requisition status changes to 'open' and the ATS automatically creates the job record recruiters will work from.
4. Recruiters attach candidates, track pipeline stages, and log activity against the req ID throughout the search.
5. At offer acceptance and hire, the req is marked filled; if the candidate falls off, it reverts to active so recruiting can continue without opening a duplicate record.
6. Filled reqs feed headcount reporting — confirming that actuals match the approved plan and closing the loop with finance.

How ATS software supports Job Requisition

Modern ATS platforms embed requisition management directly into the hiring workflow so approvals, job creation, and pipeline tracking all live in one system. Recruiters no longer chase email chains for sign-offs; hiring managers submit and approve through the same interface they use to review candidates. This integration eliminates the common problem of reqs being approved in a spreadsheet but never formally opened in the system, which creates gaps in headcount reporting and recruiter workload data.

• Configurable approval workflows — route reqs through multi-step chains with role-based approvers and automatic escalation on delays
• Requisition templates — pre-populate standard fields for common roles to reduce submission time and enforce consistent data entry
• HRIS headcount sync — automatically reconcile approved reqs against open headcount in the HR system to prevent over-hiring
• Compensation range guardrails — attach approved pay bands to the req so all stakeholders see the same range before sourcing begins
• Req-level analytics — track time-to-approve, time-to-fill, and recruiter load at the individual requisition level
• Audit trail — capture every status change and approval action with timestamps for compliance and process review

Related terms

• ATS (Applicant Tracking System) — the software platform that houses job requisitions, candidate records, and hiring workflows end to end
• Headcount Planning — the process of forecasting how many roles a company needs to hire into over a planning period, which feeds the requisition queue
• Candidate Stage — the defined steps a candidate moves through within a requisition, from application to hired or rejected
• Job Architecture — the framework that defines job families, levels, and titles, providing the taxonomy reqs are written against
• Offer Management — the downstream process of generating, approving, and delivering compensation offers once a requisition reaches finalist stage