MAINSYSTEMS 
organise the intake of a report and the initial communication
1. Regulatory Concept & Core Standards
In this video we will work through a concrete decision: organise the intake of a report and the initial communication. The aim is to explain the criterion used and apply it to a workplace situation. We will start with the concept, move to the procedure and finish with a case to solve. Handling a report requires continuity: each stage must leave enough information for the next. This course follows the team's work, distinguishing case administration, factual analysis and communications with the reporting person. The examples concern internal channels.
Receipt triggers tasks and deadlines. Preserve the communication intact, assign a reference and restrict access. For an internal report, acknowledge receipt within seven days and include clear information on the requirements, authorities and admissibility of external reporting. Acknowledgement does not validate every fact or promise an outcome.
National rule: For the internal channel, notify the reporting person of receipt within 7 days. Communicate the measures planned or taken and the reasons for them within 3 months of receiving the report. If the reporting person requests it, communicate the outcome within 15 days of completion. The 3-month period is not a general deadline for completing the investigation.
2. Practical Implementation & Procedure
Check the receipt date and attachments. Identify a secure communication method and an initial owner. Prepare a neutral message confirming the reference and explaining follow-up. For an anonymous report, use the available mechanism without demanding identification. Oral reporting requires attention to recording rules, consent where applicable and approval of the transcript or minutes. 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 report arrives with two attachments, but one will not open. The team records both, preserves what was received and requests a replacement through secure means. Acknowledgement is not suspended while the attachment issue is resolved. The case record identifies the missing information. 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: Should the team wait until every attachment is readable before acknowledging receipt? 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.
Do not confuse the two tasks. Meet the acknowledgement requirement while separately requesting the missing item and recording the technical problem and follow-up. The initial message need not anticipate findings.
One mistake to avoid is: using the acknowledgement to state that the report has already been substantiated.
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.