Requisitions: The Complete Guide

A hiring manager at a 300-person SaaS company once lost three strong backend engineers in 11 days because the requisition sat in legal review, then finance, then the VP’s inbox. By the time the role was approved, one candidate had accepted a competing offer at $185,000 base, and the team had to restart with a revised budget and a narrower scope. This requisitions guide shows employers how to prevent that kind of delay by treating requisitions as operational documents, not paperwork.

A requisition is the bridge between headcount planning and actual hiring. When it is clear, approved, and tied to a real business need, recruiters can move faster, managers can interview with purpose, and finance can control spend without creating bottlenecks. When it is vague, every downstream step slows down: job ads attract the wrong applicants, scorecards drift, and offer approvals turn into exceptions. The best teams use requisitions as a control system, not a formality.

What a requisition actually does for hiring teams

A requisition is the internal authorization to hire for a specific role, budget, and timeframe. It usually includes the job title, department, location, reporting line, compensation range, employment type, and approval chain. That sounds simple, but the document does three jobs at once: it defines the business need, protects the budget, and gives recruiting a target.

Here is a concrete example. A manufacturing company needs a maintenance supervisor after a plant expansion adds a second shift. If the requisition says only “supervisor needed ASAP,” recruiters may source for the wrong seniority level, HR may miss shift differential costs, and operations may expect a leader who can also handle compliance training. If the requisition says “Maintenance Supervisor, 2nd shift, $78,000–$92,000 base, reports to Plant Manager, must have CMMS experience and OSHA 30,” the search becomes much tighter and the approval path becomes easier to defend.

The strongest requisitions also reduce rework. Hiring teams that standardize requisition fields tend to see fewer last-minute edits to the job description, fewer compensation exceptions, and fewer candidate rejections caused by mismatched expectations. That matters because the average cost of a bad hire can reach 30% of first-year earnings in many industry estimates, and the cost of a slow hire is often invisible until revenue, customer support, or production slips. A clear requisition keeps the process anchored before those costs compound.

For employers, the practical value is simple: a requisition turns a vague staffing request into a managed workflow. It is the starting point for job posting, interview planning, offer approval, and eventually onboarding.

What belongs in a requisition: the requisitions guide employers need

A useful requisition is specific enough that three departments can act on it without a follow-up meeting. HR needs role details, finance needs budget clarity, and the hiring manager needs a practical profile of the person they are actually trying to hire. If any one of those groups has to guess, the requisition is incomplete.

Below is a simple comparison of what a weak requisition looks like versus a strong one.

Field	Weak requisition	Strong requisition
Job title	Marketing Manager	Lifecycle Marketing Manager
Need	Need help with growth	Need to improve trial-to-paid conversion by 18%
Location	Remote	Remote, U.S. only, core hours 11am–3pm ET
Compensation	Competitive	$110,000–$135,000 base + 10% bonus
Scope	General marketing tasks	Own email, onboarding, and retention campaigns
Success metric	None	Increase activation rate from 42% to 50% in 2 quarters
Approvals	“Waiting on sign-off”	Manager, finance, HRBP, and VP approval required

A requisition should usually include at least these elements:

1. Business reason for the hire
2. Exact title and level
3. Department and reporting manager
4. Location, schedule, and employment type
5. Compensation band and bonus eligibility
6. Must-have skills and deal-breakers
7. Interview panel and approval path
8. Target start date and backfill/new headcount status

Employers often underestimate the value of the business reason. “Replacing a resigned employee” is different from “creating a new revenue role tied to a product launch.” The first may need continuity and speed; the second may need a sharper competency profile and a stronger business case. If the requisition does not distinguish those situations, the review process becomes slower and more political.

This is also where tools matter. A clean requisition supports better job posts, stronger screening, and more consistent hiring decisions. If the requisition is tight, your job posting workflow and interview materials are easier to align. If it is loose, every downstream document inherits the ambiguity.

Requisition review: where approvals slow down and how to fix them

Most hiring teams do not lose time in sourcing; they lose it in requisition review. The delay usually comes from one of three places: budget approval, role level disagreement, or unclear ownership. Industry data suggests that when a requisition moves through too many hands without a standard template, the process can stretch from a few days into multiple weeks.

Here is a practical way to think about the review chain:

1. Manager review — confirms the role is real and the scope is correct.
2. HR review — checks title, level, compliance, and internal consistency.
3. Finance review — verifies budget, headcount, and compensation range.
4. Executive or department head review — resolves exceptions or strategic hires.

The highest-friction step is usually compensation. For example, a sales director request may begin at $140,000 base with a 20% bonus, but finance may only approve $125,000–$135,000 unless the role is tied to a named territory or revenue target. That gap is not just a pay issue; it affects time-to-fill, candidate quality, and whether recruiters can credibly engage passive talent.

A strong requisition review process has three safeguards. First, it uses a standard intake form so every request has the same fields. Second, it defines who can approve what, so a VP does not get pulled into routine backfills. Third, it sets a service-level expectation, such as 48 hours for manager review and 72 hours for finance. Even if your company cannot meet those exact windows, publishing a timeline reduces stalled requests.

If your team already uses scorecards and structured interviews, connect the requisition to those tools early. A requisition that names the top three outcomes makes it easier to build an employer scorecard and avoid interviews that drift into personality-based feedback. That alignment is one of the simplest ways to reduce hiring bias and make approvals defensible.

How to build a requisition process that works in practice

A good requisition process is not just a form; it is a sequence. The best employers treat it like a production line with defined inputs, owners, and checkpoints. If your process is ad hoc, every search becomes a custom project and every approval becomes a negotiation.

Step 1: Start with the business outcome

