Problem statement
Approvals are slow, inconsistent, and often happen on WhatsApp—creating risk, confusion, and repeated disputes.
What you need to know
- An approval matrix is a control tool, not a document for decoration.
- Your thresholds must reflect real transaction sizes and roles in your org.
- Routing must match how your team actually works (Drive/M365/Notion, etc.).
Step-by-step
- List the decisions that move money, risk, or reputation (payments, discounts, hires, vendor onboarding, filings).
- Define authority roles (requester, reviewer, approver, final approver) and escalation paths.
- Set thresholds per decision type (₦ ranges, risk level, exceptions).
- Create a simple routing workflow (who sends what to whom, and where it gets stored).
- Publish as a 1-page matrix + a short policy note; train the team with 3–5 real scenarios.
- Install version control: owner, review cadence, change log.
Common mistakes
- Making thresholds unrealistic (forcing everything to MD).
- No storage/record rule (approvals disappear in chats).
- No exception handling (urgent cases cause policy-breaking).
What CSTL can deliver
- Approval matrix + authority limits document (audit-friendly).
- Routing workflow + storage/version-control rules.
- Template pack for approval requests + exception logs.
- Implementation roadmap and adoption guidance.