What Is a Job Requisition? Definition, Process, and Template

Job Requisition: Core Definition

A job requisition - often called a "job req" - is a formal request from a hiring manager or business unit to fill a position. It documents the business justification for the hire, the details of the role, the budget required, and the desired timeline. Once the requisition is approved by the relevant authorities (typically HR, finance, and senior leadership), recruiting can begin.

The requisition serves several purposes simultaneously. It is a control mechanism, ensuring that headcount and compensation decisions are made deliberately and within approved budgets. It is a communication tool, ensuring that HR and recruiters understand exactly what the hiring manager needs before the search begins. And it is a compliance record, creating an auditable trail of hiring decisions that is important for internal governance, DEI reporting, and in some jurisdictions, legal compliance.

Every hire should be initiated by a requisition. In small organizations this may be an informal process - a brief email or a field in your ATS. In larger organizations, requisitions flow through multi-stage approval workflows in an HRIS or ERP system. The principle is the same regardless of scale: the need to hire should be documented and approved before resources are spent on recruiting.

Job Requisition vs. Job Description

These two documents are related but serve different purposes, and the distinction matters.

A job requisition is an internal document. It is addressed to the approvers who need to authorize the hire - HR leadership, finance, senior management. Its purpose is to justify the need for the position and document the business case. It contains information like the headcount number, the budget impact, the reporting structure, and the urgency of the hire. It is not shown to candidates.

A job description is a public-facing document. It describes the role, responsibilities, requirements, and working conditions to potential candidates. It is written in language designed to attract qualified applicants and serves as the foundation for a job posting. A well-written job description is adapted from the requisition but rewritten from the candidate's perspective.

In practice, many organizations conflate the two - using a single document that contains both the internal justification information and the candidate-facing role description. This works for small organizations but creates problems as you scale: the business justification and budget information in a requisition should not be shared externally, and the formal approval workflow that applies to a requisition does not apply to the process of refining a job posting for external audiences.

What a Complete Job Requisition Form Includes

A well-designed requisition form captures all the information needed to approve the hire, brief the recruiter, and open the role in your ATS. The key sections are:

Administrative Information

• Requisition number - A unique identifier for tracking and reference
• Date submitted - When the requisition was initiated
• Requesting manager - The hiring manager's name, title, and department
• Department and cost center - For budget allocation and reporting
• Location - Office location, remote, or hybrid arrangement

Position Details

• Job title - The official title the role will carry in the HRIS
• Job level / grade - Where the role sits in the organization's level framework
• Employment type - Full-time, part-time, contract, temporary, or intern
• Reporting manager - Who the new hire will report to (may differ from the hiring manager who submitted the req)
• Team and peers - A brief description of the team the new hire will join

Business Justification

This section is the heart of the requisition. Approvers need to understand why this hire is necessary. Common justification types:

• Backfill - Replacing an employee who left. Include the name of the departing employee and their last day. Note whether the role is being modified or filled exactly as before.
• New headcount - A net new position. Requires the strongest justification: what business need does this role address? What workload or capability gap exists? What is the business impact of not filling it?
• Conversion - Converting a contractor or temporary employee to a permanent role. Explain the rationale for conversion.
• Restructure - A role created as part of an organizational restructure. Reference the restructure plan and approval.

Compensation and Budget

• Salary range - The approved compensation band for the role, based on internal grading and market data
• Total compensation estimate - Including benefits, bonus targets, and equity if applicable
• Annual budget impact - The fully loaded cost of the position on an annualized basis, prorated to the remaining fiscal year if the hire will happen mid-year
• Budget status - Whether the role is within existing approved headcount budget or requires a budget exception approval

Requirements and Timeline

• Required skills and qualifications - The must-haves for the role, distinct from nice-to-haves
• Preferred skills - Differentiating qualifications that would strengthen a candidate's profile
• Target start date - When the hiring manager needs the role filled
• Interview panel - Proposed interviewers who need to be available and briefed
• Any special requirements - Background check level, security clearance, travel expectations, language requirements

The Requisition Approval Workflow

Once a hiring manager submits a requisition, it typically moves through an approval chain before recruiting can begin. The structure of this chain varies by organization, but a well-designed workflow balances control with speed. Common approval stages:

Hiring Manager's Direct Leader

