An effective applicant tracking system is a platform that fits your workflow, supports candidates, connects with your other systems and gives you control over reporting, security, artificial intelligence, implementation and total cost. Start with the 10 questions below if you have limited time.

Do not choose an ATS because it has the longest feature list. Choose the platform that supports your hiring process with the fewest manual workarounds.

Run a live demonstration using your job types, approval steps, interview stages, integrations and reporting requirements. Greenhouse lists workflows, permissions, interview kits, scorecards, reporting, integrations, data migration and security as separate ATS evaluation areas.

The 10 Most Important Questions to Ask an ATS Vendor

If time is limited, ask these questions first:

Evaluation Area Question to Ask
Workflow Can you demonstrate our complete hiring workflow using a realistic example?
Candidate experience How quickly and easily can candidates apply from a mobile device?
Resume screening How do resume parsing and candidate filtering work, and can recruiters override automated decisions?
Collaboration Can recruiters and hiring managers use structured interview plans, scorecards and shared feedback?
Integrations Does the ATS integrate with our HRIS, calendar, email, job boards, video interview and assessment tools?
Reporting Can we report on source performance, time in stage, conversion rates, time to hire and recruiter workload?
Artificial intelligence Which AI features are included, what data do they use and how are their results tested and monitored?
Security How are applicant data, user access, audit logs, retention, deletion and exports managed?
Implementation What does implementation include, and who handles data migration, configuration, training and support?
Pricing What will the complete three-year cost be, including setup, integrations, premium modules, support and renewal increases?

What Should You Ask Internally Before Comparing ATS Platforms?

Define your hiring process before you compare platforms. Otherwise, a sales demonstration can become a tour of features that do not address your problems.

Ask your recruiting, HR, IT and hiring management teams:

  1. Which parts of our current hiring process are slow, inconsistent or manual?
  2. How many job openings, candidates, recruiters and hiring managers must the system support?
  3. Which job types, locations, languages and legal entities must the ATS handle?
  4. Who needs access, and what should each user be allowed to view, edit or approve?
  5. Which systems must connect to the ATS?
  6. Which reports do executives, recruiters and hiring managers need each week or month?
  7. Which candidate records must be migrated from the existing system?
  8. Do we need applicant tracking only, or also candidate relationship management, employee referrals, career-site management, assessments or onboarding handoffs?
  9. Which capabilities are mandatory, and which are optional?
  10. What business result will justify the purchase?

Put the answers into a short evaluation scorecard before vendor demonstrations. Score every vendor against the same criteria.

Which Workflow Questions Should You Ask About an ATS?

Your ATS should support the full hiring workflow without forcing recruiters to maintain spreadsheets, email chains or duplicate records.

Ask the vendor:

  • Can the ATS create job requisitions with custom approval workflows?
  • Can administrators configure stages for different departments, job types and locations?
  • Can the system automate interview scheduling, reminders, candidate notifications and task assignments?
  • Can recruiters move one candidate between multiple requisitions without creating duplicate profiles?
  • Can the system identify duplicate candidates and merge records safely?
  • Can hiring managers submit feedback without receiving unnecessary access to confidential information?
  • Can the ATS preserve an audit trail of status changes, approvals, interview feedback and communications?
  • Can recruiters create reusable job, email, interview and evaluation templates?
  • Can the system support internal applicants, employee referrals, agencies and sourced candidates?
  • Can recruiters search talent pools using skills, experience, location, availability or other structured fields?

Ask the vendor to demonstrate an unusual but realistic case, such as a candidate applying to two jobs, withdrawing and later re-entering the process. Edge cases often reveal more than a standard product tour.

Which Candidate Experience Questions Should You Ask?

The candidate application should be easy to complete, accessible and consistent across devices. Resume parsing, application length and connections to external assessments can affect completion rates. iCIMS lists resume parsing, integrations and analytics among its ATS selection topics.

