MAINSYSTEMS 
apply the correct starting event and time unit
1. Regulatory Concept & Core Standards
This video focuses on how to apply the correct starting event and time unit. 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. Configuration implements the approved procedures of the particular entity. Functional descriptions are requirements and fictional tests, not claims that every UNOVOX installation automatically provides identical capabilities.
Acknowledgement and feedback are different actions. The internal channel uses seven working days for acknowledgement. Three months must not mechanically become ninety days.
Apply the following rule: Internally, article 10(2)(c) requires acknowledgement within seven working days of receipt. Feedback is due within three months after acknowledgement or, if omitted, after expiry of seven working days following submission: article 10(2)(g). The external EAD route also uses seven working days for acknowledgement, subject to article 12 exceptions, and feedback within a reasonable period not exceeding three months, or six months in duly justified cases. Keep working days distinct from calendar days and from the three-month feedback period.
2. Practical Implementation & Procedure
Apply the national calendar rule. Test Friday receipt, holidays, month-end and absence. Arrange advance reminders and substitution. 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.
3. Case Study & Compliance Action
The system starts the period when the handler opens the message five days after receipt. 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: Is that the correct starting event? 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. National law determines the starting event, not first reading.
One mistake to avoid is: replacing receipt with opening.
Now apply the national rule to a second decision. The platform counts ninety days in every country from first opening of the message. Is this setting correct?
Not without checking the national rule. Use the correct starting event and time unit. Distinguish acknowledgement and feedback. Allow only lawful extensions. Test receipt outside working hours, month-end and the officer’s absence. Opening does not automatically change the legal receipt date.