The morning daily ops pack tells the COO what happened yesterday. The SLA dashboard tells the Head of Operations what is happening right now. It is the difference between a retrospective report and a live operational control instrument. The MIS & Reporting Agent AI maintains the SLA dashboard by continuously refreshing from the LOS, CBS, collections, and QC systems — updating every 30 minutes during working hours, showing the current SLA status of every active application, every active dispute, and every compliance obligation in real time. It is the operational view that allows the Head of Operations to intervene before a breach rather than after — and to make resource allocation decisions based on where the pipeline is stressing, not where it stressed yesterday.
What a genuine SLA dashboard contains — vs what most institutions call a dashboard
Most lending institution dashboards are static exports from the LOS or CBS — a table updated once daily or once weekly, showing counts and totals. A genuine SLA dashboard is a live operational view that shows not the totals but the positions: each active application's position on the SLA clock, updated continuously. It answers the questions a Head of Operations actually asks during the day: "How many applications are within 2 hours of breaching their step SLA right now?" "Which branches have the highest proportion of at-risk applications?" "Has the Hubli credit assessment queue improved since this morning's intervention?"
The MIS & Reporting Agent AI's SLA dashboard answers all three in real time, because it is built from a live data feed rather than a daily extract. It applies the same threshold logic as the morning ops pack, but continuously — so the metric that triggered an action item at 7 AM can be checked again at 2 PM to see whether the action produced a result. This closes the management loop: the COO directs an intervention, the dashboard shows whether it worked.
The live SLA dashboard: 14:30 · November 14, 2025
What the SLA dashboard enables that the morning ops pack cannot
| Question | Morning ops pack answers | SLA dashboard answers |
|---|---|---|
| Which applications are about to breach their SLA? | Yesterday's at-risk list — not actionable if the breach happened during the day | Real-time: exact applications, current SLA consumption, time remaining before breach · Updated every 30 minutes |
| Did the morning's intervention work? | Cannot — pack is assembled overnight from prior-day data | Yes: Hubli credit queue was 8 applications at 9 AM (COO directed reallocation) · At 2:30 PM it is 4 applications · Intervention working |
| Is the Bellary QC situation improving? | Shows the QC hold rate as of yesterday morning | Shows the current hold rate (34%) and the number of files currently on hold (18) — updated as files are cleared or new holds are added |
| What compliance obligations are due today? | Compliance section shows obligations due this week | Live status: CIBIL submission due tomorrow, 78% complete · TDS remittance due next week, not started · All obligations with current completion status |
| Is the dispute approaching its 30-day limit? | Shows disputes by SLA status as of yesterday | Real-time: DIS-2025-1798 is at Day 26 of 30 · Exact days remaining visible · Nodal Officer can see the clock and prioritise accordingly |
The green alert — "Hubli credit queue: improving from 8 to 4 applications since 9 AM" — is as important as the red alerts. It tells the COO that the morning intervention worked, which means they do not need to escalate further on this issue today.
A management decision is only as good as the feedback that follows it. The COO directed analyst reallocation at 9 AM based on the morning ops pack. At 2:30 PM, the SLA dashboard shows that the Hubli credit queue has halved — from 8 at-risk applications to 4. The intervention worked. The COO does not need to ask the Head of Ops for a status update, does not need to call a check-in meeting, and does not need to escalate further. The dashboard has closed the loop. The COO's attention can now focus on the issues that have not yet resolved — the Bellary QC spike, the LA-2025-18808 valuation breach, and the DIS-2025-1798 dispute approaching its 30-day limit. The SLA dashboard is not a reporting tool — it is a control system. It shows where the institution's operations are under control and where they are not, in real time, so that management attention always flows to the problems that need it rather than the problems that have already been solved.