ATS buying guide for growing companies

Start with one repeated failure: candidates lack an owner, interview arrangements live in separate inboxes, or feedback arrives too late for the debrief. Write down an instance, its consequence and the person responsible for resolving it. Company headcount alone does not tell you which system to buy.

CIPD's public recruitment summary covers defining the role, attracting applicants, managing applications and selection, and making appointments. Use that sequence to check where your team's problem occurs. The decision route below is an editorial planning method, not a validated procurement standard or a promise of better hiring outcomes.^[1]

Repair the process first when the team cannot agree who owns a vacancy, what each stage means or when feedback is due. A new system still needs those decisions. Set owners and trial the revised process before evaluating whether the current tools can support it.

Evaluate an ATS when the process has owners but your tools repeatedly separate candidate records, messages, scheduling or feedback. Choose one representative vacancy and demonstrate the whole sequence. Postpone the purchase when there is no accountable owner, no time to implement, or an unresolved requirement that every shortlisted supplier fails. Record what must change before reopening the decision.

Keep the brief to the decisions a supplier must support. Describe the current process, the first rollout population, hiring activity, recruiter and manager roles, and the calendar and email accounts involved. Identify the internal decision owner and the people who can reject the purchase for a documented reason.

Count recent vacancies, applications, interview appointments and participating managers from your own records. These are planning inputs, not universal thresholds for buying software. A small team hiring several specialist roles may have different coordination needs from a larger company with infrequent recruitment. Include the expected next planning period and label forecasts separately from observed activity.

Name three observable acceptance criteria. For example: a recruiter can identify the next action for a candidate; an authorised manager can review the relevant vacancy without opening unrelated records; and interview feedback stays attached to the candidate after rescheduling. Replace vague requirements such as easy to use with a task, actor, expected result and evidence to retain.

A purchase blocker is a requirement whose failure prevents your agreed rollout. It might be an access boundary, a necessary calendar workflow, a migration constraint or an approved budget limit. A preference improves the experience but can be traded against another benefit. Keep the distinction explicit before anyone scores a demo.

For each blocker, record its owner, test, acceptable evidence and decision deadline. Ask the supplier to show the required workflow in the proposed package and configuration. A roadmap statement, presentation slide or verbal reassurance leaves the requirement unresolved. If the team accepts a temporary manual step, document its owner and review date rather than quietly treating the blocker as passed.

Use the ATS requirements checklist to organise detailed requirements. Use its evidence fields to record the tests, owners and unresolved answers behind your shortlist. Avoid expanding the shortlist merely to find a supplier with the longest feature list. Compare the same essential work across a small set that your team has time to test properly.

Prepare fictional candidate and vacancy details. Start by creating or opening the vacancy, then submit an application, assign ownership, send a message, arrange an interview, record feedback and inspect the accepted-candidate handoff. Choose the steps that reflect your actual process and retain the same script for each supplier.

Include an exception that exposes coordination work: a meeting changes, a recruiter is absent, a manager lacks access, or an applicant has a duplicate record. Ask who receives the next action and where the history remains. Record the observed outcome, package, configuration and any manual step. Do not count a hidden administrator action as a successful manager task.

OPM describes structured interviews using common questions and rating standards. For the feedback portion, check whether your interviewers can record the agreed evidence after the conversation and whether the debrief can find it. An ATS scorecard records post-interview feedback. Evaluate any separate candidate testing requirement separately; a feedback form does not establish that testing capability.^[2]

List which personal or shared mailboxes and calendars the first rollout needs. Name the account owner and internal administrator who can approve the connection. Ask which permissions are requested, whose account sends a message, and what changes when a connected colleague leaves or loses access.

Test an ordinary message and a reply using supplier-approved fictional records or a controlled test environment. For scheduling, observe creation, cancellation, rescheduling and the final meeting link. Check what recruiters and candidates see at each step. A logo on an integration page does not establish that the exact shared-mailbox or scheduling workflow works in your environment.

For each connection, distinguish a standard supported flow from configuration work, a third-party dependency or a proposed integration. Ask who owns failures and how the team notices them. Put unresolved integration tests in the decision record with an owner and a date. Do not make live candidate communication part of a sales demonstration merely to obtain a passing result.

Inventory the records you intend to move and why they are still needed. Include candidate fields, source references, attachments, messages, ownership and relevant dates where they exist. Ask the current system owner what can be exported, and ask each shortlisted supplier what can be imported into the proposed package.

Agree a small representative sample and an expected result before a trial import. Reconcile counts and inspect field meaning, attachment associations and date interpretation. Record excluded history and unsupported fields. A count match alone does not prove that a message belongs to the right candidate or that a former owner has the intended access.

