Questions to ask before changing your ATS vendor

Ask these ATS vendor questions before changing platforms. Compare workflows, hiring manager adoption, candidate experience, integrations, reporting, AI, pricing, and implementation support.

Alice Dodd
Content Manager
Article
7
July 21, 2026
This is the default text value

TL;DR Before changing your ATS vendor, test how each platform handles your real hiring process, not just the demo. Focus on workflow flexibility, hiring manager adoption, candidate experience, applicant volume, automation and AI, reporting, integrations, implementation, pricing, compliance, and support. Red flags include rigid workflows, unclear pricing, weak reporting, vague implementation support, unproven integrations, and AI recommendations that cannot be explained or overridden.

Changing your ATS reaches far beyond the software itself. It changes how recruiters work, how involved your hiring managers are, how candidates experience your brand, and whether your hiring data is clean enough to trust. 

Get it right and the whole team moves faster. However, get it wrong, and you've bought yourself two years of workarounds, side channels, and reports nobody quite believes.

The hard part is that most platforms look strong in a demo. The friction shows up later, once your real workflows, your real hiring managers, and your real applicant volume hit the system. The way to see past a polished demo is to ask better questions.

This guide gives you the questions to ask before changing your ATS vendor, why each one matters, what a good answer sounds like, and the red flags worth walking away from. 

Use it as a checklist during demos and stakeholder conversations, and if you want the full step-by-step buying process, pair it with our ATS buyer's guide.

Quick checklist of questions to ask before changing your ATS vendor

Scan this first. Each question is designed to make the vendor show you how the system handles your hiring, not tell you what it can do in theory.

Category
Question to ask
Why it matters
Red flag answer Good answer
Workflow fit
Can we configure different hiring workflows by role, department, region, or brand?
Different hiring teams need different processes. One rigid workflow forces teams to work around the system.
"Most customers use one standard workflow." "Yes, you build and adjust distinct workflows for each team yourself, and we'll set up your real process in the demo."
Hiring manager adoption
Can hiring managers review candidates, complete scorecards, and give feedback without full admin access?
Hiring manager adoption often decides whether the ATS works in practice.
"They can use email notifications instead." "Yes, hiring managers get a simple dedicated view to review candidates and leave structured feedback, with no per-seat charge."
Candidate experience
Can we control the application flow, candidate communication, and careers site experience?
Candidate experience affects completion rates, employer brand, and offer acceptance.
"The candidate experience is mostly fixed."
"Yes, you control the careers site, application steps, and automated messages, and can tailor them by brand or region."
Applicant volume
How does the system help teams prioritize candidates when a role receives hundreds of applications?
High-volume roles need structure without removing recruiter judgment.
"Recruiters can manually filter the list." "The system organizes and surfaces candidates against your criteria, and recruiters stay in control of who moves forward."
Automation and AI
How does automation or AI support prioritization while keeping humans in control? AI should support recruiter decisions, not replace them.
"The algorithm decides which candidates are best."
"Automation handles repeatable admin, AI surfaces and explains recommendations, and recruiters can override them at any point."
Reporting Can reporting show pipeline health, bottlenecks, source quality, and hiring manager responsiveness? TA leaders need visibility beyond basic applicant counts.
"You can export data and build reports manually in Excel."
"Built-in dashboards show all of that in real time, filtered by the cut you need, without exports."
Integrations Which integrations are native, which are custom, and which cost extra?
Integrations affect implementation effort and long-term admin.
"We have an API, so anything is possible." "Here's our list of native connectors, we'll show one working in your demo, and we'll flag anything
Implementation What does migration involve, and who owns each part of implementation? Switching ATS platforms fails when data, workflows, and change management are under-scoped. "Implementation is simple for everyone." "You get a named implementation manager, a mapped-out plan with clear ownership, and you keep hiring throughout."
Pricing What's included in the base contract, and what costs extra? Hidden fees change the total cost of ownership. "We can discuss that later in procurement." "Here's what's included, what's usage-based, and how pricing changes as you grow, in writing."
Support What support is included during and after implementation? Adoption depends on enablement, troubleshooting, and ongoing support. "Support depends on your package." "Every customer gets named support and a clear response-time commitment, during rollout and long after."

Questions about workflow fit

The best ATS for your team is the one that fits how your hiring works day-to-day. A long feature list counts for little if it doesn't match your process. When every role, department, and region is forced through the same workflow, teams quietly rebuild their real process outside the system, and that's where your data starts to leak.

Ask vendors to prove the system bends to your process, not the other way around:

  1. Can we configure different hiring workflows by role, department, region, brand, or hiring type?
  2. Can recruiters make workflow changes themselves, or does every change need vendor support?
  3. Can approval steps, scorecards, automations, and candidate communications vary by role or team?
  4. Can the platform run multiple hiring processes without messy workarounds?
  5. Can we test how our real hiring process would work inside the system during the demo?