Before anyone writes a title, define what changes if the role is hired. Examples include reducing customer churn by 2 points, cutting plant downtime by 15%, or adding 30 qualified pipeline opportunities per month. This keeps the requisition tied to output rather than generic workload relief.

Step 2: Lock the scope and level

Decide whether the role is junior, mid-level, senior, or leadership. A senior software engineer and a staff engineer may both write code, but their scope, compensation, and decision-making authority are not interchangeable. If the level is wrong, the requisition will produce the wrong applicant pool.

Step 3: Attach budget and approval rules

Set the salary band, bonus plan, and any exceptions before posting. If a recruiter can only go to $95,000 base without a second approval, that limit should be visible from the start. This prevents late-stage offer rewrites and protects candidate trust.

Step 4: Connect the requisition to the hiring workflow

Once approved, the requisition should trigger the job description, interview plan, and sourcing strategy. That is where linked tools help: a candidate-facing resume builder or resume scanner may not be employer tools, but they remind teams that candidates are optimizing for clarity too. The more precise your requisition, the easier it is to match the right people to the role.

Step 5: Review the requisition after the first 10 applicants

Do not wait until the search is failing. If the first 10 applicants are underqualified, overqualified, or concentrated in the wrong geography, revisit the requisition language, compensation, or level. Small corrections early are cheaper than a full restart after 30 days.

A practical rule: if interviewers keep asking the same three questions about scope, budget, or seniority, the requisition is not specific enough. Fix the requisition before you fix the pipeline.

Common requisition mistakes that cost time and money

The biggest requisition mistakes are usually small on paper and expensive in practice. One of the most common is writing a title that is too broad. “Operations Manager” can mean warehouse, customer success, finance, or project operations. If the title is vague, the applicant pool becomes noisy and recruiters spend more time filtering than sourcing.

Another mistake is hiding compensation until late in the process. Employers sometimes think they are preserving flexibility, but the market often interprets that as evasiveness. Candidates compare ranges quickly, especially for roles in tech, healthcare, and sales. If your requisition does not include a realistic band, your recruiter may spend hours screening people who would never accept the offer.

A third mistake is mixing must-haves with nice-to-haves. If a requisition says a candidate must know SQL, manage a team, own a budget, and have industry-specific regulatory experience, you may be describing three different profiles. The result is either an impossibly narrow search or a flood of applicants who only meet one requirement. Keep the must-have list to five or fewer items whenever possible.

Do not ignore internal equity either. If a new requisition offers $128,000 for a title that existing employees hold at $118,000, your current team will notice. A good requisition review includes a compensation sanity check against internal bands and recent offers. That is where tools like salary estimator can help teams pressure-test ranges before approval.

Finally, do not let the requisition become stale. If the role changes after a reorg, acquisition, or product pivot, update the document immediately. Hiring for the old version of the job can waste an entire quarter.

Why requisitions matter even more in tight labor markets

When labor markets tighten, requisitions become a competitive advantage. Candidates move faster, managers get more selective, and compensation expectations shift in real time. In that environment, a requisition that took two weeks to approve can become a lost opportunity.

This is especially true in roles where the market is narrow. A cloud security engineer, a bilingual nurse manager, or a plant controller with ERP experience may receive multiple offers in a single week. If your requisition does not clearly describe the role, pay, and decision timeline, your hiring team will look slower than competitors even if the actual process is reasonable.

The same logic applies to employer brand. Candidates can tell when a requisition is recycled from an old posting versus built for a current need. They notice mismatched titles, outdated location rules, and salary bands that do not match the scope. That is why the best employers treat requisition writing as part of the candidate experience, not just internal administration.

If you want to improve candidate response rates, pair a strong requisition with clear role content, realistic compensation, and a fast review loop. Then connect the workflow to interview prep and offer readiness. Tools like mock interview practice and who’s hiring are candidate-side examples of how clarity speeds decisions; employer-side, the same principle applies to requisition design.

FAQ

What is the difference between a requisition and a job description?

A requisition is the internal authorization to hire, while a job description is the external or internal summary of the role. The requisition includes budget, approvals, and business need. The job description translates that into candidate-facing language. Strong employers keep them aligned so the approved scope matches what gets posted.

Who should approve a requisition?

Most companies use a mix of the hiring manager, HR, finance, and a department leader. Some roles also require legal, compensation, or executive approval. The key is to define the approval chain upfront so requests do not stall in inboxes or get re-litigated after the search starts.

How detailed should a requisition be?

Detailed enough that a recruiter can start sourcing and finance can confirm the budget without another meeting. Include title, level, reporting line, location, compensation band, business reason, and success metrics. If the document still invites major interpretation, it is not ready for review.

How often should requisitions be updated?

Update them whenever the role changes materially: new manager, new budget, different location, altered scope, or revised start date. In fast-moving teams, that can happen more than once during a search. A stale requisition is one of the fastest ways to create a bad candidate experience.

What causes requisition review delays?

The most common causes are unclear scope, compensation disagreements, too many approvers, and missing business justification. Delays also happen when different departments use different templates. Standardizing the intake form and approval path usually cuts down on back-and-forth.

How can employers make requisitions faster to approve?

Use a standard template, pre-approved salary bands, and a clear service-level expectation for each reviewer. Keep the business case tied to measurable outcomes, not vague workload. If you need a faster handoff from approval to posting, connect the requisition to your hiring workflow and employer jobs process.

A strong requisition is one of the cheapest ways to improve hiring speed, quality, and budget control at the same time. If your team is still relying on email threads and half-finished intake notes, start with a clean template, a defined approval chain, and a realistic compensation band. SignalRoster can help teams keep that process consistent with tools that support structured hiring from the first request to the final offer. Explore the linked resources, tighten the requisition review, and make the next hire easier to approve and easier to fill.