CUSTOMER · KPI · LAGGING

Approval ratioAP-02

55.2%— No target◈MANAGEDAppraisal — daily decision report· FAILING

THIS NUMBER HAS STOPPED ARRIVING

The feed that produces it — Appraisal — daily decision report — is having its batches refused. The value above is the last one that arrived, and the metric is now not_reported: it cannot render green, and it will not be quietly carried forward. Open the feed.

ACTUAL VS PLAN

DEFINITION

Formula: approved ÷ finalised
Unit / direction: pct · lower better
Source system: Appraisal daily report
Refresh: daily_t1
Target: TBC
Target status: PROPOSED BY IKIGAI (T-01)
Baseline in context/: 55.1% (5,285 approved)

OWNERSHIP — two roles, two people (R-G-02)

Metric owner — owns the target and the result

Head of Appraisal Department

Data owner — owns the source system and pipeline

IT System Planning

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

GUARD METRIC — the check on this number (R-G-06)

FPD5+ on approved vintage

AP-09

1.8%

-2.2pp vs target 4.0%

MANUALDWH⏱ T+1

Head of Appraisal Department·IT System Planning

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

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.