The most common mistake when closing a report is that the handler only communicates the outcome verbally to the reporter, without documenting it anywhere. There is then no file showing what was investigated, what steps were taken, and why the report was closed as it was.
You prevent this by documenting every step in the process in writing, even if the report seems informal or was resolved quickly. This applies to receipt, intermediate steps, and the closure itself, including the reason why you reached that outcome.
What goes wrong in practice
In smaller organizations, much happens informally. A handler speaks briefly with the reporter, explains what was done, and considers the matter closed. That feels logical, especially when a report is resolved quickly. But without written documentation, you create a file that does not later show what happened. If the reporter asks questions later, or if a supervisor or works council wants to know how the process unfolded, there is nothing to fall back on.
A second common mistake is that the closure is documented, but without supporting information. For example, it might simply state that the report was closed, without making clear what steps were taken and on what basis the conclusion was drawn. That is difficult to defend, even if the handling itself was careful.
Why this creates a risk
The reporting system has a deadline by which the reporter receives information about the assessment of the report. That deadline can only be demonstrated to have been met if there is a documented moment when that information was provided. Without a file, an organization may say this happened, but cannot show when and how.
Additionally, the protection of the reporter is relevant. A well-documented file demonstrates that the report was treated seriously and that the outcome is based on a completed process, not on a passing impression. This is also in the organization's own interest: in the event of a follow-up question, a complaint, or a later dispute, a clear file is the only thing that convinces.
A practical example
A handler receives a report about a conflict between two colleagues. He speaks with both parties, resolves the conversation informally, and lets the reporter know it is resolved. That sounds like good handling, but if there is no record of the conversations, no date of the feedback, and no description of the steps taken, there is no evidence of what exactly was done. If the situation recurs later, the organization is left empty-handed.
How you prevent this
For each report, document at minimum three moments: receipt, the core of the investigation or the steps taken, and the closure with the date on which the reporter was informed. This does not need to be an extensive report. A short, factual summary is sufficient, as long as it makes clear what happened and when.
It helps to not leave this to the handler's memory, but to put it in a fixed structure that is followed for every report. A handling environment in which deadlines run automatically makes it easier to do this consistently, even for reports that seem quickly resolved. In the knowledge base on closing a report it is detailed which components a file minimally needs.
Retention period after closure
After closure, another important matter is how long you retain the file and who has access to it. Data that can be traced back to the reporting person requires careful handling, even after the case is closed. How this is precisely arranged depends on your organization and the nature of the report; for the correct retention period and the handling of personal data, it is advisable to consult the Data Protection Authority or a lawyer. You can read more about how data is stored and secured within the platform on the page on security and data handling.
If you want to know exactly where the information on this platform comes from and how the time limits are monitored, the page how the platform monitors the time limits explains that step by step.
Would you like to quickly see whether your organization's process for closing and recording is in order? Take the free check in a few questions or continue reading in the knowledge base about the other steps in the reporting process.