Submission, confirmation and follow-up demonstration

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. Authorities have different powers. Receiving reports, advising reporting persons, investigating breaches and collecting statistics are different functions. This course explains recipient selection and information preparation. Demonstrations use fictional data and send no real reports.

Completed fields and visible attachments do not alone prove submission. Demonstrate status changes and follow-up in a fictional model. The national portal supports dialogue, including anonymous reporting. Store access information securely and follow the actual scheme’s guidance. A demonstration of one product does not establish that all channels offer the same functions.

Apply the following rule: Internally, acknowledge receipt within seven days of receipt and provide feedback as soon as possible, no later than three months after acknowledgement: section 12(2). Externally, acknowledge promptly and within seven days, except where explicitly declined or confidentiality would be jeopardised. Section 20(2)(3) measures external feedback from acknowledgement: generally three months, exceptionally six months in duly justified cases. Do not configure this external period from receipt or treat it as an investigation-completion deadline.

2. Practical Implementation & Procedure

Use fictional data in an isolated mock-up. Show recipient selection, fields, attachments, review and simulated confirmation. Explain later messages without displaying real access codes. Do not send practice reports to an authority. Check current official screens before recording, and do not promise recovery of lost access unless the service offers it. 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 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.