Map the approval objects before demos. Ask whether the ATS supports requisition, opening or headcount approvals, job approvals and offer approvals. A tool that only approves offers may still leave finance and hiring managers arguing in Slack before a role is opened.
Test routing with a real org chart. You need to see whether approvals can route sequentially, in parallel, by office, department, legal entity or job level. Greenhouse supports scoped and ordered approvals, but buyers still need to confirm the exact plan and implementation setup.
Ask what changes trigger reapproval. Ashby lets teams decide which offer fields, such as salary or start date, should trigger reapproval. That is useful for compensation control, but Ashby Foundations has governance limits, including no custom approval reports and SSO as a $100/month add-on.
Check the audit trail, not just the approval screen. Ashby documents approval timestamps, approvers, requester fields and rejection notes, while Lever exposes audit events through its developer documentation. Greenhouse Pro adds audit log, but its documented audit-log event window is the previous 30 days.
Price the compliance package, not the headline ATS. ATSLab records Ashby at $400, Lever from roughly $4k and Greenhouse from roughly $6k, but Lever and Greenhouse publish quote-only pricing. Ask vendors to itemise SSO, SCIM, audit logs, BI exports, approval workflows, AI screening and implementation.
Treat AI features as a governance question. Lever positions AI Screening by VONQ as keeping decisions with recruiters, Greenhouse includes AI features such as Talent Matching and AI Notetaker, and Ashby has AI credits and AI talent rediscovery. The risk is not the feature itself; it is using it without clear logging, permissions, notices and human review.