ATS Buying Checklist for Indian SMBs

Choosing an applicant tracking system (ATS) is one of those decisions that looks small and ends up shaping your hiring for years. Pick well and recruiters save hours every week, candidates get a smoother experience, and leadership finally sees a clear hiring funnel. Pick badly and you end up with a tool nobody opens, data trapped in spreadsheets, and a renewal you regret.

This ATS buying checklist for Indian SMBs gives you a structured way to decide whether you need an ATS, define requirements, shortlist vendors, run demos, test with real jobs, check security and cost, and plan rollout. It is written for founders, HR managers, and recruiters at companies hiring anywhere from ten to a few hundred people a year.

Do you actually need an ATS?

Not every company needs one on day one. A shared spreadsheet and a careful inbox can work for a handful of hires a year. Consider an ATS when several of these are true:

• You hire more than a few people per quarter, or run multiple openings at once.
• Candidate data sits in personal inboxes, WhatsApp chats, and several spreadsheets.
• Hiring managers keep asking "where is this candidate?"
• You lose good candidates because replies are slow.
• You cannot say which source produces the best hires.
• Multiple recruiters or agencies work on the same roles.
• You need an audit trail of who reviewed whom and why.
• You want to protect candidate data in line with privacy expectations.

If you recognise most of these, an ATS will pay for itself in time saved. Our guide on recruitment metrics and hiring funnel analytics shows what you can measure once candidate data lives in one place.

Step 1: Define the problem and the outcome

Write down, in plain language, what you want from the ATS. Examples:

1. One place to store every candidate and every conversation.
2. Faster time to first response and time to hire.
3. A consistent process across hiring managers.
4. Easy posting to job boards and the careers page.
5. Reports on sources, funnel stages, and recruiter productivity.
6. A smooth handover from offer acceptance to onboarding.

Rank these. A clear priority list stops you from being swayed by flashy features in demos.

Baseline your current hiring

Capture a few numbers before you buy: openings per quarter, average time to hire, offer acceptance rate, share of hires from referrals, and how many candidates drop out at each stage. You do not need perfect data; rough figures are enough to judge improvement later.

Step 2: Map your hiring workflow

List each stage a candidate passes through, who acts at each stage, and what information moves between people.

A typical flow:

1. Requisition raised and approved.
2. Job created and published.
3. Applications collected from careers page, job boards, referrals, and agencies.
4. Screening: resume review, phone screen, assignment.
5. Interviews: panel scheduling, scorecards, feedback.
6. Decision: debrief and selection.
7. Offer: approval, letter, negotiation, acceptance.
8. Background verification and pre-boarding.
9. Handover to onboarding and payroll.

Mark where delays or errors happen today. Those are the places the ATS must help. For interview design, see our structured interview scorecard guide, and for the stretch between offer and day one, see our offer-to-joining dropoff playbook.

Step 3: Build your requirements list

Split requirements into must-have, should-have, and nice-to-have. Here is a starting list you can adapt.

Core ATS capabilities (usually must-have)

• Job creation with templates and approval workflow.
• Multichannel posting and a hosted careers page.
• Resume parsing that handles Indian formats, multiple languages in names, and common file types.
• Candidate database with search, tags, and filters.
• Customisable pipeline stages per role.
• Email and message templates with automation for acknowledgements and rejections.
• Interview scheduling with calendar sync.
• Structured feedback and scorecards.
• Offer management with approvals and letter generation.
• Role-based access.
• Basic reports.

Collaboration (often should-have)

• Hiring manager portal that is simple enough for non-HR users.
• Comments and mentions on candidate profiles.
• Shared shortlists.
• Agency and vendor access with controlled visibility.
• Referral tracking.

Candidate experience (should-have)

• Mobile-friendly application form with a short, fast flow.
• Application status updates.
• Self-scheduling of interviews.
• Support for resume upload from a phone.
• Clear privacy notice and consent.

Analytics (should-have)

• Funnel conversion by stage.
• Source effectiveness.
• Time in stage and time to hire.
• Recruiter and hiring manager activity.
• Diversity metrics where you collect them lawfully and fairly.

