Gate Architecture · legal checkpoint view · ARAM-HRDD-DE
How It Works Gate Architecture Attack Catalog Replay Gallery Case Repository Who We Help Run Your Case
Legal checkpoint view

Gate Architecture

This page shows how the file is reviewed, gate by gate, before counsel relies on it. It is the review surface, not the challenge surface: the question here is what the record must contain at each checkpoint.

← Back to How It WorksCompare with Attack Catalog →See Replay Gallery →
ARAM-HRDD-DE  ·  Germany Termination — Litigation Review Framework  ·  gate_registry_DE_v1
Review Point G0
Special Protection — Pre-Termination Screening
§17 MuSchG  ·  §18 BEEG  ·  §168 SGB IX  ·  §15 KSchG  ·  §38 Abs. 2 BDSG  ·  §15 Abs. 3 KSchG  ·  §2 ArbPlSchG
Before any notice is issued, the file should be reviewed for whether the employee holds a protected status requiring external authority approval or structurally barring ordinary termination. Absent the required consents or determinations, a notice issued is ordinarily fatal to the employer’s position regardless of the underlying merits. These protections operate independently of the substantive justification and must be cleared first.
G0.1
Pregnancy — Landesamt consent
Applies where: employee holds pregnant protected status

§17 MuSchG prohibits termination of a pregnant employee without prior written approval from the competent Landesamt für Arbeitsschutz. A notice issued without that approval is void as a matter of law — the defect cannot be cured retrospectively.

The file should ordinarily show
  • Written approval from the Landesamt, obtained before the notice date
  • Confirmation that the pregnancy was known or objectively knowable at the time of notice
  • Approval document specifying the individual case and the date of issue
Where records typically weaken

Approval obtained after the notice date is not remediable. Employer claims of unawareness of pregnancy create a separate factual dispute. Approval granted for an earlier notice attempt does not automatically cover a later reissued notice.

Document refsE0-dE0-e
G0.2
Parental leave — Landesamt consent
Applies where: employee is on or has applied for parental leave under BEEG

§18 BEEG protects employees during parental leave and bars ordinary termination without external authority approval. The protection applies from the date parental leave begins through its end, and the employer bears the burden of showing it was unaware of the leave status.

The file should ordinarily show
  • Written approval from the Landesamt, predating the notice
  • Documented start and end dates of the parental leave period
  • Evidence the employer was or should have been aware of the leave status at notice date
Where records typically weaken

Employers who proceed without approval and later argue unawareness of a leave application face a high evidentiary threshold. A gap between approval date and notice date is a common file deficiency.

Document refsE0-dE0-e
G0.3
Severe disability — Integrationsamt consent
Applies where: employee holds or has applied for severe disability recognition (GdB ≥50 or equivalent)

§168 SGB IX requires prior approval from the Integrationsamt before termination of a severely disabled employee. The protection attaches upon application — not only upon formal recognition — which creates significant documentation risk if the employer was aware of a pending application.

The file should ordinarily show
  • Written approval from the Integrationsamt, obtained before the notice date
  • Documentation of the employee’s disability degree (GdB) or equivalent status
  • Evidence addressing whether an application was pending and known to the employer at time of notice
Where records typically weaken

Approval obtained after the notice date does not remedy the defect. Employers most frequently fail here when an application is pending but undisclosed.

Document refsE0-dE0-e
G0.4
Works council member — ordinary termination structurally barred
Applies where: employee holds active works council membership

§15 KSchG structurally prohibits ordinary termination of active works council members. Only extraordinary termination (§626 BGB) is available, and even then requires specific consent of the works council under §103 BetrVG. This is not a procedural obstacle — it is a substantive bar. Ordinary termination of a BR member is void.

The file should ordinarily show
  • Verification of active BR membership, including tenure start and end dates
  • If extraordinary termination pursued: §103 BetrVG consent document from the works council, predating the notice
  • The §103 consent addresses this specific individual and this specific termination
Where records typically weaken

Files frequently omit BR membership verification. The §103 consent requirement is separate from and additional to the general §102 hearing — both must be satisfied.

Document refsE0-dE0-f
G0.5
Data Protection Officer — ordinary termination barred
Applies where: employee serves as company Data Protection Officer

§38 Abs. 2 BDSG prohibits ordinary termination of a DPO during their appointment and for one year following removal from the role. Only extraordinary termination for cause (§626 BGB) is available during the protected period.

The file should ordinarily show
  • Documentation of the DPO appointment date and any removal date
  • Confirmation whether the notice date falls within the protected window (appointment + one year post-removal)
  • If extraordinary termination pursued: documentation of the specific important reason
Where records typically weaken

Employers often lose track of DPO status following role transitions. The one-year post-removal window is frequently overlooked.

Document refsE0-d
G0.6
Election board member — ordinary termination barred
Applies where: employee served on a works council election board

§15 Abs. 3 KSchG extends the same protection as BR membership to election board members. Ordinary termination is barred; extraordinary termination requires §103 consent. The protection applies during the election preparation period.

The file should ordinarily show
  • Confirmation of election board membership and the operative election period
  • §103 BetrVG consent from the works council if extraordinary termination is pursued
  • Chronology confirming whether the notice date falls within the protected window
Where records typically weaken

