MAINSYSTEMS 
request only necessary information
1. Regulatory Concept & Core Standards
In this video we will work through a concrete decision: request only necessary information. The aim is to explain the criterion used and apply it to a workplace situation. We will start with the concept, move to the procedure and finish with a case to solve. 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.
Each mandatory field needs a clear purpose. Excessive forms can deter reports and collect irrelevant data. Optional information should be clearly marked.
Apply the following rule: Article 11(1) states that an anonymous disclosure is not a protected disclosure under the Act, although officers and units may receive and examine it. Article 11(3) contains a specific exception for anonymous public disclosure where the person is subsequently identified and suffers retaliation, subject to article 9(1). Explain this distinction and the channel’s actual options. Confidentiality of a known identity is not guaranteed technical anonymity.
2. Practical Implementation & Procedure
Match fields to purposes. Test factual reporting without unnecessary identity data. Explain safe attachment and communication practices. 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 form requires an identity number even for a fictional anonymous report, without a documented need. 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: Should the field remain mandatory? 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.
Not for technical convenience. Assess lawful purpose and align the field and information with the real option.
One mistake to avoid is: mandatory data without purpose.
Now apply the national rule to a second decision. The form requests a name and identity document, while the page promises anonymity. How should it be corrected?
Check the Maltese rule and actual channel option. Do not request unnecessary identification for technical convenience. Where a particular status has conditions, explain them before submission. Correct form and information together, with lawful handling of already received data.