BlogDigitalisation
Applicant tracking: sort the process before buying the tool
ByDominik Pototschnig4min

In many organisations, applications sit in three places at once: the managing director’s inbox, the department head’s inbox, and a folder on the server. With enough searching you can work out who applied. Who replied last is usually harder to establish. Before buying a system for that, it is worth looking at the process underneath it.
Software shows a process, it does not supply one
An applicant tracking system reflects whatever you give it. If nobody has settled who screens an application, within what deadline that happens, and who makes the offer, the software carries that ambiguity forward and simply displays it more neatly. Time to hire does not shorten on its own.
So before the tool question, we put a single page on the table.
Four points to settle before you buy
- Who screens, who decides. One named person per vacancy to screen applications, one to make the offer. “The team” is not an owner.
- Which deadlines apply. An acknowledgement on the day of receipt is easy to keep. A first substantive reply needs a deadline the hiring department will actually commit to.
- Which stages an application passes through. Three to five are almost always enough: received, screened, interview, decision. More stages create maintenance, not clarity.
- What happens to rejections. Set a deletion period, add people to a talent pool only with explicit consent, and record both so that somebody else can follow it later.
Those four answers are the real output of the first week. They keep their value even if you end up staying with a shared mailbox.

Signs that a system will pay for itself
No single sign is enough on its own. It becomes interesting when several apply at the same time:
- Several vacancies are open at once and more than one person screens.
- Applications arrive through different channels: your website, job boards, email, referrals.
- You cannot say off the top of your head how many applications are currently unanswered.
- Rejections are left undone because nobody owns them.
- Similar roles are advertised several times a year and the wording starts from scratch each time.
- You need to show who saw which candidate data and when that data was deleted.
With two or three hires a year and one person responsible, a well-kept mailbox with templates and a simple list will usually do. That is not a step backwards; at that size it is the cheaper answer.
What a system takes off your desk, and what it does not
It can take on a single point of entry for every channel, a status view everyone involved can see, standard texts for acknowledgements and rejections, a structured application form instead of assorted PDF attachments, and roles, permissions and deletion periods in one place.
It cannot take on the decision. If a department needs two weeks to respond, automation moves that wait to another point in the process rather than removing it. Nor does it produce applications: too few candidates is a problem with the role profile, visibility or response time, not with administration.
Recruitee as an example
In projects of this kind we work with Recruitee, among other tools. Its scope fits what smaller and mid-sized employers tend to need: a careers page that requires no development work, a pipeline with stages you define yourself, and a talent pool for candidates who were not right this time. Screening questions, deeper reporting and single sign-on depend on the plan you choose. Check the current feature set and pricing with the supplier directly, because both change.
The limits belong in the assessment:
- It is a hiring tool, not personnel administration. Payroll, time recording and personnel files stay outside it. If you are looking for HR management in the broader sense, this covers one section of it.
- Cost follows readiness, not results. Employers who advertise rarely also pay for the months with no open roles.
- The careers page follows the supplier’s templates. With a tightly governed brand you either accept compromises in the design or keep your own page and link to the forms.
- Candidate data sits with a processor. A data processing agreement, storage locations, deletion periods and the question of what you can export if you leave should all be examined before you start. Neither the supplier nor this article can carry out that assessment for you.

When we advise against it
If one person handles everything and hiring is rare, a dedicated system is effort without return. If an unused HR module already sits in your ERP, we first ask why it went unused. And if applications are not arriving at all, we start with the advert rather than the administration.
A first conversation
If you are unsure where your hiring process stalls, we will look at the sequence with you before discussing tools. An hour is usually enough to answer the four points above and to judge whether a system carries its cost at your size. Book a first meeting.
- Recruitment
- HR
- Applicant tracking
More articles
monday.com in practice: making projects and routines visible
When a work platform such as monday.com pays off, how we clarify routines beforehand, and where boards and automations reach their limits.
Quotes, contracts and e-signatures: where the time actually goes
The real delays in a quoting process sit before and after the signature. How to standardise the workflow, and where PandaDoc stops being the right fit.
Notion in practice: bringing company knowledge together
Scattered company knowledge costs time. How to build a single place for it, where Notion fits the job, and the limits worth knowing first.
