Configuring a recruitment software: what has to stay in your hands
Choosing an ATS is rarely decided on the feature list. It is decided on a simpler question: after six months, was it the tool that adapted to the agency, or the agency that adapted to the tool? The answer lies in what the configuration allows without going through bespoke development.
The tell-tale sign: the parallel file
When a stage of the process does not exist in the software, it does not disappear: it moves into a spreadsheet, a chat channel, or a consultant's head. Tracking becomes partial, the indicators become wrong, and nobody notices until the first serious review. A tool that accepts your stages, your statuses and your rules stops that leak.
Processes, rights, triggers
Three families of settings make the difference day to day. First the processes : the stages of application tracking, the sales stages of opportunities and the invoicingcycle, each with its statuses. Then the rights : access profiles, teams, entities, approvers resolved by role rather than named one by one, which spares you reworking everything the first time someone leaves. And finally the triggers : notifications, emails and documents generated at the right moment, from your templates.
Reporting comes after, not before
A dashboard is only worth something if the data it shows comes from real work. Once the process is described in the tool, the reports and the dashboards become usable: activity by consultant, application sources, lead times, revenue by client. You use the reports provided or build your own, with the visibility you choose and spreadsheet export for one-off analysis.
Multi-office, multi-brand, multi-country
As soon as an agency opens a second office or launches a specialist brand, the question of separation arrives: who sees the other office's candidates, who reaches the client accounts, how to consolidate without mixing everything together. Entities, teams and access profiles answer that within a single tool, without duplicating databases or subscriptions.
What to take away
- A process missing from the software moves back into a spreadsheet, and the indicators become wrong.
- Stages and statuses must be describable without bespoke development.
- Rights are thought through by role and by entity, not person by person.
- Notifications and templates prevent oversights and standardise the agency's documents.
- A configuration that evolves beats a configuration that was perfect on day one.
Go further: application tracking, CRM for agencies, pricing.