MAINSYSTEMS 
organise the response to an access request or data incident
1. Regulatory Concept & Core Standards
In this video we will consolidate a skill: organise the response to an access request or data incident. Use the case to test what you would do in a similar situation. We will explain the proposed response step by step so that you can understand each choice and recognise when more information would be needed. A reporting case may contain data about the reporting person, people concerned and third parties. Data protection must accompany the whole lifecycle, from the form to archiving. This course addresses operational decisions. Legal bases and restrictions on rights require assessment of the specific processing.
A personal-data access request does not give unrestricted access to the whole case or the reporting person's identity. Reconcile the requester's rights, confidentiality and third-party rights, with a legal basis for restrictions. Assess unauthorised disclosure as a possible personal data breach, including risks and GDPR notification duties.
Apply the following rule: Section 21(2) requires reports and related documents to be retained for five years from receipt. Earlier closure does not change that starting event. The Act separately requires an electronic register with specified particulars. Under section 21(3), only the competent person may access internal reports, related documents and the register; the Ministry uses its authorised employee. Assess irrelevant data and other legal retention grounds separately.
2. Practical Implementation & Procedure
Handle a rights request within its applicable deadline and give reasons for the response scope. For a breach, limit further exposure, preserve necessary evidence and assess risk. The controller notifies the authority without undue delay and where feasible within 72 hours of awareness unless risk to rights and freedoms is unlikely. Document all breaches. The processor notifies the controller without undue delay; article 34 uses the separate high-risk test and exceptions for informing individuals. 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
An attachment goes to the wrong recipient. The team restricts access where possible, requests secure deletion, documents events and assesses risk. Asking for deletion does not automatically close the incident or remove the need to assess notifications. 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 asking the wrong recipient to delete the message fulfil every obligation? 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. It is a containment measure. Assess exposed data, recipients, possible consequences and legally required notifications. Record the decision and its reasons.
One mistake to avoid is: equating access rights with delivery of the full report or treating every incident as identical.
Now apply the national rule to a second decision. The system deletes every case five years after receipt, regardless of the country and any pending proceedings. Is that appropriate?
No. Identify the local rule, starting event and any limits or extensions. A uniform schedule may delete records too early or retain them too long. Document the decision by category, include copies and define who reviews a suspension of deletion, rather than keeping everything indefinitely.