Limits are enforced, not remembered
A transaction above a threshold routes for referral because the rule fired, not because the person processing it recalled the policy.
All projects 
Workflow & controls
Approval Matrix
Turning an authority policy into something the system enforces
Authority limits usually live in a signed document and are applied from memory. Approval Matrix turns them into rules the platform applies itself, and records the reasoning each time one fires.
- Domain
- Workflow
- Scope
- Approvals & controls
- Status
- In production
- Market
- Kenya
The problem
Every organisation has an authority matrix. Very few have it in the system that processes the transactions it governs. It sits in a signed policy document, and enforcement depends on the person processing the item remembering which threshold applies and who they are meant to escalate to. Breaches are found in an audit, months later, when they are expensive to unwind.
- 01 Authority thresholds held in a document rather than in the system applying them
- 02 Escalation depending on the processor recognising that a limit was crossed
- 03 No reliable record of who approved what, at what level, and under what authority
- 04 Limit breaches discovered during audit rather than prevented at the point of decision
What we built
The authority matrix as executable configuration. Thresholds, roles and referral paths are modelled as the organisation actually defines them, so a referral fires from the rule rather than from someone noticing. Every decision writes its own entry, so how an outcome was reached is readable afterwards.
- 01 Approval limits and referral rules configured to match the organisation’s own matrix
- 02 Automatic routing to the correct authority level when a threshold is crossed
- 03 Role and delegation handling for absence and acting authority
- 04 A recorded entry per decision naming the actor, the level exercised and the rule invoked
- 05 Configuration changeable as the matrix changes, without a code release
The result
What the business can do that it could not before.
Approvals are attributable
Each decision records who exercised what authority under which rule, so a review reads the record instead of reconstructing intent.
Breaches are prevented, not discovered
The control operates at the point of decision rather than surfacing months later in an audit finding.
The matrix can change without a release
Thresholds and referral paths are configuration, so a revised authority policy takes effect without waiting on engineering.
Rules engineRole & delegation modelReferral routingAudit log
Start a project
Have a website, app, dashboard, or platform that needs to feel serious?
Share what you are building, what needs to work better, or where the current system is slowing the team down. We will help shape the next practical move.