Equal employment opportunity requirements in Europe derive from multiple overlapping legal frameworks. The EU's Equal Treatment Directive, the Employment Equality Directive, and the Race Equality Directive collectively prohibit discrimination in employment on grounds of sex, racial or ethnic origin, religion or belief, disability, age, and sexual orientation. Each EU member state implements these directives through national law, with varying scope, enforcement mechanisms, and penalty structures.

In the United Kingdom post-Brexit, the Equality Act 2010 remains in force and is the primary framework. In the United States — relevant for multinationals or US-headquartered companies with European operations — Title VII of the Civil Rights Act, the Americans with Disabilities Act, the Age Discrimination in Employment Act, and the Equal Pay Act apply alongside state-level requirements.

The common thread across all jurisdictions is this: discrimination can be direct (treating a candidate less favourably because of a protected characteristic) or indirect (applying a neutral criterion that disproportionately disadvantages a protected group without objective justification). An employer does not need to intend to discriminate to be found liable for indirect discrimination. This is why documented, consistent processes matter so much — they are both a deterrent to discriminatory behaviour and the primary defence when a complaint is made.

What Documentation You Need and Why

When a discrimination complaint is filed — whether to a labour court, an equality body, or an employment tribunal — the employer is typically required to demonstrate that the hiring decision was made on legitimate, non-discriminatory grounds. Without documentation, this is impossible. With documentation, it is straightforward.

The documentation that protects employers has five elements:

The job specification. A documented job description with clearly defined competency requirements and objective selection criteria. This must precede the recruitment process — criteria cannot be defined after the fact to justify a decision already made. The job specification is the baseline against which every candidate evaluation must be anchored.

A record of every application received. Your ATS should capture every application — including those rejected at initial screen — with a timestamp and the channel through which the application arrived. This creates the full pool record: who applied, when, and from where.

Documented rejection reasons. Every candidate who is rejected at any stage must have a rejection reason recorded in the ATS. This reason must be tied to the competency requirements of the role, not to personal characteristics. "Does not meet the minimum qualification of degree-level education in a relevant field" is a legitimate, documented reason. "Not the right fit" is not — it is legally indefensible.

Interview records. For every candidate who reaches an interview stage, the interview questions asked, the competency framework used, and the scores or evaluations recorded must be stored in the ATS. If a candidate who was not selected later claims discrimination, the employer must be able to show exactly what was evaluated and how the selected candidate scored higher on objective criteria.

Offer and rejection communications. All candidate communications — invitations, rejections, offers — should be generated from and stored within the ATS. This creates a record of what was communicated and when, prevents evaluators from making undocumented informal commitments, and ensures consistency across all candidates at each stage.

Documentation Is Your Defence

In most European employment tribunals, if a candidate presents a prima facie case of discrimination — evidence that suggests a discriminatory pattern — the burden shifts to the employer to demonstrate the decision was made on non-discriminatory grounds. Without documented, objective evaluation records, this defence is not possible. The ATS audit trail is not bureaucracy — it is legal protection.

ATS Configuration for Compliance: What to Set Up

A compliant ATS configuration is not complex, but it must be deliberately designed. These are the key setup elements that create the compliance foundation.

Mandatory rejection reason codes. Configure your ATS so that no candidate can be moved to a rejection status without a rejection reason being selected from a structured list. The reason codes must be job-related: "Does not meet minimum experience requirement," "Did not meet technical assessment threshold," "Withdrew from process," and similar. Free-text rejection reasons are insufficient — they are inconsistent and cannot be aggregated for adverse impact analysis.

Structured interview scorecards. Create interview scorecards tied to each job's competency framework. Evaluators should complete a scorecard for every candidate they interview before discussing with other interviewers. Independent scoring before debrief prevents anchoring bias and creates a documented evaluation record. Store completed scorecards against the candidate record in the ATS.

Consent and data collection controls. GDPR intersects with EEO compliance in the application form. Do not collect information about protected characteristics (age, gender, nationality, disability status) unless there is a specific, documented lawful reason. If you collect voluntary diversity and inclusion data for monitoring purposes, it must be collected separately from the application process, flagged as voluntary, and stored in a way that is not visible to the hiring team making decisions.

Audit log preservation. Every action taken in the ATS — candidate advancement, rejection, note addition, status change — should be logged with the user ID and timestamp of the person who made the action. This audit log must be preserved for at least the legal minimum retention period. Do not configure ATS cleanup processes that delete audit logs before this period expires.

EEO Reporting in Treegarden

Treegarden's EEO reporting module tracks candidate outcomes by stage and generates structured reports on application, interview, and offer rates across the hiring pipeline. Rejection reason codes are mandatory, interview scorecards are stored against candidate profiles, and full audit logs are preserved — giving your legal and compliance teams the documentation they need when it matters.

Adverse Impact Monitoring: Catching Patterns Before They Become Claims

Adverse impact monitoring is the practice of tracking hiring outcomes by demographic group to identify whether any group is being disproportionately excluded from the process. It is both a compliance requirement in some jurisdictions and a best practice for employers who want to identify and correct unintentional bias before it results in a complaint.

The standard framework for adverse impact analysis compares the pass rate of different demographic groups at each stage of the hiring funnel. If the pass rate for a protected group at any stage is less than 80% of the pass rate for the highest-passing group (the "4/5ths rule"), this triggers a review. Note: the 4/5ths rule is a guideline for triggering investigation, not a legal standard — the threshold that constitutes unlawful discrimination is determined by the court or tribunal, not a fixed percentage.

