Receiving, recording and acknowledging a report

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 the Czech duties and time limits. Record the date, preserve the report and restrict access. Written acknowledgement within seven days confirms receipt, not the truth of allegations. Apply section 12(2) exceptions only when their conditions hold. The electronic register under section 21 is not a generally accessible list of organisational problems.

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

Check the competent person, appropriate contact, identity under the applicable regime and attachments. Prepare a neutral acknowledgement. Record oral reports under section 19, obtain consent for audio and allow comments on the record or transcript. Handle an unreadable attachment separately without moving the receipt date. 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.

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.