Best way to organize hiring approvals in an ATS

Hiring approvals usually break for a simple reason: every hire gets routed through the same people in the same order. A junior replacement role waits for the same executive sign-off as a new director role, and the recruiting team loses days before anyone has spoken to a candidate.

An ATS hiring approvals workflow controls who must sign off before a hiring action moves forward. The practical version is three layers: approve headcount first, approve the job or posting setup second, and approve the offer terms last.

This guide is about buying and implementing an ATS approval design. It can support governance and auditability, but it is not legal advice and it does not guarantee compliance by itself.

What is an ATS hiring approvals workflow?

An ATS hiring approvals workflow is a set of routing rules inside the applicant tracking system. Those rules decide who must approve requisitions, postings, offers, or the vendor’s equivalent objects before work continues.

The key distinction is timing. Headcount approval happens before recruiting starts, while offer approval happens before a candidate receives pay, equity, level, start date, and contract terms.

Vendors use different language, which matters during demos. Ashby documents approvals for openings, jobs, and offers; Lever groups approvals around requisitions, postings, and offers; Greenhouse documents job approvals and offer approvals.

If the team is still unclear on the base system, start with the ATS basics before designing approvals. Approval workflow design only helps once the team knows what the ATS owns versus the CRM, HRIS, payroll, or finance system.

Why one approval chain creates bottlenecks

A single approval chain looks tidy on a process map, but it treats different risks as if they are the same. A backfill in an approved budget does not need the same scrutiny as a new senior role outside the hiring plan.

The upside of one chain is simplicity. The downside is that every exception makes the standard route slower, because finance, legal, People Ops, and executives get pulled into low-risk decisions.

It also hides the real blocker. If the same workflow covers headcount, job content, and offer terms, reporting can show that “approval” is slow without showing whether the delay is budget, process design, or compensation.

Separate approval layers fix that. They give each decision the right approvers, the right evidence, and a clearer audit trail when someone asks why a role or offer was approved.

What is the best structure for hiring approvals?

The best structure is a three-layer model: headcount or requisition approval, job or posting approval, and offer approval. Each layer should answer a different business question.

Headcount / requisition: approve the budget, hiring need, department, location, level, and whether the role is backfill or net-new. Common approvers are the hiring manager, department head, finance or FP&A, People Ops, and an executive for senior or net-new roles.

Job / posting: approve the job description, posting settings, interview plan, scorecards, and process consistency before the role goes live. Common approvers are the recruiter, hiring manager, recruiting operations, HRBP, and legal or compliance for regulated roles.

Offer: approve salary, equity, level, start date, work location, and offer terms before the candidate receives anything. Common approvers are the hiring manager, recruiter or talent lead, compensation, finance, HRBP, legal, and an executive for out-of-band offers.

The risk prevented is different at each stage. Headcount approval prevents unfunded hiring, job approval prevents inconsistent process design, and offer approval prevents unauthorised compensation or terms.

How should headcount or requisition approval work?

Use headcount approval when the company needs budget control before recruiters spend time on a role. It is most useful for scaling companies, multi-department hiring teams, formal workforce planning, and enterprise hiring.

The workflow should capture the basics before anyone sources candidates: role title, department, location, level, employment type, target start date, hiring reason, and budget owner. The catch is that too many fields make hiring managers bypass the process or submit poor data.

A sensible chain starts with the hiring manager, then goes to the department head and finance. Add People Ops or HRBP for organisational fit, and reserve executive approval for senior, net-new, or out-of-plan roles.

Ashby is a good example for scaling Talent Ops teams because it supports opening approvals, which can approve headcount before hiring against it. The limitation is plan gating: Ashby says approvals are available on Legacy Plus, Plus, and Enterprise, but not Foundations.

Lever also fits this layer because requisition approvals are one of its documented approval workflow categories. The trade-off is price visibility: Lever is recorded by ATSLab from about $4k and says pricing is available upon request, tailored by organisation size and hiring needs.

How should job or posting approval work?

Use job or posting approval when the team needs to review the role content and hiring process before publishing. This layer is less about budget and more about candidate experience, consistency, and process control.

The review should cover the job description, careers-page content, posting settings, interview plan, scorecards, and any screening questions. The downside is that content review can become subjective unless the team defines what approvers are checking.

Greenhouse is a strong enterprise example here because it supports job approvals. Its approval flows can be configured for all jobs, by office, by department, or by department within an office.

That flexibility helps larger companies avoid one global rule for every role. The catch is cost and ranking context: Greenhouse is recorded from about $6k and ranks nineteenth in ATSLab’s fixed index, below Ashby and Lever overall.

Lever also supports posting approvals, including approval-specific states such as pending and rejected when posting approval workflows are enabled. That is useful for teams with custom reporting needs, but it requires a team willing to manage a more technical ATS + CRM environment.

Ashby supports job approvals as part of its openings, jobs, and offers model. The advantage is breadth across the hiring process, while the limitation remains the same: buyers need to evaluate Plus or Enterprise if approvals are required.

How should offer approval work?

Offer approval should protect the company before the candidate receives salary, equity, level, start date, location, and contract terms. It is the approval layer most teams recognise, but it should not be the only one.

Separate normal offers from exception offers. A standard offer inside band might need the hiring manager and recruiting lead, while an out-of-band salary, senior title, remote location, or equity exception should trigger finance, compensation, legal, or executive review.

Reapproval rules are a buying requirement. If salary, equity, level, start date, or work location changes after approval, the ATS should make clear whether the offer must be approved again.

