Procurement Approval Routing
Overview
Route procurement orders through value-based approval chains with authority matrix enforcement, Human-in-the-Loop (HITL) gates, and immutable audit trail logging. Ensures every order is processed by the correct approvers based on value, type, and complexity.
Announce at start: "I'm using the procurement-approval-routing skill to configure approval chains and enforce authority limits."
When to Use This Skill
Trigger Conditions:
- Creating or modifying procurement order (> $0)
- Order value crosses approval threshold
- Approval chain needs to be determined
- HITL gate evaluation required
- Rejection handling with reason capture
Prerequisites:
- Authority matrix configured in system
- Order data complete (value, type, risk level)
- User roles and permissions loaded
Step-by-Step Procedure
1. Determine Approval Chain
Based on order value and type, determine required approvers:
| Order Value (USD) |
Order Value (ZAR) |
Approval Chain |
| < $25,000 |
< R500,000 |
Procurement Officer |
| $25,000 - $100,000 |
R500,000 - R2,000,000 |
Procurement Manager + Project Manager |
| $100,000 - $500,000 |
R2,000,000 - R10,000,000 |
Above + Finance Manager |
| > $500,000 |
> R10,000,000 |
Above + Executive Sponsor |
| Single-source |
Any value |
Above + Commercial/Legal Review |
2. Configure Routing Type
| Routing Type |
When to Use |
Behavior |
| Sequential |
High-value, complex orders |
Each approver must approve before next |
| Parallel |
Low-value, routine orders |
All approvers can approve simultaneously |
| Hybrid |
Medium-value with specialized review |
Sequential for certain steps, parallel for others |
3. Enforce Authority Limits
Rules:
- Never allow approver to approve above their authority limit
- Never allow same user to be both requestor and approver
- Never allow approval without budget availability confirmed
- Always log approval action to immutable audit trail
1---2name: procurement-approval-routing3description: Route procurement orders through value-based approval chains with authority matrix enforcement, HITL gates, and audit trail logging4---56# Procurement Approval Routing78## Overview910Route procurement orders through value-based approval chains with authority matrix enforcement, Human-in-the-Loop (HITL) gates, and immutable audit trail logging. Ensures every order is processed by the correct approvers based on value, type, and complexity.1112**Announce at start:** "I'm using the procurement-approval-routing skill to configure approval chains and enforce authority limits."1314## When to Use This Skill1516**Trigger Conditions:**17- Creating or modifying procurement order (> $0)18- Order value crosses approval threshold19- Approval chain needs to be determined20- HITL gate evaluation required21- Rejection handling with reason capture2223**Prerequisites:**24- Authority matrix configured in system25- Order data complete (value, type, risk level)26- User roles and permissions loaded2728## Step-by-Step Procedure2930### 1. Determine Approval Chain3132Based on order value and type, determine required approvers:3334| Order Value (USD) | Order Value (ZAR) | Approval Chain |35|-------------------|-------------------|----------------|36| < $25,000 | < R500,000 | Procurement Officer |37| $25,000 - $100,000 | R500,000 - R2,000,000 | Procurement Manager + Project Manager |38| $100,000 - $500,000 | R2,000,000 - R10,000,000 | Above + Finance Manager |39| > $500,000 | > R10,000,000 | Above + Executive Sponsor |40| Single-source | Any value | Above + Commercial/Legal Review |4142### 2. Configure Routing Type4344| Routing Type | When to Use | Behavior |45|-------------|-------------|----------|46| Sequential | High-value, complex orders | Each approver must approve before next |47| Parallel | Low-value, routine orders | All approvers can approve simultaneously |48| Hybrid | Medium-value with specialized review | Sequential for certain steps, parallel for others |4950### 3. Enforce Authority Limits5152**Rules:**53- Never allow approver to approve above their authority limit54- Never allow same user to be both requestor and approver55- Never allow approval without budget availability confirmed56- Always log approval action to immutable audit trail