MAINSYSTEMS 
maintain control of the case and communications throughout follow-up
1. Regulatory Concept & Core Standards
This video focuses on how to maintain control of the case and communications throughout follow-up. 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. Every case needs an identifier, a responsible handler and clear records. Handling includes acknowledgement, assessment, communication and follow-up. Feedback does not always mean every proceeding has ended. Closure requires assessment of outstanding duties and the correct retention rule.
Each action needs a purpose, owner and record. The timetable must distinguish acknowledgement, feedback, assessment and any final outcome. Some regimes impose specific assessment or investigation deadlines. A generic message saying that a case is under review does not replace legally required information. Plan tasks to meet both the required content and timing.
Apply the following rule: Internally, acknowledge within seven days of receipt and provide feedback within three months after acknowledgement, or expiry of the seven-day period if omitted; the no-contact-address exception applies. Externally, the public authority provides feedback within three months of accepting the report, or six months in justified cases after notifying the person before the initial period expires: article 41. Record the separate forwarding and acknowledgement stages; the final outcome is an additional communication.
2. Practical Implementation & Procedure
Maintain a record of actions, dependencies and dates. Anticipate delays and check whether the law permits an extension, in which circumstances and how it must be notified. Describe completed or planned steps without exposing third parties. Check national rules on communicating the final outcome and requests for updates. Keep the version sent and evidence of sending. 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
The team awaits a document from another unit and the feedback deadline approaches. Findings are incomplete. The handler prepares accurate information about action taken and intended follow-up. 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 the absence of a final result justify omitting feedback? 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. Perform the applicable duty on time, describing the permissible scope of action and its reasons. Do not invent an outcome or extend the deadline at will.
One mistake to avoid is: assuming that a feedback deadline permits postponement of every other assessment or completion obligation.
Now apply the national rule to a second decision. The platform counts 90 days from opening the message in every country. Is that configuration correct?
No. In the Polish internal procedure, receipt is acknowledged within seven days. Feedback is provided within three months of acknowledgement, or expiry of seven days after submission if no acknowledgement was sent. Consider the exception where no contact address was supplied. Months are not a fixed 90 days, and opening does not replace the statutory trigger.