Election board membership is a short-window protection that employers frequently fail to verify, particularly in smaller establishments.

Document refsE0-dE0-f
G0.7
Military or civil service — absolute bar
Applies where: employee is performing military or civil service duty

§2 ArbPlSchG imposes an absolute prohibition on termination during military or civil service. This is a categorical bar, not a procedural gate requiring consent. Any notice issued during the service period is void.

The file should ordinarily show
  • Documentation of the service start and expected end date
  • Confirmation that the notice date falls outside the service period
  • Any notice of service obligation the employer received from the employee
Where records typically weaken

The absolute nature of this bar means no procedural remedy is available once a notice has been issued during the service period.

Document refsE0-d
Review resolution — on the present record
No special protection issue surfaced on present record
No applicable protected status is identified, or all required external approvals have been obtained and predate the notice. The file does not present an obvious protection-based challenge on this review.
Record appears exposed — special protection issue present
The file shows indicators of a protected status without corresponding authority approval or consent documentation. This issue, if unresolved, is typically fatal to the termination irrespective of the substantive merits.
Document Reference Glossary
E0-d
Employee status record — protected characteristics including pregnancy, disability, BR role, DPO appointment, service status
E0-e
External authority approval — Landesamt or Integrationsamt written consent, with date of issue
E0-f
§103 BetrVG consent — works council consent to extraordinary termination of a BR or election board member
Review Point G1
Works Council Consultation — Procedural Integrity
§102 BetrVG — mandatory prior consultation before any termination where a Betriebsrat exists
Where a works council exists, §102 BetrVG requires the employer to consult the council before issuing any notice. A notice issued without prior hearing, or where the hearing was materially incomplete, is void regardless of the substantive justification. The consultation requirement is not merely formal — courts examine both the completeness of the hearing and the sequence of events.
G1.1
Hearing initiated before notice
Applies where: works council exists in the establishment

The consultation must precede the notice. If the chronology shows the hearing was opened after the notice was issued, or if dates are absent or internally inconsistent, the entire §102 process is defective.

The file should ordinarily show
  • A dated Anhörungsschreiben addressed to the works council
  • Date of the Anhörungsschreiben preceding the date of the termination letter
  • Evidence that the Anhörungsschreiben was delivered to the council (receipt, signature, or equivalent)
Where records typically weaken

Missing or undated Anhröungsschreiben, notices issued on the same date as the consultation letter, and post-dated documents are the most common filing deficiencies at this step.

Document refsEA-8EB-7EC-10ED-9
G1.2
Hearing document completeness
Applies where: works council exists in the establishment

The Anhröungsschreiben must contain sufficient information for the council to form a meaningful view. Courts have held that an incomplete hearing letter — omitting employee identity, termination type, operative reason, or route — cannot satisfy §102.

The file should ordinarily show
  • Employee identity and position
  • Termination type (ordinary or extraordinary)
  • The factual basis and operative reason for termination
  • The route classification the employer is applying
Where records typically weaken

Boilerplate hearing letters that do not address the specific factual basis of the case are a frequent failure point. Courts do not treat a generic hearing as equivalent to a substantive one.

Document refsEA-8EB-7EC-10ED-9
G1.3
Route consistency — hearing matches notice
Applies where: works council exists in the establishment

The reason and route stated in the hearing letter must correspond to those in the termination notice. If the employer presents a conduct case to the council but issues notice on operational grounds, the hearing is defective as to the reason actually stated.

The file should ordinarily show
  • The termination reason in the hearing letter corresponds to the reason in the notice
  • The route classification is consistent across both documents
  • No material additions or substitutions of grounds appear in the notice that were absent from the hearing
Where records typically weaken

Route substitution between hearing and notice is a recurring litigation pattern. Even where unintentional, a mismatch is treated as a procedural defect.

Document refsEA-8EB-7EC-10ED-9
G1.4
Response window respected
Applies where: works council exists in the establishment

§102 Abs. 2 BetrVG mandates a minimum response window: one week for ordinary terminations, three days for extraordinary. A notice issued before that window has closed is void.

The file should ordinarily show
  • Date the Anhörungsschreiben was delivered to the works council (start of window)
  • The applicable response deadline (ordinary: 7 days; extraordinary: 3 days from delivery)
  • The termination letter date confirming it postdates the deadline or a documented early response
Where records typically weaken

Files often show the notice issued one or two days before the deadline expires. This is not remediable. Ambiguity about the delivery date of the hearing letter is also a persistent issue.

Document refsEA-8EB-7EC-10ED-9
G1.5
Works council response documented
Applies where: works council exists in the establishment

Whatever the council’s response — approval, objection, partial objection, or silence — it should be on the record. Failure to document the response leaves the consultation sequence open to challenge.

The file should ordinarily show
  • A documented response from the works council, or a record of non-response on expiry of the deadline
  • Where the council objected: the objection is documented in full (§102 Abs. 3 grounds)
  • No indication that the employer treated the process as concluded before the response was received or the deadline expired
Where records typically weaken

Employers who cannot produce any works council response — even a record of silence — face difficulty demonstrating the consultation sequence was properly closed.

Document refsEA-8EB-7EC-10ED-9
G1.6
Social selection data included in hearing
Applies where: route is operational (Route C) and works council exists

