How should delegated approval authority be reviewed?
Stale delegationReview delegated authority when roles, amounts, risk, or project conditions change. A delegation should have clear scope and validity rather than becoming an indefinite workaround.
What to do now
- Identify active delegations
- Check their scope and current role holders
- Confirm limits and expiry conditions
- Update access and records consistently
When to escalate
Escalate when
An approval is being made outside current delegated authority.
Who decides
The sponsor or formally delegated governance body
Example
A temporary deputy's authority ends when the sponsor returns and the system permissions are updated.
Mistake to avoid
Leaving a former role holder's approval access active.
Prevent a repeat
Review overdue decisions and confirm that decision makers have the authority and evidence they need.
Suggested ApprovedFlow setup
- Approvals
- Documents
- Projects
Attach the decision brief and evidence to a configured approval route only after confirming the actual authority and delegation rules. See the platform
Related cases
- The sponsor is unavailable when we need approval. What should we establish?Unavailable decision authority
- Can a sponsor accept every project risk?Risk authority overreach
- The change board is a bottleneck. What should we delegate?Overcentralized change authority
- An AI agent can approve expenses automatically. Should we enable it?Excessive automated decision authority