Ashby documents offer approvals and related approval behaviour, and approvers can approve or reject from email or Slack. That speeds decisions, but the ATS still needs to keep the record because email and Slack alone are a poor audit trail.

Greenhouse supports offer approvals and lets approval steps run sequentially or all at once. Sequential routing gives more control, while all-at-once routing can cut waiting time when several approvers can review in parallel.

Lever includes offer approvals as one of its documented approval categories. It is a good fit if offer governance needs to sit beside candidate relationship management, but buyers should check which reporting, add-ons, and integrations are included in the quote.

How should approvals change by company size?

Small teams should keep approvals light. One hiring manager plus one founder, finance, or People approver is usually enough unless the company has regulated roles or strict budget controls.

The benefit is speed. The risk is weak governance if the company is already hiring across multiple departments, locations, or compensation bands.

Scaling teams should add formal headcount approval, standard job or posting review, and compensation review for offers. Conditional approvals matter here because senior roles, out-of-band compensation, and country-specific hiring should not follow the same route as standard roles.

Ashby is the highest-ranked featured tool for this stage, sitting second in ATSLab’s fixed ranking with a recorded price of $400. That recorded entry reflects Ashby’s starting point, but approval buyers must look beyond Foundations because approvals are not available there.

Enterprise teams should use conditions based on department, office, level, compensation band, employment type, and geography. Use sequential approval where control matters, and parallel approval where speed matters.

The enterprise downside is process weight. If every low-risk role gets the full approval chain, recruiting teams will treat the ATS as a delay rather than the source of truth.

Enterprise teams should also report on approval cycle time and bottlenecks. Greenhouse even describes analysing offer approval bottlenecks as a use case for approved AI tools connected to Greenhouse Recruiting, but buyers should still verify what is available on their plan and implementation.

Which ATS approval features should buyers ask about?

Do not ask only whether the ATS has approvals. Ask what objects it can approve, what conditions it supports, which plans include the feature, and what happens when an approved item changes.

Start with coverage. Can the ATS approve requisitions or headcount, not just offers? Can job or posting approvals review job descriptions, interview plans, scorecards, and posting settings before a role goes live?

Then test routing. Can approvals vary by department, office, role level, location, employment type, and compensation band? Can approvers be role-based, such as “department head”, rather than only named users?

Ask about sequence and speed. Can approvals run in order and in parallel? Can approvers approve from email or Slack, and does the ATS still keep an audit trail inside the system?

Ask about reapproval. Which changes trigger a new approval: salary, equity, level, start date, location, employment type, offer template, or reporting manager? A weak answer here usually means manual policing later.

Ask about reporting. Can the team report on approval cycle time, stuck approvals, rejected approvals, and common exception reasons? Ashby can report on approvals on Plus, Enterprise, and Legacy Plus, but not Foundations.

Finally, ask what is outside the base quote. Approval features, conditional routing, automation, AI, SMS, job boards, background checks, assessments, API access, SSO, sandbox, implementation, and premium support can all depend on plan or contract.

Which ATS is best for hiring approvals?

For the featured approval tools, Ashby is the strongest-ranked overall choice if the team is scaling and needs approvals for openings, jobs, and offers with reporting. The catch is clear: Ashby approvals are not on Foundations, so approval-heavy buyers should evaluate Plus or Enterprise.

Lever is the better fit if the company wants ATS + CRM workflows with approvals across requisitions, postings, and offers. It also exposes approval state and steps through its API model, which helps teams with a data warehouse or custom workflow needs.

The trade-off with Lever is buying complexity. ATSLab records Lever from about $4k, while Lever says pricing is tailored by organisation size and hiring needs, and items such as Candidate Insights, AI Screening by VONQ, and Onboarding are listed as add-ons.

Greenhouse is the best fit among the three for enterprise structured-hiring governance and office or department-specific controls. It supports job and offer approvals, with configuration for all jobs, office, department, or department within an office.

Greenhouse is not ATSLab’s top overall ATS. It ranks nineteenth in the fixed index and is recorded from about $6k, so it makes most sense when structured hiring governance matters more than starting price or overall index position.

Other tools can still be sensible in narrower cases. Workable supports e-signature offer approval workflows on Premier and Enterprise, Breezy HR lists Job Approvals and Offer Approvals on Business, Zoho Recruit supports offer approvals, and Pinpoint describes multi-stage requisition approvals.

If the team is comparing the whole ATS market, Breezy HR remains ATSLab’s number-one ranked tool overall at $157. That does not make it the default answer for complex approval governance, where Ashby, Lever, and Greenhouse are more directly relevant.

What mistakes slow approval workflows down?

The biggest mistake is using the same approval chain for every role, level, and location. It feels fair, but it makes low-risk hiring wait behind high-risk exceptions.

Another mistake is adding too many approvers to ordinary hires. If finance must approve every typo correction or minor process change, the team will either wait unnecessarily or move the discussion outside the ATS.

Skipping headcount approval is also risky. If the first formal check happens at offer stage, recruiters may spend weeks on a role that was never funded or approved.

Email and Slack approvals can help speed, especially when the ATS records the decision. Used alone, they create scattered evidence and make it harder to answer who approved what, when, and on which terms.

Teams also forget reapproval triggers. Salary, equity, level, start date, location, and employment type changes should have clear rules, because these are the edits that create most approval disputes.

The final mistake is buying the wrong plan. Several vendors gate approvals, conditional steps, reporting, automation, API access, SSO, sandbox environments, implementation, or support, so the demo checklist needs to match the contract.