In an operational redundancy case, the works council must be informed of the social selection criteria and results. A hearing letter that omits the pool of comparable employees and the selection methodology does not satisfy §102 for Route C.

The file should ordinarily show
  • The hearing letter includes identification of the comparable employee pool
  • The social selection criteria applied are stated or referenced
  • Any exemptions from the pool are identified in the hearing document
Where records typically weaken

Employers frequently use a generic hearing template for all routes and fail to adapt it for the additional social selection disclosure required under Route C.

Document refsEC-10
G1.7
Notice not issued before response window closed
Applies where: works council exists in the establishment

A notice issued before the response window has fully elapsed — or before the council’s response has been conclusively received — is defective, even where the window was otherwise correctly set.

The file should ordinarily show
  • The notice date postdates either the deadline or the council’s conclusive response, whichever is earlier
  • Where the council responded early: the response is recorded as received before the notice was issued
  • No gap or overlap between response receipt and notice issue that creates ambiguity
Where records typically weaken

Files with handwritten date amendments or inconsistent date stamps on the termination letter create particular vulnerability here.

Document refsEA-8EB-7EC-10ED-9
G1.8
§103 BetrVG consent — extraordinary termination of BR member
Applies where: employee is a works council member and termination is extraordinary (Route D)

Where the employer seeks to terminate a works council member by extraordinary notice, §103 BetrVG requires the works council’s consent as a separate and additional step to the §102 hearing. Absence of §103 consent renders the extraordinary notice void.

The file should ordinarily show
  • Written §103 consent from the works council, predating the notice
  • Confirmation that the §103 procedure was initiated separately from and in addition to the §102 hearing
  • The consent specifically addresses the extraordinary termination of this individual
Where records typically weaken

Employers conflate the §102 hearing with §103 consent, particularly where the works council is small. The two procedures are legally distinct and both are required.

Document refsE0-f
Review resolution — on the present record
Consultation record appears procedurally sound
On the present record, the chronology, documentation, and content of the works council consultation appear consistent with §102 BetrVG requirements. No obvious procedural gap is identified at this review.
Consultation record appears procedurally incomplete
The file shows one or more gaps in the consultation sequence — timing, document content, or response documentation — that would ordinarily attract closer scrutiny. A §102 defect renders the notice void regardless of substantive justification.
Document Reference Glossary
EA-8
Works council hearing document — Route A (conduct-based)
EB-7
Works council hearing document — Route B (personal/illness-based)
EC-10
Works council hearing document — Route C (operational/redundancy)
ED-9
Works council hearing document — Route D (extraordinary §626 BGB)
E0-f
§103 BetrVG consent — works council consent to extraordinary termination of a BR member
Review Point G2
Substantive Justification — Standard Compliance
§1 KSchG (social justification)  ·  §623 BGB (written form)  ·  §622 BGB (notice periods)  ·  §626 BGB (extraordinary termination)
Two formal requirements apply universally regardless of the nature of the termination: written form and notice period compliance. Beyond those, the applicable substantive review depends on the route. Select the applicable route below. Where KSchG does not apply (fewer than 10 employees, or less than 6 months’ tenure), the social justification requirements are disapplied — but written form and notice period requirements remain.
Applied to all routes regardless of termination type.
G2.WF
Written form — §623 BGB

§623 BGB requires that every termination be issued in writing, on paper, with an original wet-ink signature, and with documented proof of delivery to the employee. An email, fax, or electronically signed document is void.

The file should ordinarily show
  • Original paper document with original (wet ink) signature of an authorised signatory
  • Proof of delivery to the employee — personal service receipt, registered mail record, or equivalent
  • Where a representative signed: written power of attorney (Vollmacht) attached to or referenced in the notice
Where records typically weaken

Original signature requirements are frequently overlooked in remote or multi-site operations. Delivery proof is absent in a significant proportion of contested cases at the labour court stage.

Document refsEU-WF
G2.NP
Notice period compliance — §622 BGB
Applies where: ordinary termination only

§622 BGB establishes minimum notice periods based on tenure, supplemented by any longer contractual or CBA periods. A notice specifying an effective date that falls short of the minimum period is not void — but the employee is entitled to continued employment through the correct date.

The file should ordinarily show
  • Calculation of the statutory minimum period based on tenure as at the notice date
  • Confirmation that the contractual or CBA-based period has been checked and applied if longer
  • The notice specifies an effective end date at least equal to the applicable minimum
  • The end date falls on a valid termination date (quarter-end, calendar month-end, or as agreed)
Where records typically weaken

Tenure is miscalculated in a material proportion of contested cases, particularly where the employee had prior fixed-term periods. Contracts containing longer periods than the statutory minimum are also frequently overlooked.

Document refsEU-NP
Route A: conduct-based termination — misconduct, breach of duty, or behavioural grounds.
G2.A1
Incident documentation

A conduct-based termination requires that the underlying incident be specifically documented: what occurred, when, what contractual duty was breached. Vague or conclusory recitations of misconduct are insufficient.

The file should ordinarily show
  • A contemporaneous or near-contemporaneous record identifying the incident date and setting
  • A description of the conduct at a level of specificity that would allow a court to evaluate it
  • Identification of the contractual or statutory duty that was breached
Where records typically weaken

