MAINSYSTEMS 
map the data and people involved in a reporting case
1. Regulatory Concept & Core Standards
In this video we will work through a concrete decision: map the data and people involved in a reporting case. 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. 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.
Personal data concern identified or identifiable individuals. They include names, contacts, roles, images, opinions and details enabling indirect identification. Reports may contain health information, trade-union membership or alleged offences. Special categories and offence-related data need additional legal consideration. Labelling a file confidential does not change the nature of its contents.
Apply the following rule: The HinSchG covers criminal offences, certain administrative offences protecting life, health or workers' rights, and the matters listed in section 2. A breach of an internal rule does not automatically fall within the statutory scope.
2. Practical Implementation & Procedure
Map data subjects, categories, origin, purposes, recipients and storage locations. Identify who determines purposes and means and the supplier's role. Assess the proper legal basis. Consent is not an automatic solution for a legally required channel. Consent to record a communication serves a specific purpose and does not replace assessment of all processing. 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
A procurement report includes messages containing a colleague's sick-leave information. Relevant approval data sit alongside health data that may be unrelated. Mapping separates purposes and identifies information needing stronger protection or deletion because it is irrelevant. 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 removing a name automatically make all remaining data anonymous? 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. Roles, events and combinations of details may enable identification. Pseudonymisation reduces exposure, but data remain personal if additional information can link them to a person.
One mistake to avoid is: using a consent checkbox to justify every type of channel processing indiscriminately.
Now apply the national rule to a second decision. A report is automatically classified as protected because it contains the word corruption. What check is missing?
Read the facts and apply the national scope, context and conditions for protection. A form label helps organise information but does not determine the legal framework. If the case falls outside the regime, identify an appropriate route without unnecessarily disclosing information.