The first level of approval is usually the hiring manager's direct supervisor or department head. This ensures alignment within the business unit: the leader confirms that the hire is consistent with team strategy and that the timing and level are correct. This approval should be routine and fast for backfills in established roles - no more than 24-48 hours. For net new headcount, the business unit leader review may involve more deliberation.

HR Business Partner

The HR business partner review ensures that the role is properly leveled, that the compensation range is within the approved band for the grade, and that the role does not duplicate existing capacity elsewhere in the organization. HR may also flag whether an internal transfer or promotion should be considered before opening an external search. This review stage also formally opens the requisition in the ATS, enabling recruiting to start the moment financial approval is received.

Finance Approval

For net new headcount, or any backfill that is being leveled up from the original position, finance approval confirms that the budget exists. Finance may approve against an annual headcount plan, or for smaller organizations, a finance partner may review each requisition individually. The key information finance needs is the total annualized cost, the cost center, and whether the role is within approved plan or requires a plan amendment.

Senior Leadership

Many organizations require C-suite or VP-level approval for roles above a certain salary threshold or seniority level. This final tier adds oversight for the highest-impact hiring decisions without creating a bottleneck on everyday operational hiring. A common threshold is any role at Director level and above, or any role with a total compensation above a defined budget threshold.

Common Requisition Process Problems and How to Fix Them

Approvals That Take Too Long

The most common complaint about requisition processes is speed. When a key employee resigns on a Friday and the team needs a replacement, a two-week approval cycle before recruiting can begin is a genuine business cost. The root cause is usually one of three things: too many approval layers for routine hires, approvers who are not clear on their expected response time, or a manual process (email, paper forms) that does not create urgency or visibility.

The fix is to tier your approval process. Backfills for pre-approved headcount at existing salary bands should have a streamlined one or two-step approval with a 48-hour target. Net new headcount and senior roles warrant a fuller multi-step process. Document the expected turnaround at each approval stage and track compliance. Most organizations that measure approval cycle time and report it to senior leaders see it improve significantly within a quarter.

Requisitions That Are Incomplete

Recruiters cannot begin an effective search if the requisition does not contain clear requirements, an approved compensation range, and a realistic target start date. A well-designed requisition form with required fields prevents incomplete submissions from reaching the approval stage - but only if the form design is enforced. Allowing free-text justification fields with no minimum required content is a frequent source of vague requisitions that generate back-and-forth between recruiting and the hiring manager before the search can begin in earnest.

Scope Changes After Approval

A requisition that is approved for a senior engineer hire should not become a principal engineer hire mid-search without going through an amended approval process. Scope creep - the hiring manager deciding partway through the search that they actually want a more senior person, or a different function, or a different location - is common and undermines the integrity of the approval process. Building a lightweight amendment workflow for material scope changes prevents the requisition from becoming irrelevant to the actual hire being made.

A Simple Job Requisition Template

Below is a practical template suitable for most organizations. Adapt the approval chain to your structure and add or remove fields based on what is genuinely useful for your approval decision-makers.

When Requisitions Are Not Used and Why That Is a Problem

Some organizations - particularly smaller ones - hire without a formal requisition process. Managers identify a need, email HR, and recruiting begins. This works at very small scale but creates serious problems as the organization grows.

Without requisitions, headcount and compensation decisions are made inconsistently and often without adequate business justification. Finance has no reliable mechanism for tracking hiring against budget. DEI initiatives cannot be embedded in the process because there is no process to embed them in. Compliance documentation for regulated industries is missing. And when the organization needs to reduce headcount, the absence of documented business cases for each role makes the process harder and more legally exposed.

A lightweight requisition process - even just a simple form that captures the essentials and routes to one or two approvers - is worth implementing well before the formal HRIS workflows become necessary. Building the habit of documented, approved hiring is much easier when the organization is small than after years of informal practice.

Conclusion

A job requisition is the starting point of every hire and the foundation of an organized, accountable recruiting function. Well-designed requisitions ensure that every hire is justified, budgeted, and aligned with business priorities before a recruiter invests time in the search. They create the audit trail that compliance and finance require, and they give recruiters the clear brief they need to run an effective search. Invest time in designing a requisition process that balances thoroughness with speed - the quality of information flowing into your recruiting process will determine the quality of the hires that flow out of it.