top of page
Search

Escalation Management: When More Reviews Add Cost, Not Control

  • Writer: shishir shrimal
    shishir shrimal
  • 3 days ago
  • 3 min read

Most organisations believe escalation is a sign of control.


Something goes wrong → it gets escalated → more people review → more visibility → problem should get fixed.


In reality, what matters is not escalation.


It’s how escalation behaves inside the system.


What Is Escalation Geometry?


Escalation Geometry is the structure of how issues move across the organisation.


Not whether escalation happens —but:

  • how many layers an issue travels through

  • how many parallel reviews it triggers

  • how many forums it touches

  • whether it expands before it resolves


In short:

The shape of escalation inside the organisation.

The Three Shapes of Escalation


1) Linear (Healthy)


Branch → Regional → HO → Closed

  • minimal branching

  • clear ownership

  • fast resolution


Cost: Low

Learning: High


2) Layered Vertical (Heavy but Controlled)


Branch → Regional → Zonal → HO → Risk → Audit

  • multiple layers

  • sequential reviews

  • slower but contained


Cost: Medium

Learning: Moderate


3) Expanding / Networked (Where Problems Begin)


Branch→ Regional→ Credit→ QC→ Risk→ Audit→ Governance forums→ Back to Regional

  • parallel loops

  • repeated reviews

  • unclear ownership

Cost: High

Learning: Low


This is where escalation stops solving problems and starts creating work.


SARTHI NBFC Operations Framework | Escalation paths expanding across teams and management layers in an organisation
SARTHI NBFC Operations Framework | Escalation paths expanding across teams and management layers in an organisation

What It Looks Like on the Ground


You don’t need org charts to see this.


You’ll notice it in everyday signals:

  • the same issue shows up in multiple meetings

  • different teams review the same case

  • escalation mails marked “for visibility” increase

  • actions get tracked, but recurrence doesn’t reduce

  • managers spend more time reviewing than resolving

The system feels “busy”.


But not necessarily effective.


Why This Drives Cost (Without Anyone Noticing)


Escalation geometry expands quietly.


No one approves it explicitly.


It builds layer by layer:

  • one more review call

  • one more approval step

  • one more control check

  • one more tracker

Over time, this leads to:

  • more coordination effort

  • more mid-layer roles

  • more meetings and documentation

  • slower decision cycles

Headcount grows.But not because risk increased —because escalation expanded.

A Familiar Pattern


Consider a simple situation:

  • early delinquency rises

  • leadership reacts

  • new escalation calls are introduced

  • additional reviews get added

  • QC sampling increases

  • audit deepens checks

All valid actions.


But if the root cause is not fixed,the system responds by adding layers.


Escalation becomes:

  • wider (more teams involved)

  • taller (more levels involved)

That’s escalation geometry inflation.


What Actually Fixes It


The answer is not “less escalation”.


It is better geometry.


Which means:

  • clear ownership at the lowest possible level

  • minimal horizontal movement

  • escalation only when decision rights shift

  • closure linked to root cause, not review completion

In practice, strong systems:

  • resolve more issues where they originate

  • escalate fewer but more meaningful cases

  • reduce repeat escalations over time


Why This Matters Beyond NBFCs


You’ll see this pattern everywhere:

  • operations teams

  • credit and risk functions

  • customer support environments

  • even large corporate decision processes

Whenever complexity increases, escalation geometry tends to expand, escalation management becomes complex, inefficient


Unless it is actively designed.


SARTHI Perspective


In SARTHI, this sits at the intersection of:

  • process design (who owns what)

  • control design (who reviews what)

  • operating rhythm (when escalation happens)

The focus is not on adding controls.


It is on:

ensuring escalation paths stay tight, purposeful, and outcome-linked

Because beyond a point,more escalation doesn’t improve control.


It dilutes it.


Closing Thought


If escalation volume is rising in your system,

don’t just ask:

“Why are there so many issues?”

Ask:

What shape is escalation taking inside our organisation?

That answer usually explains both:

  • your cost structure

  • and your control effectiveness


SARTHI is an operations framework for NBFCs that improves growth and risk outcomes by strengthening field execution through 300+ defined practices.


To know more: sarthiworks.com

 
 
 

Comments


bottom of page