EU Whistleblower Directive · Module 1 of 5
Day 0 · Tuesday · 07:52 · Köhler-Marchais HQ, Düsseldorf
You are Elena Vasquez, Chief Compliance Officer at Köhler-Marchais — a French-German industrial group. An encrypted message arrived through the internal reporting channel at 23:31 last night. The reporter cited HinSchG by name. They know the law. They will know if you breach their protection.
Three decisions, five activities, twenty-five minutes. You have seven days under Article 9(1)(b) to acknowledge the report. The CFO will call before 10:00. He wants this handled quietly.
Every module of this course is a flashback. You are remembering Day 0 from a Bundesamt für Justiz hearing room six months later — Day 186 — where Dr. Linke is asking you what happened. The hearing is the frame. Every module bookends back to it.
Estimated time: 20–25 minutes
The report contains four attachments. You can open three of them before the 7-day acknowledgment deadline forces you to respond. The attachment you leave closed becomes a gap in your investigation. Choose carefully — you cannot go back.
Day 3. The 7-day acknowledgment deadline under Article 9(1)(b) requires you to confirm receipt. How do you acknowledge — and what do you say?
The reporter receives a clean, procedurally correct acknowledgment. They don't reply further — which is normal. Your compliance with Article 9(1)(b) is documented. Your Confidentiality, Investigation Quality, and Retaliation Shield bars all move in the right direction.
Art. 9(1)(b) requires acknowledgment of receipt within 7 days. It does not require you to explain the investigation process, disclose who will handle it, or request information from the reporter. The minimum viable acknowledgment is the maximum safe one.
The reporter's silence after receipt is normal and expected. Do not interpret it as an invitation to ask further questions.
Your detailed acknowledgment lands in the reporter's inbox at 14:30. The request for identity confirmation — even framed as optional — lands like a test. By 15:45 Dr. Hoffmann has called. He has read your draft before it was sent. His tone is even but firm.
HinSchG §15 protects the independence of the reporting channel. Asking the reporter to identify themselves — even as an optional courtesy — communicates that identification would be preferred. That preference is itself a chilling act. The law treats the ask, not the answer, as the procedural defect.
Your Confidentiality bar takes a material hit. Your Retaliation Shield also drops — the reporter now reasonably suspects that identity protection is negotiable inside this organisation.
You cannot request an extension. The 7-day deadline is absolute. Day 7 passes without acknowledgment — you are now in breach of Article 9(1)(b). On Day 8 the reporter files an external report with the BaFin.
Art. 9(1)(b) is not a guideline. The 7-day acknowledgment window is a hard regulatory obligation — missing it is a standalone breach regardless of whether the substantive investigation is otherwise competent.
Once the reporter escalates externally, your Process Integrity collapses. The M5 hot-seat in the BfJ framing device will open with this specific question. On this path, the final ending routes toward The Aftermath — a tribunal years later with damages awarded.
Dr. Hoffmann is on the phone. The revenue recognition issue touches the Paris parent — the VP Sales role that the email thread implicates reports to the Group CEO in France. Friedrich Köhler is also asking whether this should go to the Group CFO.
How do you route the investigation?
Dr. Hoffmann concurs. German law governs the German entity. Investigation proceeds under HinSchG without Paris visibility until you have findings to report. This protects reporter identity and investigation integrity.
Group-structure allocation permits joint investigation but doesn't require it when the conduct is substantively domestic. Routing to Paris automatically widens the circle of people who see the report — which widens the attack surface for confidentiality leaks.
Your Confidentiality and Investigation Quality both move up. The sidebar HUD reflects the strengthened posture going into the retaliation analysis next.
Group Legal in Paris now has access to a report that implicates someone who reports to the Group CEO. Confidentiality is materially compromised. Dr. Hoffmann notes this as a HinSchG §15 independence breach in his working papers.
HinSchG §15 treats independence as a continuing property of the handling chain. Every additional person who sees the report is a new point where independence can fail. A routing decision that widens the chain without necessity is itself a §15 concern.
Confidentiality drops sharply. Investigation Quality dips. Process Integrity takes the largest hit — this is the metric the M5 BfJ hot-seat is most sensitive to.
You ask Dr. Hoffmann for a written jurisdictional memo before routing anything further. He agrees. By Day 5 end-of-business, his two-page memo lands: local investigation under HinSchG with a separate escalation path to the Supervisory Board — not Paris management — if findings require it.
Asking for counsel's written view before routing costs you one working day. It also creates a contemporaneous record of why the routing decision was made — which is the exact document a later reviewer (Bundesamt, tribunal, or Supervisory Board) will ask for.
Confidentiality and Investigation Quality edge up. Not the strongest posture — but defensible on any angle.
Eight workplace actions have been proposed or taken involving Finance team employees since the report was filed. Classify each as Retaliation or Legitimate Management. Remember — Art. 19 and Art. 21(5) reverse the burden of proof. Timing matters. The employer must disprove retaliation, not the other way round.
Loading your classification summary…
Art. 21(5) reverses the burden of proof on retaliation. In any proceeding where the reporter alleges detriment, the employer must show the adverse action had independent grounds. The investigator's classification record — the document you've just built — is the evidence that reversal runs on.
Every action you correctly classified as retaliation becomes a data point in the protection architecture. Every one you missed becomes a gap the employer can lean on in a dispute. This is the mechanical core of Art. 19 — not the rule itself, but the way it operates in practice.
Friedrich Köhler has requested a meeting. He wants the investigation handled internally — corrected accounts, no external involvement. This is a three-round negotiation. Each response you make shifts your position between Compromised and Compliant. The final position determines what you carry into the Supervisory Board meeting.
Loading negotiation outcome…
Friedrich's instinct to resolve the matter internally is normal executive behaviour under pressure. It is your job as Compliance Officer to decline that framing without making him an adversary. The HinSchG architecture does not permit pre-commitments about scope, routing, or escalation. Every response you gave was either protecting that discipline or eroding it.
Your final position carries forward into the Supervisory Board briefing (Decision 2). A Compliant posture gives you the ground to recommend proper escalation. A Compromised posture constrains your options.
Three people want information from you this week. Each deserves a different calibration between Complete Silence and Full Disclosure. Use each slider to set where your response should land. The zone feedback shows whether you're within the appropriate range.
Dr. Hoffmann has collated six financial documents. Classify each as Suspicious (supports wrongdoing finding), Normal (routine, explained), or Inconclusive (relevant but not dispositive alone). Your classification feeds the SBAR composer and the Supervisory Board briefing.
The reporter has sent a short follow-up through the secure channel. Read the external text first. Then use the toggle to see what lies beneath the formal words. Both readings matter — one for the process, one for your decision about Art. 19 protection.
Investigation findings are substantive. Systematic revenue recognition issues across 34 transactions. A clear incentive structure that enabled it. A VP Sales who was aware. Auditor queries that were closed without proper scrutiny. Friedrich Köhler has not been implicated directly — but his management oversight of the Finance Controller is a question. Dr. Hoffmann is advising on escalation.
The escalation cannot go forward as a narrative email. It goes forward as SBAR — Situation, Background, Assessment, Recommendation. Each section below has three options. Pick the line that most accurately and completely fulfils the purpose of that element. Precision matters more than formality; the record of what compliance said, and when, is itself discoverable. You can change your selections up to the moment you submit.