Disciplinary records assembled retrospectively and incident descriptions that are conclusory without particulars are the most common weaknesses in conduct-based files.

Document refsEA-1
G2.A2
Abmahnung (formal warning) — validity

Before conduct-based termination, the employer must ordinarily have issued a formal warning (Abmahnung) identifying the same conduct, demanding improvement, and warning of termination consequences. Absence of a valid warning is remediable only where the conduct is so severe that continued employment cannot reasonably be expected.

The file should ordinarily show
  • A formal Abmahnung document specifying the conduct in question
  • Date of issue and documented delivery to the employee
  • The Abmahnung specifically identifies the same conduct now cited as the basis for termination (same-conduct requirement)
  • The Abmahnung fulfils all three required functions: documentation, censure, and warning of termination consequences
  • Where no warning exists: documented basis for the no-warning exception
Where records typically weaken

Abmahnungen older than 36 months may carry reduced weight. Warnings addressing different conduct than the termination ground do not satisfy the same-conduct requirement.

Document refsEA-2EA-3
G2.A3
Culpability assessment and negative prognosis

Conduct-based termination requires both that the employee was culpable and that there is a negative prognosis — a reasonable expectation that the conduct will recur. Where the employee demonstrates remorse or the conduct is isolated, courts will scrutinise whether termination rather than a milder measure was warranted.

The file should ordinarily show
  • A documented assessment of why the employee bore culpable responsibility for the conduct
  • Consideration of any mitigating circumstances the employee raised
  • A documented basis for the employer’s prognosis that the conduct would recur
Where records typically weaken

Files relying on a single serious incident without addressing culpability or prognosis are frequently weakened on cross-examination.

Document refsEA-4EA-5
Route B: personal-reason termination — typically illness, incapacity, or other personal circumstances unrelated to conduct.
G2.B1
Absence record and BEM process

Illness-based termination requires both an adequate absence record and documented completion of the statutory integration management process (BEM) under §167 SGB IX. A BEM not initiated, inadequately conducted, or refused without documentation significantly weakens the employer’s position.

The file should ordinarily show
  • Absence record covering at least 24 months, showing dates, durations, and reason classifications
  • BEM invitation letter sent to the employee, with date
  • The employee’s written response to the invitation (acceptance, refusal, or non-response)
  • Documentation of the BEM process outcome or the refusal
Where records typically weaken

Courts treat BEM as a mandatory prerequisite, not merely a best practice. A BEM conducted without genuine engagement with alternative measures is treated as a procedural shell.

Document refsEB-1EB-2
G2.B2
Negative health prognosis and operational impact

Beyond the absence history, an illness-based termination requires a supported negative prognosis and demonstration that the absence level causes unreasonable operational disruption.

The file should ordinarily show
  • A documented basis for the negative health prognosis — medical evidence, pattern analysis, or equivalent
  • The employer’s operational impact assessment: which functions were affected, what arrangements were required
  • Evidence that the disruption was unreasonable and not merely inconvenient
Where records typically weaken

Operational impact is frequently addressed superficially. Bare assertions of disruption without particulars are vulnerable to challenge.

Document refsEB-3EB-4
Route C: operational/redundancy termination — elimination of position due to business restructuring or reduction in workforce.
G2.C1
Business decision documentation

An operational redundancy termination rests on an underlying business decision that eliminates the employee’s position. That decision must be real, documented, and not pretextual.

The file should ordinarily show
  • A document recording the business decision — board resolution, management directive, or equivalent
  • Identification of the positions affected and the headcount reduction rationale
  • Evidence that the decision has been or will be implemented
Where records typically weaken

Business decisions documented only after a termination challenge has been filed attract judicial scepticism. A decision that merely reorganises responsibilities without eliminating the underlying need for the work is difficult to sustain.

Document refsEC-1
G2.C2
Comparable pool definition

Social selection under §1 Abs. 3 KSchG requires identification of all comparable employees. Three tests of comparability apply: hierarchical interchangeability, functional interchangeability, and same-establishment criterion. Unjustified narrowing of the pool is a common and significant vulnerability.

The file should ordinarily show
  • A list of all employees assessed for comparability
  • Documentation of the three comparability tests applied to each employee considered
  • A reasoned basis for why any employee excluded from the pool was found non-comparable
Where records typically weaken

Employers systematically underestimate the breadth of the comparable pool. Excluding employees with slightly different titles without functional analysis is a recurring error.

Document refsEC-2
G2.C3
Social data — completeness across pool

For each employee in the comparable pool, the social selection analysis must be based on complete and accurate data across the four statutory criteria: tenure, age, dependants, and disability status.

The file should ordinarily show
  • A data record showing tenure, age, dependants, and disability status for every pool member
  • Documented source of each data point (HR records, employee self-declaration, disability certificate)
  • Confirmation that data was current as at the decision date
Where records typically weaken

Disability status is the most frequently incomplete data field. Dependant counts are often not updated following life changes.

Document refsEC-3
G2.C4
Weighting model — documented and justified

The employer must apply a weighting model to the four social criteria. That model must be documented and justified before the scoring is conducted. A model constructed after the selection is complete cannot reliably be distinguished from post hoc rationalisation.

The file should ordinarily show
  • A documented weighting model specifying the relative weight of each social criterion
  • A contemporaneous justification for the weightings chosen
  • Evidence that the weighting model predates or was contemporaneous with the scoring exercise
