Module Learning Objective

configure the correct starting event and distinguish responses

1. Regulatory Concept & Core Standards

This video focuses on how to configure the correct starting event and distinguish responses. 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. Configuration examples describe general working methods. Verify features in the actual system. Changes must connect permissions, procedures and Estonian legal requirements. Use fictional test cases so that verification creates no new confidentiality risk.

Estonian seven-day acknowledgement and three-month follow-up periods start on receipt. The justified six-month external option must not automatically be applied internally. Exceptions require reasons. Opening does not replace receipt.

Apply the following rule: Under section 10, acknowledge receipt within seven days of receipt, subject to express prohibition by the reporter or confidentiality-risk exceptions. Section 11 requires follow-up feedback as soon as possible and within three months of receipt. External channels may use six months in justified cases. An authority lacking competence forwards promptly, no later than the fifth working day. Acknowledgement, follow-up feedback and final-outcome feedback are separate events.

2. Practical Implementation & Procedure

Separate receipt, acknowledgement, feedback and closure events. Test month-end, out-of-hours arrival and absence. Send alerts to authorised people with minimal detail. Record exceptions and their grounds. 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

Software counts 90 days from opening although receipt occurred earlier. Both the starting event and unit may produce the wrong deadline, so the team corrects the logic and tests. 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: Can three months always be replaced by 90 days? 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. Calendar months vary. Apply the legal unit and starting event. Track acknowledgement and follow-up separately with applicable exceptions.

One mistake to avoid is: copying a foreign deadline template.

Now apply the national rule to a second decision. The platform counts 90 days from opening in every country. Does this suit Estonia?

No. Acknowledgement is generally due within seven days of receipt. Follow-up is due within three months of receipt, or six months for a justified external-channel case. Apply statutory exceptions and distinguish working from calendar days. Three months is not always 90 days and opening does not replace receipt.

National Legal Framework: Rikkumisest teavitaja kaitse seadus, transposing Directive (EU) 2019/1937 of the European Parliament and of the Council on the protection of persons who report breaches of Union law.