Configuring the channel and forms

1. Regulatory Concept & Core Standards

In this video we will work through a concrete decision: create a form that collects useful information without unnecessary identification. The aim is to explain the criterion used and apply it to a workplace situation. We will start with the concept, move to the procedure and finish with a case to solve. The demonstrations in this course use a generic platform and fictional data. Field names depend on the chosen product. The aim is to understand which settings to look for and how to verify the result, keeping technical administration rights separate from access to case content.

The form should help users describe facts: what happened, when, where and what material may help. Excessive fields create barriers and increase data collection. The choice between identification and anonymity must match the channel and the law. Do not make names mandatory in a route presented as anonymous or require users to know the legal classification of the situation.

Apply the following rule: The Act accommodates anonymous reports; the section 11 register does not require an anonymous person’s name and residence. Someone later identified may meet protection conditions. Section 10(7) protects the identity of both the reporting person and the person concerned. Written consent and lawful provision for criminal or administrative-offence proceedings have specific conditions. Do not promise absolute unidentifiability.

2. Practical Implementation & Procedure

Start with a title and a short explanation. Configure essential and optional fields, attachment limits and help messages. Use neutral wording, such as people mentioned instead of guilty parties. Test unidentified submission, the readability of the privacy notice and the follow-up mechanism. Check whether hidden fields or integrations introduce data that users would not expect. Before moving on, turn this procedure into a sequence you could explain to a colleague. Identify the first check, the action that depends on its outcome and the record that allows the decision to be reconstructed. Follow the sequence on screen and identify the point where an error would change the result.

3. Case Study & Compliance Action

In the mock-up, the department field is mandatory and offers only two teams, each with one worker. Even without a name, the answer may reveal identity. The administrator makes the field optional and explains that users should provide only the context needed to assess the facts. Now read the case carefully. Separate established facts from information you would still need to confirm. Do not add motives or events that have not been described. This distinction matters when choosing a response proportionate to the information available.

The exercise is as follows: Does a form without a name field, by itself, guarantee that nobody can identify the reporting person? Choose an answer and write one sentence explaining it. During the pause, compare your choice with the criteria we have just considered. Also think about the material you would retain to explain the decision later.

No. Context, attachments and other fields may enable indirect identification. Configuration should reduce unnecessary information, and handling must protect those elements too, without promising absolute anonymity in every circumstance.

One mistake to avoid is: requiring personal details that are unnecessary to assess the report.

Now apply the national rule to a second decision. The form requires a name and identity document although it promises anonymity. What must change?

Align the functions and user information. Do not require unnecessary identification. Check attachments and indirect identifiers too. Explain anonymity and confidentiality, restrict access, and assess existing data by legal basis and necessity. Do not promise absolute anonymity.