Advanced (nice-to-have unless essential)

• AI-assisted matching, ranking, or summarising.
• Chatbot for candidate FAQs.
• Video interview integration.
• Assessment platform integration.
• Talent pools and campaigns for silver medallists.
• Career site builder with branding options.
• Campus hiring modules. See our campus hiring playbook.

Step 4: Think about integrations

An ATS that stands alone creates double entry. Check how it connects with:

• HRMS and payroll. On offer acceptance, can candidate data flow to employee records without retyping? This reduces errors and speeds onboarding. Our HR tech stack guide explains how the pieces fit.
• Email and calendar. Google Workspace and Microsoft 365 sync is essential for scheduling.
• Job boards and social platforms. Confirm which boards are supported and whether posting is one-click or manual.
• Background verification providers. See our background verification guide.
• Assessment and video tools.
• Messaging. WhatsApp and SMS are common in India; confirm what is supported and under what consent rules.
• E-signature. For offer letters and agreements.
• Single sign-on, if you use it.

Ask for a list of live integrations and request references for the ones you care about. "On the roadmap" is not the same as "available".

Step 5: Understand AI features, and their risks

Many vendors now advertise AI for screening, ranking, and matching. Treat these claims with care.

Questions to ask:

• What exactly does the AI do: parse, summarise, rank, recommend, or auto-reject?
• Can recruiters see why a candidate was ranked a certain way?
• Can you turn features off?
• What data was the model trained on, and is your data used to train it?
• How does the vendor test for bias across gender, caste-associated names, location, institution, and age proxies?
• Is there always a human review before rejection?

AI can save time on summarising resumes or drafting job descriptions. Using it to auto-reject candidates without human oversight creates fairness and legal risk. Our guide on AI resume screening and bias-compliant hiring sets out practical safeguards.

Step 6: Check data protection and security

Candidate data includes names, contact details, work history, and sometimes sensitive information. You are responsible for protecting it.

Evaluate:

• Access control. Role-based permissions, with the ability to restrict who sees which jobs and candidates.
• Audit logs. Records of who viewed, exported, or changed candidate data.
• Encryption. In transit and at rest.
• Data location and sub-processors. Where is data stored, and who else touches it?
• Retention and deletion. Can you set automatic deletion of old candidate data, and can you delete a candidate on request?
• Consent management. Does the application form capture consent and show a privacy notice?
• Export and portability. Can you export your data in a usable format if you leave?
• Backups and incident response. What is the process if something goes wrong?

Align your choices with the principles discussed in our DPDP Act guide for HR and payroll: collect only what you need, use it for stated purposes, and honour deletion and correction requests.

Step 7: Compare pricing the smart way

ATS pricing varies widely. Understand the model before comparing numbers.

Common models:

• Per user per month. Good for small recruiting teams; watch costs if many hiring managers need seats.
• Per active job. Suits companies with few open roles at a time.
• Per employee or headcount. Often used when the ATS is part of an HRMS suite.
• Tiered plans with feature gates.
• Usage-based add-ons such as job board credits, SMS, or assessments.

Ask about:

• Setup and onboarding fees.
• Limits on candidates stored, jobs, or emails.
• Charges for additional hiring manager seats or agency users.
• Cost of integrations and API access.
• Contract length, renewal increases, and cancellation terms.
• Data export fees on exit.

Build a three-year cost estimate, not just year one. Include internal time for setup and training.

Step 8: Build a shortlist

Begin with five to eight vendors from peer recommendations, review sites, and your existing HR tools. Then narrow to three using a quick screen:

• Does it meet all must-haves?
• Does it fit your size and budget?
• Is the vendor responsive and clear?
• Are there reference customers similar to you in size and industry?
• Does it work well for Indian hiring needs: regional job boards, Indian resume formats, WhatsApp, and campus drives if relevant?

If you already use an HRMS or payroll platform, check whether its recruitment module covers your needs. A tightly connected suite can reduce integration pain, though a specialised ATS may offer deeper features.

