
Process Discovery
Part of Automation governance
Reviewing changes to automated decision rules
Compare old and new rule outcomes, confirm authority, check boundary cases and record the release and its effect on pending work.
Review a proposed rule change by comparing current and proposed outcomes for the same kinds of case. The business owner approves what the rule means. The technical owner establishes how the approved version will run and be checked.
A changed threshold or eligibility condition is a business change, even when it takes one configuration edit. Where the rule uses personal information, it can also change what the organisation must disclose under the Privacy Act 1988 (Cth).
Describe the change in cases
Open a change request with its own reference and record the current and proposed rule, the reason, the effective time and the source of authority, such as the policy, delegation or board decision that sets the threshold. Identify affected cases and decide whether open cases stay under the old rule or move to the new one.
“Update routing logic” is too vague for an approver. “Send credit applications with an unverified income document to manual review instead of automatic decline” states the condition, both outcomes and the population affected.
| Case condition | Current outcome | Proposed outcome | Question to settle |
|---|---|---|---|
| Meets normal criteria | Current route or decision | Intended route or decision | Is this still authorised? |
| Falls on the changed boundary | Existing result | New result | Which cases change, and why? |
| Has missing or conflicting information | Current hold or exception route | Proposed route | Could uncertainty now appear to meet the rule? |
Use the organisation’s actual rules to fill the table. In the credit example, the boundary row is an application whose income document cannot be verified: currently declined, proposed for manual review. The missing-information row asks whether an application with no income document at all should follow the same path.
Check impact and authority
Identify the inputs, any changed upstream definitions and the downstream action the rule permits. Ask whether the change could affect access, a financial commitment, a person’s interests or the use of personal information. Involve the responsible specialist where needed.
If personal information is used, the privacy owner should check Australian Privacy Principle 1. From 10 December 2026, APP 1.7-1.9 apply where an entity has arranged for a computer program to make, or do a thing substantially and directly related to making, a decision that could reasonably be expected to significantly affect an individual’s rights or interests, using personal information about them.
The Office of the Australian Information Commissioner (OAIC) states that a computer program includes pre-programmed rule-based processes, and that configuring or customising off-the-shelf software can count as arranging for one. Human review of the output does not by itself take a decision out of scope. Approving or rejecting a loan or credit application is one of the OAIC’s in-scope examples.
For a rule in scope, confirm that the APP privacy policy still describes the kinds of personal information used, the kinds of decisions made solely by the program, and the kinds of decisions for which it does a thing substantially and directly related to the decision. Update the policy if the change alters any of these.
Record who requested the change, who approved its business meaning, who assessed implementation and who authorised release, with the date of each sign-off in the change request. An urgent path still needs an owner, a reason and later review.
Preserve the superseded rule and its effective time so a past case can be interpreted against the version that applied.
Key Compliance Requirements for Automated Decision Rules
- OAIC Definition of Computer Program
- Includes pre-programmed rule-based processes and configured off-the-shelf software
- In-Scope Example (OAIC)
- Approving or rejecting a loan or credit application
- Cyber Security Guideline Reference
- Guidelines for cyber security documentation – ASD Cyber Security Framework
Define checks before release
Use safe cases on both sides of the changed boundary, plus a case with missing or conflicting input and a case already in progress. State expected outcomes before checking the implementation.
Verify a resulting business state in the destination where the rule causes an action. Check that cases outside the approved population keep their existing route.
The release plan should state how the version is activated, who inspects early outcomes, who may halt it and what can be restored. Name this as the stop procedure: the person authorised to pause the rule, the way it is paused, such as reinstating the prior version or disabling the automation, and where held cases wait.
Reinstating an earlier rule cannot undo decisions or writes already made; affected cases need a separate review.
Close the change
Compare early cases and exceptions with the approved outcomes. Record differences, affected case references and the owner’s response.
Complete the release record with the change request reference, the rule version released, the activation time, the verification cases and their results, any privacy policy update and the approvals given. Update the automation inventory with the rule version and linked change record. Hold further affected work under the stop procedure if an unexpected consequential outcome appears.



