MAINSYSTEMS 
configure alerts that support deadline compliance without exposing information
1. Regulatory Concept & Core Standards
This video focuses on how to configure alerts that support deadline compliance without exposing information. 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. Examples use a generic platform and fictional data. Function names depend on the product. Suitability and compliance of a particular installation must be checked; the demonstration does not certify functions in a particular UNOVOX licence.
Time runs from the event specified by law, not a convenient system status. Internal reporting includes the seven-day examination and the three-month report or communication from receipt. An internal reminder does not prove that the reporting person was informed.
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
Record receipt, configure advance alerts and assign responsibility for responding. Separate system notifications from information actually provided to the reporting person. Use neutral subjects and messages without factual allegations. Test different receipt dates, absences and delivery failures. Where anonymity prevents external contact, use the available secure follow-up facility. 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
The handler reads an alert but leaves the reply in draft. The dashboard marks the task complete although the person was not informed. The team corrects status and checks actual communication. 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 read alert prove timely communication? 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. A reliable record of the required communication is needed. Opening and sending are different events.
One mistake to avoid is: using an internal notification's status as proof of a reply to the reporting person.
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.