Recording reasons for decisions 111-15040020
This document outlines the standards that apply to staff recording reasons for decisions relating to Centrelink payments. This is to ensure that Centrelink maintains the Getting it Right standard Management of customer records/interactions when recording the reasons to support and explain a particular decision
Making accurate decisions
Table 1: the 6 principles required for a Service Officer to make an accurate decision and information on system generated grants or cancellations.
Item |
Description |
1 |
Identify the issues + Read more ... For the decision making process to proceed it is important to identify the issues at hand. Some questions that may help in identifying the issues include:
|
2 |
Find the rules + Read more ... To make a correct decision it is important to understand which rules apply to the situation. These rules, and advice on how to apply them, are usually found in the relevant legislation guidelines. |
3 |
Investigate facts and gather supporting evidence + Read more ... Decisions must be based on relevant facts and evidence. The decision making process can be made more difficult if there is insufficient investigation or evidence obtained. The following points may help with this stage of the decision making process:
|
4 |
Decide by applying the law to the facts + Read more ... Findings of fact are the conclusions a decision maker draws from the available facts and evidence. To make a decision the decision maker will need to:
|
5 |
Document the decision + Read more ... It is important to document the decision made so that the decision can be readily explained to the customer or if the decision is queried or challenged. The decision should be recorded on a DOC and should include:
This information must be included when the Service Officer completes an activity where decisions about eligibility or entitlement are made. Note: the DOC must meet the Online Document Recording Standards when a significant decision is made. Most straight forward decisions will only require the Service Officer to DOC the conversation with the customer or reason for making the change (for example, mail). |
6 |
Advise the customer + Read more ... It is important to explain the reasons for your decision in terms that allow the customer to fully understand why the decision was made. Two questions that may help with this include:
Discussing the reasons for an adverse decision with a customer before sending the written advice can also improve customer service and reduce the likelihood of the customer seeking a review of a decision. |
7 |
Decisions to grant payments automatically determined by the system + Read more ... In some situations the decision to grant a payment or service is automatically determined by the system. The entitlement is assessed and paid using information already recorded on the customer's record and no manual action is required by a Service Officer. In these cases, sufficient information exists on the system and there is no requirement for a significant decision DOC to be created. Examples of such payments or services include:
The decision to issue the payment is made automatically and is approved by the Secretary. |
Quality checking
Table 2
Step |
Action |
1 |
Determine if a significant decision has been made + Read more ... When a Service Officer makes a significant decision, the details must be recorded on the customer's record in accordance to the Getting it Right (GIR) Standard - Management of customer records/interactions. Details include:
It is essential that all reasons for the significant decision are recorded. A significant decision is defined as:
When quality checking the work, has a significant decision been made?
|
2 |
Has all of the information required been recorded? + Read more ... Additional information required includes:
Note: if the reason for the decision is not obvious from elsewhere in the record, this will need to be documented in more detail.
|
3 |
Has the decision (not a significant decision) been recorded adequately? + Read more ... To determine what is adequate refer to ODR Standards and the specific Operational Blueprint file relating to the decision.
|
4 |
Quality On Line (QOL) + Read more ... When to release with feedback When the outcome of the activity can be determined as correct, but the significant decision information is not fully documented. Select GIR DOC Minimum Standard option in QOL Check tool and provide feedback. When to return When a QOL Checker cannot determine if the result of the activity meets the Four Pillars of Payment Correctness (Right Person, Right Program, Right Rate and Right Date) due to missing or no information recorded in the record. Select GIR Doc Minimum Standard options as well as the corresponding critical error relating to the Four Pillars as applicable in QOL check tool. Returning the activity using QOL will refer the activity back to the Service Officer for correction and resubmission. Provide written feedback using the QOL feedback. Procedure ends here. |
5 |
Quality Management Application (QMA) + Read more ... Record an error with feedback Where the outcome of the checked work item can be determined as correct, but the significant decision information is not fully documented, the catch all error Q00015 - Getting it Right - Doc Minimum Standards within QMA must be recorded as a minimum. When a Quality Management Officer (QMO) cannot determine if the result of the activity is correct due to missing or no information recorded in the record, the catch all error Q00015 - Getting it Right - Doc Minimum Standards within QMA must be recorded along with other appropriate errors related to the missing information. The DOC or Note must be updated and the activity finalised by the QMO. Feedback must be provided to the Service Officer. |