Who this is for
How to choose an applicant tracking system starts with your hiring process, not a demo. The tool has to record who moved a candidate, why, and what happens next. If you cannot describe those steps on one page, fix that first. A vendor cannot guess your process from a feature list.
This checklist is for founders, HR leads, and operations managers buying an ATS for the first time or replacing one that no longer fits. It suits teams hiring a handful of people a year and teams with several open roles across departments. The same checks apply, but small teams can skip features they will not use.
Read it before you book demos. You will get more from each demo if you bring real job descriptions, your current pipeline stages, and the reports your finance or leadership team asks for.
Before you begin
Write down your current hiring path from application to accepted offer. Include every handoff: recruiter screen, hiring manager review, team interview, offer approval, and onboarding handoff. Name the person who owns each step and the reason a candidate can be rejected at that step. This list becomes your test script.
Collect the systems the ATS must talk to. Check your calendar, email, HRIS, payroll, e-signature, background check, and careers page setup. Note whether you use Google Workspace or Microsoft 365, and whether your company requires single sign-on. Ask security what data can leave your network and where candidate records may be stored.
Decide how you will measure success. Common measures are time to hire, source of hire, stage conversion, offer acceptance, and interviewer feedback completion. Pick three you will actually review each month. If a report cannot be built from the fields you collect, the ATS will not fix it later.
Set a budget range and a decision date. Include implementation time, admin training, and the cost of any add-ons you need, such as job board posting, SMS, or background checks. Keep the list of must-haves short. A long list invites demos that show everything and prove nothing.
The checklist
Use the checklist below as a scoring sheet. For each item, ask the vendor to show the workflow live, not in a slide. Then ask your own admin to do it in a trial account. The second test matters more because it shows how much training and clicking the tool requires.
Score each item as must-have, nice-to-have, or not needed. If a must-have is missing, stop. Do not plan to bridge a core gap with spreadsheets unless you accept the extra work and the reporting blind spot. Watch for add-on modules that are required for basic steps.
Bring two roles to the demo: one high-volume role and one specialized role. Run the same steps for both. The high-volume role tests speed and bulk actions. The specialized role tests custom fields, interview kits, and approval steps.
- Map pipeline stages with clear exit criteria, and confirm the ATS lets you rename, reorder, and add stages without vendor help.
- Check that the careers page and job board feeds cover the boards you use, with a branded page and a clean apply flow on mobile.
- Test resume parsing from email and bulk upload from a spreadsheet, including duplicate candidates and odd file names.
- Confirm role-based permissions so interviewers see only assigned candidates and HR controls offers, exports, and deletion.
- Review calendar scheduling, time zone handling, reminders, reschedule links, and the candidate confirmation email before you commit.
- Ask for structured scorecards and interview kits by role family, with required fields and a clear submit deadline.
- Check the offer approval flow, versioned offer letters, e-signature status, and the handoff to onboarding or HRIS.
- List the reports you need, then ask the vendor to build time to hire, source, stage conversion, and rejection reasons in the demo.
- Test search, tags, saved lists, and the talent pool, including how consent status and retention rules are tracked.
- Confirm integrations for email, calendar, HRIS, payroll, background checks, and e-signature, and ask whether they are native or middleware.
- Ask about SSO, audit logs, data export, deletion requests, and the admin guide you will get after go-live.
- Run a trial with a real job, three fake candidates, one rejection, one offer, and one report export.
- Check support hours, response path, implementation plan, and who trains your recruiters and hiring managers.
What good looks like
A good ATS makes the next step obvious. A recruiter opens a candidate, sees the stage, the last note, the scorecards, and the next action. A hiring manager gets a reminder and submits feedback from a phone without a login puzzle. An admin can add a rejection reason or change an email template without opening a ticket.
Reports should match the process you designed. Time to hire should show where time is spent, not a single number. Source data should survive the apply flow. Stage conversion should use the same stages your team uses in reviews. If a report needs a spreadsheet cleanup every month, the setup is wrong.
The best fit is usually the tool your team will use without a manual. A larger suite may win on integrations and controls, but it can slow a small team down. A lighter tool may be faster to start, but check its export, permissions, and reporting before you rely on it. The trade-off is real, so choose the one that matches your hiring volume and admin capacity.
Good implementation includes a written admin guide, recruiter training, and a plan for the first live role. You should know who owns the system after launch, how changes are approved, and how candidates are told what happens next.
What to do next
Shortlist two or three systems that passed the must-have checks. Give each vendor the same job descriptions, stages, and report list. Book a working session, not a sales presentation. Ask your recruiter and one hiring manager to join and try the workflow themselves.
Run a paid trial or a sandbox with a real job. Import a small set of candidates, move them through every stage, send an offer for approval, and export the reports. Check the candidate emails and the mobile experience. Time how long each step takes.
Before you sign, confirm the implementation dates, data import plan, training hours, support channel, and exit terms. Ask for the admin guide and a sample report. Check your security review and data processing terms. A good vendor will answer plain questions without a slide deck.
If you want the setup handled, Cloudverg's Recruiting system implementation package is $9,500 at a fixed price and runs 3 to 4 weeks, starting within 10 business days. It is one option among others. A vendor-led setup or your own admin can also work if you have the time and the process written down.
Frequently asked questions
What features should an applicant tracking system have?
At minimum, it needs pipeline stages, a careers page, job board posting, candidate search, interview scorecards, scheduling, offer approval, permissions, and reports on source, time to hire, and stage conversion. Add integrations for your calendar, email, HRIS, and e-signature. The exact list depends on your hiring volume and process.
How long does it take to implement an ATS?
A small team with a simple process can go live in a few weeks if the stages and reports are already defined. Larger teams need more time for data import, integrations, security review, and training. The vendor's implementation plan should name dates and owners, not phases alone.
Do small companies need an applicant tracking system?
If you hire a few people a year and your inbox works, you may not need one. Once several people review candidates or you need to prove why a hire was made, a shared system saves time and keeps records straight. Choose a light setup and skip features you will not use.