What Is a Job Requisition?
A job requisition is the formal, approved internal request to open a role and start recruiting for it. Before a recruiter posts anything to LinkedIn, an ATS, or a career site, a requisition has to exist, be justified, and be signed off. It is the paperwork that turns "we want to hire someone" into "we are legally and financially cleared to hire someone." Skip it and you get duplicate postings, headcount overruns, and finance surprises at quarter end.
This guide covers requisition meaning in plain English, how to define requisition inside your HR workflow, the standard approval process, what belongs on a job requisition template, and how requisitions plug into the wider recruitment process. It also covers the point where most requisitions actually go wrong: the gap between the requisition text and the responsibilities the recruiter ends up screening for.
Table of contents
- Requisition meaning: the plain definition
- What is a job requisition in HR?
- Job requisition vs. job description vs. job posting
- The standard requisition approval process
- Job requisition template: fields to include
- Common failure modes on requisitions
- How requisitions feed the screening layer
- Related posts
- FAQ
Requisition meaning: the plain definition
The plain requisition meaning is: a formal, approved request for something the organisation needs. The word predates HR by a long way. Finance uses purchase requisitions, procurement uses supply requisitions, and hospitals use lab requisitions. All of them are the same pattern: an internal request, run through an approval chain, that authorises a downstream action. If you have ever wondered what does requisition mean or wanted a clean requisition def to share with a stakeholder, that is it.
In HR, requisitioning means opening one of these formal requests to hire. The record itself is the job requisition. Everything downstream, from the job posting to the shortlist to the eventual offer letter, ties back to the requisition number.
The variant spellings you might have searched for ("requistion", "requisitions meaning", "meaning of requisitioning") all refer to the same thing. If a stakeholder asks you to define requisition, the safest one-liner is: an authorised internal request, complete with an approval trail, that lets a downstream team act on it.
What is a job requisition in HR?
A job requisition is the HR-specific version of that pattern: a formal document, usually created inside the ATS or HRIS, that authorises the recruiting team to begin sourcing and screening for a specific role. It records why the role is being opened (backfill after a resignation, net-new headcount tied to a plan), who has approved it, the budget or pay band, the hiring manager, the target start date, and enough detail about the role for a recruiter to write a job posting from it.
The requisition is the source of truth for the role inside the company. Reporting, headcount tracking, and cost analyses all roll up from requisition data. If you have raised a req and later realise the pay band is wrong or the role scope has shifted, you amend the requisition and re-route approvals. You do not just quietly change the job posting.
The Society for Human Resource Management's toolkit on managing recruitment treats requisitions as the point where hiring authority is created; without one, a recruiter has no mandate. That framing matters because it explains why finance and HR both need to sit on the approval chain: the requisition is what commits future salary spend.
Job requisition vs. job description vs. job posting
These three documents get conflated constantly. They are not the same, and they serve different audiences.
| Document | Audience | Purpose |
|---|---|---|
| Job requisition | Internal (HR, hiring manager, finance) | Authorises the role and commits budget |
| Job description | Internal + external | Documents duties, requirements, reporting line |
| Job posting | External (candidates) | Markets the role and drives applications |
The requisition comes first. The job description is drafted against the approved requisition. The job posting is a marketing version of the job description, written for candidates.
The standard requisition approval process
Most companies follow a four-step approval chain, adjusted for size:
- Hiring manager raises the requisition — role details, headcount justification, target start date.
- Department head reviews — confirms the role fits the team's headcount plan.
- HR reviews — checks job title, pay band, level, and market alignment.
- Finance signs off — confirms budget availability and headcount is in the plan.
At larger enterprises this can extend to five or six steps once diversity review, compensation review, and executive sign-off get added for senior roles. The LinkedIn Future of Recruiting research has repeatedly found that the requisition-to-open-role step is where hiring cycle time first starts to slip: approvals sitting in someone's inbox, not sourcing speed.
Two rules keep this workflow honest. First, no sourcing before final approval, even informally, because it creates candidate-experience problems if the role gets denied. Second, any material change to the requisition, especially the pay band or the seniority level, re-triggers approvals.
Job requisition template: fields to include
A clean job requisition template covers three things: what the role is, why it is being opened, and who has approved it. Use this as a starting point and adapt the field set to your HRIS.
| Section | Fields |
|---|---|
| Role identity | Job title, level, department, function, reporting line |
| Employment terms | Full-time / part-time / contract, location, remote policy, target start date |
| Justification | Backfill (whose role) or net-new (linked business case), headcount plan reference |
| Compensation | Pay band, bonus eligibility, equity band, budget code |
| Role requirements | Must-have skills, minimum experience, education if required, key responsibilities |
| Approvals | Hiring manager, department head, HRBP, finance, exec sign-off (if senior) |
| Recruiter assignment | Assigned recruiter, priority level, target close date |
Once these fields are filled in, the requisition becomes the working record for the role for the entire hiring cycle: sourcing metrics, funnel data, and cost-per-hire all report against it.
Common failure modes on requisitions
Three failure patterns show up repeatedly.
Vague requirements. "Strong communication skills, self-starter, 5+ years experience" is not a requisition, it is a wish list. Recruiters cannot screen against it and candidates cannot self-select. Requirements need to be specific enough that two independent recruiters would shortlist roughly the same set of candidates.
Missing must-have vs. nice-to-have separation. When every requirement reads as mandatory, the funnel narrows to almost nobody. When nothing is marked as mandatory, the funnel opens too wide and recruiters spend their week filtering resumes that never should have applied.
Requisition drift. The role scope quietly changes over the hiring cycle, but the requisition is never updated. Six weeks in, the recruiter is screening against a set of requirements that no one signed off on and finance is committed to a pay band that no longer matches.
How requisitions feed the screening layer
The requisition is where the responsibilities that recruiters actually screen against are set. When a recruiter reviews resumes at high volume, they are not comparing them to the job posting: they are comparing them to the requisition. If the requisition is loose, the screen is loose.
Fabric's Interview Engine pulls the responsibilities and eligibility criteria directly from the requisition. It screens resumes against those criteria (budget, location, years of experience, must-have skills), then runs the AI Round 1 conversational interview against role-relevant scenarios (pair programming for engineering, case studies for product, cold-call and cold-email simulations for sales, prompting exercises for non-tech roles). Fabric's eligibility screening is designed to flag mismatches against what the requisition asks for, and surface them to your recruiter. It's a signal for your team to weigh, not an automatic reject. The recruiter or hiring panel still decides who moves forward.
For enterprises where a single requisition might attract several thousand applications, the requisition-to-shortlist gap is where the screening cost lives. Cleaner requisitions produce cleaner Round 1 pools.
Related posts
- The recruitment process, end to end
- What is a job description?
- What is a job applicant?
- Job title vs. job role
- Employee referral program guide
FAQ
What does requisition mean?
A requisition is a formal, approved request for something a business needs, such as a new hire, a piece of equipment, or a budget line. In HR, a job requisition is the formal request to open a role and start recruiting for it.
What is a job requisition in HR?
A job requisition is the internal document that authorises a recruiter to begin sourcing and screening candidates for a specific role. It carries the role details, headcount justification, budget, and approvals.
Who approves a job requisition?
Typically the hiring manager, their department head, HR, and finance. The exact chain depends on the company's approval workflow and whether the role is a backfill or net-new headcount.
What is the difference between a job requisition and a job description?
The requisition is the internal request and approval record. The job description is the outward-facing document describing the role's responsibilities and requirements for candidates.
What is requisitioning?
Requisitioning is the act of raising a formal request through the approval workflow. In hiring, it means opening a job requisition and moving it through the required approvals before any sourcing starts.
What fields belong on a job requisition template?
Job title, department, hiring manager, reporting line, headcount type (backfill or new), budget or pay band, location, employment type, target start date, must-have skills, and the approval trail.