Deadline settings

1. Regulatory Concept & Core Standards

This video focuses on how to configure deadlines and starting events separately. 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 turns procedures into real user and staff actions. Every field, permission and reminder needs a reason. Technical settings do not replace Lithuanian legal conditions or the responsible person’s assessment.

Lithuanian internal channels distinguish receipt, acknowledgement and examination completion. Two and ten working days are not the generic seven-day and three-month model.

Apply the following rule: Internal receipt is acknowledged within two working days of receipt. Progress or refusal to examine is communicated within ten working days of acknowledgement. After examination, the outcome is communicated within two working days under paragraph 29. The Prosecutor’s Office also acknowledges within two working days, subject to Article 6 exceptions, decides status within ten working days of receipt and communicates that decision within two working days. Its progress and final-response deadlines are set out in Article 6(6).

2. Practical Implementation & Procedure

Create separate event fields and a working-day calendar. Check weekends, holidays and substitute alerts. Preserve the original receipt time. 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.

At each step, compare the information available with what is still needed for the decision. Arrange continuity when the designated worker is absent. A substitute receives only the information needed for the task, and their actions must remain verifiable.

Mark an unanswered question as a fact to verify. Identify who could confirm it and what access they actually need. A correct exercise choice alone does not show that the reasoning is understood. If the answer depends on an additional fact, state that condition explicitly.

For the workplace task, name the person who can approve the change and the person who will check that it works. Produce a concrete verifiable action, rather than only a promise to follow rules. Check effects on access rights and user information. Record questions that your organisation still needs to resolve.

3. Case Study & Compliance Action

The system starts counting only when an administrator opens an earlier report. The starting event and future reminder logic are corrected. 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 first reading replace receipt time? 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. The law specifies receipt or acknowledgement depending on the action. Record both rather than merging them into one date.

One mistake to avoid is: counting every deadline from first login.

Now apply the national rule to a second decision. The platform waits seven days to acknowledge and three months to respond. Is that suitable for Lithuania?

No. Acknowledge internal receipt within two working days of receipt and communicate progress or refusal to examine within ten working days of acknowledgement. Record examination completion separately and apply the two-working-day final-response deadline. The Prosecutor’s Office’s status-decision period starts at receipt. Do not replace working days with calendar days or move the starting event to the administrator’s first login.