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.

The Ministry publishes reporting methods, including a web form. Section 16 requires written acknowledgement within seven days, subject to exceptions, and a requested personal meeting within at most 14 days. Section 17 assessment and written results are due within 30 days of receipt, with one extension of up to 30 days for complexity. This is not the completion deadline for every subsequent proceeding.

Apply the following rule: Acknowledge in writing within seven days of receipt, except where the reporting person expressly requests otherwise or acknowledgement would clearly disclose their identity. Internally, assess and notify the result within 30 days of receipt; factually or legally complex cases may be extended by up to 30 days, at most twice, with written reasons before the current deadline expires: section 12. The Ministry’s external assessment has a 30-day period and only one extension of up to 30 days under section 17. Do not configure the two procedures identically.

2. Practical Implementation & Procedure

Use fictional data in a labelled mock-up. Verify the official entry and current instructions before recording a live demonstration. Separate technical confirmation, statutory notification and later information. Retain an available proof of submission and clarify securely; do not claim that every current screen or follow-up feature has been tested. 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 the external system permit the same two 30-day extensions as the internal system? 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. Section 17 permits only one extension of up to 30 days. The basic period is 30 days from receipt. Distinguish the Ministry’s assessment from the duration of later proceedings.

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.