MAINSYSTEMS 
verify changes without real case data
1. Regulatory Concept & Core Standards
In this video we will consolidate a skill: verify changes without real case data. 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. 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.
A successful submission test does not establish that access restrictions work. Negative tests, account removal and export or notification checks are also needed.
Apply the following rule: Article 21A requires records of reports and retention no longer than necessary and proportionate for the Act or other legal requirements. Article 6A prohibits collecting manifestly irrelevant data and requires deletion without undue delay if accidentally collected. Document purpose, pending proceedings, review ownership and secure deletion including copies and exports. These provisions do not impose a universal five-year period.
2. Practical Implementation & Procedure
Record expected results first. Use authorised test accounts. Document fault, correction and retest. 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
A former handler loses their organisational role but can still read cases in the system. 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: What proves correction? 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.
Unauthorised access now fails while authorised people retain the access necessary for their duties.
One mistake to avoid is: testing only successful submission.
Now apply the national rule to a second decision. The system deletes every case five years after receipt regardless of country and pending proceedings. Is this suitable?
No. Apply Malta’s necessity and proportionality rule and relevant legal duties. Consider pending proceedings. Record the decision for each category, include copies and identify who reviews a suspension of deletion. Do not retain everything forever.