What you'll learn
- What a Job Requisition Is (and What It Is Not)
- The 10 Fields Every Job Requisition Should Include
- How to Write the Business Justification
- Job Requisition Approval Workflow
- A Filled-In Job Requisition Example
- How a Clean Requisition Accelerates Time-to-Hire
A job requisition is the document that officially authorizes a company to begin hiring for a role. It is not a job description, not a LinkedIn post, and not a Slack message to HR saying "we need someone." It is a formal internal document that passes through an approval chain, reserves budget, and hands the recruiting team a clear brief for the hire. Without an approved req, nothing moves — no sourcing, no job board posts, no interviews. That is either a safeguard or a bottleneck, depending on how well the document is written. The most common failure mode is a req that stalls. It sits with a department head for two weeks because the business justification is vague. It bounces back from finance because there is no cost center listed. It arrives in HR without a comp range, so the business partner cannot benchmark the role or begin configuring a screening process. Every one of these delays costs real time — and in competitive hiring markets, that time costs candidates. This guide covers what belongs in a job requisition, how to write the business justification section that most often determines whether a req gets approved or returned, how the approval workflow typically runs in US enterprises, and what a complete, filled-in req looks like for a real role. If you are also working on the downstream job description once the req clears, we cover that separately at /blog/how-to-write-job-description. The goal here is practical: give you a template structure and enough context to write a req that moves through your approval chain the first time, without revisions and without follow-up nudges. For a deeper look at where time-to-hire gets lost across the full pipeline, see our guide at /blog/reduce-time-to-hire.
What a Job Requisition Is (and What It Is Not)
Quick answer
A job requisition is an internal authorization document. Its purpose is to get organizational sign-off that a specific position should be filled, that budget exists to fund it, and that the recruiting team has enough information to execute the search. Once approved, it becomes the foundational brief that drives everything downstream: the job description, the sourcing strategy, the interview plan, and the offer parameters.
A job description is a public-facing document that explains the role to candidates. A headcount request is a higher-level ask made during annual planning, covering multiple potential hires across a department. A job posting is the external advertisement on a job board. The requisition sits between the headcount request and the job description: it is the formal, per-role approval document that translates a headcount approval into a real hire.
A well-written job requisition serves three functions. First, it is an authorization document — it proves that the right people have signed off that this role should exist and be funded. Second, it is a budget reservation. Third, it is a hiring brief for the talent acquisition team — it tells recruiters what the role is, why it exists, what success looks like, and what the interview process should be.
In most US companies, a hiring manager or department head submits the requisition. It typically lives in an HRIS like Workday, BambooHR, Greenhouse, or Lever. Approval routing is usually automated through the HRIS, with each approver getting a notification when the req lands in their queue.
The 10 Fields Every Job Requisition Should Include
Quick answer
Position title and level matter more than most hiring managers assume. A title like 'Engineer' is not enough — the req should specify 'Senior Software Engineer, L5' or whatever level nomenclature your company uses. This determines compensation band, interview rigor, and how HR classifies the hire. A missing level often forces a return trip through approvals when comp ranges do not line up.
Department and cost center tell finance exactly where the headcount expense lands. Hiring manager name is straightforward, but it matters — HR needs to know who owns this search and who has final say on the offer. Business justification should clearly mark the req as a backfill or new headcount, as these two types follow different approval paths.
Requested start date sets expectations for the timeline. Compensation range in USD, tied to your internal band, keeps the search focused and prevents the team from bringing in candidates whose expectations cannot be met. Reporting structure identifies who the new hire reports to and whether they will have any direct reports.
Remote, hybrid, or onsite designation must be explicit — 'Flexible' is not a designation. Interview process outline is the field most hiring managers skip, and it is the one that creates the most downstream friction. Listing the intended interview stages lets the TA team configure the process in your ATS before the req is approved. Success metrics for the role answer: how will you know this hire worked? 'Owns the first production deployment within 60 days' is specific. 'Contributes to the team' is not.
A job requisition is not a job description — it is the internal authorization document that clears budget, gets organizational sign-off, and hands the TA team a hiring brief. The fields that most often cause reqs to stall are the business justification and the compensation range; both should be specific, complete, and ready before the req enters the approval chain.
How to Write the Business Justification
Quick answer
The business justification section is the single field that determines whether a req sails through approval or bounces. Approvers — particularly finance and senior leadership — are evaluating whether the cost of the hire is justified by a quantifiable business return. A justification that reads 'the team is busy and needs help' will not clear that bar.
The framework is straightforward: state the business problem, quantify the cost of the gap, and project the return of filling the role. Here is what that looks like in practice for a customer success role: 'The current customer success team handles 180 accounts per CSM. The industry benchmark for our ARR tier is 120 accounts per CSM. Our response time on escalations has increased 40% over the past two quarters, which correlates with our 14% annual churn rate. Filling this role reduces the per-CSM account load to 140, which is projected to recover approximately $340,000 in retained ARR in year one.'
That justification gives every approver what they need. The VP of Sales can see the problem. Finance can see the return. Compare that to 'we are growing quickly and the team is stretched thin' — which is probably also true but gives nobody a reason to approve this week rather than next quarter.
For new headcount outside of an annual planning cycle, you are asking approvers to make an exception. Acknowledge that directly and justify why the exception is warranted. Approvers are more likely to move fast when you show you understand the bar you are asking them to clear.
Job Requisition Approval Workflow
Quick answer
The standard approval chain in US enterprise companies runs through four stops: hiring manager, department head, HR business partner, and finance. In practice, these often overlap — the hiring manager and department head may be the same person for senior roles, and some companies route HRBP and finance approval in parallel.
VP or C-suite approval gets added to the chain in specific situations. Any role that was not in the approved headcount plan typically requires an executive exception. Backfills outside of an open headcount cycle often require the same. Contract-to-hire conversions require their own approval sequence.
A well-structured req in a functional approval process should clear in three to five business days. Two-week timelines are usually a signal of one of three things: an incomplete req that is bouncing back for revisions, an approver who has not received a notification, or an organizational norm where nobody has established a clear SLA for the approval step.
The most common causes of approval delays: missing or weak business justification, no compensation range listed, incorrect or missing cost center, unclear backfill-versus-new-headcount designation, and the req going to the wrong approver in the routing chain. All five are preventable with a complete, well-written req.
A Filled-In Job Requisition Example
Quick answer
The following is a complete, filled-in req for a Senior Software Engineer role, written as it would appear in a real submission.
Position Title and Level: Senior Software Engineer, L5. Department: Product Engineering. Cost Center: CC-4210. Hiring Manager: Priya Mehta, Director of Engineering. Business Justification (New Headcount): Our payments infrastructure team currently has three engineers supporting a service that processes $2.4M in monthly transaction volume. We had two payment processing incidents in the last 90 days, each causing measurable drop-off in checkout completion rate. Adding a fourth engineer restores our ability to maintain the service while continuing development on the card-on-file feature, committed to enterprise customers in our Q3 release. Engineering leadership estimates the card-on-file feature at $180,000 in incremental ARR.
Requested Start Date: August 4, 2026. Compensation Range: $155,000 to $185,000 base, plus standard equity grant per L5 band. Reporting Structure: Reports to Priya Mehta. No direct reports. Work Location: Hybrid — Austin, TX. Tuesday and Wednesday on-site required.
Interview Process: Recruiter screen (30 min), hiring manager intro call (45 min), technical screen with two senior engineers (90 min), take-home project (4-hour async, compensated), final panel with Director and Head of Product (60 min). Total process: 12 to 16 business days from first contact to offer. Success Metrics: Within 30 days, completed onboarding and shipped one small reliability fix. Within 60 days, independently reviewing pull requests and contributing to card-on-file build. Within 90 days, assigned as lead on one incident response track.
A complete req does more than just clear approvals faster — it compresses time-to-hire at every stage that follows. When the interview process is defined in the req itself, recruiters can configure ATS stages and AI screening tools before the first candidate applies, which means the search is already operationally ready the moment approval lands.
How a Clean Requisition Accelerates Time-to-Hire
Quick answer
The req is approved and lands with the recruiting team. If the req is complete, the recruiter has everything they need to start immediately: the role is understood, the comp range is clear, the interview process is defined, and the success bar is explicit. If the req is incomplete, the first day is spent tracking down answers — which means the first sourcing run happens on day two or three instead of day one.
The interview process field in the req has a specific downstream benefit that is easy to overlook. When the interview plan is documented before the req is approved, the TA team can configure the interview stages in your ATS, set up structured feedback forms, and — if your company uses /products/interview-as-a-service or AI-assisted screening — configure those tools before the first candidate applies.
This matters more than it sounds. A recruiter who receives a complete req can have a sourcing campaign running, interview stages configured, and an intake call scheduled with the hiring manager within the first business day. Our analysis of hiring data shows that time-to-approve and time-from-approve-to-first-interview are the two stages where the most time gets lost — and both are directly affected by req quality. For a full breakdown of where time-to-hire gets lost and how to address each stage, see /blog/reduce-time-to-hire.
The compounding effect of a well-written req is that it sets the tone for the entire search. A hiring manager who submits a detailed, specific req has already done the thinking work to know what they want. Searches that stall in the middle — where there are three finalists and no decision — almost always trace back to fuzzy requirements at the start.
Frequently asked questions
Common questions about recruitment operations and how InCruiter helps teams solve them.
InCruiter Editorial Team
AI Hiring Research · Interview Intelligence · Enterprise Talent Strategy
The InCruiter editorial team covers AI-driven hiring, interview intelligence, and modern talent acquisition strategy. Our guides draw on platform data from 2,000+ hiring teams, conversations with talent leaders, and published research in industrial-organizational psychology.
