Five incidents. Five days. Every single one, on its own, was survivable.
Monday morning at your branch. Over the next five days: a gold loan audit discrepancy, a suspicious account pattern, a phishing-triggered systems breach, a KYC red flag on a valued customer, and a credit account everyone has quietly hoped would recover on its own. By Friday evening, a viral video forces a Zonal review of how the whole week was handled.
Every one of these five incidents, taken alone, was survivable.
The number that explains what actually went wrong: 0 of 5 — escalated on time.
Figure out why. Figure out what you'd do differently.
For each of the week's five issues, mark whether it was actually escalated on time (per policy) or not.
Each card reveals a piece of the week. The full picture only emerges when all cards are open.
Rank each party. You can update this in the Zonal Review.
Cast your vote first to unlock the reveal.
The Chief Manager for Recovery raised this exact pattern once before, in a zonal meeting, after watching it happen at a different branch. Nothing changed as a result — not because anyone disagreed, but because a single verbal observation, raised once, doesn't automatically become a policy change.
Noticing a pattern is not the same as fixing it. A pattern only becomes a fix when it's converted into something structural: a threshold, an auto-escalation rule, a mandatory second reviewer — something that doesn't depend on any one person remembering to raise it again next time.
If that first observation had been logged as a formal RCSA finding rather than a comment in a meeting, this exact week might not have happened a fourth time.
Toggle each issue to "escalated on time" and see how the week's outcome message changes.
The Compliance Officer's week looks very different from the Chief Manager (Branch Head)'s.