Step 9: Run demos that actually test the product

Vendor demos are rehearsed. Take control.

Send a scenario in advance

Share two or three real scenarios and ask the vendor to walk through them live:

1. Standard hire. Create a requisition, post a job, receive applications, screen, schedule interviews, collect feedback, make an offer.
2. High-volume role. Handle 300 applications for a support role: bulk actions, filters, templates, and shortlists.
3. Agency and referral. Add a referral, give an agency limited access, and track source.

Evaluate the experience from each side

• Recruiter: how many clicks to move a candidate, send a message, or schedule an interview?
• Hiring manager: can a busy manager review and give feedback from a phone in two minutes?
• Candidate: apply to a job on a mid-range phone and see how long it takes.
• Admin: configure a new pipeline stage or template without calling the vendor.

Score objectively

Create a simple scorecard with weighted criteria such as workflow fit, ease of use, integrations, reporting, security, support, and cost. Have two or three people score independently, then compare.

Step 10: Run a proof of concept

Before signing, ask for a trial or pilot using a real role.

• Load one or two live jobs.
• Import a few hundred past candidates to test parsing and search.
• Invite two hiring managers and a recruiter.
• Test scheduling, feedback, and offer flows.
• Try reporting on real data.
• Contact support with a genuine question and measure response time.

Gather feedback from everyone who touched it. If hiring managers dislike it, adoption will suffer no matter how good the features are.

Step 11: Check references and reputation

Ask for two or three customers with similar size and hiring patterns. Questions to ask them:

• How long did implementation take?
• What surprised you after go-live?
• How responsive is support?
• Has pricing changed at renewal?
• What would you change?
• Did you hit any limits on volume or integrations?

Also look at independent reviews, but read them with care; focus on recurring themes rather than single complaints.

Step 12: Negotiate and review the contract

Key points:

• Term and renewal. Prefer shorter initial terms if you are unsure; negotiate caps on renewal increases.
• Service levels. Uptime commitments and support response times.
• Data ownership and exit. Your data stays yours; the vendor must provide a full export in a standard format on request and delete it on termination.
• Security commitments. Written statements on encryption, access control, and incident notification.
• Pricing protections. Clarity on what triggers extra charges.
• Implementation scope. What is included in onboarding, and what is extra.
• Liability and indemnity. Have your legal advisor review.

Step 13: Plan implementation

A good plan prevents the "bought it, nobody uses it" problem.

Before go-live

• Name an owner. A person who will configure, train, and manage the ATS.
• Define pipelines and templates. Standard stages for most roles; variations only where necessary.
• Prepare job description templates and an approval workflow.
• Configure roles and permissions.
• Set up the careers page with your branding and a clear, short application form.
• Create communication templates for acknowledgement, interview invites, rejections, and offers.
• Import historic data carefully; clean duplicates and remove records that should not be retained.
• Integrate calendars, job boards, and HRMS.
• Define your retention policy and set automatic rules.

Training

• Recruiters: full workflow, bulk actions, reporting.
• Hiring managers: reviewing candidates, giving feedback, and approving offers in a few steps.
• Leadership: dashboards and what to expect.

Short, role-specific sessions work better than one long training.

Go-live and adoption

• Start with a few active roles, then expand.
• Set a clear date after which all candidates must be tracked in the ATS.
• Review usage weekly in the first month.
• Gather feedback and adjust workflows.
• Share early wins: faster response times, fewer lost candidates.

Step 14: Measure whether it works

Compare against your baseline after 90 days and again at six months.

Useful measures:

• Time to first response for applicants.
• Time to hire.
• Stage conversion rates.
• Offer acceptance rate.
• Source of hire and cost per hire.
• Hiring manager satisfaction.
• Candidate feedback.
• Share of hiring activity recorded in the ATS.

If metrics do not improve, find out whether the issue is the tool, the configuration, or the process.

Common mistakes when buying an ATS

Buying for features you will never use

Long feature lists impress but rarely matter. Prioritise what your team does every day.

Ignoring hiring manager experience

