A maker-checker engine, used everywhere something needs sign-off.
Fee waivers, voucher postings, leave requests, loans, promotions — every approval in the institution runs through one engine, with multi-stage routing, SLA escalation, and delegation when someone's on leave.
One approval engine, not a different sign-off process per module.
Modules don't build their own approval logic — they submit into this engine and subscribe to the outcome, so every approval looks and behaves the same way.
Amount-bracket, school, and department-scoped routing rules decide who approves what, at every stage, before it's finalised.
The person who raised a request can't also approve it — a hard guard, not a policy someone has to remember to follow.
A request sitting past its SLA automatically escalates, instead of quietly ageing in someone's inbox indefinitely.
An approver going on leave can delegate their pending approvals, with delegation windows activated and expired automatically.
A daily digest reminds each approver of their pending count, so nothing sits unnoticed during a busy week.
Every request shows its complete stage history — submitted, reviewed, approved or returned, by whom, and when.
Fee waivers, voucher posting, leave, loans, promotions, and fund-grants all route through the same engine — one inbox, not five.
A risk badge strip flags unusual requests — large amounts, repeated returns — for closer review before approval.
What finance and HR heads ask first
Is this one central inbox, or does every module have its own separate approval screen?
One central inbox — every module (Fee, Finance, HR, Payroll, and more) submits into the same engine, so an approver checks one place instead of hunting across five different module screens.
Can the same person raise and approve their own request?
No — this is enforced as a hard guard in the engine, not a policy that relies on someone remembering the rule.
What happens if an approver is on leave and requests pile up?
They can delegate to another approver for a defined window; delegation activates and expires automatically, so nothing sits waiting for someone who isn't available.
Does routing change based on the amount or department involved?
Yes — routing rules can be scoped by amount bracket, school, and department, so a small routine request and a large one can follow entirely different approval chains.
Which processes actually use this engine today?
Fee waivers, voucher posting, leave requests, staff loans, and fund-grant requests all route through it, with more processes adopting it over time as each module migrates its own status field onto the shared engine.