Ninjahire LogoNinjahire
Recruitment Operations

What Is a Job Requisition?

A job requisition is the official starting gun for a hire. Before sourcing begins, before a job is posted, the req needs to be approved — confirming the headcount, the budget, and the business justification. Unclear or slow req processes are a hidden driver of time-to-fill.

3 min read·Updated 2026-11-01

What a Job Requisition Includes

  • Role details — job title, department, reporting line, employment type (full-time, contract, part-time)
  • Business justification — why is this headcount needed? New role, backfill, expansion? This is what finance and HR approval often scrutinises.
  • Compensation range — approved salary band, bonus structure if applicable
  • Target start date — when the role needs to be filled. Drives urgency in the recruiting process.
  • Location and work arrangement — remote, hybrid, or on-site; specific office location if applicable
  • Approval chain — who needs to sign off before recruiting can begin (usually hiring manager, department head, HR, and sometimes Finance for budget confirmation)

Job Requisition vs. Job Description

A job requisition is an internal document — it's a business approval to hire. A job description is an external document — it describes the role to candidates and is used for sourcing and screening.

The req feeds the job description: the approved title, compensation band, and requirements become the foundation for the posting. But they serve different audiences. A req might include internal headcount justification and budget details that never appear in the external job description.

How the Req Process Affects Time-to-Fill

Organisations where req approval takes more than a week before sourcing begins are building a structural delay into every hire. This is often invisible in time-to-fill reporting if the clock starts at req approval rather than req submission.

Improving the req process is one of the highest-ROI improvements a TA team can make: a faster approval cycle means recruiting starts earlier, roles are posted earlier, and competitive timelines are protected. Automated req routing — where the system tracks approvals and sends reminders to approvers who haven't responded — reduces approval lag without requiring manual follow-up.

From Requisition to Intake Meeting

Once a req is approved, the first step in most structured recruiting processes is an intake meeting between the recruiter and the hiring manager — a conversation to translate the approved req into a practical sourcing and screening strategy.

The intake meeting converts the req's business information (title, budget, start date) into operational recruiting information: what does a qualified candidate actually look like? What's the hiring manager's real priority — speed, fit, or specific skills? What's the interview process, and who needs to be involved?

Skipping the intake meeting — going straight from approved req to job posting — is one of the most common sources of wasted sourcing effort. When the recruiter's mental model of the role doesn't match the hiring manager's, entire candidate pipelines get rejected at the first review. The intake meeting prevents this.

AI tools are beginning to support req-to-intake workflows: some platforms can parse the req document, generate a draft intake question set, and flag requirements that are likely to create sourcing challenges (unusual skill combinations, below-market compensation bands, overly restrictive experience requirements).

Frequently Asked Questions

Is a job requisition the same as a job opening?▾
Related but technically distinct. A job opening is a vacancy — a role that needs to be filled. A job requisition is the internal document and approval process that authorises the company to recruit for that vacancy. An opening exists when there's a business need; a req is the formal process that validates and funds the hire.
Can recruiting start before a req is approved?▾
Sometimes, informally — recruiters may build candidate pipelines speculatively before formal approval, especially for roles that are frequently needed. But formal ATS tracking and offer extension require an approved req in most organisations. Informal pipeline building reduces time-to-fill once approval comes through.
What causes req approvals to slow down?▾
Three common causes: approval chains with too many required sign-offs for routine hires; approvers who aren't held accountable for turnaround time; and business justifications that require significant documentation for straightforward backfill hires. Streamlining means distinguishing between backfills (fast lane) and new headcount (full approval process).

Try AI Recruiting Free

Source, screen, and book interviews automatically.

Start free trial