If managers find the system clumsy, they will go back to email, and your data will fragment.

Skipping the data and privacy review

Candidate data is personal data. Treat it seriously from the start.

Underestimating setup effort

Pipelines, templates, permissions, and integrations take time. Allow weeks, not days.

Overreliance on AI scoring

Rankings can reflect hidden bias. Keep humans in charge of decisions.

Not planning for exit

Without data portability, switching later becomes painful.

Choosing based on price alone

The cheapest tool may cost more in lost time and weak adoption.

India-specific considerations

• Volume and variety. You may handle high-volume hiring for support and sales roles and specialised hiring for tech and leadership; the ATS should handle both.
• Resume formats and names. Parsers should handle varied formats and naming conventions.
• Notice periods. Track notice periods, buyout possibilities, and expected joining dates; they heavily affect offer-to-joining planning. See our guide on notice period buyout recovery for the payroll side.
• Candidate communication channels. WhatsApp and calls are common; ensure you have consent and a record of conversations.
• Campus and early-career hiring. Look for bulk import, test integration, and event management.
• Statutory and policy needs. Hiring of persons with disabilities, apprentices, and interns may require tracking; see our guides on hiring persons with disabilities and on the Apprentices Act.
• Referral culture. A strong referral module with transparent tracking helps; see our employee referral program design guide.
• Vendor support hours. Confirm support in Indian time zones.

Build vs buy vs extend your HRMS

Some teams consider building a simple tracker on a spreadsheet or low-code tool. This can work for very small volumes, but you will end up recreating features like parsing, scheduling, permissions, and reporting. On the other hand, a full-featured ATS may be overkill for a team making a few hires a year.

A middle path is using the recruitment module in your HRMS, especially if it connects directly to onboarding and payroll. Evaluate it with the same checklist; do not assume that "included" means "sufficient".

A one-page ATS evaluation checklist

Copy this list into your notes.

Fit

• Supports our pipeline stages and approval flows.
• Handles our volume and role types.
• Mobile-friendly for candidates and managers.

Core features

• Job posting and careers page.
• Resume parsing and search.
• Templates and automation.
• Scheduling and feedback.
• Offer management.

Integration

• HRMS and payroll.
• Calendar and email.
• Job boards.
• BGV and assessments.
• E-signature.

Data and security

• Role-based access and logs.
• Encryption and backups.
• Retention and deletion controls.
• Consent capture.
• Export on exit.

AI

• Transparent and optional.
• Human review required.
• Bias testing described.

Commercial

• Three-year cost estimate.
• Clear renewal terms.
• Reasonable onboarding support.

Experience

• Recruiter, manager, and candidate tests passed.
• References positive.
• Support responsive.

A sample requirements document you can copy

Writing requirements down before talking to vendors keeps demos focused. Use a short document with these sections:

1. Context. Company size, number of hires per year, roles hired, locations, and current tools.
2. Goals. The ranked outcomes you want in the next twelve months.
3. Users. Recruiters, hiring managers, interviewers, agencies, and candidates, and what each needs.
4. Workflow. Your stages, approvals, and handovers.
5. Must-haves. The features without which the tool is not viable.
6. Integrations. Systems you need to connect, with priority.
7. Data and security. Your privacy, retention, and access expectations.
8. Budget and timeline. Your range and desired go-live.
9. Evaluation criteria. The weighted scorecard you will use.

Share this with vendors and ask them to respond point by point. The quality of their answers tells you a lot about how well they listen.

Questions to ask every vendor

Beyond features, these questions reveal how the vendor will behave after you sign.

• How many customers of our size and industry do you have in India?
• What does a typical implementation look like, and who does the work?
• How are product updates released, and can we influence the roadmap?
• What is your support model: channels, hours, response targets, and escalation path?
• What happened in your last significant outage or security incident, and what changed?
• How do you handle requests from candidates to access or delete their data?
• Which parts of the product are built by you and which rely on third parties?
• What are the most common reasons customers leave you?

A confident, specific vendor will answer plainly. Vague or defensive answers deserve weight in your scorecard.

