Applicant Tracking System Features Checklist for Small Teams

An applicant tracking system for a small team should do six things well: collect applications in one place, move candidates through clear stages, keep notes and interview feedback together, let several people work without overwriting each other, export your data, and stay affordable. Everything else is optional, and often unused.

Why a checklist beats a feature list

Every applicant tracking system sells itself with a long feature page, and long pages make small teams feel they must buy a lot. In practice a team of two to ten people uses a short core of features every week and a long tail almost never. The cost of a long tail is real: more screens to learn, more settings to maintain, and often a higher price. A checklist turns the question around. Instead of asking what the product can do, you ask what your hiring actually needs, then check that the product does those things well and shows you how. This guide gives you that checklist for small and mid-size teams, split into must-haves, nice-to-haves and things you can safely skip. It also gives you a weighted scoring table, a worked example with example numbers, and a list of common mistakes. For a plain definition of the category, see our guide to /applicant-tracking-system, and for the wider tool landscape see /recruitment-software. Where a feature is described here, it is described in general terms. Always check each vendor's current pricing and features on their own site, because both change, and a checklist is only as good as the facts you put into it.

Must-have features for a small team

These are the features where a gap will hurt within the first month. First, one place for applications. Candidates should arrive by an apply page, by email, or by upload, and land in the same list, not in three inboxes. Second, a visible pipeline with stages that you can rename, so everyone sees where each person stands. Third, a candidate record that holds the CV, notes, messages and decisions, so the history does not live in someone's head. Fourth, structured interview feedback, ideally one scorecard per role that every interviewer fills in, so comments can be compared. Fifth, shared access with sensible permissions, so a hiring manager can see a shortlist without seeing everything. Sixth, search and filters that work, so you can find a person from last year. Seventh, export of all your data in a standard format, because you will want to leave one day and you should be able to. Eighth, a way to remove or anonymise a candidate when asked. Ninth, a duplicate check, so the same person is not worked twice. If a tool misses any of these, treat it as a serious gap rather than a small one, and ask the vendor in writing how they handle it.

Nice-to-have features worth paying a little for

These raise speed and quality, but a team can live without them at first. Self-service interview scheduling, where candidates pick a time from a link, saves a surprising amount of email. Scoring of CVs against your must-haves, with the evidence shown, speeds up the first read, provided a person still decides. Email templates and automatic confirmations make the candidate experience more consistent. A hiring manager review page lets managers vote on a shortlist without learning the whole tool. Offer letter creation with approval and e-signing keeps the last step in the same place as the rest. Simple reports, such as time in stage and source of hires, help you spot where candidates drop out. An API or webhooks let other tools react to events when you need that. Calendar sync is useful if your interviewers live in their calendars. You do not need every one of these. Pick the two or three that remove your own biggest chore, and treat the rest as a bonus. For how scoring works and how to judge it, see /ai-resume-screening, and for what happens at the offer stage see /offer-letter-template.

Features you can usually skip

Large vendors build for large customers, and some features only pay off at scale. Skip, unless you have a specific need, deep approval chains with many levels, custom fields by the dozen, complex career-site builders, advanced analytics suites, tight HRIS and payroll integrations, and built-in video interviewing, since you probably already have video calls. Skip anything that needs a dedicated administrator, because you will not have one. Be careful with multiposting. Posting a job to many boards in one click is attractive, but it depends on each board's rules and fees, and many small teams post to two or three boards by hand without trouble. Also treat talent pools and sourcing databases with caution. They are useful if you hire the same role repeatedly, and clutter if you do not. The rule is simple: if you cannot name the person who will use a feature and the week they will use it, leave it out of your scoring or give it a weight of zero. Unused features still cost you in training time and in screens that distract from the few that matter.

A weighted checklist you can copy

Score each tool from zero to three on each line: zero means missing, one partly, two yes, three yes and shown working on your own data. Weights are examples, so change them to match your needs.

The example weights add to 28, so the top possible total is 84. Any zero on a weight-3 line should be discussed even if the total is high. Fill the sheet in alone first, then with a colleague, and keep the sheets so you can explain the choice later. If two people score a line very differently, that is a sign the vendor's answer was unclear, so go back and ask again.

