What Is a Job Requisition Approval Workflow—and Which ATS Handles It Best (2026)

When a hiring manager submits a job requisition, the clock starts. In many organizations, no one can see it. The requisition moves through an email chain or a Slack thread. It passes between finance, department heads, and human resources (HR). Days or weeks can pass before a recruiter starts work.

SHRM’s 2026 benchmarking data shows a median of 39 calendar days from requisition open to offer acceptance for nonexecutive roles. In 2025, the median was 44 days.

The U.S. Bureau of Labor Statistics (BLS) reported about 7.1 million job openings in August 2026. The figure is preliminary, and BLS revises JOLTS data each month.

This guide compares five applicant tracking system (ATS) tools on how well they handle job requisition approvals.

What is a job requisition approval?

A job requisition is the formal request to open a new role. It captures the job title, department, headcount justification, salary band, start date, and any other information a company requires before recruiting begins. A job requisition approval is the structured review process that validates and authorizes that request before HR can post the role or brief a recruiter.

In a typical approval workflow, multiple stakeholders are involved:

• The hiring manager who initiates the request

• The department head or VP who validates the business case

• The finance team that confirms the budget

• HR or talent acquisition who verifies the role fits the approved headcount plan

Most organizations require sign-off from all of them before recruiting starts.

The approval workflow is the control point for organizational headcount. A role that bypasses proper approval can create budget overruns, duplicate positions, or compliance exposure, particularly for companies operating across multiple jurisdictions.

The approval trail is the record: when a question arises later about why a role was opened, the chain of approvals answers it. Without that chain, finance and HR are left reconstructing decisions that should have been captured upfront.

Why most ATS tools fail at requisition approvals

Most ATS platforms focus on candidate management. This includes sourcing, screening, interviews, and offers. Requisition approvals happen earlier, before that work starts. Most tools handle them in the same limited way.

No structured approval routing

Many ATS tools do not include a formal requisition approval module. Teams build their own process with email and Slack. The hiring manager sends a draft requisition. A manager replies with approval. HR creates the role by hand. The system does not record who approved what, or when. If a compliance question comes up later, no audit trail exists.

No conditional logic

Some tools support only linear chains. Person A approves, then person B approves. Most organizations need conditional routing. Roles above a salary threshold go to finance. Roles in some locations go to a local HR lead. Backfills can skip the department-head review that a new headcount requires. Without conditional logic, teams route requisitions by hand or skip the system. This recreates the email workaround that the ATS was meant to replace.

No visibility on pending requisitions

When an approval is in progress, many ATS tools do not show its status to HR or talent acquisition. There is no approval dashboard. There are no reminders for approvers who stall. There is no escalation path when a decision-maker is away. Requisitions wait, and no one outside the email chain knows. The recruiter is ready to start, but no one tells them there is nothing to start on yet.

No HRIS sync

Approval decisions that are not recorded in the human resources information system (HRIS) cause later problems. These include duplicate headcount entries, inconsistent org-chart data, and payroll setup errors when the hire occurs. Delays can build up in the period between position open and approved-to-fill.

Most platforms still make teams work around the tool at this stage. Check each tool against the criteria below.

What to look for in an ATS for job requisition approvals

Before you compare vendors, define what your approval process needs. For most mid-market HR and finance teams, five criteria matter.

Multi-step routing

Can the tool send a requisition to several approvers in order? Can it use different sequences for each department, role level, or location? A startup with one approval step needs little here. An organization with a finance sign-off and more than one approver will feel the gap quickly.

Conditional logic

Can approval chains change based on job attributes? These include budget, level, headcount type (new or backfill), and location. Conditional logic turns a basic checklist into a real approval workflow. It also lets one system handle all requisition types, without separate workarounds for exceptions.

Stakeholder visibility

Can approvers see what waits for them? Can HR track each pending requisition without sending follow-up emails? Approvers should know what they must review. HR should not have to chase approvers to learn their status.

