Know if the Kündigung holds — before it goes out.
Built for the three people who carry a German termination. For HR: know what a termination will cost you, before you sign it. For in-house counsel: the termination you lose is rarely the one you got wrong — it's the one you can't reconstruct. For the employment lawyer: the question was never whether your client can terminate, but whether the file survives eighteen months from now.
Verfahrenscheck runs the termination file against the eight statutory gates German courts test it on. Each gate passes, fails, or flags a gap — silence is never a pass. An unflagged gap is what voids a correct decision and becomes Annahmeverzug you never forecast.
One live matter, de-identified locally, documented read in 72 hours. The engine runs on your own device — AI is used only to build it, never on a client matter. HR can start it — no legal sign-off needed to generate the de-identified read.
Procedural completeness review (Tier 1) · not Rechtsberatung
The output is not “here is the answer.” The output is here is what is defensible — a per-finding map of evidence, gate, and BAG warrant. Inspectable end to end.
- Built from 50BAG decisions 500 planned
- Evaluates 8 gates 53 sub-gates 78 evidence codes
- Produces Onedefensibility report Three views planned
- Delivered 72 htypical turnaround, file to report
On-device · raw documents never leave the device · no cloud inference — see Security & data handling →
Start from where you sit.
Each seat has two ways in: read the walkthrough written for your role, or — if you’re not ready to bring a file — run the 3-minute scenario check first.
Eight gates. One fail-closed standard.
Each gate is anchored to a statutory provision or established authority. Where authority cannot be verified, the gate flags the limitation rather than asserting certainty. Same methodology, every matter, every manager, every site.
- G0Special Protection Screen · §17 MuSchG · §168 SGB IX
- G1Works Council Hearing · §102 BetrVG
- G2Social Justification · §1 KSchG · §626 BGB
- G3Ultima Ratio · Verhältnismäßigkeit
- G4Consistency · Equal-treatment principle
- G5Co-Determination Tech · §87(1) Nr. 6 BetrVG
- G6Model Transparency · GDPR Art. 22 · AI Act
- G7Anti-Discrimination · §1, §22 AGG
The challenge is not generating recommendations. The challenge is defending decisions.
The same file always produces the same read — today and in five years. Nothing about the verdict is generated, guessed, or quietly softened, which is what lets the audit trail hold up when someone tests it later.
What we check. What we don't.
We test whether a dismissal will hold up procedurally — not how a judge will feel about it. Every boundary below is deliberate, and every gap is named.
Run one file through the gates.
Bring one live matter. Generate the de-identified intake locally. Receive a documented defensibility read, typically within 72 hours.
Prefer to read first? See a sample read (de-identified).
Advising on the file rather than signing it? Pressure-test it the way the bench will →

