An Applicant Tracking System saves recruiters the most time when it takes over the steps that repeat identically for every candidate, and leaves the judgement calls with people. Sending a confirmation of receipt, creating the next task after a stage change and reminding a client about a pending reply happen the same way every time. Deciding who is rejected, who is presented to a client and what goes into an offer does not. Automate the first group in the Applicant Tracking System, keep the second group with a named recruiter, and make every automated step visible in the candidate record. No invented time savings, and no promise that artificial intelligence replaces recruiters.
The split looks slightly different per segment. Recruitment agencies handle high volumes of applications and client submissions. Staffing desks repeat the same intake and availability checks many times a week. Secondment teams follow consultants across assignments. Executive search firms run fewer, more confidential processes where personal contact matters more. In-house recruitment teams coordinate with hiring managers who are not recruiters. The principle stays the same: automate repetition, keep judgement.
Why automation in recruitment often disappoints
The same patterns show up on many desks:
- Automations are switched on before the process is agreed, so they speed up an inconsistent way of working
- Messages reach candidates in the wrong language or with the wrong vacancy name, and nobody notices until a candidate replies
- A rule fires in the background and nobody can see afterwards why a candidate received an email or moved to another stage
- Every recruiter builds personal templates and reminders, so the desk ends up with five versions of the same step
- Decisions that need a conversation, such as a rejection after an interview, are left to an automatic message
The problem is rarely the tool. It is automating steps that were never clearly defined, or steps that should not be automated at all.
A simple test: does the step repeat identically, and does it need judgement?
Before you automate a step, ask two questions. Does it happen the same way for every candidate or vacancy? And can it run without someone weighing the situation? If the step repeats identically and needs no judgement, the Applicant Tracking System can take it over. If either condition fails, the system may prepare the step, but a recruiter completes it.
Steps the Applicant Tracking System can take over
- Confirmation of receipt — an immediate message to every applicant in their language, plus a review task tied to the first-review deadline
- Tasks after a stage change — when a candidate moves to the next stage, the system creates the follow-up task with a next-action date for the owner
- Interview scheduling and reminders — offering the available time slots, sending confirmations and reminding both the candidate and the interviewer
- Reminders on open deadlines — to the client on a pending submission, to the hiring manager on open feedback, and to the owner when a candidate is stuck too long in a stage
- Data hygiene — flagging a possible duplicate when a known email address or phone number arrives, asking for the candidate source at first application, and listing records whose retention date has passed for review
Steps that stay with the recruiter
- Rejection after a conversation — the system can propose a reason and a draft message, but the recruiter decides and sends it; standardised rejection reasons make this faster, not automatic
- Presenting a candidate to a client — only after recorded candidate consent and a deliberate choice of which profile to send
- Offers and negotiation — salary, start date and conditions need a conversation, not a rule
- Merging records — the system flags a possible duplicate, a person confirms which data is kept
- Closing a vacancy or pausing a client — these change the relationship and belong to the owner of the role
Each of these steps can be prepared automatically. None of them should be completed without a person.
How to set up automations the team can trust
- Give every automation a named owner, consistent with a single owner per role
- Describe the trigger, the action and the language of each automation in one shared overview, not in personal settings
- Log every automated action in the candidate or vacancy record, in the same way a manual stage change records who moved the candidate, with the system named as the actor
- Make it easy to pause an automation for one candidate, one vacancy or one client without switching it off for everyone
- Review the overview per desk at fixed moments: remove rules nobody uses and rewrite messages that candidates or clients misunderstand
Automation and the client relationship
Many repeated steps touch clients: reminders about submitted candidates, interview confirmations, updates on a vacancy. Tie them to the candidate and client relationship records beside the pipeline, so each contact person receives one coherent message instead of three overlapping ones. Agree per client which automatic messages they want, and record that preference. Measure only what you can verify, such as which automations fired and how often a recruiter overrode them, instead of claiming hours saved that nobody counted.
Where artificial intelligence may help — and where it must not
Artificial intelligence may draft the text of a message template, point out repeated steps in your current process that could be automated, or summarise a candidate record before a recruiter takes a decision. It must stay secondary. Artificial intelligence does not replace recruiters, does not reject candidates on its own, does not choose who is presented to a client and does not send messages that were never approved as templates. The Applicant Tracking System stores the rules, the owners and the log of what was done.
A practical week to get started
- List the steps your desk repeats for every candidate, and mark which ones pass the two-question test
- Choose a small first set to automate, for example confirmation of receipt, tasks after a stage change and interview reminders
- Write the message templates in every language you recruit in, and have a second recruiter check them
- Switch the automations on for one vacancy first, and read the log in the candidate records at the end of the week
- Write down the steps that stay manual, with their owner, so nobody assumes the system handles them
A few well-defined automations do more for a desk than a long list of rules nobody can explain.
Automate the repetition, keep the judgement
If your Applicant Tracking System automates everything or nothing, recruiters either lose control or lose time. Automate the steps that repeat identically and need no judgement, keep decisions with a named recruiter, log every automated action, and keep artificial intelligence as a helper only. Then explore the product or book a demo — we walk through BoldATS automation in your segment.