To conduct adverse impact monitoring, you need voluntary demographic data from candidates — typically collected through a separate equal opportunities monitoring form that is explicitly decoupled from the application. This data must be anonymised before it reaches the hiring team and used only in aggregate for monitoring purposes. Your ATS should support this separation: demographic monitoring data stored in a separate module, accessible only to HR and compliance teams, with no linkage to the candidate's profile as visible to recruiters and hiring managers.

Run adverse impact analyses quarterly for high-volume roles, and annually for the full hiring programme. When a stage shows statistically significant adverse impact, investigate the selection criterion being applied at that stage. Is it genuinely job-related? Is it being applied consistently? Is there a less discriminatory alternative that achieves the same objective?

Interview Compliance: Questions, Structure, and Prohibited Areas

Unstructured interviews are the highest single-point compliance risk in recruitment. An interviewer who asks unprompted questions about a candidate's family plans, their nationality, their religious practices, or their health has potentially created a discrimination liability — even if those questions were asked innocently and with no discriminatory intent.

Structured interviews eliminate this risk by constraining the conversation to documented, pre-approved, job-relevant questions. Every interviewer asks the same questions in the same order. Questions are designed around defined competencies and validated against the job specification before the interview process begins. Supplementary follow-up questions should be limited to clarifying candidate responses, not exploring new territory.

The prohibited question areas are consistent across European jurisdictions, though the specific framing of the prohibition varies. Questions to avoid include: anything about pregnancy, children, or plans to have children; marital status; religion or religious practices that are not directly relevant to the role; sexual orientation; age or date of birth beyond right-to-work verification; disability or health conditions (except in the context of discussing reasonable adjustments for the role); and nationality or ethnic origin beyond legal right-to-work documentation.

Configure your ATS to store the interview question set for each role, along with the competency it maps to. This creates a documented record that the interviews were conducted consistently and within legal boundaries.

The Reasonable Adjustments Obligation

In most European jurisdictions, employers are required to make reasonable adjustments to the recruitment process for candidates with disabilities. This may include providing application forms in accessible formats, allowing additional time for assessments, or making physical adjustments to interview locations. The ATS should include a field for candidates to request adjustments at application, and a workflow that flags these requests for HR review before the candidate progresses.

Data Retention, GDPR, and the Right to Erasure

GDPR adds data protection obligations that run alongside — and sometimes in tension with — EEO documentation requirements. The GDPR principle of data minimisation requires you to retain personal data only as long as necessary. The EEO documentation obligation requires you to retain records long enough to defend against a discrimination complaint.

Resolving this tension requires a documented retention policy that specifies: how long unsuccessful candidate records are retained (commonly 6–24 months, depending on jurisdiction), what data is retained at each stage (full application data vs. a summary record), when automatic deletion is triggered, and how data subject access requests and erasure requests are handled within the retention framework.

The right to erasure (Article 17 GDPR) does not override legitimate legal obligations. If a candidate whose application was retained for compliance purposes submits an erasure request, you may be able to decline if retention is necessary for the establishment, exercise, or defence of legal claims. Document this exception explicitly in your privacy policy and your internal data retention procedures.

Your ATS must support this lifecycle. Automated retention and deletion workflows, data subject access request management, and anonymisation of candidate records at the end of the retention period should all be ATS capabilities, not manual processes dependent on HR remembering to delete records on schedule.

Frequently Asked Questions

What is the difference between EEO and GDPR compliance in recruitment?

EEO (Equal Employment Opportunity) compliance concerns non-discrimination in hiring decisions — ensuring that protected characteristics like race, gender, age, disability, and religion do not influence who is selected. GDPR compliance concerns personal data protection — how you collect, store, process, and delete candidate personal information. A compliant ATS must address both: preventing discriminatory decisions and protecting personal data throughout the process.

How long must I retain recruitment records for legal compliance?

In Europe, the standard retention period for unsuccessful candidates is 6 months to 2 years, depending on jurisdiction and applicable challenge windows. In some EU member states, labour law allows discrimination claims for up to 3 years. Your retention policy should be informed by legal advice specific to your jurisdiction and documented formally. Retain records of the successful candidate for the duration of employment plus a defined period after.

Do I need to keep records of candidates I rejected at CV screen stage?

Yes. Any application that entered your process — even one rejected at initial screen — may be subject to a data subject access request or referenced in a discrimination complaint. Your ATS should retain a basic record of every application received, the stage at which it was rejected, the reason code applied, and the date. This does not require storing the full CV indefinitely — a summary record with a documented reason is sufficient.

Can I ask candidates about salary history during recruitment?

Salary history questions are restricted or prohibited in a growing number of jurisdictions due to their role in perpetuating gender pay gaps. In the EU, the Pay Transparency Directive (effective from 2026) requires employers to provide salary information to candidates before or at the first interview, and restricts the use of salary history in hiring decisions. Check the specific law in your jurisdiction, but the direction of travel across Europe is clear: do not base offers on salary history.

What questions are illegal to ask in a job interview?

Questions that elicit information about protected characteristics are illegal or legally risky in most European jurisdictions. These include questions about pregnancy, plans to have children, marital status, religion, sexual orientation, nationality or ethnic origin (beyond right to work verification), age or date of birth, and disability status (except in the context of reasonable adjustments). All interview questions should be documented and tied to job-relevant competencies.