See what's new

Testlify
HR & recruitment
Last updated on: 10 August 202612 min read

Job Requisition: Definition, Process, and How to Write One

Job Requisition: Definition, Process, and How to Write One

A job requisition outlines the need for a new hire. Learn how to write an effective one to attract top talent by clearly defining role requirements and expectations.

Hiring starts long before a job is posted. It begins with a job requisition, an internal request that justifies the need for a new hire, secures approvals, and aligns hiring managers, HR, and finance before recruitment begins.

A well-written job requisition helps organizations hire faster, avoid miscommunication, and ensure every open role has a clear business purpose. In this guide, you’ll learn what a job requisition is, what it includes, how the approval process works, and best practices for writing one effectively.

Summarise this post with:ChatGPTGeminiClaudeGrokPerplexity

TL;DR

  • A job requisition is the internal, approved request to fill a role. It comes before the job description and the public job posting.
  • Its job is to align the hiring manager, HR, and finance on the role, the budget, and the reason for the hire.
  • A good one names the role, the must-have skills, the salary range, the reporting line, and the business case in plain language.
  • The fastest way to weaken one: vague titles, a wish-list of requirements, and no business justification.
  • Decide how you will measure each skill (a short assessment, for example) while you write the requisition, not after the offer.
Build your dream team — Book a product demo

What is a job requisition?

A job requisition is an internal document that formally requests approval to hire for a new or existing position. It marks the official start of the hiring process by explaining why the role is needed, confirming budget availability, and documenting key details such as the job title, department, reporting manager, employment type, salary range, and required qualifications.

Unlike a job posting, which is written to attract candidates, a job requisition is created for internal stakeholders, including hiring managers, HR, finance, and leadership. It ensures everyone agrees that the position should be filled before recruiters begin sourcing candidates or advertising the role.

Job requisition vs job posting vs job description

Although these terms are often used interchangeably, they serve different purposes in the hiring process. A job requisition is an internal document used to request approval to hire, a job description defines the responsibilities and qualifications for the role, and a job postingis the external advertisement used to attract candidates.

The three documents are closely connected but are created at different stages of recruitment. A job requisition comes first. Once it’s approved, HR uses the information to prepare or update the job description, which is then adapted into a job posting for candidates.

Aspect

Job Requisition

Job Description

Job Posting

Purpose

Requests approval to fill a position

Defines the role, responsibilities, and qualifications

Promotes the vacancy to attract candidates

Primary audience

Hiring managers, HR, finance, leadership

HR, hiring managers, employees, candidates

Job seekers

Created by

Hiring manager with HR support

HR and hiring manager

HR or recruiter

Includes

Business justification, budget, headcount, approvals, hiring timeline

Job duties, required skills, qualifications, reporting structure, working conditions

Job summary, benefits, location, salary (if shared), application instructions

Used when

Before recruitment begins

After the role is approved

Once the vacancy is ready to be advertised

Visibility

Internal

Internal and external

External

How they work together

Think of these documents as three stages of the same hiring workflow:

  1. Job requisition: Confirms that the organization needs to hire and secures the necessary approvals.
  2. Job description: Defines what the employee will do and the qualifications required to succeed in the role.
  3. Job posting: Uses information from the job description to create a candidate-friendly advertisement that encourages qualified applicants to apply.

Without an approved job requisition, organizations risk hiring without budget approval or business justification. Without an accurate job description, recruiters may attract the wrong candidates. And without a well-written job posting, even qualified candidates may overlook the opportunity.

If you want to go deeper on the next step, our job description templates pick up where the requisition leaves off.

What should a job requisition include?

A job requisition should include everything an approver needs to say yes quickly and everything a recruiter needs to start work. That means the role, the money, the reason, and the skills, stated plainly. If an approver has to ask a follow-up question, the requisition is missing something.

  • Job title: clear and searchable, the way candidates would actually type it.
  • Department and reporting line: where the role sits and who it answers to.
  • Job summary: two or three sentences on what the role is for.
  • Must-have vs nice-to-have skills: separate the two on purpose.
  • Salary range: a real band, based on market data and internal equity.
  • Business justification: why this role, why now.
  • Budget status: confirmation the money exists.
  • Hiring manager and a target start date.
  • How success is measured: the KPIs the role will own in its first year.

Why does a job requisition matter?

A job requisition matters because it is the cheapest point in the whole hiring process to prevent a bad hire. It forces alignment on budget and need before money is spent, and it sets the criteria by which every later stage is judged on. Skip it, and you are hiring on an opinion.

The cost math is blunt. Gallup estimates that replacing one employee costs from one-half to two times their annual salary, and that voluntary turnover costs US businesses about $1 trillion a year. A requisition that nails the role and the must-have skills is the first guard against joining that number.

Pro tip: Write the business case as if you are defending the headcount to your CFO, because you usually are. One sentence on the revenue, cost, or risk this role addresses moves approvals faster than a long duty list.

A sharp requisition also feeds a cleaner downstream process. See how it connects to the rest of the workflow in our guide to managing the hiring process.

How do you write a good job requisition?

How do you write a good job requisition?

A well-written job requisition helps hiring managers, HR, and finance align on why a role is needed before recruitment begins. It should clearly explain the business need, define the position, and provide enough information for recruiters to source the right candidates without repeated clarification.

Follow these best practices when creating a job requisition.

1. Define the hiring need

Start by explaining why the position needs to be filled. Is it replacing an employee who left, supporting business growth, or adding capacity for a new project? A clear business justification helps approvers understand the value of the hire and reduces delays during the approval process.

2. Confirm budget and headcount approval

Before preparing the requisition, verify that funding for the role has been approved. Include the salary range, employment type, and headcount status so finance and leadership can review the request without additional follow-ups.