A strong vendor will reshape a workflow live in the demo and confirm your team can make changes later without raising a support ticket every time hiring evolves.

Questions about hiring manager adoption

Hiring manager adoption is one of the clearest signals of whether an ATS will work in practice. When hiring managers can't easily review candidates, leave feedback, and stay in the loop, recruiters end up chasing updates by hand, and the hiring record fills with gaps.

  1. Can hiring managers review candidates without full admin access?
  2. Can hiring managers complete scorecards and give feedback inside the ATS?
  3. Can recruiters see where hiring managers are slowing the process down?
  4. Can hiring managers compare candidates in context, rather than from email threads?
  5. Can the system prompt or remind hiring managers when their input is needed?
  6. Can hiring teams collaborate without moving decisions into Slack, email, or spreadsheets?

Watch the pricing model here too. When a vendor charges per hiring-manager seat, involving more managers costs more, so teams involve fewer of them, and the work drifts back out of the system.

Look for a vendor that gives every hiring manager a clean, dedicated way in, with structured scorecards that keep feedback in one place rather than scattered across inboxes.

Questions about candidate experience

Candidate experience does more than protect your brand. It affects application completion, candidate trust, offer acceptance, and how consistently your organization shows up across every role and team. Roughly 60% of candidates abandon a job application when it's too long or complex, so friction in the flow is friction in your pipeline.

  1. What does the candidate experience look like from job search to application to communication?
  2. Can we customize the careers site and application process to reflect our employer brand?
  3. Can candidates apply easily on mobile?
  4. Can we control automated candidate emails and status updates?
  5. Can we create different candidate experiences for different brands, departments, or regions?
  6. Can the platform support multilingual or localized candidate experiences where needed?

A good platform gives you a fast, on-brand application, keeps candidates informed automatically, and lets you vary the experience by brand, region, or language where you need it. Ask to walk through a real application on a phone, start to finish, during the demo.

Questions about applicant volume and screening

High applicant volume is a real operational problem, not a vanity metric. You post a role on Friday, come back Monday to several hundred applications, and still need to find the strongest people without reviewing every profile from scratch. A good ATS helps recruiters prioritize and organize candidates while keeping human judgment in the loop.

  1. How does the ATS help recruiters manage high applicant volume?
  2. Can recruiters quickly identify candidates who meet the role criteria?
  3. Can the system support knockout questions, structured screening, or role-specific criteria?
  4. Can we prioritize candidates without relying on opaque AI scoring?
  5. Can recruiters review candidate context before deciding who moves forward?
  6. What happens when a job goes live on Friday and has hundreds of applicants by Monday?

The answer you want describes structure plus control: structured screening and clear criteria that surface the right candidates, with recruiters making the call. Be wary of any answer that hands the decision to a black-box score.

Questions about automation and AI

Automation should take the repeatable admin off your team's plate: reminders, status updates, candidate communication, approvals, and follow-ups. AI should help with the work that needs judgment, such as reading a resume, summarizing an interview, or surfacing a shortlist. The distinction matters, and the vendors worth shortlisting can explain it clearly.

  1. What parts of the hiring process can be automated?
  2. Can recruiters configure automations themselves?
  3. How does the platform use AI, if at all?
  4. Can the vendor explain how AI recommendations are generated?
  5. Can recruiters override AI-assisted recommendations?
  6. Are candidates told when AI is used in screening, scoring, or recommendations?
  7. What safeguards exist against bias or black-box decision-making?
  8. Does the system keep humans in control of candidate decisions?

The strongest answers keep humans in charge: AI surfaces insights, recruiters and hiring managers decide, and every recommendation can be explained and overridden. Ask the deeper question too, which is whether the AI will have clean data to work with. AI in hiring only delivers when the whole team uses the system, because that's what keeps the data complete.

This is the argument Pinpoint AI is built around: its AI is opt-in, it never trains external models on your data, and its scoring works from the input you give it rather than inferring patterns from your past hiring, so you can always see why a candidate scored the way they did. For a wider view of how platforms compare, see our guide to the best applicant tracking system.

Questions about integrations

Integrations can make or break implementation. "We have an API" isn't the same as a reliable, supported integration that works with the tools your team already relies on. Get specific about what's native, what's custom, and what carries a cost.

  1. Which HRIS, payroll, assessment, background check, calendar, job board, and communication tools does the ATS integrate with?
  2. Which integrations are native?
  3. Which integrations need custom work?
  4. Which integrations cost extra?
  5. Does the system connect to local or regional job boards where you need them?
  6. How does candidate and hiring data move between systems?
  7. What happens if an integration breaks?
  8. Can the vendor show an integration working during the demo?

