Custom software to manage your internal whistleblowing policy
If a whistleblower suffers a disadvantage, they do not have to prove it was caused by their report. The employer must show that the disadvantage had nothing to do with the report. That is an evidential position you build long before you need it, or one you can no longer create at the moment itself.
What the law requires of the employer
Organisations with fifty or more employees must set up an internal reporting channel. The internal reporting procedure sets out how a report is handled, when there is a suspicion of wrongdoing, which independent officers receive reports, and that a whistleblower can consult an adviser in confidence. It also contains two deadlines: an acknowledgement of receipt within seven days and feedback on follow-up within a reasonable period of no more than three months.
The procedure itself cannot be set freely. With the addition of a new component to Article 27 of the Works Councils Act, the reporting procedure falls under the works council's right of consent. An amended procedure without consent is, formally, a procedure that does not exist.
The employer also has a duty to provide information. Employees must receive information about the reporting procedure itself, about the external reporting routes to the competent authorities, and about legal protection against adverse consequences following a report. That is not a one-off announcement but something that must be demonstrably available.
Then there is the prohibition of retaliation, with the reversal of the burden of proof. In proceedings, the employer who was the subject of a report must show that the disadvantage was not a result of the report. If a reorganisation, an appraisal or a non-renewed contract happens to follow a report, the question is not whether that link exists, but whether you can show that it does not.
How we build this
The core is the procedure and the context around it, not the report itself. Reporting takes place in a protected channel; this system is about what must be demonstrable around it.
Every version of the reporting procedure with its date, the works council's consent and the period in which it applied.
What was made available to whom and when about the internal and external routes and legal protection.
Different locations or legal entities have their own procedures and their own points of contact, with their own deadlines.
Personnel decisions are recorded with their justification and timeline, so that it can later be shown that they stand on their own.
What the software actually does
Managing the procedure carries the whole. What else you need depends on your size and on the number of entities within the organisation.
Version control with consent
For each version, the date, the consent and the period of validity. This makes it possible to say which procedure applied when a report came in.
Demonstrable duty to inform
Which information about internal routes, external routes and legal protection was available, and since when.
Points of contact per entity
Who receives reports at which part of the organisation, and who covers during absence. Without this, deadlines stall.
Deadlines at organisation level
The seven days and the three months apply per report. At board level, what counts is whether they are met consistently.
Retaliation file
For decisions involving a whistleblower, the justification and the timeline, built up before there is a dispute.
Aggregated overview
Numbers and turnaround times across entities, without anyone having to look at individual reports.
Who we build for
Who manages this differs per organisation. Four situations.
HR directors
They take the personnel decisions about which the question may later arise whether they were unrelated to a report.
Compliance officers
They manage the procedure and must be able to show that it was validly adopted and communicated.
Board members
They bear the responsibility and want to know whether the deadlines are met consistently, not just occasionally.
Works councils
They have a right of consent and want to see exactly what has changed compared with the previous version.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
The law gets amended, supervisory tasks shift and organisations restructure. Policies, entities and deadlines should be configurable, not hard-coded.
If a report is not about wrongdoing but about bullying, intimidation, discrimination or aggression at work, take a look at our registration system for unacceptable behaviour.
Why Appfront
The burden of proof is on you
If a reporter is disadvantaged, you must show it had nothing to do with the report. We build the record-keeping that makes this possible, before any dispute arises.
A policy without consent doesn't count
The reporting policy falls under the right of consent. We record version, consent and period of validity together.
Informing is not the same as being able to prove it
The duty to inform is about availability. We keep track of what was published and since when.
We don't build the reporting channel into this system
The reporting itself belongs in a shielded environment with its own access. That separation is the core of the protection.
Security and privacy
A reporter's identity must remain confidential, and that is not a setting but a design principle. That's why we keep the management of the policy strictly separate from the reports themselves: whoever manages the policy sees no report content, and aggregated figures cannot be traced back. Data is not kept longer than necessary, and access is logged, including access by administrators.
For this subject, the reliability of the moment is what matters. A decision rationale that was only written down after a report came in will work against you in proceedings. We record decisions and documents immutably, with timestamp and person, and turn a correction into a visible correction alongside the original entry. How we handle security ourselves is described in our information security policy.
Frequently asked questions about the internal reporting policy
Organisations with fifty or more employees must set up an internal reporting channel. For the financial sector, this also applies below that threshold.
A reporter receives an acknowledgement of receipt within seven days, and within a reasonable period of no more than three months, information about the follow-up to the report.
Yes. With the addition of a new provision to Article 27 of the Works Councils Act, the reporting policy falls under the works council's right of consent.
In proceedings, the employer must show that the disadvantage was not a result of the report. The reporter does not have to prove the link; you must show that there isn't one.
About the reporting policy itself, about the external reporting routes to competent authorities, and about legal protection against adverse consequences after a report.
In a shielded reporting channel, separate from this management system. We describe reporting with or without a name and the monitoring of deadlines per report on our page about the internal reporting policy app.
Can you show that this decision was unrelated to that report?
Take one personnel decision from the past year and find the rationale along with its date. If it turns out it was only written down once questions arose, that is exactly the position the law denies you. We build this as a standalone application and as part of a broader custom software development project.