Why the CRO dashboard is almost always stale — and why that matters
A risk dashboard built from manually extracted, periodically refreshed data is almost always behind reality. The portfolio NPL figure shown on a Monday morning dashboard was computed on Friday — and it reflects the portfolio as it was on Thursday, because the Friday run used Thursday's CBS snapshot. An account that crossed the 90-day NPL threshold on Saturday is not on the Monday dashboard. A large LAP account that was written off on Friday afternoon is not on the Monday dashboard. The CRO is making risk-based decisions from a two-to-four day old picture of the portfolio.
In a stable, slowly changing portfolio, this lag is tolerable. In a portfolio where NPL classification runs daily and collections activity is continuous, a four-day dashboard lag is a governance failure. The CRO cannot perform their function — assessing whether the institution's risk position is within appetite, escalating emerging risks to the Board, directing management attention to deteriorating segments — from stale data.
The Risk Reporting Agent AI connects directly to the live data sources — the CBS, the Provisioning AI's classification database, the Stress Testing AI's scenario outputs, the collections system, and the Bureau pull log — and assembles the dashboard in under 60 seconds, on demand, showing the position as it stands at the moment of assembly.
The data sources that feed the dashboard — and their latency
Outstanding balances, payment status, GIRO / direct debit results, instalment schedule
CBS is the authoritative source for account balances and payment behaviour. The Risk Reporting AI pulls the live CBS balance for every NPL account and the payment register for the current day — not a nightly snapshot. Any GIRO / direct debit result received since midnight is included in today's dashboard.
API pull
Current NPL classification, DPD count, provision required and held, 75-day watch list
The Provisioning AI runs its classification check at midnight every day and makes the results available via API. The CRO dashboard pulls the current classification for every account — post the overnight run — giving the CRO the day's freshest NPL picture before they open their laptop.
Post midnight
Latest stress scenario results, current CAR, rate shock impact at current portfolio composition
The most recent stress test scenario output is included in the CRO dashboard, showing the current CAR and the CAR under the MAS / Central Bank benchmark 200bps shock. If an on-demand stress test was run since the last dashboard assembly (triggered by an MAS / Central Bank rate change or CAR proximity alert), the latest result is used.
Auto-refreshed
DPD 1–90 distribution, collection contact rates, PTP rates, broken PTP counts, GIRO / direct debit failure rates
The collections system provides the leading indicators of future NPL: how many accounts are in the 60–89 DPD range (approaching the NPL threshold), what the current month's GIRO / direct debit failure rate is, and whether collection activity has resulted in PTPs at an acceptable rate. These are forward-looking credit quality signals.
Intraday
Current portfolio NIM, yield by segment, rate-shock NIM compression, pricing adequacy vs risk
The Risk-Based Pricing AI's current NIM estimate is included in the dashboard, showing whether the portfolio is generating adequate margin relative to the risk being carried. The NIM figure is segment-level — the CRO can see which segments are generating adequate yield and which are not.
Market rates live
Current week disbursements, average credit score, TDSR (Total Debt Servicing Ratio) distribution, and score quality vs portfolio average
New disbursements create future risk — the CRO needs to see not just the current portfolio but the risk characteristics of what is being added to it. The Origination AI provides the current week's disbursement quality metrics: average credit score, TDSR (Total Debt Servicing Ratio) distribution, and product mix — so the CRO can assess whether origination quality is improving or deteriorating relative to the portfolio standard.
Current week
The live CRO dashboard: what assembles in 58 seconds
The 60-second dashboard is not a speed achievement — it is a governance requirement
A CRO who can see the current risk position in under a minute, on demand, any day of the week, is a CRO who is equipped to perform their function. A CRO who must wait for a weekly report or request a manual data extraction is structurally impaired in their ability to identify emerging risks before they become material events. The Risk Reporting Agent AI does not speed up the old process — it eliminates the wait by replacing the extraction-transformation-reporting chain with a direct connection between the live operational systems and the decision-maker who needs to see them. The 58 seconds is the connection time. The data has always been there.
