ATS implementation checklist for EU HR teams

Before configuration: agree on the operating model

Write the future process in plain language: how a job becomes approved, how applications arrive, who reviews each stage, what evidence is required, who contacts the candidate and who can make the final decision. An ATS cannot resolve unclear responsibility; it can only make the ambiguity faster.

Name an implementation owner and a decision owner for each workflow. Include recruiting, hiring managers, HR administration, privacy or security responsibility and the people who will use the system every day. Record unresolved policy questions instead of hiding them inside configuration choices.

1. List required workflows, roles, integrations, reports and exports.
2. Define the authoritative system for jobs, applications, employee records and identity.
3. Approve role permissions, retention rules and deletion responsibilities.
4. Choose measurable acceptance criteria for the pilot and go-live.

An eight-week ATS implementation plan

Keep the first release small enough to test end to end. A complete application-to-decision flow is more valuable than partially configuring every feature. The dates below are a planning pattern; adjust them to the size, risk and integration needs of your organisation.

1. Week 1: map the current and future workflow, owners, data and decision points.
2. Week 2: configure workspace roles, job templates, stages and required evidence.
3. Week 3: configure candidate communication, interview scorecards and approvals.
4. Week 4: clean and map migration data; test a small reversible import.
5. Week 5: connect required email, calendar or identity integrations in a test environment.
6. Week 6: run role-based acceptance tests and realistic failure scenarios.
7. Week 7: pilot one real hiring workflow with daily support and correction logging.
8. Week 8: review acceptance criteria, train remaining users and approve or postpone go-live.

Migrate less data, with more evidence

Do not import every historical file by default. Classify records as active, required for a documented purpose, subject to a retention obligation or eligible for deletion. Remove duplicates and unrelated fields before import. Preserve source identifiers and a migration log so the team can explain where a record came from.

Reconcile counts and required fields after each test import. Sample attachments, dates, ownership and consent or notice records where they matter. Decide how to handle records that fail validation rather than silently creating incomplete candidate profiles.

Test privacy, access and AI controls

Use a role matrix to test what recruiters, hiring managers, interviewers, administrators and ordinary employees can see and change. Include negative tests: a person who should not access a candidate, an expired link, a deleted record and a revoked integration. Confirm how audit records, backups and retention behave after deletion.

If the ATS uses AI to support recruitment, document the purpose, provider, data flow, human review and fallback. The EU AI Act identifies certain employment and recruitment uses as high risk. The exact obligations depend on the role and use, but teams should design for clear information, logging, documentation, human oversight, accuracy and risk management rather than add these after launch.

Make user acceptance concrete

Ask a new hiring manager to complete the workflow without private coaching: request a job, review assigned applications, record interview evidence, make a permitted decision and find overdue work. Observe where the person hesitates. A login is not adoption and a training attendance list is not proof that the process works.

1. A job can be created, approved, published and closed with the expected owners.
2. An application can enter, move, pause, withdraw and be deleted according to policy.
3. Candidate messages and internal tasks show the right owner, status and history.
4. Reports update after operational changes and respect the viewer’s permissions.
5. Exports, corrections, retention actions and incident contacts have been tested.

A practical Kadroflow rollout

Start a Kadroflow pilot with one workspace, one role and fictional candidates. Configure the pipeline and scorecard, invite the smallest cross-functional team and complete the workflow through a decision. Then test deletion, export, permissions, reporting and the handoff into onboarding before importing live data.

Use the downloadable checklist as an acceptance record. Mark each item demonstrated, partly demonstrated or not demonstrated and attach the evidence. Product configuration supports the process; your organisation remains responsible for its policies, lawful use and final hiring decisions.