Seven days for the acknowledgement Three months for the response Reporting without giving your name

Custom app for an internal whistleblowing procedure

A reporting procedure that exists only on paper is worse than none at all: it creates the expectation that something will happen with a report. The law sets deadlines for this. An acknowledgement within seven days and a substantive response within three months at most are not goals but obligations, and the clock starts running from the moment of the report.

What the law requires of the channel

Employers with at least fifty employees must have an internal reporting procedure that meets the requirements of the Whistleblowers Protection Act (Wet bescherming klokkenluiders). The same applies to some employers with fewer employees, for example in the financial sector. The procedure describes how a report is handled and whom someone can turn to, and there must be points of contact with an independent officer.

Two deadlines apply to handling a report. An acknowledgement of receipt within seven days, and a substantive response within a reasonable period of three months at most. The first is short enough to miss when a report lands in a shared mailbox and the person handling it is on holiday. That is not a theoretical risk: it is exactly how most deadlines are missed.

In addition, you must record all reports in a dedicated register. That register is also the most sensitive file you hold, because it contains suspicions about colleagues and the identity of whoever made the report. It must therefore exist, be complete, and at the same time be strictly protected. Meeting all three requirements at once is not possible with a mailbox and a folder.

How we build this

Confidentiality and deadline monitoring pull in opposite directions. If you want to protect the reporter, you cannot let the handling run through a mailbox; if you want to meet the deadline, you cannot either.

1
Keeping the channel separate from your regular systems

A report does not belong in a shared mailbox, a ticketing system or an HR file. Whoever has access to one should not automatically have access to the other.

2
Allowing anonymous reporting while still being able to respond

A reporter who does not want to give their name must still be able to receive a reply. That requires a communication channel without identity, and that is a design choice, not a setting.

3
Starting the clock from the moment of the report

Seven days and three months start at the moment of reporting, not at the moment someone read it. That clock belongs in the system.

4
Getting the register right from the start

Every report goes in, including the report that turns out not to be a wrongdoing. Filling it in afterwards is not an option, because then you miss precisely the reports that were closed without being recorded.

What the app actually does

The reporting channel with deadline monitoring carries the whole. What you add beyond that depends on your size and on who handles the reports.

Reporting with or without a name

A reporter chooses for themselves. With anonymous reporting, a communication channel stays open without the identity becoming known, because otherwise anonymous reporting is a dead end.

The seven days and the three months monitored

Both deadlines run from the moment of the report and are tracked visibly, with a warning before they expire rather than after.

Handling with a visible status

The reporter can see which stage their report is in, without substantive details. Silence is the main reason people report externally.

The mandatory register filled automatically

Every report goes in, with date, nature and outcome. A register compiled afterwards by definition misses the reports that were dealt with informally.

Points of contact and external confidential adviser

The law requires contact points with an independent officer. That can be an external party, who then has their own access to only their own reports.

Everything recorded, including who looked

When a report concerns a manager, the question of who has viewed the file is just as relevant as the report itself.

Who we build for

The set-up depends on your size and on who handles the reports. Four situations.

Companies with fifty or more employees

This is where the obligation begins. The pitfall is a procedure that has been adopted but whose channel is a mailbox nobody monitors. Training around it is covered under integrity training.

Healthcare and education

Large organisations with multiple locations and a sensitive relationship between reporter and manager. Access separation carries the most weight here.

Organisations with a public task

Alongside the law, there are your own integrity frameworks and sometimes an external supervisory body. That calls for a register that can serve several frameworks at once, through integrations with your existing systems.

External confidential advisers and lawyers

You act for multiple employers. Strict separation per client is then not a luxury but the core of your position. For the quality documentation around it, there is a quality management system.

Not sure about a large project yet?

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

Deadlines, categories and contact points differ per organisation and change over time. All of this should be configurable and not hard-coded in the app.

React Native or native iOS and Android, with a web channel Reporting with or without identity Conversation channel for anonymous reports Deadline monitoring from the moment of reporting Status information for the reporter Report register with categories Access strictly separated from HR systems External confidential adviser with their own access Full access logging Retention periods with destruction Configurable contact points and routes Export for accountability without identity Audit logging Hosting in the EU

Why Appfront

Anonymous reporters must be able to receive a reply too

We build a conversation channel without identity. Anonymous reporting without feedback is a letterbox, not a procedure.

Seven days pass quickly

We start the clock from the moment of the report and flag deadlines in advance. In a shared mailbox, meeting that deadline is a matter of luck.

The channel should be kept separate

We set this up separately from your HR and ticketing systems. Anyone with access to personnel files should not automatically be able to access reports.

Silence drives people to go outside

We show the reporter the status of their report without revealing its content. That is the cheapest way to prevent an external report.

Security and privacy

This is probably the most sensitive file in your organisation: it contains suspicions about individuals and the identity of those who reported. We grant access exclusively to the designated handlers, keep it strictly separate from HR and ticketing systems, and record every access, including attempts that were refused. When a report concerns a manager, it must be demonstrable that this person had no access.

For anonymity, technology and policy have to work together. For an anonymous report, we store no identifying data and build the conversation channel so that feedback remains possible without making the reporter traceable. Retention periods are configured and destruction moments are carried out, because a register that keeps everything forever is a risk in itself. How we handle security ourselves is set out in our information security policy; reports from outside go through our CVD policy.

Frequently asked questions about the internal reporting policy

Employers with at least fifty employees must have an internal reporting procedure that meets the requirements of the Dutch Whistleblower Protection Act. For some employers with fewer employees the obligation also applies, for example in the financial sector. Have your own position assessed by a lawyer; the counting of employees follows its own rules.

An acknowledgement of receipt within seven days of the report, and a substantive response within a reasonable period of no more than three months. Both run from the moment of reporting, not from the moment someone picks up the report. That distinction is where most deadlines are missed.

The law does not require anonymous reporting in every case, but in practice it is the only way some wrongdoing comes to light. If you offer it, you need to do it properly: an anonymous report without a feedback channel is just a letterbox. Have your procedure reviewed legally on this point.

All reports of suspected wrongdoing, in a dedicated register. That includes reports that turn out not to be wrongdoing after investigation. These are precisely the ones that tend to be dealt with informally and never recorded, and that is the gap an inspection picks up on.

We advise against it. A ticketing system is designed to distribute work and make it visible, which is exactly the opposite of what is needed here. Access to reports should be strictly limited and fully logged, and that is hard to guarantee in a shared system.

An incident reporting portal is about reports to a regulator within a short deadline, such as in the event of a calamity or a data breach. This page is about reports from employees about suspected wrongdoing within their own organisation, with protection of the reporter at its core.

Yes, and that is often wise. The law asks for contact points within an independent function; this can be an integrity officer, a lawyer or an independent third party. We give that person their own access to only their own reports, separate from your internal handlers.

That depends on your size, whether there are multiple locations or entities, and whether an external confidential adviser is involved. The reporting channel with deadline monitoring and the register can usually be used quickly and covers the core of the obligation; investigation files and reporting grow from there. We give a well-founded estimate after the discovery phase.

Want to know whether your channel really works?

Send a test report to your own reporting channel yourself and see how many days it takes before a confirmation arrives. If it takes longer than seven days, your procedure does not currently comply. We build this as a standalone app and as part of a broader app development project.

If you manage the procedure yourself across multiple entities, take a look at software for managing your internal whistleblowing procedure.

Edit content