Where records typically weaken

Undated weighting documents are a persistent problem. Models that diverge from prior practice, or that produce a result eliminating someone already identified, attract judicial scrutiny.

Document refsEC-4
G2.C5
Scoring matrix and selection outcome

The social selection process must produce a completed scoring matrix for all pool members and a ranked list. Where the selected employee is not the lowest-scoring member, the deviation requires specific justification.

The file should ordinarily show
  • A complete scoring matrix with scores for all pool members across all criteria
  • A ranked list derived from the matrix
  • The selected employee is the lowest-scoring member, or the deviation is specifically and contemporaneously justified
Where records typically weaken

Incomplete matrices — with cells missing for some employees — are common. Selection of a higher-scoring employee without documented justification is among the most frequently litigated points in Route C cases.

Document refsEC-5EC-6
G2.C6
Exemptions from social selection — specific justification
Applies where: exemptions from the pool have been claimed under §1 Abs. 3 S. 2 KSchG

§1 Abs. 3 S. 2 KSchG allows exclusion of employees holding special indispensable knowledge or skills. Each such exemption must be specifically justified — a blanket claim of indispensability is insufficient.

The file should ordinarily show
  • Each exempted employee is individually identified
  • A specific, documented basis for each exemption (the particular knowledge or skill and why it cannot be substituted)
  • No pattern suggesting the exemption mechanism was used to protect higher-scoring individuals from selection
Where records typically weaken

Exemptions claimed for employees with standard qualifications, or exemptions that protect most of the pool from selection, are scrutinised heavily.

Document refsEC-7
G2.C7
Mass layoff notification — §17 KSchG
Applies where: number of dismissals triggers §17 KSchG thresholds

Where the scale of the redundancy triggers §17 KSchG, the employer must notify the Bundesagentur für Arbeit before issuing any notices. A notice issued before notification is properly filed is void.

The file should ordinarily show
  • A copy of the §17 KSchG notification submitted to the BA
  • The BA receipt confirmation, dated before any notice was issued
  • The notification is substantively complete (identifies affected employees, timeframe, grounds, consultation status)
Where records typically weaken

Errors at this stage are frequently discovered late. The notification requirement is triggered by dismissal numbers over a defined period — employers sometimes fail to aggregate dismissals or miscalculate the relevant period.

Document refsEC-11
Route D: extraordinary termination for cause under §626 BGB — where continued employment to the end of the notice period is unreasonable.
G2.D1
Important reason — documented basis

An extraordinary termination under §626 BGB requires an ‘important reason’ — facts and circumstances that make continued employment to the end of the ordinary notice period unreasonable. General assertions of trust breakdown or reference to an unspecified incident are insufficient.

The file should ordinarily show
  • A specific, dated triggering event with a factual description
  • An analysis of why the event constitutes an important reason under §626 Abs. 1
  • Documentation of the facts as they were known to the employer at the time of the decision
Where records typically weaken

Post hoc construction of the important reason narrative is a significant litigation vulnerability. Where the reason is characterised as a series of events, each should be documented.

Document refsED-1ED-5
G2.D2
Two-week deadline — §626 Abs. 2 BGB

§626 Abs. 2 BGB requires the extraordinary notice to be issued within two weeks of the employer obtaining positive knowledge of the facts constituting the important reason. A notice issued on day 15 or later is void as a matter of law.

The file should ordinarily show
  • A documented record of when, and by whom, the triggering facts first came to the employer’s knowledge
  • The termination notice issued within 14 calendar days of that date
  • Where the knowledge date is disputed: contemporaneous records supporting the employer’s position
Where records typically weaken

The clock starts when the employer has enough information to form a reasonable view — not when the internal investigation formally closes. The burden of proof on the knowledge date rests with the employer.

Document refsED-2ED-3
G2.D3
Warning necessity — extraordinary context

Even for extraordinary termination, courts require that the employer considered whether a formal warning would have been sufficient to correct the conduct. Where the conduct is so severe that continued employment is impossible, the warning step may be dispensed with — but that determination must be documented.

The file should ordinarily show
  • A documented assessment of whether a formal warning was considered before extraordinary notice
  • If warning was not issued: a specific recorded basis for why the severity of the conduct made warning unnecessary
  • If a prior warning exists for related conduct: reference to it and documentation of its inadequacy
Where records typically weaken

The warning necessity assessment is frequently omitted from extraordinary termination files. This omission invites a court argument that the employer did not genuinely apply the proportionality test.

