Req Approval: Greenhouse vs Lever vs Automation — 3 Ways 2026
Key Takeaways
Requisition approval automation connects the req creation event in your ATS (Greenhouse or Lever) to an approval routing workflow in Slack, email, or a dedicated platform—eliminating inbox-based delays.
Manual req approval is one of the most consistent contributors to time-to-fill inflation for white-collar roles; a req sitting in a hiring manager's email queue for 5 days costs time-to-fill directly.
Greenhouse and Lever each have native approval workflow features, but both require orchestration extensions when approval chains span multiple departments or systems.
White-collar average time-to-fill: 44 days for professional roles according to SHRM 2024 Talent Acquisition Benchmarks, and req approval delays account for a meaningful share of that elapsed time before sourcing even begins.
US Tech Automations builds the cross-system orchestration that connects Greenhouse or Lever approval events to Slack notifications, hiring manager calendars, and compensation review workflows.
What Is Requisition Approval Automation?
Requisition approval automation is the process of replacing manual routing—emailing a req form to a manager, waiting for a reply, forwarding to finance for headcount confirmation—with a workflow that triggers automatically when a req is created in the ATS, routes it to the correct approvers in a structured sequence, and escalates or re-routes when an approver does not act within a defined window.
When it works well, a new req moves from creation to fully approved in under 24 hours. Without automation, the same process often takes 5 to 10 business days—and that delay is invisible to candidates and recruiters until the role is ready to post.
TL;DR: Req approval automation is a routing problem, not a technology problem. The tools (Greenhouse, Lever, Slack) already exist; the gap is the orchestration logic that connects them and enforces SLAs.
Why Req Approval Delays Cost More Than They Appear
US direct-hire staffing market: $185 billion in 2024 revenues according to Staffing Industry Analysts 2025 forecast. In that environment, the cost of a delayed req is not just internal—it is competitive. A role that sits in approval for 7 days is a role the competition can start sourcing 7 days sooner.
The delay compounds downstream. A recruiter cannot post the role, source candidates, or start screening until the req is approved. LinkedIn InMail acceptance rate: approximately 25% for professional roles according to LinkedIn Talent Insights 2024 — meaning the outreach volume required is high, and every day of sourcing delay compounds against the final candidate pool.
Recruiters at companies with automated req approval report spending 70% less time on approval status follow-up, according to Greenhouse 2024 Talent Benchmarks Report — recovering 2–4 hours per week for sourcing and candidate engagement work.
The internal cost is also real. Recruiters who chase req approvals manually—following up with hiring managers by email or Slack message—report spending 2 to 4 hours per week on req status management that has nothing to do with sourcing or candidate evaluation.
Who This Is For
This workflow guide is written for TA leads, recruiting ops managers, and HR systems administrators at companies with 50 to 2,000 employees using Greenhouse, Lever, or a combination ATS environment, processing 10 or more new req approvals per month.
Red flags: Skip this if you are a startup under 20 employees with informal hiring processes, if req approvals happen verbally in team meetings with no formal ATS workflow, or if you have no integration between your ATS and Slack (the orchestration layer requires at least one connected channel for routing).
The 3 Approaches to Req Approval Automation in 2026
Approach 1: Native Greenhouse Approval Workflows
Greenhouse includes a built-in approval workflow module. When a recruiter creates a job req, Greenhouse routes it through a defined approval chain—typically hiring manager, then finance or headcount owner, then HR leadership—sending email notifications at each step.
What works: The native workflow handles linear approval chains (A approves, then B approves) cleanly within the Greenhouse environment. It logs the approval chain and timestamps each action for audit purposes.
What does not work: Greenhouse's native approvals are email-based, which means they compete with every other email in the approver's inbox. There is no native Slack push, no SLA escalation if an approver is slow, and no conditional branching (e.g., reqs above a certain salary band route to a compensation review step before manager approval).
Best for: Companies with linear approval chains, all approvers active in email, and req volumes under 20/month.
Approach 2: Native Lever Approval Workflows
Lever's approval module (available in the Hire and Nurture plans) follows a similar structure: req creation triggers an email notification to the approval chain, with each approver receiving a link to review and approve within Lever.
What works: Lever's approval UI is clean and intuitive for approvers who infrequently log in—the approval action can be completed directly from the email link without navigating the full Lever interface. Lever also supports configurable approval chains by department or role type.
What does not work: Same limitation as Greenhouse—email-based notifications, no native Slack routing, no SLA enforcement, and no cross-system branching for reqs that require a compensation committee review.
Best for: Companies using Lever as their primary ATS with a straightforward approval chain and approvers who respond reliably to email.
Approach 3: Orchestrated Approval Automation (Greenhouse or Lever + Slack + Orchestration Layer)
The third approach connects the ATS approval trigger to a Slack workflow that routes the approval request as an interactive message, sets SLA timers, escalates to backup approvers if the primary does not act, and branches based on req attributes (level, salary band, department headcount status).
This approach requires an orchestration layer—either a native Slack workflow, Zapier/Make for simple cases, or US Tech Automations for complex cross-system logic.
What works: Approvers receive a structured Slack message with the req details, a one-click approve or reject button, and a comment field. The workflow logs the action, notifies the recruiter, and triggers the next step (posting, sourcing kickoff, or compensation review) automatically. SLA escalation fires after 24 hours if no action is taken.
What does not work: Requires setup investment and a Slack environment where approvers are active. Not suitable for organizations where approval authority holders do not use Slack.
Comparison Table: Greenhouse vs Lever vs Orchestrated Automation
| Feature | Greenhouse Native | Lever Native | Orchestrated (USTA) |
|---|---|---|---|
| Email-based approval routing | Yes | Yes | Optional (email + Slack) |
| Slack approval routing | No (requires integration) | No (requires integration) | Yes (native Slack push) |
| SLA escalation to backup approver | No | No | Yes (configurable) |
| Conditional approval branching | No | Limited | Yes (by level, salary, dept) |
| Cross-system (ATS + HRIS) req validation | No | No | Yes |
| Approval audit trail | Yes | Yes | Yes (cross-system) |
| Compensation review routing | No | No | Yes (conditional branch) |
| Setup complexity | Low | Low | Medium |
| Honest edge | Clean within-ecosystem workflow | Clean approver UX from email | Complex multi-system routing |
Where the named platforms win: Greenhouse's native approval workflow is the right choice for companies that have already standardized on Greenhouse and whose approval chains are linear and email-friendly. If your hiring managers respond reliably to Greenhouse email notifications and your reqs do not require compensation review branches, the native module is sufficient—there is no need for additional orchestration. Lever wins on approver UX: the ability to approve directly from an email link without logging in is genuinely useful for executives who are occasional approvers and do not want another system to navigate.
When NOT to use US Tech Automations: If your team is under 50 employees with fewer than 10 monthly req approvals and a simple linear approval chain, the native Greenhouse or Lever approval modules handle this adequately. The orchestration layer earns its value when approval chains are multi-level and conditional, when approvers are distributed across functions with different SLA expectations, or when the req approval process needs to trigger downstream actions (posting the role, kicking off sourcing, or routing to a compensation review) without manual follow-up from the recruiter.
The Req Approval Workflow: Step-by-Step Recipe
Req created in ATS. Recruiter creates the job req in Greenhouse or Lever, including role title, department, level, location, salary band, and headcount justification.
Orchestration layer receives the creation event. Via webhook from the ATS, the orchestration layer captures the req data and begins routing.
Compensation band validation. If the req is above a defined level or salary band threshold, the workflow routes it to the compensation team for review before the approval chain starts. This step runs in parallel with step 4 for reqs below the threshold.
Slack approval message sent to primary approver. The hiring manager or departmental head receives a Slack message containing the req summary, a link to the full req in the ATS, and approve/reject buttons. The SLA timer starts.
SLA timer runs. If no action is taken within 24 hours (configurable), the workflow sends a reminder. If no action at 48 hours, it escalates to the designated backup approver and notifies the TA lead.
Secondary approver routing. Approved reqs route to the next approver in the chain (finance, HR leadership, or skip-level depending on the req's level). The same SLA logic applies.
Final approval recorded. When all approvers have approved, the workflow logs the final approval timestamp in the ATS and moves the req to "Open" status.
Recruiter notification and sourcing kickoff. The recruiter receives a notification with the approved req details, the approved salary band, and a link to the posted role. If the agency uses a sourcing kickoff checklist, the workflow triggers it automatically.
Rejected req routing. If a req is rejected at any stage, the workflow notifies the recruiter with the rejecting approver's comments and routes the req to a revision queue. The recruiter can update and resubmit without restarting the full chain.
Full audit trail logged. Every approval action, timestamp, approver identity, and SLA event is logged to the ATS and optionally to an HRIS system for headcount reporting.
Req Approval SLA Benchmarks by Company Size
| Company Size | Target Approval Time | Acceptable Ceiling | Common Bottleneck |
|---|---|---|---|
| Under 100 employees | 4–8 hours | 24 hours | Single approver availability |
| 100–500 employees | 8–24 hours | 48 hours | Multi-level chain + finance sign-off |
| 500–2,000 employees | 24–48 hours | 72 hours | Cross-departmental routing |
| 2,000+ employees | 48–72 hours | 5 business days | Legal/comp review required |
Cost-of-Delay Model: What a 5-Day Approval Backlog Costs
| Role Level | Avg. Fully-Loaded Salary | Cost Per Day Vacant | 5-Day Approval Delay Cost |
|---|---|---|---|
| Individual contributor | $70,000 | $270 | $1,350 |
| Senior IC / specialist | $110,000 | $423 | $2,115 |
| Manager | $140,000 | $538 | $2,690 |
| Director | $185,000 | $712 | $3,560 |
| VP / executive | $280,000 | $1,077 | $5,385 |
Vacancy cost estimates assume 50% productive output lost per day — the role generates no output but the organizational demand it serves continues. At 20 new reqs per month with a 5-day average approval delay, the aggregate vacancy cost approaches $30,000–$50,000/month in organizational capacity, depending on role mix.
The average cost-per-hire across US industries reached $4,700 in 2024, according to SHRM 2024 Talent Acquisition Benchmarks — a figure that rises significantly when extended approval timelines push time-to-fill past 60 days and require more sourcing cycles.
Companies with structured digital approval workflows reduce req-to-offer timelines by an average of 9 business days, according to Greenhouse 2024 Talent Benchmarks Report, primarily through eliminating the approval waiting period before sourcing begins.
Common Mistakes in Req Approval Automation
Building approval chains with no escalation logic. A req that sits with an unresponsive approver indefinitely is worse than a manual process because there is a false sense that "the system is handling it."
Not connecting the approval to the posting trigger. The most common recruiter complaint is that an approved req still requires a manual step to post the role. The workflow should close that gap.
Ignoring the rejected-req experience. Rejection without context sends the recruiter back to square one. Approval workflows should require a comment field for rejections.
Over-engineering the compensation review step. If every req routes to a compensation review regardless of level, you create a bottleneck that defeats the speed goal. Threshold-based routing keeps the comp review reserved for cases that genuinely need it.
Glossary
Req (requisition): A formal internal request to open a new or replacement position, typically requiring manager and HR approval before recruitment begins.
ATS (Applicant Tracking System): Software used to manage the recruitment process, from req creation through offer acceptance—Greenhouse and Lever are examples.
Approval chain: The sequence of individuals who must approve a req before it is considered active and eligible for posting.
SLA (Service Level Agreement): A defined time window within which an action must be completed—in req approval automation, typically 24 to 48 hours per approver.
Orchestration layer: Middleware that connects multiple systems (ATS, Slack, HRIS) via APIs, managing workflow logic and data routing without replacing any underlying tool.
Headcount justification: The business case attached to a req explaining why the position is needed—new headcount, backfill, or restructure.
How US Tech Automations Orchestrates the Req Approval Loop
US Tech Automations connects Greenhouse or Lever's req creation webhook to a Slack approval workflow, routes based on configurable approval chain rules, enforces SLA escalation, and triggers the posting and sourcing kickoff steps on final approval. The platform does not replace Greenhouse or Lever—it extends their native approval modules with the conditional logic, Slack integration, and cross-system triggers that the ATS tools do not provide natively.
For TA teams that have built approval processes on email and are frustrated by delays and lack of visibility, US Tech Automations provides both the automation and the reporting layer—so TA leads can see exactly where every in-flight req is in the approval chain at any moment.
See pricing and workflow templates for recruiting teams at ustechautomations.com/pricing.
Related Recruiting Automation Resources
Also see the full recruiting automation resource library at ustechautomations.com/ai-agents/recruitment.
FAQs
Does Greenhouse support Slack integration for req approvals natively?
Greenhouse does not have a native Slack approval integration as of 2026. Greenhouse approval notifications are email-based. Connecting Greenhouse approval events to Slack requires either a third-party integration (Zapier, Make) or a custom orchestration layer that subscribes to Greenhouse webhook events and posts approval requests to Slack.
What is the difference between Greenhouse and Lever for approval workflows?
Both platforms offer email-based approval chains, but they differ in approver UX and configuration depth. Lever allows approvers to act directly from an email link without logging in, which is useful for executive approvers. Greenhouse's approval module is more configurable in terms of chain structure but requires the approver to log in to Greenhouse to approve. Neither supports native Slack routing or SLA escalation.
How do we prevent req approvals from sitting unactioned for days?
SLA escalation logic is the key. Build a workflow that sends a Slack reminder after 24 hours of no action, escalates to a backup approver after 48 hours, and notifies the TA lead. The escalation rules need to be defined at workflow design time—the specific timers depend on your organization's standard for req turnaround.
Can we automate the transition from req approval to job posting?
Yes. When the final approver acts on the req, the workflow can trigger the posting step automatically—pushing the role to the ATS's job board integrations, notifying the recruiter, and initiating a sourcing kickoff checklist. This eliminates the gap between "req approved" and "role live" that often adds another day or two to the pre-sourcing timeline.
What data does the req approval workflow need from the ATS?
At minimum: role title, department, level, location, hiring manager name, salary band, and headcount type (new or backfill). The orchestration layer uses this data to determine the correct approval chain, route to compensation review if applicable, and populate the Slack approval message with the information approvers need to make a decision.
Is the approval audit trail sufficient for SOX or HR compliance?
For most companies, yes—provided the workflow logs approver identity, timestamp, action (approve/reject), and any rejection comments. For SOX-regulated environments, the audit trail should be stored in a system that is not modifiable by the people being audited. An orchestration layer that writes approval logs to an HRIS or a separate audit log database meets this requirement.
About the Author
Helping businesses leverage automation for operational efficiency.
