Submitting a report through a platform

1. Regulatory Concept & Core Standards

This video focuses on how to complete submission and keep the means of accessing follow-up. Follow the sequence of decisions in the example rather than simply memorising a list. Notice who is involved, what information is needed and the expected result. These points help turn the content into a practice that another person can verify. This course takes the perspective of someone who wants to report a concern. The demonstration uses a fictional channel. You do not need legal terminology to describe facts. You need to distinguish what you know, what you suspect and what you cannot confirm.

Completing fields, saving a draft and submitting are different acts. Follow the service and Bulgarian identification requirements. Anonymous reports do not initiate proceedings under the Act. The CPDP unique identification number and internal reference follow a specified procedure; a fictional screen code does not prove official registration. Confidentiality is not anonymity.

Apply the following rule: Article 9 provides that anonymous reports do not initiate proceedings under this Act. This does not mean risk information must be ignored under another applicable procedure. Under article 10, people who initially reported anonymously outside the Act’s procedure or disclosed anonymously, and are later identified and subjected to retaliation, may be protected if the statutory conditions are met. Do not promise that every anonymous message will be handled as a valid ZZLPSPOIN report.

2. Practical Implementation & Procedure

In a training environment, check recipient, fields, attachments and status. Show simulated submission and confirmation. Store the required reference and contact instructions securely without displaying real credentials. Do not send a test report to a real organisation or authority. Check current screens and instructions before recording. 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 a simulation, a user closes the page after submitting without retaining the follow-up reference. Later, she cannot find messages. The demonstration repeats the steps with fictional data and explains which contact information to keep. 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: What should you check and save before closing the final submission page? 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.

Check that submission is complete and save the follow-up details provided. Recovery options depend on the platform. The demonstration must use fictional codes and explain the procedure actually available in the product used.

One mistake to avoid is: confusing a draft message with a report that has actually been submitted.

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.