Submission, confirmation and follow-up demonstration

1. Regulatory Concept & Core Standards

This video focuses on how to separate technical confirmation from a substantive outcome. 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 Estonian external recipient depends on the field of breach. Advice, receipt and investigation may be different roles. TÕRTKS permits direct external reporting. Exercises do not submit real reports or identify one universal authority for every subject.

Acknowledgement is generally due within seven days. An incompetent authority forwards promptly and no later than the fifth working day. External follow-up is due within three months of receipt, or six months when justified. Statutory confidentiality and express-prohibition exceptions remain.

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

Use a verified route and protect the reference. Monitor messages and clarify as needed. Distinguish automated delivery from statutory feedback. Never submit a fictional exercise to a real authority. 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 learner sees a mock submission and acknowledgement and identifies the event starting follow-up time. No real report is sent. 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 clicking submit establish that wrongdoing was confirmed? 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. It shows a technical step. Receipt, competence, follow-up and final outcome are distinct.

One mistake to avoid is: treating a technical message as a substantive decision.

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.