Requested action
Open job J-104
Draft submitted by an authorised user.
Submission received07 / Governance
Operational policies and approvals.
Connect policies, approval requirements and recorded decisions to the work they govern. In the example, job submission triggers a pending request for an authorised decision; it does not show an approval already granted. Access permissions remain separate from that decision.
An active rule matches this job’s value. It requests review; a policy document alone does not enforce this condition.
Current outcome
PendingAwaiting approval
Job not open · Reviewer decision outstanding
Applicable requirement
Value review
Active rule · Job value above AUD $10,000.
Example configurationApproval boundary
Review required
One request awaits an authorised reviewer.
No decision recordedWhy this requirement applies
- Condition
- AUD $12,000 exceeds $10,000
- Effect
- Request approval before opening the job
Illustrative governance workflow · Example data
Requirements in context
Evaluate configured approval conditions when a draft job is submitted. Requirements depend on the action and configuration.
Visible approvals
See pending requests and the roles assigned to review them. Permission and approval remain separate checks.
Reviewable history
Follow recorded evaluation and approval events back to the job. Keep supported decisions available for follow-up.
What happens after review?
In this job workflow, resolving the final required approval can open the job automatically when no approval remains pending or rejected and the lifecycle transition is valid. Production still has its own stage requirements. Not every job requires approval. Assigned organisation roles and action permissions control review access; a position title alone does not grant it. Recorded events contain selected context, not a complete historical policy snapshot.