Document refsED-8
Review resolution — on the present record
File appears sufficient on applicable route
On the present record, the file addresses the substantive requirements for the applicable route without obvious gaps on the points reviewed.
File appears exposed on one or more substantive points
The file shows gaps or weaknesses in the substantive justification that would ordinarily attract challenge. The exposed points are identified above.
Document Reference Glossary
EU-WF
Written form — original notice, signature verification, delivery proof
EU-NP
Notice period — tenure, statutory minimum, contractual provision, effective date
EA-1
Conduct incident record — date, description, duty breached
EA-2
Abmahnung document — text, date, delivery proof, three-function analysis
EA-3
No-warning exception basis — justification for dispensing with prior warning
EA-4
Culpability assessment — analysis of employee fault and mitigating circumstances
EA-5
Negative prognosis — documented basis for expectation of future misconduct
EB-1
Absence record — 24-month history of dates, durations, reason classification
EB-2
BEM process — initiation, invitation, employee response, outcome
EB-3
Health prognosis — negative prognosis with medical or operational basis
EB-4
Operational impact — documented disruption to operations from absence pattern
EC-1
Business decision record — restructuring rationale, affected positions, headcount basis
EC-2
Comparable pool — three comparability tests applied to each employee considered
EC-3
Social data — tenure, age, dependants, disability status per pool member
EC-4
Weighting model — scoring weights and contemporaneous justification
EC-5
Scoring matrix — complete scores for all pool members across all criteria
EC-6
Ranked selection list — lowest-scoring employee identified
EC-7
Exemption justifications — per-employee §1 Abs. 3 S. 2 basis
EC-11
§17 KSchG notification — BA filing and receipt confirmation
ED-1
Triggering event — date, description, characterisation as important reason
ED-2
Knowledge date — date of responsible decision-maker’s knowledge
ED-3
Two-week deadline calculation — knowledge date to notice date
ED-5
Important reason analysis — §626 BGB proportionality assessment
ED-8
Warning necessity assessment — consideration of Abmahnung before extraordinary termination
Review Point G3
Last Resort — Proportionality and Alternatives
§1 Abs. 2 KSchG  ·  Verhältnismäßigkeitsgrundsatz (general proportionality principle in German employment law)
German employment doctrine requires that termination be a last resort — that the employer genuinely considered and documented why less severe measures were insufficient before deciding to terminate. This is not a box-ticking exercise: courts inspect the substance of the proportionality assessment. A file that does not demonstrate genuine engagement with alternatives is exposed regardless of the strength of the substantive ground.
G3.1
Proportionality analysis — documented

The employer must be able to show that the decision to terminate, rather than apply a lesser measure, was proportionate to the legitimate aim. This requires specific, documented consideration of the factual circumstances — not a generic assertion that termination was necessary.

The file should ordinarily show
  • A document or contemporaneous record showing that proportionality was specifically considered
  • Identification of the legitimate aim the termination serves
  • A reasoned basis for why termination was proportionate to that aim in the specific circumstances of this case
Where records typically weaken

Proportionality analyses that are standard-form, post hoc, or that do not engage with the employee’s specific circumstances are treated by courts as insufficient.

Document refsEA-6EA-7EB-5EB-6EC-9ED-6ED-7
G3.2
Alternatives — evaluated and documented

Before termination, the employer must have genuinely considered whether less severe measures could have addressed the underlying issue. In a conduct case: whether a further warning or demotion would have sufficed. In an illness case: whether adjusted duties or part-time work were viable. In a redundancy case: whether a vacant position elsewhere was available.

The file should ordinarily show
  • A record of the alternative measures considered before termination was decided upon
  • For each alternative: a reasoned basis for why it was insufficient or unavailable in the specific circumstances
  • Evidence that the consideration of alternatives was genuine and contemporaneous with the decision
  • In redundancy cases: a documented vacancy search or duty-modification assessment
Where records typically weaken

Files in which the alternatives assessment is entirely absent, or in which it is a single sentence, are consistently the most exposed. Where the employer argues no alternatives were available, absence of any vacancy search is particularly difficult to defend.

Document refsEA-6EA-7EB-5EB-6EC-9ED-6ED-7
Review resolution — on the present record
Proportionality appears documented on the present record
The file shows a reasoned, contemporaneous proportionality assessment and documents the alternatives considered and why they were insufficient.
Proportionality assessment is absent or insufficient
The file does not demonstrate genuine engagement with proportionality or alternatives. This is a significant vulnerability across all termination routes.
Document Reference Glossary
EA-6
Route A — proportionality analysis: milder measures considered in conduct context
EA-7
Route A — alternatives: redeployment, demotion, transfer assessed
EB-5
Route B — proportionality analysis: milder measures in illness context
EB-6
Route B — alternatives: adjusted duties, part-time, transfer
EC-9
Route C — proportionality: alternative to headcount reduction assessed
ED-6
Route D — proportionality: severity of reason vs. termination
ED-7
Route D — alternatives: suspension or graduated measures
Review Point G4
Consistency — Equal Treatment Review
Allgemeiner Gleichbehandlungsgrundsatz  ·  Betriebliche Übung
This review examines whether the employer has treated similarly situated employees consistently. Inconsistent treatment does not make a termination void, but it materially weakens the employer’s position and invites a court to question whether the underlying reason was pretextual. Where consistency evidence is absent from the file, this issue remains open and may surface in proceedings.
Note on scope: Unlike the other review points, absence of consistency documentation does not by itself render a termination defective. It creates an evidentiary gap — the employer may be unable to rebut a challenge to consistent treatment if the issue is raised in litigation. The significance of this gap depends on the specific circumstances of the case.
G4.1
Comparable treatment — documented basis

Where the employer has, in prior cases, applied milder measures to employees in comparable circumstances, the decision to terminate this particular employee requires a documented explanation. Courts scrutinise inconsistency as a potential indicator of selective enforcement or undisclosed motivation.

