A formal internal document requesting approval to fill a position, including budget justification, role details, and management sign-off before recruiting begins.
Key Takeaways
A job requisition is the formal starting point of any hiring process. Before a job gets posted, before a recruiter starts sourcing, before a single candidate is screened, someone has to get permission to hire. That's what the requisition does. It's an internal document (usually submitted through an ATS or HRIS platform) where a hiring manager requests approval to fill a specific position. The requisition includes why the role is needed, what it will cost, where it fits in the org chart, and who needs to approve it. Think of it as a business case for adding headcount. It forces the hiring manager to justify the investment and ensures the organization doesn't hire reactively or without budget alignment. Without a formal requisition process, companies end up with unbudgeted hires, duplicated roles, and no paper trail for audit or compliance purposes.
These three documents serve different purposes at different stages. The job requisition is an internal approval request: "Can we hire for this role?" It goes to finance, HR, and senior management. The job description is an internal operational document that details every duty, skill, and specification for the role. The job posting is the external advertisement derived from the description, designed to attract candidates. The sequence is: requisition (approval) then description (documentation) then posting (marketing). Some organizations combine the requisition and description into a single submission, especially for standardized roles where the job specs don't change between hires.
Every new hire represents a significant financial commitment: salary, benefits, equipment, workspace, training, and management overhead. The loaded cost of an employee (salary plus benefits and overhead) is typically 1.25x to 1.4x their base salary. A role with a $100K salary actually costs the organization $125K to $140K per year. The requisition process ensures this investment is planned, budgeted, and approved. Without it, department heads might hire freely, blowing past headcount budgets and creating compensation imbalances across teams.
A standard job requisition contains these elements. The exact format varies by organization, but the core information is consistent.
| Component | Description | Who Provides It |
|---|---|---|
| Job title and department | The role's title, team, and business unit | Hiring manager |
| Position type | Full-time, part-time, contract, temporary, or intern | Hiring manager + HR |
| New role vs backfill | Whether this is a new headcount addition or a replacement for someone who left | Hiring manager |
| Business justification | Why this role is needed now: revenue impact, workload data, strategic initiatives | Hiring manager |
| Compensation range | Proposed salary band, bonus eligibility, equity (if applicable) | HR/Compensation team |
| Budget code/cost center | Which budget or cost center will fund the position | Finance |
| Reporting structure | Who the role reports to and where it sits in the org chart | Hiring manager |
| Key responsibilities | Summary of the role's core duties (abbreviated version of the full job description) | Hiring manager |
| Required qualifications | Minimum skills, experience, education, and certifications | Hiring manager + HR |
| Approval chain | Who must sign off: direct manager, VP, finance, HR | Organization policy |
Requisition approval workflows vary by company size and governance structure. Here's a typical flow.
The hiring manager fills out the requisition form in the company's ATS (Greenhouse, Lever, Workday, iCIMS) or HRIS platform. They provide the role details, business justification, and proposed compensation. A strong justification includes specific data: "Team workload has increased 40% in the last quarter, current headcount can't support Q3 product launches, and this role will own the mobile app feature pipeline." Vague justifications ("We need more people") get sent back for revision.
The hiring manager's direct leader reviews the request against department budget and priorities. They may approve, reject, or ask for modifications (different seniority level, different start date, contract instead of full-time). At this stage, the decision is about whether the role aligns with the department's strategic plan and available budget.
Finance confirms budget availability and validates the proposed compensation against the approved headcount plan. If the role was included in the annual workforce plan, approval is typically fast. If it's unplanned headcount, finance scrutinizes the justification more closely and may require additional data on ROI or revenue impact.
HR validates that the role title, compensation range, and requirements are aligned with the company's compensation framework, job architecture, and compliance requirements. HR also checks for potential issues: Is the salary range competitive for the market? Do the requirements comply with anti-discrimination laws? Is the role properly classified as exempt or non-exempt?
Once all approvals are in, the requisition moves to "open" status in the ATS. The talent acquisition team is notified and begins the recruiting process: writing the job posting, developing a sourcing strategy, and scheduling an intake meeting with the hiring manager. The requisition number becomes the tracking ID for all hiring activity associated with that role.
A well-run requisition process balances control with speed. Too much bureaucracy slows hiring. Too little oversight leads to budget overruns and misaligned hires.
Even well-designed requisition processes can break down. Here are the most frequent issues and how to fix them.
Requisitions get stuck in approval queues because approvers are busy, on vacation, or don't prioritize hiring requests. The fix: set SLA expectations for each approval level (e.g., 2 business days per approver), auto-escalate after the SLA expires, and add a delegate approver for when the primary approver is unavailable. Some companies use conditional auto-approval for roles below a certain salary threshold.
The requisition is approved, but recruiting doesn't start for another 2 weeks because no one scheduled the intake meeting, the job posting isn't written, or the recruiter is overloaded. Build an SLA: the first candidate outreach should happen within 3 to 5 business days of requisition approval. Use automated workflows in your ATS to trigger the intake meeting and posting creation as soon as the req is approved.
15 to 20% of approved requisitions are eventually canceled or frozen (Lever, 2023). This wastes recruiter time and creates frustration. Reduce cancellations by requiring stronger business justifications upfront and reviewing open requisitions monthly. If a requisition has been open for 90+ days without a hire, reassess whether the role is still needed.
The hiring manager submits a salary range that's below market, leading to candidate declines and extended time-to-fill. Prevent this by requiring HR or the compensation team to validate the proposed range against market data during the requisition review. Don't let requisitions through with unrealistic compensation that will waste everyone's time downstream.
Most modern ATS and HRIS platforms include requisition management. Here's how the major platforms handle it.
| Platform | Requisition Features | Best For | Integration |
|---|---|---|---|
| Greenhouse | Custom approval chains, kick-off forms, offer approval workflows | Mid-size to large companies with structured hiring | Deep ATS integration, finance tools via API |
| Lever | Requisition creation, multi-level approvals, budget tracking | Growth-stage companies scaling hiring | CRM + ATS combined, HRIS integrations |
| Workday Recruiting | Enterprise requisition management tied to workforce planning | Large enterprises using Workday HCM | Native integration with Workday Finance and HR |
| iCIMS | Automated requisition workflows, compliance tracking, analytics | Enterprise high-volume hiring | Extensive marketplace of integrations |
| SAP SuccessFactors | Global requisition management with multi-country compliance | Multinational enterprises | Native integration with SAP ERP and finance |
These metrics help identify bottlenecks and improve the requisition process over time.