MAINSYSTEMS 
1. Core Concepts and Legal Context
This video's topic is functional testing of the channel. By the end, you should be able to verify the submission and protection journey. We will connect the information available, the criterion guiding the decision and the action that must be recorded. Follow the case and compare your answer with the proposed response. Audit requires clear scope, criteria and appropriate evidence. Testing protects confidentiality and uses fictional data where possible. A limited sample must not be presented as complete certification of the whole organisation.
Functional tests examine receipt, safe communication, deadlines and exclusion of unauthorised users. Using actual reports for training may create unnecessary risk.
Apply the following rule: Internally, acknowledge receipt within 7 days of receipt. Provide feedback within a reasonable period not exceeding 3 months from acknowledgement or, if none is sent, 3 months after expiry of the 7-day period following the report. Externally, acknowledgement is within 7 days unless the reporting person requests otherwise or identity protection would be jeopardised; feedback is within 3 months or 6 months in duly justified cases. Acknowledgement is neither feedback nor final resolution.
2. Practical Application and National Rule
Specify expected results. Use an authorised test environment with fictional data. Record outcome, fault and retest. 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.
Consider how a colleague taking over tomorrow would understand the decision. Identify the verified information and its source, who is authorised to decide and who checks the result. The record should connect the decision to the material actually used rather than repeat the whole file. State critical gaps and assign a specific action to resolve them. This makes continuity independent of one person’s memory. Apply the proposed organisational steps within legal powers. In the case, distinguish observation, conclusion and hypothesis. An observation describes available evidence, a conclusion explains what can reasonably be inferred and a hypothesis still needs checking. Do not infer motives merely from unusual behaviour. Identify which further information could change the decision and whether it can be obtained lawfully and proportionately. Incomplete knowledge justifies neither certainty of guilt nor indifference to an actual risk.
Submission works, but a test user from another department can view an attachment through a shared link. 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.
3. Case Study and Key Decision Points
The exercise is as follows: Did the overall test pass? 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. Unauthorised access is a material finding requiring correction and verification.
One mistake to avoid is: testing only whether submission works.
Now apply the national rule to a second decision. The platform counts ninety days in every country from first opening the message. Is this configuration correct?
Not without checking the national rule. Use the correct starting event and time unit. Distinguish acknowledgement from feedback. Allow only permitted extensions. Test arrival outside working hours, month-end and the handler’s absence. Opening does not automatically change the lawful receipt date.
Remember these three points. First: Complete journey. Second: Negative test. Third: Retest.
To apply this learning, retrieve the procedure used in your organisation or consider how you would create it. Identify one difference between that procedure and the case we have just resolved. Write down the change you would propose and the information needed to justify it. You can complete this short task in the handout accompanying the video.
The expected outcome of this unit is the ability to verify the submission and protection journey. Review the explained answer whenever you are unsure and keep the summary to support a future decision.
In the worksheet, connect your proposal to this video's national rule. Identify the document or platform field that would need to change and who should approve the change. If you conclude that it is good practice, explain the risk you intend to reduce. If you conclude that there is a legal duty, record its source and scope.