HRIS integration

When an ATS and an HRIS connect, approved headcount can appear in the system of record without manual transfer. This lowers the risk of reconciliation errors. The connection also keeps approval history and employee records in one linked system.

Audit trail

Who approved the requisition? When? Was the budget changed before final sign-off? A complete audit trail supports finance reconciliation, compliance reviews, and board-level headcount reporting. It is a required record, not an optional feature.

For a wider framework across the full hiring process, see Deel's ATS buyers' guide.

How leading ATS tools handle job requisition approvals

The five tools below cover a range of approaches. They run from multi-layer enterprise approval chains to simpler flows that are fast to set up. Each section covers the tool’s strengths and limits against the five criteria above.

Deel's ATS

Deel’s ATS is connected directly within Deel. It requires Deel HR, the HRIS, as its foundation. Workforce Planning and onboarding workflows sit alongside it.

The main difference is where approval happens. Roles approved in Deel Workforce Planning move into the ATS as open requisitions. Hiring managers do not create a requisition and route it through the ATS. They activate positions that already passed approval at the planning stage. The ATS also supports configurable job and offer approval workflows.

This connection removes approval friction before recruiting starts. The headcount decision is made and recorded upstream. From there, Deel HR links hiring data to onboarding and Deel’s payroll solution. Candidate details move forward without repeated manual entry.

Greenhouse

Greenhouse has a mature approval structure for the ATS market. It supports three approval types: approval to start recruiting, job approval, and offer approval. Hiring managers start a requisition, attach a job description, and send it to approvers in a set order. The system logs each decision.

Teams that need structured processes and clear audit trails can use this engine well. It fits mid-market and enterprise teams that run several approval paths at once across departments. Deel integrates with Greenhouse, so teams can use both platforms together.

Ashby

Ashby is built for HR and talent acquisition teams that work with data. Its approval workflow supports multi-step chains, conditional steps, and assigned approvers. Approvers see headcount planning data next to the requisition, so they decide with full context.

Conditional approval steps require the Plus or Enterprise tier. Teams on other tiers should confirm their plan before they design the workflow.

Growing mid-market teams can use Ashby as requisition volume rises. Ashby is a Deel preferred partner. Teams that use both can strengthen their hiring process.

Workable

Workable offers an approval flow that is quick to set up. Its custom approval workflow selects a path that matches the requisition’s department and location. It also supports sequential routing across approver groups.

Non-technical HR teams can launch the flow without a dedicated systems resource. Deel integrates with Workable, so teams can keep hiring and HR work connected.

Teams that need approval logic beyond department and location should test the flow with a real requisition before they commit.

Pinpoint

Pinpoint has purpose-built requisition approval workflows. It offers configurable routing, status tracking, and a clear approval interface. The approval module is a core feature of the product.

Pinpoint offers about 35 native HRIS connectors. These include Workday, BambooHR, HiBob, SuccessFactors, and Oracle HCM. Pinpoint is a partner-built integration with Deel. Teams that use both can strengthen their approval process and connect it to their HR work.

Comparison: approval workflow features at a glance

The table reflects typical mid-market setups. Enterprise setups with custom integrations can change these results. Vendor capabilities change over time.

Streamline hiring approvals with Deel

Requisition approval bottlenecks rarely come from one slow person. They come from tools that were not built for this stage. Approval chains live in email. Only the requester sees the status. HRIS records need manual updates after the fact.

Deel’s ATS connects with Workforce Planning. Headcount approved at planning moves into recruiting without a separate requisition step. Deel HR links recruiting with onboarding and Deel’s payroll solution. Manual re-entry falls as each approved hire moves forward.

Deel Hire is the hiring front door. It routes an approved hiring decision into the right employment path: direct employment, EOR, PEO, or contractor. Deel HR supports recruiting and the employee lifecycle after that.

If your approval process depends on email threads and manual status checks, book a demo below to see a connected system in practice.