The file should ordinarily show
  • A record of how comparable situations have been handled in the same establishment or organisation
  • Where prior cases resulted in milder sanctions: documentation of the specific differences in the present case that justify the more severe measure
  • An absence of any indicators that the employee’s protected characteristics or union activity played any role in the selection
Where records typically weaken

Employers who have previously issued warnings for substantially the same conduct, and who cannot explain why termination rather than a further warning was applied here, face a heightened proportionality challenge.

Document refsEU-CON
Review resolution — on the present record
No consistency issue identified on present record
The file does not surface obvious inconsistency or disparate treatment concerns. No comparable cases creating a contradiction have been identified in the materials reviewed.
Consistency record absent — issue remains open
The file does not contain consistency documentation. This does not establish a defect, but the employer may be unable to rebut a comparator argument if one is raised.
Consistency concern identified
The file contains indicators of inconsistent treatment. This warrants closer review before any proceedings.
Document Reference Glossary
EU-CON
Consistency / equal treatment evidence — comparable cases, disciplinary history, prior terminations in similar circumstances
Review Point G5
Co-Determination over Technical and Monitoring Systems
§87 Abs. 1 Nr. 6 BetrVG — works council right of co-determination over technical employee-monitoring systems
Where monitoring, analytical, or performance-tracking systems contributed materially to the evidence base, the works council’s co-determination rights under §87 Abs. 1 Nr. 6 BetrVG are engaged. Evidence derived from a system deployed without the required co-determination may be procedurally tainted and subject to an evidence-use prohibition (Beweisverwertungsverbot), significantly limiting the employer’s ability to rely on it in proceedings.
G5.1
Works council involvement in system deployment
Applies where: technical or analytical systems materially contributed to the evidence base

§87 Abs. 1 Nr. 6 BetrVG grants the works council a co-determination right over the introduction and use of technical equipment designed to monitor employee performance or behaviour. If data derived from such a system is used to support a termination decision, its deployment must have been co-determined.

The file should ordinarily show
  • Documentation of the works council’s involvement in the deployment of the relevant system
  • Confirmation that the system was introduced with council consent or under a procedure consistent with co-determination rights
  • Evidence of when the system was first deployed relative to the data forming part of the termination record
Where records typically weaken

Systems deployed years earlier without proper co-determination and then used for the first time in a disciplinary context create particular vulnerability. The passage of time does not remedy the original procedural defect.

Document refsET-CD
G5.2
Betriebsvereinbarung (works agreement) governing system use
Applies where: technical or analytical systems materially contributed to the evidence base

Where a works agreement governs the system, it defines the scope within which data may be used. Use of system data outside the purposes or limitations specified in the agreement undermines the permissibility of that evidence.

The file should ordinarily show
  • A Betriebsvereinbarung or equivalent agreement governing the specific system used
  • The agreement permits use of the data for the purpose for which it is being deployed in this case
  • No gap between the scope of the agreement and the use being made of the data
Where records typically weaken

Works agreements that authorise data collection for time-management purposes but not for disciplinary use are frequently the subject of challenge when the employer attempts to use the same data to support a termination.

Document refsET-CD
Review resolution — on the present record
Co-determination record appears in order
On the present record, the relevant system appears to have been deployed with appropriate co-determination, and any governing works agreement covers the use being made of the data.
Technical evidence may be procedurally tainted
The file shows indicators that the system was deployed without proper co-determination or that the data is being used outside the scope of the governing agreement. Admissibility may be challenged in proceedings.
Document Reference Glossary
ET-CD
Tech co-determination — §87(1) Nr. 6 BetrVG works council involvement in system deployment, Betriebsvereinbarung scope and coverage
Review Point G6
Decision-Path Explainability — Algorithmic and Analytic Involvement
GDPR Art. 22 (automated individual decision-making)  ·  EU AI Act Annex III (high-risk AI systems)  ·  BDSG §31
Where algorithmic, predictive, or AI-based systems played a role in the analysis or evidence underlying the termination decision, the employer must demonstrate that a human decision-maker independently reviewed and adopted the decision. A decision that cannot be explained in terms of human judgment, or where the algorithmic contribution is not transparently documented, is exposed to challenge under GDPR Art. 22 and the EU AI Act.
G6.1
Employee notified of algorithmic involvement
Applies where: algorithmic or AI-based systems contributed to the decision path

Where an algorithmic or AI-assisted system materially contributed to the decision — by generating a recommendation, scoring the employee, or surfacing data that was relied upon — the employee is ordinarily entitled to be informed of that fact. Failure to notify creates a transparency risk and may engage Art. 22 GDPR.

The file should ordinarily show
  • Documentation confirming that the employee was informed of the role of any algorithmic or AI system in the process
  • The notification was timely — before or at the point of the decision, not retrospectively
  • The notification was specific enough to allow the employee to understand what system was used and for what purpose
Where records typically weaken

Employers frequently fail to distinguish between internal use of analytic tooling and use of system outputs as the basis for an employment decision. The line between these categories is the focus of developing regulatory attention.

Document refsET-MT
G6.2
Human adoption of the decision — independently documented
Applies where: algorithmic or AI-based systems contributed to the decision path

Regardless of the role played by any system, the termination decision must have been taken by a human decision-maker who independently reviewed the relevant facts. A decision adopted wholesale from a system recommendation, without independent human review, is at risk under Art. 22 GDPR where the system’s output was determinative.

