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. The Whistleblower Protection Office, prosecutors and administrative authorities have different powers. Reporting, advice, protection applications and statistics use their own procedures. The course does not assume that every company must submit the same annual return.
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 section 10(6), acknowledge receipt within seven days of receipt. Under section 10(8), examine the report and communicate the result and measures within 90 days of acknowledgement; if not acknowledged, within 90 days after expiry of seven days from receipt. These are 90 days, not three calendar months. Referral to criminal or other relevant proceedings has its own rules: advance information, except where this could jeopardise examination; requesting the outcome within the legally permitted scope; and informing the reporting person within ten days of receiving that outcome.
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
A user sees an uploaded document and assumes submission, although status remains draft. In another simulation submission succeeds but the follow-up code is lost. The demonstration corrects both errors and distinguishes case status from an automatic message. 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 visible attachment prove that a communication was submitted? 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 submission status or the portal's confirmation. Keep reference and follow-up instructions securely. A draft or visible attachment does not establish receipt by the authority.
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 that correct?
No. Slovak internal receipt is acknowledged within seven days. Examination and communication of its result and measures are subject to the section 10(8) period of 90 days after acknowledgement, or expiry of seven days after receipt if unacknowledged. Opening is not the trigger and 90 days are not three months. Referral has a specific statutory procedure.