MAINSYSTEMS 
1. Core Concepts and Legal Context
Today we will learn to apply data minimisation when receiving and handling reports. Throughout the video, consider the difference between knowing a rule and applying it to a decision. We will work through an example, identify a possible failure and develop a response that can be used at work. A reporting case may contain data about the reporting person, people concerned and third parties. Data protection must accompany the whole lifecycle, from the form to archiving. This course addresses operational decisions. Legal bases and restrictions on rights require assessment of the specific processing.
Data minimisation requires adequate, relevant information limited to what is necessary. Avoid excessive collection and remove clearly irrelevant data under applicable rules. This does not authorise destruction of relevant evidence or silent alteration of a document. Document the decision, preserve necessary material intact and use redacted copies where appropriate.
Apply the following rule: Section 5A(1) does not generally require acceptance and follow-up of anonymous reports made through the internal route in section 6, without prejudice to other enactments. This exception must not be applied indiscriminately to external routes. A subsequently identified worker who suffers penalisation may receive protection under section 5A(2). Section 16C nevertheless requires a record of receipt or transmission of an anonymous report and appropriate information about it. State the internal channel's anonymity policy and preserve the legally required record.
2. Practical Application and National Rule
Review form fields and the need for attachments. At intake, identify clearly unrelated information, decide what to do and record the decision without reproducing deleted data. Obtain competent assessment if relevance or retention is uncertain. Do not use reporting to create parallel worker information databases without a legitimate purpose. 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.
An attachment accidentally includes an unrelated customer list. The team confirms irrelevance, deletes unnecessary data through the appropriate procedure and makes a limited record of the event. It does not retain a complete copy merely because it accompanied a report. 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.
3. Case Study and Key Decision Points
The exercise is as follows: Is keeping everything ‘just in case’ compatible with data minimisation? 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.
Not as a general rule. Retention needs a purpose and a basis. Clearly irrelevant data follow specific deletion rules, while material necessary for the case must be preserved under applicable requirements.
One mistake to avoid is: confusing case integrity with indiscriminate retention of everything received.
Now apply the national rule to a second decision. The form always requires a name and identity document, but the page advertises anonymity. How should this be corrected?
First apply the national regime and define what the channel actually offers. Where identity is unnecessary, do not require it for technical convenience. Where it is a condition for a particular status, explain that before submission. Correct the fields and public information together while preserving material already received.
Remember these three points. First: Request only necessary information. Second: Identify clearly irrelevant data. Third: Record decisions without duplicating excessive data.
To apply this learning, retrieve the procedure used in your organisation or consider how you would create it. Identify one difference between that procedure and the case we have just resolved. Write down the change you would propose and the information needed to justify it. You can complete this short task in the handout accompanying the video.
The expected outcome of this unit is the ability to apply data minimisation when receiving and handling reports. Review the explained answer whenever you are unsure and keep the summary to support a future decision.
In the worksheet, connect your proposal to this video's national rule. Identify the document or platform field that would need to change and who should approve the change. If you conclude that it is good practice, explain the risk you intend to reduce. If you conclude that there is a legal duty, record its source and scope.