A job requisition is a formal internal document that authorizes a company to open a new or replacement position. To write one, capture the role, business case, budget, location, compensation range, and approval chain in a single submission before any candidate-facing posting goes live. Because the requisition acts as the contract between the hiring manager, HR, FP&A, and leadership, recruiting cannot legally or financially start until it clears sign-off. According to SHRM’s 2025 Recruiting Benchmarking Report, the average cost per hire reached $5,475 for nonexecutive roles and $35,879 for executive roles, with a median time to fill of 44 days. Every dollar and day of that runs through this document. Get it right and the hire moves; get it wrong and it stalls in budget review.
What Is a Job Requisition?
At its simplest, this internal authorization document is what a hiring manager submits to open a position. It is not a job description, not a job posting, and not a candidate-facing artifact. Think of it as a headcount request and a business case rolled into one structured submission. Once it clears approval, the record activates in your applicant tracking system and acts as the green light for sourcing to begin.
While the hiring manager owns the first draft, the requisition itself belongs to the organization. HR business partners review for completeness and workforce-plan alignment; department heads sign off on need; FP&A weighs the cost against headcount plans; and senior leadership approves any new heads or executive additions. By the time a sourcer touches it, the position has cleared four to five sets of eyes.
In brief:
- A job requisition authorizes a hire. It is an internal artifact signed off by HR, FP&A, and leadership before any candidate-facing posting goes live.
- It is not the job description. Requisitions justify the role and lock the cost; job descriptions spell out responsibilities and qualifications.
- 15 fields are standard. Title, department, hiring manager, reason for hire, employment type, location, start date, compensation range, cost code, and the approval chain are all required.
- In 13 states, the comp range is now legally load-bearing. Salary transparency laws mean the pay band you approve internally flows directly to the public posting.
Why does it matter that the requisition is its own artifact? Because the cost of skipping the discipline is high. According to the U.S. Department of Labor, a bad hire costs roughly 30% of first-year salary, while SHRM’s research on recruitment costs places the all-in replacement cost between 50% and 200% of annual salary depending on seniority. This is where you catch a half-baked position definition before it produces a half-baked hire.
Job Requisition vs. Job Description vs. Job Posting
Three documents handle one hire, with three different audiences and three different approval chains. People use these terms interchangeably; they should not. Each artifact has a distinct audience, format, and purpose, and conflating them is the single most common reason a requisition stalls before sign-off.
| Document | Audience | Purpose | Format | Approver |
|---|---|---|---|---|
| Job requisition | HR, FP&A, leadership | Authorize the hire and lock spend | Internal structured form | HRBP + FP&A + exec |
| Job description | Recruiter, interviewers, candidate | Define scope, responsibilities, qualifications | Prose + bulleted competencies | Hiring manager |
| Job posting | Job seekers | Attract qualified applicants | Brand-led, externally compliant | Recruiter / employer brand |
Internal and operational, the job requisition serves HR, FP&A, and the executive who has to approve the headcount. Its purpose is to justify and authorize the hire. Structured fields cover a cost code, a reason for hire, a start date, a compensation range, and an approval chain. Nothing in this artifact is meant for a candidate to read.
Aimed internally with limited candidate visibility, the job description addresses the recruiter, the interviewers, and sometimes the applicant. Its purpose is to define the role’s scope, responsibilities, and required qualifications in enough detail that two interviewers will assess the same person against the same standard. Format runs to prose plus a bulleted competency list, usually 400 to 700 words. While job descriptions can be attached to or derived from the requisition, they remain separate artifacts. When ready-made structures save time, our job description templates for recruiters cover the most common role types.
Public-facing by definition, the job posting targets the job seeker. Its purpose is to attract and convert qualified applicants. Format runs shorter, brand-led, and increasingly regulated. Per Ogletree’s 2025 pay transparency tracker, 13 states (CA, CO, CT, HI, IL, MA, MN, NJ, NV, NY, RI, VT, WA) now require salary range disclosure in postings, with Delaware effective 2027. Whatever compensation band you approve on the requisition becomes the band that lands on Indeed and LinkedIn. No compliant way exists to post a different number than the one you authorized.
Why does the distinction matter? Different people sign off on each artifact, and they live in different systems. Requisitions live in the HRIS or ATS approval flow. Job descriptions live in the role library. Postings live on the careers site and job boards. Three documents, three lifecycles, one position.
What Should a Job Requisition Form Include?
Fifteen distinct fields make up a complete requisition form. Skip any of them and the request will bounce back from FP&A or HR for clarification, costing you days. Include all of them and the document moves through approval in hours instead of weeks.
Standard fields run as follows:
- Requisition ID. System-generated when the form is submitted. Used to track the role across HRIS, ATS, and accounting.
- Job title and job code. The exact title that will appear on the posting, mapped to your internal job-leveling framework so finance can verify the salary band.
- Department and cost center. Where the headcount sits in the org chart and which P&L absorbs the cost.
- Hiring manager and reporting line. Who the new hire reports to and who that person reports to. Two levels matter for approval routing.
- Reason for hire. Backfill, new headcount, replacement, or contract-to-perm. Backfill reqs use existing budget; new headcount needs separate approval.
- Employment type. Full-time, part-time, contractor, or temp. Drives benefits eligibility and accounting treatment.
- Location and work model. Onsite, hybrid, or remote. Includes city, state, country, and any in-office day requirements.
- Proposed start date. When the role needs to begin. Sets the recruiter’s clock.
- Compensation range. Base salary minimum and maximum, plus bonus target, equity grant, and any sign-on. Mandatory in 13 states for the public posting.
- Budget code or headcount ID. The line item this addition reconciles against. Without it, FP&A cannot approve.
- Required and preferred qualifications. A summary, not the full job description. Three to five must-haves and three to five nice-to-haves.
- Business justification. One to three sentences answering: why this role, why now, and what breaks if it stays unfilled.
- Approval chain. Names and roles of every person who must sign off, in order.
- Attached job description. A link to the existing JD in your role library, or a draft attached to this requisition.
- ATS routing instructions. Which pipeline template applies, which screening questions are required, and any compliance flags (visa sponsorship, security clearance, OFCCP coverage).
Without all 15 inputs in place, gaps surface downstream as ATS data hygiene problems, comp band drift, or FP&A disputes about which line item this addition belonged to. Per Jobscan’s 2025 ATS Usage Report, 97.8% of Fortune 500 companies use a detectable ATS. A botched requisition feeds bad data into the same system that will run reporting on this hire for years.
How Do You Write a Job Requisition Step by Step?
Writing the document takes 30 to 60 minutes once your inputs are ready. Most of the elapsed time on a requisition gets spent waiting on approvals, not writing. Below is the sequence that minimizes back-and-forth.
Step 1: Confirm the headcount is approved. Before you draft anything, check your annual workforce plan. Is this a backfill of an existing position? A net-new hire that was already budgeted for this quarter? Or an unbudgeted ask? Each answer determines who needs to sign off. When the ask is unbudgeted, you will need a business case deck before the requisition itself.
Step 2: Write the business justification first. Three sentences. Why does this role exist, what does it produce, and what breaks if you do not hire? FP&A reads this before any of the other fields. When those three sentences are weak, the request bounces.
Step 3: Lock the compensation range. Pull a current market band from your comp tool or from a benchmarking source. Do not guess. According to SHRM’s 2025 benchmarking, comp band drift is one of the most common reasons offers get withdrawn at the FP&A review stage. Start from a defensible band; price in line with market and cite the source. Tools like the ones in our salary benchmarking tools roundup make the lookup take minutes instead of hours.
Step 4: Draft or link the job description. When a current JD exists for this title, link it. Otherwise, write one before you submit the requisition, not after. Approval chains stall when an FP&A reviewer cannot tell what the position does.
Step 5: Fill the structured fields. Title, department, reason for hire, employment type, location, start date, cost code, qualifications. Use exact values from your HRIS dropdowns. Free-text entries trigger manual review.
Step 6: Run the approval chain in order. Hiring manager submits, HR business partner reviews, department head approves, FP&A approves, leadership signs (for senior or new headcount). Skipping a step does not save time; it sends the requisition back two stages later.
Step 7: Hand off to the recruiter. Once approved, the requisition activates in the ATS and the sourcing partner begins work. When your stack is well configured, this is automatic. Otherwise, your TA team rekeys data into the ATS, which is where time-to-fill silently expands. For where the requisition fits in the broader workflow, see our walkthrough of the hiring process end to end.
The whole sequence works only if the inputs are real. A requisition built on guesses about salary, vague qualifications, and a missing cost code does not get filled. It gets argued about.
Job Requisition Template (Sample)
A standard requisition template organizes the 15 fields above into six visual blocks: Position, Classification, Compensation, Budget, Role Summary, and Approval Chain. The format below is a clean, fillable structure you can adapt to your HRIS or paste into a Google Doc as a starting point. Notice how each reviewer can locate their field within five seconds without reading prose.
JOB REQUISITION FORM
Requisition ID: [auto-generated]
Date submitted: [YYYY-MM-DD]
POSITION
Job title: Senior Product Manager
Job code (level): IC5
Department: Product
Cost center: CC-2041
Reporting to: VP Product
Skip-level: Chief Product Officer
CLASSIFICATION
Reason for hire: New headcount (Q2 plan, line 14)
Employment type: Full-time
Work model: Hybrid (3 days onsite NYC)
Location: New York, NY
Proposed start date: 2026-07-15
COMPENSATION
Base salary range: $185,000 to $215,000
Target bonus: 15% of base
Equity grant: 0.05% to 0.08% (Tier 4)
Sign-on: Up to $25,000 (case-by-case)
Pay range source: Radford 2026 Q1 NYC tech band
BUDGET
Headcount ID: HC-2026-Q2-014
Budget code: 5102-PROD-IC5
Annualized cost (loaded): $312,000
ROLE SUMMARY
Required qualifications: 7+ years PM experience; B2B SaaS; led 0-1 product launch.
Preferred qualifications: Experience with developer tooling; technical degree.
Business justification: Owns the new dev-tools surface area shipping in Q3.
Without this hire, launch slips one quarter and Q4
revenue plan slips by an estimated $1.2M.
APPROVAL CHAIN (in order)
1. Hiring manager: VP Product (Jane Smith)
2. HRBP: Sarah Chen
3. Department head: Chief Product Officer (Marco Liu)
4. Finance: FP&A Director (Priya Shah)
5. Executive sign-off: CEO (required for new headcount over $250K loaded)
ATTACHMENTS
Job description: [Link to JD in role library]
ATS pipeline template: Senior IC PM (TPL-104)
Compliance flags: OFCCP-covered position; 2-year applicant retention.A real requisition is plainer than the marketing version of itself. Every reviewer should find the field they care about within five seconds. Plain text. Fixed labels. Clear approvers. This document does not have to be pretty; it has to be unambiguous.
How Does the Requisition Approval Workflow Work?
Backfill requisitions clear in 24 to 72 hours; new headcount can stretch one to three weeks. Each request runs through three to five approvers depending on whether it is a backfill or a new addition. Backfills move fastest because the spend and the job already exist. New headcount, especially senior or executive, runs the longest because FP&A and the C-suite are both involved.
Standard chains follow this order. Hiring manager submits. HR business partner reviews for completeness, comp band fit, and workforce-plan alignment. Department head approves the operational need. FP&A clears the cost against the headcount plan. For director-level and above, or for any net-new position, an executive (typically CHRO, CFO, or CEO) signs the final approval. Once cleared, HR generates the requisition ID and activates the record in the ATS.
Where reqs stall is almost always at the FP&A stage. Two issues account for most of those stalls: a missing cost code (the request bounces back to the hiring manager) and a comp range that exceeds the approved band (the request bounces to HRBP for a justification). Both are avoidable when Step 3 of the writing sequence above is done with discipline.
Once the requisition is live in the ATS, sourcing starts. Faster handoffs mean faster fills. For sourcing against an approved requisition, Pin is the strongest fit in the stack. Native field mapping into Greenhouse, Lever, and Workday means the moment a requisition activates, the TA team has 850M+ candidate profiles ready to query. SOC 2 Type 2 compliance, a 14-day average time-to-fill across Pin customers, and a 4.8/5 G2 rating are why teams replacing LinkedIn Recruiter consistently pick Pin for this handoff.
For organizations that have moved past spreadsheet-driven approvals, automation is the next leg. Our guide to automating the hiring process covers what to wire up first when reqs routinely take more than a week to clear sign-off.
What predicts how fast a requisition gets filled?
Cleanliness at submission. Sloppy submissions produce slow approvals. Slow approvals produce stale candidates and lost offers.
What Are the Most Common Job Requisition Mistakes?
Roughly eight predictable failures cause most requisitions to stall, with the finance bounce-back accounting for the majority. Most requisitions that stall fail in predictable ways, and the pattern repeats across companies, industries, and headcount sizes:
- Vague business justification. “We need more capacity in product” is not a justification. “Without this hire, the dev-tools launch slips one quarter and Q4 revenue plan misses by $1.2M” is.
- Missing or guessed compensation range. A made-up band gets challenged by HRBP, and the requisition bounces back. Pull a real number from your comp tool.
- No cost code. FP&A cannot approve a requisition without a line item to charge it against. This is the single most common reason a request sits in queue.
- Wrong employment type. Submitting a contractor role as full-time (or vice versa) sends it through the wrong approval chain entirely.
- Skipping the job description. A requisition with “JD to follow” usually means a JD that never gets written. That position then attracts the wrong candidates and your TA team loses two weeks calibrating.
- Approval chain in the wrong order. Sending FP&A the requisition before HRBP almost always bounces. HRBP is the gatekeeper for completeness; budget reviewers should never see an incomplete document.
- Reusing a stale requisition. Cloning last year’s req without re-pulling comp data, re-checking the org chart, or updating the work model is how comp band drift starts.
- No start date. “ASAP” is not a start date. Sourcers cannot prioritize against other open positions without a real one.
Every issue above is fixable in the document, before submission. None is fixable downstream without restarting the approval cycle.
What Are the Biggest Job Requisition Trends in 2026?
Three trends are reshaping how requisitions get written and approved this year: salary transparency laws, recruiter workload pressure, and the AI handoff to sourcing. Each one changes a specific field on the form.
Salary transparency. As of mid-2025, 13 states and a growing list of cities require pay range disclosure in job postings. Implication for the requisition is direct: whatever comp range you approve internally is the comp range that gets published externally. No longer is there a private internal band and a public “competitive” hand-wave. Per Mitratech’s 2025 time-to-fill analysis, nearly 40% of senior-level roles already take 90+ days to fill. Getting the comp band wrong adds weeks more, since offers get clawed back at FP&A or rejected by candidates seeing higher external bands. Get the band right at requisition stage or face an EEOC complaint at posting stage.
Recruiter workload pressure. According to Gem’s 2025 Recruiting Benchmarks Report (drawn from 1M+ hires and 140M+ applications across 2021 to 2024), the average sourcer now manages 14 open requisitions simultaneously, up 56% from three years prior. Each one handles 2,500+ applications, 2.7x the 2021 number. Average team size shrank from 31 in 2022 to 24 in 2024. Requisitions are now a triage tool. Reqs without a clean business justification get deprioritized because TA teams cannot tell which fire to put out first.
The AI handoff. Per Employ’s 2024 Recruiter Nation Report, 89% of recruiters now use AI frequently or very frequently in their workflow. Where has the bottleneck moved? Upstream, to the requisition. A clean, structured submission with all 15 fields populated lets AI sourcing tools query against a real role spec from minute one. A messy one (missing comp band, ambiguous title, vague qualifications) forces a sourcer to re-derive the spec by hand before any tool can help.
We’ve noticed this pattern in our own work with TA teams. Sourcers using Pin’s AI sourcing to fill 14 simultaneous reqs are not asking for more candidates per req; they are asking for sharper requisitions. When the comp band, must-haves, and work model are all locked, a sourcing run that takes 30 minutes for a clean req takes 90 minutes for a vague one. Sloppy requisitions are no longer just an approval delay; they act as a direct multiplier on every downstream sourcing hour.
“As a small people and talent team, we don’t have a ton of time to spend hours sourcing and messaging. Pin has made it possible for us to focus on the people side of things!”
Miles Randle, Head of People & Talent at Flip CX
Teams pulling time-to-fill below the 44-day SHRM median treat the requisition as the control point, not the sourcer. Speed comes from a clean document, not a faster pipeline.
Frequently Asked Questions
What is the difference between a job requisition and a job description?
A requisition is the internal authorization document that justifies and approves a hire. Sign-off comes from HR, FP&A, and leadership before any external posting goes live. By contrast, a description is the role specification that defines responsibilities and qualifications for the recruiter, interviewers, and candidates. Requisitions contain the spend and the approval chain; descriptions contain the role’s scope.
Who initiates a job requisition?
Hiring managers initiate the requisition by completing the form. From there, it routes to the HR business partner for review, the department head for operational sign-off, FP&A for budget approval, and (for senior or new headcount) executive leadership. Three to five approvers is standard. Recruiters do not write the requisition; they receive it once approved.
What does an “open requisition” mean?
An open requisition is a position that has been approved and is actively being recruited but has not yet been filled. In some industries (healthcare, retail, manufacturing) an “evergreen requisition” stays open continuously and supports multiple hires for the same role over time. Per SHRM’s 2025 talent acquisition benchmarking, only 20% of organizations formally track quality of hire across these long-running reqs. Evergreen requisitions require different ATS configuration and have OFCCP record-retention implications.
How long does requisition approval typically take?
Backfill requisitions (where the spend and JD already exist) often clear in 24 to 72 hours. New-headcount requisitions, especially for director-level and above, can take one to three weeks because FP&A and executive sign-off are both involved. Stalls happen most often at the FP&A stage, usually because of a missing cost code or a comp range that exceeds the approved band.
Does the salary range on the requisition have to match the public posting?
In 13 states (CA, CO, CT, HI, IL, MA, MN, NJ, NV, NY, RI, VT, WA), yes. Salary transparency laws require pay range disclosure in job postings, and the posted range cannot meaningfully differ from the band approved on the requisition without legal exposure. Compensation on the requisition is now a load-bearing input, not a placeholder.
Where to Start
When your organization does not have a standard requisition template, build one this quarter. Start with the 15 fields above. Place the document inside your HRIS or ATS so submissions auto-route to the right approvers. Pull comp ranges from a real benchmarking source. Require a one-paragraph business justification on every submission. Audit your last 20 hires to see where requisitions stalled, and fix that field first.
A requisition is not paperwork. It is what determines whether your next hire takes 30 days or 90, costs $5,000 or $35,000, lands at market band or above it. With sourcers now juggling 14 open reqs and 2,500+ applications each, the requisition is the one place where a hiring manager holds full control. Tools like Pin’s recruiter platform only get useful once the document is clean; until then, sourcing software is solving the wrong problem.
Get the document right and everything else about the hire gets easier.
