Platform & Insights

Workflow & Approvals

Configurable approval chains across modules.

Overview

Institutions run on approvals — leave, purchases, record changes, mark unlocks — and most run them on chance encounters in corridors. Workflow & Approvals turns them into configured chains: the right people, in the right order, with waiting time visible and escalation when things sit too long.

  • Configurable approval chains
  • Multi-level routing
  • Response commitments & escalations
  • Notifications
  • Full audit trail
Case study · Workflow & Approvals

From corridor approvals to chains that clear themselves

Representative scenario — illustrative

A trust running three schools approves everything — staff leave, purchase indents, mark-sheet unlocks, record corrections — by walking a paper file from desk to desk to gather signatures.

Doing it by hand

A leave form waits on the principal’s desk while she is away at a seminar; a purchase indent for lab chemicals sits three weeks because nobody knew it needed the accountant’s sign-off first. Requesters chase their own files through the corridor, and when something is urgent the loudest voice jumps the queue.

The cheap-ERP trap

The cheap ERP added a “request” button, but every request landed in one inbox with no order and no rules — a ₹500 stationery ask and a ₹5-lakh purchase looked identical, and nothing escalated when an approver went quiet. There was no record of who decided what, so disputes still ended in “I never saw it.” Six months in, staff went back to walking the paper file, because at least a physical file could be pointed at on someone’s desk.

With ez.school

ez.school turns each request type into a configured chain — by department, by value, by role — so the right people sign in the right order, small requests move fast, and consequential ones gather the right signatures. Waiting times and items over SLA are visible, idle requests escalate to the next level on their own, and every decision is recorded with the chain that produced it.

The difference, side by side
By handOrdinary ERPez.school
Routing a requestWalk the file desk to deskOne inbox, no orderChain by type, value, department
Big vs smallSame signatures for bothTreated identicallyThresholds route by value
When it stallsIt just sitsSilence is a vetoAuto-escalates to the next level
Who decided“I never saw it”No trailEvery decision logged with its chain
The outcome
  • By valueRequests routed
  • AutoOverdue escalation
  • Every stepOn the record

The decision trail for one purchase indent — who approved, when, and where it escalated — so “I never saw it” stops being an answer.

Inside the app

How Workflow & Approvals works for you

Chains you configure, queues people clear

Each request type gets a chain — by department, by value, by role. Approvers work from a queue with full context; requesters see exactly where their item waits. Nothing depends on catching someone in the staff room.

Accountability the polite way

Median approval time, items over SLA and escalations are visible — so bottlenecks are process facts, not accusations. Every decision is logged with the chain that produced it.

The cycle

A request’s path

  1. 1Raised in any module
  2. 2Chain resolves approvers
  3. 3Queue & decide
  4. 4Escalate if idle
  5. 5Outcome recorded
Who uses it

One app, seen from every seat

RequesterKnows where their request sits — no more asking around.
ApproverClears a queue with context instead of signing paper blind.
DirectorSees which processes drag and fixes the chain, not the people.
Evaluation questions

Workflow & Approvals — asked and answered

Which modules can use approval chains?

Leave and staff requests, procurement, record-change requests and examination governance actions — chains are configured per request type.

Can chains branch by value or department?

Yes. Routing rules consider type, department and thresholds — small requests move fast, consequential ones gather the right signatures.

What stops approvals from stalling?

Waiting times are visible per item, SLAs mark overdue approvals, and escalation notifies the next level — silence is no longer a veto.

Bring Workflow & Approvals to your campus

Guided onboarding, local-currency pricing, and human support from day one.