A confident vendor will show you a live connection rather than describe a hypothetical one, and hand you a written list of what's native, what's custom, and what costs extra.

Questions about reporting and visibility

An ATS should show you where hiring is working and where it's stuck. When reporting depends on manual exports, bottlenecks stay hidden, source quality is guesswork, and every stakeholder conversation starts with a spreadsheet nobody fully trusts.

  1. Can the ATS show pipeline health by role, department, source, brand, region, or hiring manager?
  2. Can we see where candidates are dropping off?
  3. Can we measure source quality, not just source volume?
  4. Can we track hiring manager responsiveness?
  5. Can we report on time-to-hire, time-in-stage, and conversion rates?
  6. Can we build reports without exports or manual spreadsheets?
  7. Can reporting serve different stakeholders, from recruiters to TA leaders to executives?

The answer you're listening for is real-time, built-in reporting that rolls up cleanly across teams and regions. If the honest answer is "export it and build the report yourself," that's an admin tax you'll pay every week.

Questions about implementation and migration

Changing ATS vendors is as much a process change for recruiters, hiring managers, and candidates as it is a technical migration. Understand what implementation includes, what it doesn't, and what the vendor expects your internal team to own before you sign.

  1. What does the implementation process involve?
  2. Who owns workflow setup, data migration, integrations, and training?
  3. How long does implementation usually take for a team like ours?
  4. What data can be migrated from our current ATS?
  5. What data can't be migrated?
  6. How do you handle duplicate, incomplete, or outdated candidate records?
  7. How do you support hiring teams during the transition?
  8. Can we keep hiring while migration is in progress?
  9. What does onboarding look like for recruiters and hiring managers?
  10. What support is available after launch?

Strong vendors scope this honestly: a named point of contact, a clear plan with owners on both sides, integrations remapped and tested before go-live, and a way to keep hiring while you migrate. For a fuller walkthrough, see the ATS implementation guide.

Questions about pricing and total cost

Evaluate ATS pricing on total cost of ownership, not the base subscription alone. Confirm the contract structure, implementation fees, migration costs, support tiers, integration fees, seat limits, and add-on modules before you choose.

  1. What's included in the base subscription, and what's charged separately?
  2. Are hiring managers included, or charged as seats?
  3. Are automations and integrations included?
  4. Are implementation and data migration included?
  5. Are support tiers separate?
  6. Are there limits on active jobs, candidates, brands, workflows, or users?
  7. How does pricing change as we grow?

The goal is no surprises. A vendor that defers pricing detail to "later in procurement" is a vendor whose costs stack up after you've committed. Ask for the full picture in writing, including how the model behaves as your hiring scales.

Questions about compliance and data privacy

Compliance and data privacy matter more as teams grow, hire across regions, or manage multiple entities. Ask vendors to show how privacy, retention, access permissions, and security work inside the platform, rather than pointing at a policy page.

  1. How does the ATS handle candidate consent and data privacy?
  2. Can we configure data retention policies?
  3. Can candidate data be deleted, anonymized, or archived by policy?
  4. Where is candidate data stored?
  5. Does the vendor support GDPR or other regional privacy requirements where relevant?
  6. Can access permissions be set by role, team, region, or department?
  7. Can the vendor provide security documentation, certifications, or audit information?
  8. How are AI features governed when they affect screening, scoring, or recommendations?

Look for named certifications, a clear answer on where candidate data is stored, and a straight explanation of how AI features are governed. Vague answers on any of these are a reason to keep asking.

Questions about support and scalability

The right ATS works for the team you have today and the team you're becoming. Ask how the platform scales as hiring volume, team structure, workflow complexity, and stakeholder needs change.

  1. What support is included during implementation and after launch?
  2. What's the expected response time, and is support available across time zones?
  3. How are product updates communicated?
  4. Can the platform support more teams, roles, regions, or brands as we grow?
  5. Can the system handle new workflows without a rebuild?
  6. What happens when we need to add hiring managers, workflows, or integrations later?

You want a partner for the long haul, not just a login. Ask for named support, a clear response-time commitment, and evidence that the platform keeps improving, so it grows with your hiring instead of holding it back.

Red flags when evaluating an ATS vendor

The wrong ATS often looks good during the sale and creates friction after go-live. Watch for these warning signs, and dig into any that come up:

  • The demo only shows a simple workflow, not the complexity of your real hiring process.
  • Hiring manager adoption is assumed rather than shown with real examples.
  • The vendor can't demonstrate how recruiters and hiring managers collaborate inside the system.
  • Workflow changes need vendor support or a technical ticket every time.
  • Reporting depends on data exports or manual spreadsheets for anything useful.
  • Pricing is unclear, or significant add-on costs surface late in the process.
  • Integrations are described as "possible" but never shown or proven.
  • The vendor can't clearly explain implementation, migration, or security.
  • AI recommendations can't be explained, audited, or overridden by recruiters.