The file should ordinarily show
  • A documented record of the human decision-maker who authorised the termination and the date of authorisation
  • Evidence that the decision-maker reviewed the underlying facts and did not merely ratify a system recommendation
  • Where a system produced a recommendation: documentation showing it was considered alongside, not instead of, independent review
Where records typically weaken

The key question is whether the human review was substantive or merely formal. A decision-maker who approves a recommendation within minutes of receiving a system output, without any documented independent consideration, is unlikely to be treated as having exercised genuine human oversight.

Document refsET-MT
G6.3
GDPR Art. 22 and EU AI Act assessment
Applies where: algorithmic or AI-based systems contributed to the decision path

Where a system produced an output — a recommendation, score, or classification — relied upon as part of the decision, the employer should have assessed whether Art. 22 GDPR applies and, if so, what lawful basis permits it. Under the EU AI Act, systems used to make or materially influence employment decisions may be classified as high-risk.

The file should ordinarily show
  • A documented assessment of whether Art. 22 GDPR applies to the specific use of the system in this case
  • If Art. 22 applies: the lawful basis (explicit consent, contractual necessity, or authorised Member State law) is identified
  • Where the EU AI Act is engaged: documentation of conformity obligations, human oversight measures, and employee rights under the Act
Where records typically weaken

Many employers have not conducted Art. 22 assessments for internal HR analytics tools, assuming a human ‘in the loop’ automatically exempts the process. Courts and regulators are increasingly examining whether that human involvement was substantive.

Document refsET-MT
Review resolution — on the present record
Decision-path documentation appears adequate
On the present record, the human decision-maker’s independent review is documented, employee notification appears to have been addressed, and the regulatory assessment is on file.
Decision-path explainability is incomplete
The file does not demonstrate independent human review, or the employee notification and regulatory assessment are absent. This creates exposure where the system played a material role in the evidence base or recommendation.
Document Reference Glossary
ET-MT
Decision-path documentation — employee notification of system use, human oversight record, GDPR Art. 22 / EU AI Act assessment
Review Point G7
Anti-Discrimination — Decision Basis and Protected Grounds
AGG — §1 (protected characteristics)  ·  §3 (direct and indirect discrimination)  ·  §22 (burden of proof)
The AGG prohibits termination motivated by a protected characteristic. The employer does not need to intend discrimination — the mere presence of protected-ground indicators in the decision-making record shifts the burden of proof to the employer under §22 AGG. The file’s role here is to document that the decision rested on stated, legitimate grounds. A file with gaps or ambiguity in the decision basis is at risk of a burden-shift challenge.
Protected characteristics under §1 AGG: Race and ethnic origin  ·  Gender (including pregnancy and maternity)  ·  Religion or belief  ·  Disability  ·  Age  ·  Sexual orientation. Any indicator in the file connecting the termination decision to one of these characteristics engages §22 and may shift the burden of proof.
G7.1
Decision basis — documented and specific

The employer’s basis for the termination decision must be explicitly documented in terms that allow the employer to demonstrate, if challenged, that the decision rested on the stated factual grounds and not on a protected characteristic. A file in which the decision basis is vague, unstated, or inconsistent across documents creates a burden-shift risk under §22 AGG.

The file should ordinarily show
  • The decision documentation specifically identifies the factual basis for termination
  • The documented basis is consistent across all relevant documents (hearing letter, internal authorisation, termination notice)
  • No inconsistency between the stated basis and any other record that might suggest an alternative motivation
Where records typically weaken

Files in which the termination reason evolved between internal discussion and the formal hearing letter, or in which informal communications suggest a different motivating factor, are particularly exposed. Even an innocuous remark can become a §22 indicator in adversarial proceedings.

Document refsEU-AGG
G7.2
No protected-ground indicators in the decision record

Beyond the formal decision basis, the broader record — internal communications, performance reviews, manager assessments, works council correspondence — should be reviewed for any language or reasoning that connects the decision to a protected characteristic. Such indicators do not require discriminatory intent — their presence alone is sufficient to engage the §22 burden shift.

The file should ordinarily show
  • A review of internal communications contemporaneous with the decision for any reference to protected characteristics
  • Performance records and manager assessments do not use language that references or is code for a protected characteristic
  • Where the employee belongs to a group that may have been disproportionately affected: consideration of indirect discrimination exposure
Where records typically weaken

Age and disability are the protected grounds that most frequently appear in termination files without the employer’s awareness — through indirect references to ‘fit with a younger team’, or assessments of capacity that may implicitly engage disability. These are the most common unintended AGG exposure points.

Document refsEU-AGG
Review resolution — on the present record
No obvious protected-ground signal on present record
On the present record, the decision basis is documented and no indicators connecting the decision to a protected characteristic have been identified. This review does not constitute a clean bill of health — it reflects the current state of the file.
Decision basis gap or protected-ground signal present
The file shows either an undocumented or inconsistent decision basis, or indicators that connect the decision to a protected characteristic. The §22 AGG burden of proof may shift to the employer if this issue is raised in proceedings.
Document Reference Glossary
EU-AGG
Anti-discrimination record — decision basis documentation, protected-ground indicator review, §22 AGG burden-of-proof defence materials