Roles guidance
Approver guide
Make attributable decisions within assigned authority and record enough reasoning for later review.
- FOR
- Approver
- OUTCOME
- Use RAQOZ to make attributable decisions within assigned authority and record enough reasoning for later review.
Before you begin
- An active membership in the intended organisation.
- The role described in this article, or administrator access for review.
Guidance
- 1
Review only decisions assigned to you and confirm the request is within your authority.
- 2
Consider purpose, specification, budget context and policy results before deciding.
- 3
Approve, return or reject with a concise reason that another reviewer can understand.
- 4
Do not use approval to replace procurement's supplier-selection responsibility.
Evidence RAQOZ retains
- Approver identity and assignment
- Decision, timestamp and reason
- Policy context at the decision
Common issues
A screen or action is missing.
Check the active organisation, assigned role and record-specific assignment. Navigation is role-filtered, but the server-side permission check is the security boundary.
A person needs broader access for one task.
Use the narrowest supported role or governed exception. Do not share accounts or leave elevated access in place.
Related articles
Last reviewed 2 September 2026. Review against the current production release before relying on exact screen behavior.