Demonstrating submission procedures

1. Regulatory Concept & Core Standards

This video focuses on how to distinguish preparation, uploading and actual submission. 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. MENAC's RGPC Platform communicates compliance information. It differs from the platform an entity uses to receive reports of wrongdoing. This walkthrough follows the official January 2025 manual. Video production must verify the screens and instructions available at that time.

The consulted manual distinguishes saving work from sending information. In that journey, selecting progress or submission status precedes saving the operation. A document visible in the form may not yet have been communicated to MENAC. Verify labels and sequence in the version used for filming.

National rule: In the process described in the User Manual, saving work and submitting information are different operations. Check the operation’s status and retain evidence of submission. The labels and sequence shown must match the platform version being used.

2. Practical Implementation & Procedure

In a mock-up, open the entity area, check details and enter consistent information. Upload each document and choose its classification. Review mandatory fields, attachments and status. Demonstrate a draft, then simulated submission. Check the result and available confirmation or record. Do not make a real submission solely to produce the video. 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 uploads the PPR, saves progress and assumes communication is complete. Review shows that it remains unsubmitted. Using fictional data, the team explains the distinction and demonstrates the action completing the manual's journey. 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 document in the upload area prove submission? 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 final status and sending evidence. Saving progress enables later work and is not completed communication. Verification is part of submission.

One mistake to avoid is: ending the demonstration at file upload without verifying the sending result.

Which document, responsible person and evidence from your entity demonstrate application of this rule?

Confirm the scope and applicable source. Record the decision, who can approve it and the evidence required. Application in this lesson should support the following objective: distinguish preparation, uploading and actual submission Distinguish the legal duty from the organisational method chosen by the entity.