MAINSYSTEMS 
1. Core Concepts and Legal Context
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. The demonstrations in this course use a generic platform and fictional data. Field names depend on the chosen product. The aim is to understand which settings to look for and how to verify the result, keeping technical administration rights separate from access to case content.
Configuration must represent the national rule: the starting event, duration, unit and any exceptions. Receipt and acknowledgement are different dates. Working-day deadlines require the relevant calendar; months must not automatically be converted into 90 days. An internal alert should precede expiry and identify who prepares, approves and sends the communication.
Apply the following rule: Acknowledge an internal report in writing no later than seven days after receipt. Provide feedback within a reasonable period, no later than three months from the date the acknowledgement was sent. If none was sent, the maximum is three months from expiry of the seven-day period after the report was made. A written request triggers further feedback every three months until closure. Feedback explains action taken or envisaged and the reasons for it; the initial feedback deadline does not require every investigation to have finished.
2. Practical Application and National Rule
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.
Configure the Irish rule around two events: receipt for sending acknowledgement, and the acknowledgement’s sending date for calculating first feedback. A system alert is not a written acknowledgement. Test acknowledgement sent several days after receipt and a separate case with none. Save both expected results before approving configuration.
The system alerts the manager, but the manager communicates no measures to the reporting person. The dashboard marks the alert complete. The team changes the configuration to distinguish an alert dealt with from a communication sent, recording its content and sending date. 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: Does marking an alert as read demonstrate compliance with the duty to communicate with the reporting person? 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. Evidence of the required communication through an appropriate means must exist. An alert is an internal aid; the obligation concerns information actually communicated to the reporting person within the applicable period.
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 uses a fixed 90-day period for every country, starting when someone opens the message. Can this setting be retained?
Not without validating the local rule. Use the correct starting event and unit, distinguish acknowledgement from follow-up and allow only permitted extensions. Test receipt outside working hours, month-end dates and the responsible person's absence. Opening a message does not automatically change the legal date of receipt.
Remember these three points. First: Identify the starting event. Second: Distinguish days from months. Third: Test the national rule.
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 configure alerts that support deadline compliance without exposing information. 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.