Designing the candidate experience inside the ATS

Your ATS shapes how candidates feel about your company. Small choices matter.

Keep the application short

Every extra field reduces completion. Ask for the essentials first, such as contact details and resume, and gather more detail later for shortlisted candidates. Test the form on a phone with a weak connection.

Communicate at every stage

Set up automatic acknowledgements, status updates, and rejection messages that are respectful and timely. Candidates who hear nothing form a poor view of the employer, even if they were never a fit. Personalise templates with the role, the stage, and a contact name.

Make scheduling effortless

Offer self-scheduling with real calendar availability, clear joining links for virtual interviews, and automatic reminders. This reduces no-shows and saves recruiters hours of back and forth.

Give feedback where you can

Short, constructive feedback to candidates who reached late stages builds goodwill and a stronger talent pool. Use templates but allow personalisation.

Respect privacy

Explain how long you keep data, why you collect it, and how candidates can request correction or deletion. Make the notice easy to find rather than hiding it in fine print.

Using ATS data to improve hiring

Once the system is live, use the data. A monthly review of a few views will show you where hiring is stuck.

• Funnel view. Which stage loses the most candidates? If many drop after the first call, your pitch or compensation may be off.
• Source view. Which channels produce interviews and hires, not just applications? Move budget toward what works.
• Speed view. How long do candidates wait at each stage? Long gaps often sit with busy interviewers or slow approvals.
• Interviewer view. Do some interviewers always reject, or never reject? Calibration sessions can fix this.
• Offer view. Why are offers declined? Capture reasons and feed them into your compensation reviews. See our salary benchmarking guide for the pay side of the story.

Share a one-page summary with leadership each quarter, so hiring is treated as a managed process rather than a series of urgent requests.

Frequently asked questions

1. When should a small company start using an ATS?

When hiring volume or complexity makes spreadsheets and inboxes unreliable: for example, several concurrent openings, multiple interviewers, or candidates getting lost. Many companies begin when they hire regularly through the year.

2. How much does an ATS cost for an Indian SMB?

Pricing varies widely by model, features, and number of users. Ask vendors for a written quote and a three-year estimate, including onboarding and add-ons. Avoid relying on a single published number as pricing changes often.

3. Is AI screening safe to use?

AI can help with summarising and organising, but automatic rejection without human review carries fairness and legal risk. Look for transparency, the ability to disable features, and documented bias testing, and always keep a human decision-maker.

4. How long does it take to implement an ATS?

For a small team with clear workflows, a basic rollout can take a few weeks. Integrations, data migration, and multiple pipelines extend the timeline. Plan a pilot with a few roles before full launch.

5. Should the ATS integrate with payroll and HRMS?

Ideally yes. Passing accepted-offer data directly into employee records reduces errors and speeds onboarding. At minimum, ensure you can export and import data cleanly.

6. How do we handle candidate data after a hiring process ends?

Define a retention period, inform candidates in your privacy notice, and delete or anonymise data once the purpose has ended, unless the candidate consents to be kept in a talent pool. Confirm requirements with your legal advisor.

7. What if our hiring managers refuse to use the ATS?

Keep their experience simple: mobile-friendly review, quick feedback forms, and email-based actions where possible. Involve them in the pilot, and show that their input leads to faster hires.

8. Can we switch ATS vendors later?

Yes, but plan for data export and clean mapping. Insist on data portability in the contract so you are not locked in.

Conclusion

The right ATS is the one your recruiters, hiring managers, and candidates will actually use. Begin with outcomes, map your workflow, build a prioritised requirements list, test with real scenarios, check privacy and security, compare three-year costs, and run a small pilot before committing. Keep humans in control of hiring decisions, even when AI features help with the busywork.

If you want hiring that connects smoothly to onboarding, attendance, and payroll, CozyHR can help you keep candidate-to-employee data in one place and reduce handover errors. Explore CozyHR and see how a connected workflow can speed up your next hire.

This article offers general guidance and is not legal advice. Please review privacy, employment, and contract requirements with a qualified professional.