For a fuller list of what to watch for and what good looks like, see our guide to ATS vendor red flags and green lights.

How to choose an ATS software

Choosing an ATS should start with your hiring process, not the vendor's feature list. Before you compare platforms, get clear on what your current system can't support, which workflows need to change, and which stakeholders need better visibility or control.

A good ATS helps recruiters move faster, makes it easy for hiring managers to take part, keeps candidate communication consistent, and gives TA leaders the reporting they need to improve hiring over time. Use the questions in this guide as your checklist during demos and vendor conversations. For the full buying process, from scoping needs through to contract review, work through our ATS buyer's guide.

The most important questions to ask before switching ATS vendors

If you're replacing an existing system rather than buying your first one, prioritize the questions that expose switching risk. In order:

  1. Migration. What data can move, what can't, and how are duplicate or outdated records handled?
  2. Existing workflow gaps. Which parts of your current process are broken, and can the new system fix them rather than recreate them?
  3. Implementation ownership. Who owns setup, migration, integrations, and training, and what does your team need to resource?
  4. Data quality. Will the migration clean up your data, or carry the mess across?
  5. Integrations. Are your existing connections remapped and tested before go-live?
  6. Hiring manager adoption. Will the switch improve participation, or repeat the reasons managers routed around the old system?
  7. Change management and support. How does the vendor support recruiters, hiring managers, and candidates through the transition?
  8. Continuity. Can you keep hiring while you migrate?

Switching is as much a change-management project as a technology one. Our guide on what most teams underestimate when switching ATS covers the parts that catch teams out.

The most important ATS questions for in-house TA teams

In-house talent acquisition teams have a different set of priorities from staffing agencies or single-role buyers. If you're hiring across an organization, weight your evaluation toward:

  • Workflow control. Can you configure and adjust hiring processes by role, department, region, and brand yourself?
  • Hiring manager adoption. Will managers actually use it to review candidates and leave structured feedback, or push work back into email?
  • Candidate experience. Can you deliver a consistent, on-brand experience across every team and location?
  • Reporting visibility. Can you see pipeline health and bottlenecks across the whole organization, in real time?
  • Multi-stream hiring. Can one system handle high-volume, professional, early-career, and executive hiring without forcing them into the same mold?
  • Applicant volume. Does it help recruiters prioritize at scale while keeping judgment human?
  • Automation and recruiter control. Does automation remove admin while recruiters keep control of decisions?

A platform that adapts to hiring workflows across industries and hiring types will keep fitting as your organization grows. A system built for one shape of hiring quietly falls short.

Choose the ATS that fits how your team hires

The best ATS fits your hiring model, helps recruiters and hiring managers work in one place, supports a strong candidate experience, and gives your team enough control to adapt as hiring changes. A long feature list won't do any of that on its own.

If you're changing ATS vendors, use the questions in this guide during demos and stakeholder conversations. The goal goes beyond managing applicants. Choose the system your team will actually use.

Meet the Pinpoint platform and see how it helps in-house hiring teams manage candidates, workflows, hiring manager collaboration, reporting, and candidate experience in one place.

FAQs

What questions should I ask an ATS vendor?

Ask about workflow flexibility, hiring manager adoption, candidate experience, applicant volume, automation, AI, reporting, integrations, implementation, pricing, data privacy, and support. The best questions make the vendor show how the system handles your real hiring process rather than describe it in theory.

What should I ask before changing my ATS?

Ask what isn't working in your current process, which workflows need to change, how hiring managers will use the new system, what data needs to migrate, which integrations are required, and how the vendor will support implementation and change management.

How do I choose an ATS software?

Choose an ATS based on your hiring model, workflow complexity, hiring manager needs, candidate experience, reporting requirements, integrations, implementation support, and total cost of ownership. Don't choose on the longest feature list. Start with your process, then find the system that fits it.

What are the red flags when evaluating an ATS?

Red flags include unclear pricing, rigid workflows, weak hiring manager adoption, limited reporting, vague implementation support, thin integrations, opaque AI features, and demos that don't reflect your real hiring process.

What should I ask about AI in an ATS?

Ask how AI is used, whether recommendations are explainable, whether recruiters can override AI-assisted suggestions, how bias is monitored, whether candidates are told when AI is used, and how the platform keeps humans in control of decisions.

Author

Alice Dodd
Content Manager

With over seven years in B2B SaaS, Alice creates data-driven content that makes complex topics simple and engaging. She believes every good story (no matter how dry or technical) should feel human, useful, and built on insight.

Manage every hiring stream in one place

Support multiple roles, teams, and workflows in one platform, with the clarity and consistency your team needs.
G2
4.8
Capterra
4.8
SSR
4.8