Applicant management & hiring workflow
How this is scored
The daily work of hiring: pipeline stages per job, collaboration with hiring managers, structured evaluation, interview scheduling and candidate communication — judged on whether a decision is documented rather than merely made.
0 — An inbox of applications with a status field; no stages per job, no shared evaluation and no record of who decided what.
3 — A fixed pipeline with drag-and-drop stages and email templates, but hiring managers see everything or nothing, and evaluation is free-text comments.
5 — Configurable pipelines per job, hiring-manager access limited to their own vacancies, structured scorecards, interview scheduling with calendar integration, and templated candidate emails in German.
8 — Approval workflows for requisitions and offers, role-based access per team and location, structured interview kits, bulk actions with automated but reviewable candidate communication, and a history on each candidate of every stage change and who made it.
10 — The pipeline is an auditable record of a fair process: every decision attributed and reasoned, evaluation criteria fixed before applications arrive, reporting on time-to-hire and drop-off per stage, and the full history exportable per candidate for an AGG dispute.
The Works Council Advocate
Ten application stages and unlimited interview workflows are configurable per job, interview scheduling runs against Google and Office 365 calendars, and moving a candidate can trigger questionnaires, sub-statuses and onboarding workflows. What I found no public information on is structured scorecards and, crucially for a works council, a per-candidate history showing who moved them at each stage and why — the documented audit trail logs access attempts, not decisions — so a selection process here is traceable as activity, not yet as attributable, reasoned judgement. 4 5 13 3