Skip to content
PROTOTYPE — MOCK DATAFigures are generated fixtures derived from the registry. Not ACF actuals.
Menu (13)
← Collections / Debt Recovery
CUSTOMER · KPI · LAGGING

Resolved rate by bucketCO-01

103.7%— No target◇MANUALCollections — Nexusti roll rates
OPEN ALERTS ON THIS METRIC
OPEN — 1
KPIResolved rate by bucketCO-01open 7h

Value 54.97 against threshold 70.

ACTUAL VS PLAN
DELINQUENCY ROLL

Which bucket is the book leaking from?

How much of this is measured: Resolved rates are published; the roll-FORWARD splits between them are derived as (100 − resolved) and are not separately reported. Cure (roll-back) is near zero late-stage, so the sankey shows it only where ACF reports it.

DEFINITION
Formula
resolved POS ÷ bucket POS
Unit / direction
pct · higher better
Source system
Nexusti
Refresh
daily_t1
Target
per bucket TBC
Target status
PROPOSED BY IKIGAI (T-01)
Baseline in context/
B0 98.59% · B1 54.97% (below KPI) · B2 41.67% · B3 31.45% · B4 4.98%
OWNERSHIP — two roles, two people (R-G-02)
Metric owner — owns the target and the result
Head of Debt Collection Operations
Data owner — owns the source system and pipeline
IT System Development

Both proposed by Ikigai and awaiting ACF confirmation (DEC-02).

GUARD METRIC — the check on this number (R-G-06)
Conduct / complaint rate
CO-09
29.4%
Off target
MANUALCS + Nexusti⏱ T+1

Head of Debt Collection Operations·IT System Development

A headline KPI is resolved with its guard, so the pairing cannot be forgotten by the UI.

COMMENTARY — why the number is what it is
  1. Head of Debt Collection Operationsperiod 2026-09 · 21 Sep 2026

    B1 below KPI again. Root cause is coverage, not effort — 65,215 cases still have no assigned collector.

Commentary is attached to the metric and period, not to a slide. It survives the month — which is what makes a variance reviewable at the next meeting instead of re-argued. Prototype — read-only fixtures; at fullstack this is the COMMENT table with author identity from AD.