3. Use an accurate job title

Choose a job title that reflects industry standards and matches the terms candidates commonly search for. Avoid internal titles or creative names that may confuse recruiters or applicants. A clear title also improves the visibility of future job postings.

4. Clearly define the role

Summarize the purpose of the position and outline the key responsibilities. Include reporting relationships, work location, employment type, and any information that helps recruiters and hiring managers understand what success looks like in the role.

5. Separate required and preferred qualifications

Distinguish between qualifications that are essential for performing the job and those that are simply desirable. Listing every skill as mandatory can unnecessarily reduce the candidate pool and make the hiring process less inclusive.

6. Include realistic hiring requirements

Review the education, experience, certifications, and technical skills to ensure they reflect the actual needs of the role. Outdated or unrealistic requirements can slow hiring and discourage qualified candidates from applying.

7. Define how candidates will be evaluated

Identify the competencies that matter most and decide how they will be assessed. For example, technical skills may be evaluated through skills assessments, while communication and problem-solving can be measured through structured interview questions. Establishing evaluation criteria before recruitment begins creates a more consistent and objective hiring process.

8. Review the requisition before submitting it

Have HR or another stakeholder review the requisition for clarity, accuracy, and completeness. A final review helps identify missing information, inconsistent requirements, or approval gaps before the requisition enters the hiring workflow.

Best practices for writing a job requisition

  • Keep role requirements specific and relevant to the position.
  • Use clear, consistent language that all stakeholders can understand.
  • Align responsibilities, qualifications, and salary with current business needs.
  • Involve hiring managers, HR, and finance early in the process.
  • Review and update requisition templates regularly to reflect changes in the organization or labor market.

A job requisition is more than an approval form—it establishes the foundation for the entire hiring process. Taking the time to define the role accurately, secure stakeholder alignment, and establish objective hiring criteria helps recruiters move faster and improves the quality of hiring decisions.

Job requisition template

Use this as a starting structure. Fill the middle column for your role and keep the examples as a guide for the level of detail that gets a fast yes.

Field

What to Include

Example

Job title

Clear, searchable title for the position

Senior Backend Engineer

Department

Business unit or team where the role belongs

Engineering

Employment type

Full-time, part-time, contract, temporary, or internship

Full-time

Location

Work location or remote/hybrid arrangement

Bengaluru (Hybrid)

Reports to

Hiring manager or reporting manager

Engineering Manager

Job summary

Brief overview of the role’s purpose and responsibilities

Build and maintain scalable payment services for a growing SaaS platform.

Key responsibilities

Primary duties the employee will perform

Develop APIs, optimize system performance, mentor junior engineers

Required qualifications

Essential education, certifications, or experience

Bachelor’s degree and 5+ years of backend development experience

Required skills

Must-have technical and soft skills

Python, SQL, distributed systems, problem-solving

Preferred skills

Skills that are beneficial but not mandatory

AWS, Kafka, fintech experience

Salary range

Approved compensation range for the role

₹25–30 LPA

Business justification

Why the role is needed and the business impact

Support product expansion and reduce engineering backlog

Budget approval

Confirmation that funding and headcount have been approved

Approved in FY2026 hiring plan

Target start date

Expected joining or hiring date

Within 8 weeks

Approvers

Stakeholders who must approve the requisition

Hiring Manager, HR Business Partner, Finance Director

What mistakes should you avoid in a job requisition?

The common mistakes all share one root: skipping a decision and hoping a later stage will fix it. It rarely does. Here are the ones that cause the most damage.

  • Vague job titles that no candidate would search for, so the right people never see the role.
  • Requirement wish-lists that mark every skill essential and deter strong, partly-qualified applicants.
  • No business case, which leaves the requisition stuck in approval limbo.
  • Copy-pasting an old req without checking the salary, skills, or reporting line are still current.
  • No salary range, which slows approval and, in many regions, breaks pay-transparency rules.
  • Listing skills you never plan to test, so the bar you set on paper never gets checked in practice.

Key takeaway: A requisition is a set of decisions, not a form. The teams that hire well make the budget, skills, and measurement calls here, where changing your mind is free.

How does technology help manage job requisitions?

Technology helps by turning the requisition from a one-off document into a tracked, repeatable workflow. An applicant tracking system stores every requisition in one place, routes approvals automatically, and reports on how long each stage takes, so bottlenecks stop hiding.

Adoption is climbing fast. The CIPD’s 2024 Resourcing and Talent Planning research found 78% of organisations increased their use of recruitment and onboarding technology over the previous year, and 31% of those now use some form of AI or machine learning, up from 16% in 2022.

  • Centralized records: every requisition and its approval trail in one searchable place.
  • Automated approvals: routing and reminders so nothing sits in an inbox for a week.
  • Analytics: data on volume, time-to-approve, and source quality to improve the next cycle.

Where Testlify fits is the skills column of your requisition: once you have named the must-have skills, you can attach a short, role-specific assessment so the criteria you set are tested, not assumed.

Turn your next requisition into a faster hire

Your next strong hire starts with the decisions you make in the requisition. Name the must-have skills, then prove them. Testlify lets you attach a role-specific skills assessment to the criteria you just defined, so the shortlist is scored before the first call. Start free, or book a demo to see it on your own roles.

Frequently asked questions

Yashika Khandelwal
Yashika Khandelwal

Content Writer

Yashika Khandelwal is a Content Writer with 3+ years of experience creating research-backed content on hiring, talent assessment, and HR technology. She is a registered Organizational Psychologist and subject matter expert who combines behavioral science with practical recruitment insights to produce accurate, evidence-based content.

LinkedIn

Get started.

Hire on proof, not resumes.

Run your first skills-based assessment free — no credit card required.

We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking "Accept All", you consent to our use of cookies.