MAINSYSTEMS 
recognise submission stages and preserve follow-up access
1. Regulatory Concept & Core Standards
This video focuses on how to recognise submission stages and preserve follow-up access. 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. Slovenia has several external reporting authorities. Choice depends on subject and competence. Distinguish reporting a breach, support for the person and statistical reporting to KPK.
Completing fields, saving a draft and submitting are different operations. A demonstration must show confirmation and reference retention without real credentials or data. Portals differ in anonymity and dialogue. The journey must match the selected official procedure.
Apply the following rule: Under article 11, the trusted person examines an internal report within seven days of receipt and acknowledges acceptance or explains why it will not be handled. Anonymous reporting requires a specified reply route for these communications. Article 12 requires a report within three months of receipt. Inform the reporting person at closure and no later than three months after receipt; where procedures to remedy breaches continue, explain status and measures. Opening the message is not the trigger. External reporting has separate provisions in articles 15 and 16.
2. Practical Implementation & Procedure
Use a mock-up with fictional data. Identify recipient, fields, attachments, confirmation and mailbox. Explain each status. Recording must stop before any real submission. Show a simulated receipt and secure storage. Check current screens before video production. 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
An attachment remains in draft and a user loses the follow-up code. The user believes everything was submitted but has no sending evidence. 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 file on the computer establish the authority’s receipt? 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. Check actual submission and confirmation through the official route. Store codes according to instructions without public sharing.
One mistake to avoid is: using real data in training recordings or submitting test reports to an authority.
Now apply the national rule to a second decision. The platform counts three months from opening the message in every country. Is this correct?
No. In Slovenia an internal report is examined and accepted, or non-handling explained, within seven days of receipt. The article 12 report and communication have a three-month period from receipt, with status information where remedial procedures continue. Opening the message is not the trigger.