Gate Architecture (Stufenprüfung G0–G7) — how the termination file is reviewed, gate by gate.
This page shows the review surface: what the contemporaneous file (zeitnahe Dokumentation) must contain at each legal checkpoint before counsel relies on it. Select a gate below to isolate the requirement that governs the record at that stage.
§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.
- 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
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.
§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.
- 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
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.
§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.
- 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
Approval obtained after the notice date does not remedy the defect. Employers most frequently fail here when an application is pending but undisclosed.
§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.
- 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
Files frequently omit BR membership verification. The §103 consent requirement is separate from and additional to the general §102 hearing — both must be satisfied.
§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.
- 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
Employers often lose track of DPO status following role transitions. The one-year post-removal window is frequently overlooked.
§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.
- 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
Election board membership is a short-window protection that employers frequently fail to verify, particularly in smaller establishments.
§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.
- 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
The absolute nature of this bar means no procedural remedy is available once a notice has been issued during the service period.
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.
- 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)
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.
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.
- Employee identity and position
- Termination type (ordinary or extraordinary)
- The factual basis and operative reason for termination
- The route classification the employer is applying
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.
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 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
Route substitution between hearing and notice is a recurring litigation pattern. Even where unintentional, a mismatch is treated as a procedural defect.
§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.
- 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
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.
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.
- 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
Employers who cannot produce any works council response — even a record of silence — face difficulty demonstrating the consultation sequence was properly closed.
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 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
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.
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 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
Files with handwritten date amendments or inconsistent date stamps on the termination letter create particular vulnerability here.
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.
- 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
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.
§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.
- 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
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.
§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.
- 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)
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.
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.
- 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
Disciplinary records assembled retrospectively and incident descriptions that are conclusory without particulars are the most common weaknesses in conduct-based files.
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.
- 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
Abmahnungen older than 36 months may carry reduced weight. Warnings addressing different conduct than the termination ground do not satisfy the same-conduct requirement.
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.
- 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
Files relying on a single serious incident without addressing culpability or prognosis are frequently weakened on cross-examination.
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.
- 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
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.
Beyond the absence history, an illness-based termination requires a supported negative prognosis and demonstration that the absence level causes unreasonable operational disruption.
- 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
Operational impact is frequently addressed superficially. Bare assertions of disruption without particulars are vulnerable to challenge.
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.
- 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
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.
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.
- 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
Employers systematically underestimate the breadth of the comparable pool. Excluding employees with slightly different titles without functional analysis is a recurring error.
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.
- 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
Disability status is the most frequently incomplete data field. Dependant counts are often not updated following life changes.
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.
- 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
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.
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.
- 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
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.
§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.
- 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
Exemptions claimed for employees with standard qualifications, or exemptions that protect most of the pool from selection, are scrutinised heavily.
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.
- 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)
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.
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.
- 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
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.
§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.
- 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
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.
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.
- 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
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.
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.
- 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
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.
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.
- 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
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.
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.
- 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
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.
§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.
- 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
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.
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.
- 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
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.
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.
- 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
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.
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.
- 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
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.
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.
- 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
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.
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 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
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.
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.
- 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
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.
What is the Gate Architecture (Stufenprüfung G0–G7)?
The Gate Architecture (Stufenprüfung) is the eight-gate sequential review framework at the core of the Aram Algorithm termination file review system. Each gate (Prüfstufe) evaluates a specific legal requirement of German termination law — from formal prerequisites (KSchG §§ 1–4) through works council consultation (Anhörung des Betriebsrats, BetrVG § 102) to documentation completeness (Vollständigkeit der zeitnahen Dokumentation) — using strict pass/fail criteria (Ausschlussprinzip): if the contemporaneous record does not satisfy a gate, the file does not pass that stage.
Who uses this?
Fachanwälte für Arbeitsrecht, Syndikusrechtsanwälte (in-house counsel), and Personalleiter (HR directors) use the gate architecture to identify where a termination file does not satisfy the legal requirements — before litigation strategy is finalised and the Kündigungsschutzklage deadline runs.