Ask:

  • How many steps does a typical application require?
  • Can candidates apply using a resume, professional profile or mobile device?
  • Does the ATS parse resumes accurately into structured application fields?
  • Can candidates save an incomplete application and return later?
  • Can candidates see application status updates?
  • Can the system send personalized, automated communications without making them appear generic?
  • Does the application work with screen readers, keyboard navigation, browser zoom and other assistive technologies?
  • Can candidates request a reasonable accommodation during the application process?
  • Can the employer provide an alternative process if an automated assessment creates an accessibility problem?
  • Can the vendor show evidence of accessibility testing and explain how accessibility issues are reported and resolved?

For U.S. employers, accessibility deserves specific attention. The Equal Employment Opportunity Commission states that algorithmic tools can screen out applicants with disabilities and that employers may need to provide reasonable accommodations for technology-based assessments.

Which Screening and Artificial Intelligence Questions Should You Ask?

Treat AI recruiting features as decision-support tools that require review, testing and clear controls. Find out what the system does, what data it uses and whether a human can review or reverse its recommendations.

Ask:

  • Does the ATS rank, filter, score or automatically reject candidates?
  • Which candidate attributes influence an automated recommendation?
  • Does the system use keywords, knockout questions, job history, assessments or inferred characteristics?
  • Can recruiters see why a candidate was recommended, filtered or rejected?
  • Can recruiters override an automated recommendation?
  • Does the system make decisions automatically, or does it only provide suggestions?
  • What testing has the vendor performed for accuracy, disparate impact, accessibility and false negatives?
  • Does the vendor test results across relevant demographic groups?
  • Can the vendor provide documentation about model training data, updates and performance monitoring?
  • Is customer or candidate data used to train a shared model?
  • Can the organization disable specific AI features?
  • What happens when the system is uncertain or produces an incorrect recommendation?
  • Are applicants told when automated tools are used, where required?
  • Can recruiters export records showing how an automated tool affected a hiring decision?

The EEOC has warned that automated systems may filter or rank applicants through knockout questions, keyword requirements and other algorithmic methods. The agency also emphasizes the risk that automated tools can create barriers for applicants with disabilities.

Which Integration and Technical Questions Should You Ask?

An ATS rarely operates alone, so integration quality can matter more than the number of integrations listed on a product page.

Ask:

  • Does the ATS integrate with our HRIS or HCM, such as Workday, UKG, SAP SuccessFactors or ADP?
  • Does it connect with our email and calendar systems?
  • Does it integrate with job boards, social sourcing, video interviewing, assessments, background checks and e-signature tools?
  • Is each integration native, partner-built, API-based or dependent on middleware?
  • Which data moves between systems?
  • Is data synchronized in real time, on a schedule or only through manual exports?
  • Which system is the source of truth for candidate, requisition and new-hire data?
  • Does the vendor provide webhooks, APIs, documentation, rate limits and sandbox access?
  • Are API access and premium integrations included in the subscription?
  • What happens to integrations when the vendor changes its API?
  • Can the organization build custom integrations without vendor professional services?

A credible demonstration should show data moving from the ATS to another system and back. Ask the vendor to identify the exact fields, triggers, error handling and ownership for each integration. iCIMS, for example, documents integration workflows involving data models, authentication, APIs and application-complete events.

Which Reporting and Analytics Questions Should You Ask?

Your ATS should show where candidates enter the pipeline, where they leave it and how long each stage takes.

Ask:

  • Can reports show applicants, candidates, interviews, offers and hires by job, department, location and recruiter?
  • Can the system measure time to fill, time in stage, source conversion and offer acceptance?
  • Can recruiters compare job board and sourcing channel performance?
  • Can managers see the current status of every open requisition?
  • Can reports be filtered by date, recruiter, hiring manager, location, job type and candidate source?
  • Can users create custom reports without SQL or vendor assistance?
  • Can data be exported to spreadsheets, business intelligence tools or data warehouses?
  • Are historical stage changes preserved?
  • Can the ATS distinguish between candidate activity, recruiter activity and hiring manager activity?
  • Can the platform report on diversity or equal employment opportunity data while applying appropriate access controls?
  • Are reports based on consistent definitions, such as how the vendor defines "time to hire" and "time to fill"?

Ask to see a report built from your own required metrics. A polished dashboard is less useful if the vendor cannot explain the definitions behind it.

Which Security and Privacy Questions Should You Ask?

An ATS stores resumes, contact details, interview notes, assessments and sometimes sensitive demographic information. Security questions should cover both the platform and the vendor's operating practices.

