Administration guidance
Version procurement policies
Preserve which policy version applied to each evaluation instead of rewriting history.
- FOR
- Organisation administrator, Auditor
- OUTCOME
- Use RAQOZ to preserve which policy version applied to each evaluation instead of rewriting history.
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
Create a new draft when a policy must change.
- 2
Record the reason, scope and intended effective date for the revision.
- 3
Complete review and activation through the governed lifecycle.
- 4
Keep prior versions available for the purchases evaluated under them.
Evidence RAQOZ retains
- Version history and reason
- Approval and activation
- Evaluation-to-version association
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.