Many applicant tracking systems impose a rigid set of application statuses – for example just "New", "Under review", "Rejected" and "Accepted". In practice, though, a recruiting process is rarely that simple: there are intermediate steps such as a first interview, a second round, reference checks or contract negotiations that cannot be mapped in a rigid four-status model. 1Tool addresses this problem with a configurable, hierarchical status tree in its applicant management module.
Applicant statuses instead of rigid presets
In 1Tool's applicant management, every application can be assigned an applicant status. These statuses are not hard-coded in the software but can be adapted to your own recruiting process. This allows a company to map exactly the steps its application process actually goes through – including every intermediate stage that matters to its organisation.
Hierarchy and order
The statuses are structured hierarchically: there is a parent structure under which individual status values can be grouped. In addition, a defined sort order (sort_order) can be set for each status. This lets you determine not only which statuses exist at all, but also in which logical order and under which parent category they appear in the application process – from the first screening of an application to the final decision.
Why flexibility matters here
Recruiting processes differ greatly between industries, company sizes and even individual job profiles. A rigid set of statuses forces teams to squeeze their actual process into someone else's scheme – with the result that important intermediate steps are either ignored or documented makeshift in comment fields. 1Tool's configurable, hierarchical status tree instead lets you map the application process exactly as it really runs in your company.
Frequently asked questions
Are the application statuses in 1Tool fixed?
No. The applicant statuses can be configured and thus adapted to the company's individual recruiting process.
What does the hierarchical structure of the statuses mean in practice?
There is a parent structure under which individual status values are organised, so that intermediate steps can be grouped logically.
Can I define the order of the statuses myself?
Yes, a defined sort order (sort_order) lets you set the sequence in which the statuses appear in the process.
Would you like to see the configurable status tree for your recruiting in action?