An exception that reaches the wrong desk is an exception that takes three days to resolve. An exception that reaches the right desk — with the right context, at the right level of authority, with the resolution options already outlined — takes three hours. The Ops Programme Manager AI routes every exception in the lending operations pipeline through a decision tree that determines: what kind of exception this is, who has the authority to resolve it, what information they need, and how long they have before the delay cascades into a pipeline failure.
Why exceptions route to the wrong place in manual operations
In a manual lending operations environment, exceptions are typically routed by whoever noticed them first — usually the team that could not proceed with their work because of the exception. A credit analyst who cannot complete a sanction because the property valuation report has a discrepancy emails the manager, who forwards to the legal head, who says it is a valuation issue, who says it is a policy issue for credit, who eventually gets to the CCO three days later. The exception has been handled by four people who could not resolve it before reaching the one person who could.
The Ops Programme Manager AI classifies every exception at the moment it is identified — by type, by severity, by which function has resolution authority, and by the urgency created by downstream dependencies. The routing decision is made in seconds, not hours. And the routing destination receives a brief, not a forwarded email chain.
The exception classification: type determines routing
Policy
Exception
An application that falls outside approved credit policy — requires credit authority to approve or decline
Examples: LTV above policy ceiling for the product; FOIR above the maximum; applicant in a restricted sector; loan amount above the normal auto-approval limit. These exceptions require a human credit authority holder to review and make a determination — they cannot be resolved procedurally. The Ops PM AI routes to the appropriate credit authority level based on the deviation type and magnitude, with the deviation clearly stated and the policy reference cited.
→ Route to: Credit Risk Head (deviation >10%) or Senior Underwriter (<10%) · SLA: 4 hours · Brief includes deviation magnitude, policy reference, recommended actionData
Exception
Application cannot proceed because a required document is missing, insufficient, or inconsistent
Examples: income document does not cover the required period; property document has a discrepancy in the survey number; KYC document shows a different address than the application form. These exceptions have a specific document or data resolution required — they are not policy judgements. The Ops PM AI routes to the origination team or the borrower-facing channel with a specific data request, not to a decision-maker.
→ Route to: Origination Head (internal doc request) or borrower communication (customer data required) · SLA: 48 hrs · Brief includes specific document missing, why it is required, how to obtain itSystem
Exception
A system failure has stopped a process from executing — bureau API down, LOS integration error, NACH registration failure
Examples: CIBIL API returning errors on a batch of applications; NACH registration confirmation not received from the bank; LOS-to-core system data sync failure. These exceptions need technology resolution — they are not credit or policy decisions. Routing them to operations or credit wastes time. The Ops PM AI routes directly to the CTO or the relevant technology team with the error code, the affected application batch, and the downstream impact if not resolved within the SLA.
→ Route to: CTO / relevant system team · SLA: 2 hours (disbursement blocker) or 4 hours (non-critical) · Brief includes error code, affected volume, downstream impactCompliance
Exception
An action required to proceed with the application creates a potential compliance risk that requires CCO review
Examples: a borrower who has appeared on a watchlist update; a credit policy exception that would also breach an RBI guideline limit; an unusual transaction pattern in the borrower's account statement that triggers an AML review. These exceptions cannot be resolved by operations or credit alone — they require the CCO to confirm that proceeding is compliant. The Ops PM AI routes to the CCO with a compliance brief, not to an operational queue.
→ Route to: CCO (always) · MD if regulatory consequence is material · SLA: 2 hours · Brief includes specific compliance concern, applicable regulation, recommended hold action pending reviewCommercial
Exception
A situation where the credit rules do not clearly resolve the question and a commercial judgement is needed
Examples: a high-value borrower whose application marginally fails one criterion but whose overall profile is strong; a strategic relationship borrower where the credit team recommends approval but policy requires escalation; a case where the institution's market positioning suggests flexibility is appropriate. These require senior commercial judgment — not policy interpretation, not technical resolution, but business decision-making authority.
→ Route to: MD or designated business authority · SLA: 24 hours · Brief includes commercial context, credit team recommendation, risk assessment, comparable precedentsThe decision tree in action: a same-day LTV exception
A home loan application for ₹58 lakhs arrives at the credit team. The property is valued at ₹65 lakhs — giving an LTV of 89.2%. Credit policy permits up to 80% LTV for home loans. The application has a CIBIL of 784, a FOIR of 32%, and a borrower in formal salaried employment with 12 years at the same employer. Credit is strong on every metric except LTV.
In a manual system, this exception travels from the underwriter, to the credit manager, to the credit head, possibly back to the underwriter for a revised documentation request, and then back up. Timeline: 2–3 days.
In the Ops PM AI system: the LTV breach is classified as a Type A policy exception (LTV deviation of 9.2pp above the 80% ceiling) at the moment it is detected. The credit authority matrix shows that LTV exceptions of this magnitude require Credit Risk Head approval. The Ops PM AI routes the exception brief to the Credit Risk Head within minutes of the credit team flagging the LTV breach, with: the exact deviation, the application's full credit profile (784 CIBIL, 32% FOIR, 12-year employment tenure), the policy reference, and the three resolution options (approve with enhanced monitoring conditions, decline and inform borrower, request borrower to increase down payment to bring LTV to 80%). Timeline: Credit Risk Head reviews the brief and makes a determination in 90 minutes.
What the Credit Risk Head receives
Application reference, current LTV (89.2%) vs policy limit (80%), exact deviation (9.2pp), borrower's full credit profile in 5 key metrics, policy reference number, three resolution options with implications of each, and the downstream disbursement date impact if the exception is not resolved today.
→ Routing: Credit Risk Head · SLA: 4 hours · Context: complete · No follow-up calls neededThe routing the Ops PM AI prevents
Underwriter emails credit manager. Credit manager asks for additional documentation. Underwriter sends to legal for property assessment. Legal says it is a credit policy issue. Credit manager says it needs MD approval. MD asks what the credit head thinks. Credit head says they never received it. Exception resolved on Day 3.
→ 3 days → 90 minutes · Same authority · Better information · Direct routingThree options, one click to select
Option A: Approve with enhanced monitoring and quarterly review covenant. Option B: Decline — standard communication to borrower. Option C: Approve conditionally — borrower increases down payment to reduce LTV to 80% (requires additional ₹5.9L from borrower). The authority holder selects; the Ops PM AI executes the downstream actions.
→ Authority makes the decision · Ops PM AI executes the selected path automaticallyAfter the decision: automatic task generation
If Option A selected: enhanced monitoring flag set, quarterly review covenant documented, sanction letter updated with condition, credit team notified, file released to legal. If Option C selected: borrower communication drafted and queued, application held pending response, 5-day response window set, expiry reminder scheduled.
→ Decision to execution: automated · No further manual routing requiredThe escalation matrix: authority levels and SLAs
| Exception Type | Classification Criteria | First Route | Escalation If Unresolved | SLA | Brief Contains |
|---|---|---|---|---|---|
| Type A — Policy | Any underwriting parameter outside approved credit policy | Credit Risk Head (deviation >10%) or Sr. Underwriter | MD after SLA breach | 4 hrs | Deviation magnitude, policy ref, credit profile, 3 options |
| Type B — Data | Missing, inconsistent, or insufficient documentation | Origination Head or borrower channel | COO if borrower unresponsive after 48 hrs | 48 hrs | Specific document missing, reason required, how to obtain |
| Type C — System | API failure, integration error, or system downtime | CTO / system owner | COO if business impact significant | 2 hrs (disburse blocker) · 4 hrs (other) | Error code, affected volume, downstream impact, workaround if available |
| Type D — Compliance | Regulatory, watchlist, AML, or conduct risk concern | CCO (always) | MD if regulatory consequence material | 2 hrs | Specific concern, applicable regulation, hold action taken, risk assessment |
| Type E — Commercial | Business judgement required beyond policy parameters | MD or designated business authority | Board if material risk involved | 24 hrs | Commercial context, credit rec, risk assessment, comparable precedents |
The exception that reaches the right desk is already half resolved
The most common cause of long exception resolution times is not difficulty — it is misdirection. An exception that requires the Credit Risk Head reaches the credit manager first, then the operations team, then back to credit, then finally to the Credit Risk Head on Day 3 with a context that has been filtered through three people who could not resolve it. The Credit Risk Head receives the exception without the original data. They ask for it. It takes another day. The Ops Programme Manager AI eliminates the filtering — the Credit Risk Head receives the exception within minutes of its identification, with the complete original data, the deviation clearly stated, and the three resolution options outlined. The decision is straightforward because the brief is complete.