Job Requisition Guide: Draft, Approve, and Fill the Role
A job requisition is the internal green light for a hire.
It records why a role is needed, what the job involves, which qualifications matter, and what the pay range will be, then routes that request to the people who can approve headcount and budget. This guide walks through drafting one, getting it signed off, publishing the opening, and managing candidates against it. It also separates a requisition from the two documents it is most often confused with: the job description and the job order.
What a job requisition is
A department raises a job requisition when it wants management to approve filling a position. The document is formal and internal: it exists so that hiring decisions are made with the role's purpose, cost, and requirements in view rather than on an informal request.
At minimum, a requisition carries the job title, the responsibilities, the qualifications the role requires, and the salary range. Those details let approvers check the hire against the organization's strategy and budget before any recruiting spend begins.
Recruiters sit in the middle of this exchange. They work with the hiring manager to turn a business need into a written request that approvers can evaluate, and they later use the approved document as the reference point for sourcing and screening.
Which fields belong in a requisition
A useful way to draft the document is to sort its fields by who will read them. Approvers need the business case and the money. Recruiters need the screening criteria. Candidates eventually see a public version of the role, but not the internal approval trail.
- Approval fields: requesting department, hiring manager, headcount status (new role or replacement), budget line, and the sign-off chain.
- Role fields: job title, core responsibilities, required qualifications, and salary range.
- Screening fields: the must-have qualifications that will be used to filter applicants, kept separate from nice-to-haves.
- Public fields: the parts that will be rewritten into the job description, such as duties, growth opportunities, and benefits.
Keeping these groups distinct prevents a common problem: approval details leaking into the public posting, or screening criteria being left vague because nobody wrote them down at the requisition stage.
How to create a job requisition
The drafting work falls into three moves.
- Establish the hiring need. Decide whether the role is new or a replacement for someone leaving, and research what the job actually requires. The answer changes the justification approvers will read.
- Work with the hiring manager. The manager holds the context on the team's workload, the skills gap, and how the role fits the group. A requisition written without that input tends to list generic duties that do not match the team.
- Write the role description. Set out the responsibilities plainly and state the must-haves separately from the nice-to-haves. This description becomes the first filter once applications arrive, so vague wording costs screening time later.
Moving the requisition through approval
Approval usually runs in three stages.
Internal review and validation. The requisition is checked against organizational goals, the recruitment budget, and the overall hiring plan. Expect at least one round of feedback before it moves on.
Sign-off from the right people. Depending on the organization, this can involve stakeholders, finance, HR, and department managers. The case is stronger when it explains why the position matters to the organization's results, not just why the team is busy.
Compliance check. Equal employment opportunity rules, non-discrimination policies, and other applicable regulations shape what the requisition and the eventual posting may say. Getting this right protects the organization and keeps the process fair.
Promoting an approved requisition
Once approved, the opening needs an audience. Start inside: intranets, internal newsletters, and employee referral schemes reach people who already know the organization. Then go external through relevant job boards, social platforms, and the careers page.
Channel choice should follow the role. Professional networks and industry events suit specialist hiring; niche platforms can reach skills that general boards miss. Wherever the posting appears, the message should carry the organization's own character, its benefits, and what makes the role worth taking, because a generic listing competes poorly for attention.
Managing the requisition once applications arrive
An approved requisition becomes a working document. Three activities keep it useful.
Track applicants. An applicant tracking system holds applications in one place, so progress, resumes, and notes stay attached to the right role instead of scattered across inboxes.
Shortlist against the requisition. Compare each candidate with the qualifications written into the document. That is the point of having recorded them: it makes the shortlist defensible and consistent.
Coordinate the interviews. Assessments and interview stages need scheduling and communication from first contact to final decision. Smooth coordination is often what separates a candidate who accepts an offer from one who takes a competing one.
Requisition, job description, and job order: how they differ
These three documents are easy to mix up because they describe the same role at different stages.
The requisition comes first and is internal. The job description is public and usually draws on the requisition's details. The job order is the recruitment team's instruction to start work, and it typically carries the skills and qualifications the team will screen against throughout the search.
Worked example: a replacement role
Suppose a support team loses a senior agent. The hiring manager raises a requisition marked as a replacement rather than new headcount. The document lists the title, the responsibilities the team actually covers, the qualifications the role requires, and the salary range already budgeted for the position.
During internal review, finance confirms the budget line and HR checks the wording against non-discrimination policy. Once approved, the recruiter writes a public job description from the requisition's role fields, posts it internally first, then externally. Applications land in the applicant tracking system, where the recruiter shortlists against the must-have qualifications recorded at the start. Interviews are scheduled from that shortlist.
The example shows why the requisition matters beyond paperwork: every later step, from the posting's wording to the shortlist criteria, traces back to what was approved.
Telling failures apart
Requisitions stall for different reasons, and the fix depends on which one applies.
- Rejected at review: the business case or budget did not hold up. The remedy is a stronger justification or a revised scope, not more sourcing.
- Approved but stuck in sourcing: the posting is not reaching the right people. Revisit channels and the public description.
- Approved and sourcing well, but shortlists are weak: the must-have qualifications may be unrealistic or the screening criteria unclear. Revisit the requisition's role fields.
- Approved and shortlisted, but offers are declined: the problem is likely in coordination, timing, or the offer itself, not in the requisition.
Naming the stage correctly stops teams from rewriting documents when the real issue sits further down the pipeline.
| Document | Audience | Purpose |
|---|---|---|
| Job requisition | Internal approvers | Request permission and budget to hire |
| Job description | External candidates | Attract suitable applicants with duties and qualifications |
| Job order | Recruitment team | Directive to begin sourcing once the requisition is approved |
Frequently asked questions
What is the purpose of a job requisition?
It is the formal request for approval to hire for a specific position. As a written record, it sets out why the role is needed, what the position involves, which qualifications are wanted, and the expected salary range, so the hire can be checked against the organization's strategy and budget.
Who typically fills out a job requisition?
The hiring manager usually starts it, and higher-level managers or executives review and approve it. HR may also be involved, and many organizations use a standard requisition template to keep the fields consistent.
How does a job requisition differ from a job description?
The requisition is internal and exists to obtain approval for hiring. The job description is public and aimed at candidates, describing the role, duties, and qualifications to attract applicants. The description is often built from details already recorded in the requisition.
What is the difference between a job order and a job requisition?
The requisition documents the need for a new hire. The job order is the instruction that tells the recruitment team to begin the search, and it is issued once the requisition has been approved. Job orders usually carry the detailed skills and qualifications the team will refer to during recruitment.
What should a job requisition include?
At minimum: job title, responsibilities, required qualifications, and salary range. Add the requesting department, hiring manager, whether the role is new or a replacement, and the approval chain. Keep must-have qualifications separate from nice-to-haves so screening stays consistent.