Compare by job to be done, not by brand

When two tools both claim the whole list, compare how each one handles your real jobs. Write four or five scenes from your own week and run each one in a trial. Scene one: a new application arrives by email at night, and you want it in the right job by morning. Scene two: a hiring manager asks for the three best candidates, and you need to share them without exposing the rest. Scene three: two interviewers disagree, and you need their feedback side by side. Scene four: a former candidate asks you to delete their data. Scene five: you want to move to another tool next year. Time how long each scene takes and note where you got stuck. This turns an abstract feature list into a lived comparison, and it is hard for a sales page to fake. The table below shows how to record it, with example results only.

A scene that one tool cannot complete at all is more informative than ten that both complete quickly.

Worked example with example numbers

The numbers here are examples only. A 25-person company hires about ten people a year, across three open roles at a time, with one recruiter, one office manager and four hiring managers involved. They want to stop tracking candidates in a shared spreadsheet. They list their pain points: lost emails, no record of interview feedback, and managers asking for status. From those they weight the checklist: single inbox, scorecards and manager access each get 3, scheduling gets 2, offers get 1, and sourcing databases get 0. They test two tools on one real role, using the five scenes above. Tool A scores 62 of 84, with strong scorecards and a fast export but a plain offer step. Tool B scores 51, with a larger feature list but no shared scorecards and a harder export. Tool B costs less per month, yet it fails two weight-3 lines. They choose Tool A on a monthly plan, set a review date after two roles, and note down what they will check: time from application to first review, and whether managers actually open the shortlists. The result of the checklist is not a perfect tool. It is a decision they can explain and revisit when facts change.

Common mistakes when choosing an ATS

The first mistake is buying for the company you hope to be in three years. Choose for the next twelve months and keep the exit easy. The second is paying for modules you will not use, such as analytics or sourcing, because they came in a bundle. The third is skipping the data question: ask how to export everything, and how candidates are deleted. The fourth is trusting a demo on the vendor's tidy data instead of your messy files. The fifth is ignoring the hiring managers, who must use the shortlist pages or the tool will become a place only the recruiter looks. The sixth is treating a score as a decision. Any scoring feature should show its evidence and leave the choice to a person. The seventh is starting a long contract before one real role has run through the tool. The eighth is forgetting migration, covered in our guide to moving from a spreadsheet to an ATS. The ninth is not setting a review date. The tenth is believing any claim without checking it, including claims in this article. Look at each vendor's own pages for current details, and ask for anything important in writing.

Where Rezumz fits

Rezumz is a hiring workspace for small and mid-size hiring teams. In line with the checklist above, it gives you an apply page and screening questions, a CV inbox where candidates can be added by email, import from a CSV, scoring of each CV against the requirements of a job with the supporting CV lines quoted, a shortlist you can show to a hiring manager, self-service interview scheduling, scorecards that each interviewer fills in from a personal link, a debrief, offer letters with approval and electronic signing, and export to a CSV. It also offers an API and webhooks. People make every decision, and the scoring does not reject anyone. Rezumz suits small and mid-size teams, and the Team plan is meant for teams with four or more recruiters. It does not suit large enterprises that need deep HRIS or payroll connections, and it does not do one-click multiposting to job boards. Prices: a free plan with 2 free candidate analyses, then $29 a month, $199 a year, or a limited $499 lifetime option. Team is $79 a month or $699 a year for up to 10 teammates. See /pricing for current details, and /free-applicant-tracking-system for what a free start looks like. You can try the workflow at /demo.

Who this checklist is not for

If you hire two or three people a year and already know every applicant, a spreadsheet and a shared inbox may serve you well, and a dedicated system may be more overhead than help. If you need enterprise controls such as multi-level approvals across many business units, regional legal entities, or tight links to payroll and HR systems, this small-team checklist will under-weight what matters to you, and you should build a longer list with your IT and legal teams. If most of your hiring happens through agencies or through campus drives with thousands of applicants, your priorities will differ again. And no checklist replaces a trial with real work. Use the list to narrow the field to two tools, then let one real role decide. Recruiting rules and data duties differ by country, so check local law before you decide how long to keep records or how to handle automated scoring of candidates.