Administration guidance
Manage overrides and waivers
Use bounded maker-checker exceptions without erasing the control result that prompted them.
- FOR
- Organisation administrator, Approver, Procurement, Finance
- OUTCOME
- Use RAQOZ to use bounded maker-checker exceptions without erasing the control result that prompted them.
Before you begin
- Organisation administrator access, or another role explicitly permitted for the setting.
- The organisation has agreed the control or operating decision before configuration.
Guidance
- 1
Confirm the underlying control result and evidence gap before requesting an exception.
- 2
State the reason, scope and validity required for the waiver or override.
- 3
Send the request to an independent eligible decision maker.
- 4
Keep the original result, decision and later consumption connected.
Evidence RAQOZ retains
- Original control result
- Exception request and rationale
- Independent decision and bounded use
Common issues
A configuration change behaves differently than expected.
Review scope, effective date, inheritance and status. Use a representative test or no-write simulation before activating a policy change.
A prior transaction appears to use an older rule.
That may be correct. Effective-dated versions preserve the policy context used at the time instead of rewriting history.
Related articles
Last reviewed 2 September 2026. Review against the current production release before relying on exact screen behavior.