Job Requisition

A complete req contains the job title, department and reporting line, whether the position is new headcount or a backfill, the approved salary range and compensation band, the target start date, a brief business justification, and the key qualifications required. Some organizations also include the preferred sourcing channels and whether an agency may be engaged. The salary range and business justification fields are the most commonly skipped — their absence consistently causes downstream delays when finance or HR needs to reconcile the hire against budgeted headcount, particularly in organizations with strict headcount controls.

Time to Fill is conventionally measured from the moment the req is opened, but the approval process before opening — the pre-req stage — often adds days or weeks that are invisible in the metric. A req that requires three levels of approval and sits in an inbox for five days at each level adds fifteen days of delay before the recruiter has even begun sourcing. Mapping and shortening the approval workflow, setting SLAs for each approver, and routing via automated workflow tools (rather than email chains) are structural interventions that reduce this invisible pre-clock latency and improve perceived recruiting speed.

A job requisition is an internal control document — it is about whether the organization is authorized and budgeted to hire. A job description is a candidate-facing communication document — it describes what the role does and what qualifications are sought. The req typically precedes and informs the job description: once a req is approved, the recruiter works with the hiring manager to translate the req's requirements into a published job description. Treating these as the same document is a common source of confusion that leads to job postings that are internally inconsistent with approved role parameters.

A job requisition is the formal internal request to open a role, and it is the document that authorizes recruiting to begin. Beyond the job title, it typically records the department and reporting line, the reason for the opening — growth, backfill or replacement — the budgeted salary range, the employment type, and the target start date. It also names the hiring manager and the approvers.

Because it is an internal control document rather than a public advert, the requisition carries details a job posting never shows: headcount budget, cost center, and business justification. It is the point where finance, the hiring manager and recruiting agree that a role should exist before any money is spent attracting candidates.

Most organizations route a requisition through an approval chain before sourcing starts — commonly the hiring manager to a department head to finance or HR. Each approver confirms a different thing: that the role is genuinely needed, that it fits the plan, and that the budget exists. Only once fully approved does the requisition become an active, fillable role.

This gate exists to prevent uncontrolled or unfunded hiring, but it is also a frequent source of delay. Requisitions that sit waiting for sign-off inflate time-to-fill before recruiting has even begun, which is why streamlining approvals inside an ATS — with clear owners and automatic reminders — is a common efficiency win.

The requisition is the anchor that everything downstream references. Reporting counts open, filled and aging requisitions to understand hiring load; the job posting is derived from it; and the pipeline of candidates is attached to it. A unique requisition ID lets a team track a single role from approval to hire across systems.

Because it links budget, ownership and outcome, the requisition is also where accountability lives. If a role stalls, the requisition record shows who approved it, when, and where it is stuck — turning hiring from a set of informal requests into a managed, auditable process.

Vague or rushed requisitions cause problems that surface much later. If the role, level and must-have criteria are not agreed at requisition time, recruiters source against a moving target and shortlists get rejected for reasons never written down, wasting weeks. Opening a requisition before the budget or the true need is confirmed leads to cancelled searches that damage credibility.

Poor hygiene is the other issue: stale requisitions left open after a hire, or duplicate requisitions for the same role, corrupt reporting and make hiring load impossible to read. Treating the requisition as a disciplined, well-defined starting point prevents most of these downstream headaches.

The requisition is the governance gate where finance and leadership confirm a role is budgeted and justified before recruiting spends any effort, tying every hire back to approved headcount and cost rather than to informal manager requests.

This control prevents unbudgeted or duplicate hiring and creates an auditable record of why, when, and at what level each role was opened, information that is essential for cost discipline and for honest workforce planning later.