The ATS migration guide covers mapping and reconciliation in depth. During buying, the decision is whether a credible migration path exists, who performs it, what it costs and which limitations the business accepts. Keep the original records under your organisation's approved controls while the migration owner defines acceptance. Do not assume every item should move merely because an export contains it.

Bring the proposed workflow, data categories and participant roles to the people responsible for your organisation's review. Ask suppliers for current contractual and technical evidence covering access, processing locations, retention, deletion, incident handling, support access, backups and exit. Your reviewers decide which obligations and controls apply to your organisation.

Use a real access scenario with fictional records: a hiring manager opens the assigned vacancy and then attempts to open an unrelated one. Inspect what the proposed roles permit and which events the audit history records. Check how an administrator removes access when a manager changes team. A supplier's security document and a configured access test answer different questions; retain both where needed.

Record whether each answer is documented, demonstrated, contractually agreed or unresolved. Do not treat a certification logo or a general security statement as proof of every required control. Ask the responsible reviewer to record remaining conditions before signature. This section is a procurement question set, not legal advice or a determination of compliance.

Request costs for the same term, user groups, hiring activity and required workflows. Separate subscription, implementation, migration, integrations, training, support and exit charges. Ask which limits trigger a different package or additional cost. Record the quote date, currency, assumptions and exclusions, including tax treatment as confirmed by your Finance owner.

Include internal implementation work. Someone must agree stages, clean records, validate permissions, connect accounts and help managers learn the process. Value this time separately using an approach agreed with Finance. A supplier setup fee and your own team's implementation time represent different work. Do not hide either inside an unexplained total.

Use the ATS business case template when preparing the investment decision and the recruitment cost calculator for a defined period of current hiring effort. Keep forecast time savings separate from contracted supplier costs. A shorter demo task does not establish a future payroll saving, and a lower subscription does not resolve a failed access or migration requirement.

Imagine a 150-person company selecting a first rollout for one recruitment team and six hiring managers. It has agreed five purchase blockers: relevant-vacancy access, its required calendar workflow, a candidate sample import, feedback attached to the candidate, and an approved first-year budget. Supplier names A, B and C refer only to invented options.

Supplier A passes all five blockers. Its fictional first-year external cost is 12,000 subscription + 3,000 setup + 1,000 migration = 16,000 currency units. Supplier B quotes 9,000 subscription + 2,000 setup + 1,000 migration = 12,000, but cannot demonstrate the required access boundary. Supplier C totals 14,000, but the calendar test remains unresolved. No price is a CapoFine offer or market benchmark.

The team excludes B from a purchase decision until the access requirement passes. It keeps C pending rather than scoring an unknown as a failure or a success. A can proceed to preference comparison and rollout planning; passing the blockers does not require the team to buy it. The owner may still reject the investment if the expected benefit does not justify the cost and effort.

For a simple preference example, the team assigns weights of 3 for recruiter task completion, 2 for manager feedback and 1 for reporting clarity. It uses an illustrative 0-2 scale: 0 not demonstrated, 1 completed with an agreed workaround, 2 completed as required. A receives 2, 1, 2, giving 3 × 2 + 2 × 1 + 1 × 2 = 10 out of 12. This local scale is a discussion aid, not a validated vendor ranking.

If C later passes every blocker and scores 1, 2, 2, its preference total is 9 out of 12. Compare the underlying observations and the 2,000 cost difference before deciding. Changing reporting's weight from 1 to 3 would give A 14 out of 16 and C 13 out of 16; state the new denominator. Do not use the preference score to average away a failed blocker or to turn missing evidence into a recommendation.

Name the rollout owner, participating recruiters, manager group, source-data owner and support contact. Set an order for configuration, sample migration, permission review, account connections, manager orientation and a controlled first vacancy. Use your own capacity and supplier commitments to set dates. This guide supplies no universal implementation duration.

Agree what must be observable before expanding. The designated recruiter should complete the candidate sequence, the manager should submit feedback within the agreed process, and the migration owner should accept the selected records. State who handles exceptions and where support requests go. Keep unresolved issues visible rather than relying on the project owner's memory.

Use the ATS implementation guide for the detailed launch work. The buying decision should leave you with signed scope, named owners, acceptance evidence and a route to pause expansion when a required flow fails. Set a review date after the first complete hiring cycle so the team can compare actual work with the assumptions that justified the purchase.

Hire supports vacancy and candidate management, connected candidate communication, interview scheduling and structured feedback after interviews. Use your buying brief to request a demonstration of one representative vacancy, including the access boundary and exception that matter to your team. Confirm the required package and connection scope during that review.

Compare Hire plans against the same written requirements used for the other options. Bring the decision owner and the colleague who operates the current workflow. Finish with a record of what passed, what remains unresolved and who will supply the missing evidence before a purchase decision.