Ask:

  • Is data encrypted in transit and at rest?
  • Does the ATS support single sign-on and multi-factor authentication?
  • Can administrators create permissions based on user roles?
  • Are permissions available at the company, department, requisition and candidate-record level?
  • Does the system maintain audit logs for access, edits, exports and deletions?
  • Where is applicant data stored and processed?
  • Which subprocessors can access applicant data?
  • How long does the vendor retain candidate records?
  • Can administrators configure retention and deletion rules by location or record type?
  • Can the organization export all data in a usable format before terminating the contract?
  • What is the process for correcting, deleting or restricting access to a candidate record?
  • How quickly does the vendor notify customers about security incidents?
  • What security certifications, independent assessments or penetration testing reports can the vendor provide?
  • What happens to backups after data is deleted?

NIST recommends a risk-based approach to selecting and managing technology suppliers and emphasizes controls that protect confidentiality, integrity and availability. Use that principle to ask for evidence instead of accepting general statements such as "your data is secure."

Which Implementation and Support Questions Should You Ask?

Implementation depends on clear ownership, complete data migration and enough training for each type of user.

Ask:

  • How long does implementation usually take for an organization of our size?
  • Which tasks will the vendor perform, and which tasks will our team own?
  • What data can be migrated, including candidates, resumes, notes, requisitions, applications and attachments?
  • Will the vendor clean, deduplicate and validate migrated data?
  • Can the vendor provide a test migration before launch?
  • Is a sandbox or staging environment included?
  • Who configures workflows, templates, permissions, integrations and reports?
  • What training is provided for recruiters, hiring managers and administrators?
  • What support channels are available after launch?
  • What are the support response and resolution targets?
  • Does the contract include a service-level agreement?
  • How are product updates communicated and tested?
  • Can the vendor provide two customers with similar hiring complexity as references?

Data migration should preserve relationships between candidates, jobs, applications, workflow stages, notes and documents. A migration that exports only resumes may leave behind the history needed for recruiting operations and reporting.

Which Pricing and Contract Questions Should You Ask?

Compare the complete cost of ownership, not only the advertised subscription price.

Ask:

  • Is pricing based on employees, recruiters, active jobs, applications, candidates, modules or usage?
  • Is there a minimum contract size?
  • Are implementation, migration, training and configuration charged separately?
  • Are job board postings, text messaging, assessments, background checks, e-signatures, AI features or API access extra?
  • Are support and customer success included?
  • What is the expected total cost over three years?
  • How often can the vendor increase prices?
  • Are renewal increases capped?
  • What happens if hiring volume increases or decreases?
  • What are the cancellation, notice and early termination terms?
  • Can the organization retrieve its data after cancellation?
  • Are there fees for data export, API usage or transition assistance?

Request a written quote that separates recurring subscription fees, one-time fees, usage-based charges, optional modules and renewal assumptions.

How Should You Test ATS Vendors Before Choosing One?

Use the same practical test for every shortlisted vendor:

  1. Provide the vendor with two or three representative job descriptions.
  2. Provide sample resumes with varied formats and experience levels.
  3. Ask the vendor to create a requisition and approval workflow.
  4. Test a candidate application on desktop and mobile.
  5. Create interview stages, scorecards and feedback forms.
  6. Run a sample candidate search and screening workflow.
  7. Build the reports your team actually uses.
  8. Demonstrate one HRIS or HCM integration.
  9. Review permissions using recruiter, hiring manager and administrator accounts.
  10. Request the security, pricing, implementation and data export documentation.

Score each area from 1 to 5, but record evidence for every score. If a vendor says a feature is "configurable," ask to see the configuration, identify any professional services cost and understand its effect on implementation time.

What Is the Final Decision Rule?

Choose the ATS that proves it can support your workflow, protect applicant data, produce usable reports and connect with the systems your team already relies on. Give extra weight to candidate accessibility, AI transparency, data export, implementation ownership and three-year cost.

The strongest buying question is simple: Can this system make our hiring process more consistent and measurable without creating new manual work or candidate barriers? A live demonstration using your own requirements will answer that more reliably than a feature checklist.