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

Roll-back / cure rateCO-03

6.4% No targetMANUALCollections — Nexusti roll rates
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
balance curing ÷ opening bucket
Unit / direction
pct · higher better
Source system
Nexusti + T24
Refresh
daily_t1
Target
TBC
Target status
PROPOSED BY IKIGAI (T-01)
Baseline in context/
late-stage near zero: B04–B06 %RS_POS ~4–7%
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 Planning

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

COMMENTARY — why the number is what it is

No commentary recorded for this metric. A red tile with no explanation is the failure mode the current monthly pack already has.

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.