REGISTRY ADMIN · READ-ONLY IN THE PROTOTYPE

The metric registry

140 definitions. The registry — not the dashboard — is the system of record for what a metric means, who owns it and what its threshold is. Changing a threshold is a registry change under change control (R-G-10), not a code change, which is why every chart on this site reads its bands from here.

Every definition now carries a priority band (13 §A.2), derived by a published rule from facts already in the registry — on the company BSC, regulatory, guarding something, target taken from an ACF document, phase. Each one shows the clause that produced it on hover, and every one of the 140 is proposed by Ikigai. None is agreed by ACF — and Q-28 asks who owns that decision, because a band ranks one department’s work against another’s.

140

DEFINITIONS

110

🔴 MANUAL TIER

101

WITH NO AGREED TARGET

107

TARGET PROPOSED BY IKIGAI

SOURCE IN NO INVENTORY

PRIORITIES AGREED OF 140

GOVERNANCE RULES, EVALUATED AGAINST THE ACTUAL REGISTRY

✓R-G-02 — metric_owner and data_owner must be different roles— 0 metrics share one role
✕R-G-11 — a metric may not publish without an agreed target— 101 would be blocked from publishing
✕R-G-01 — every metric names a source system in the ACF inventory— 5 name a system in no inventory

These are the same checks tools/validate_registry.py runs in CI. A governance rule that is only written down is a wish; these are executable, and at fullstack R-G-02 is additionally a database CHECK constraint so it cannot be bypassed by an application bug.

ALL DEFINITIONS — EDIT IS DISABLED (H-01 DELIVERS WRITES AT FULLSTACK)

SEARCH — ID, NAME, FORMULA, OWNERDEPARTMENTPERSPECTIVETYPETIERPRIORITYORDERGOVERNANCE

Showing 140 of 140 definitions

ID COLOURFINANCIAL CUSTOMER INTERNAL PROCESS PEOPLE & LEARNING· the PERSPECTIVE column says the same thing in words

ID	PRIORITY	NAME	DEPT	PERSPECTIVE	TYPE	TIER	TARGET	METRIC OWNER	DATA OWNER
PD-07	P5	Time-to-launch a scheme	Product Development & Marketing	INTERNAL PROCESS	KPI	◇MANUAL	— none agreed	Head of Product Development & Marketing	IT System Planning
PD-08	P5	Insurance conduct indicator	Product Development & Marketing	CUSTOMER	KRI	◇MANUAL	— none agreed	Head of Product Development & Marketing	IT System Development
PD-09	P5	Scheme concentration	Product Development & Marketing	FINANCIAL	KRI	◇MANUAL	— none agreed	Head of Product Development & Marketing	IT System Development
TS-01	P4	Dials per agent per day	Telesales	INTERNAL PROCESS	KPI	◈MANAGED	TBC	Head of Telesales	IT System Development
TS-02	P4	Contactability rate	Telesales	INTERNAL PROCESS	KPI	◈MANAGED	TBC	Head of Telesales	IT System Development
TS-03	P2	Consent rate	Telesales	CUSTOMER	KPI	◇MANUAL	≥ 4%	Head of Telesales	IT System Development
TS-04	P4	Refusal rate	Telesales	CUSTOMER	GUARD	◈MANAGED	monitor	Head of Telesales	IT System Development
TS-05	P4	Lead → application conversion	Telesales	CUSTOMER	KPI	◈MANAGED	TBC	Head of Telesales	IT System Development
TS-06	P4	Application → disbursement conversion	Telesales	CUSTOMER	KPI	◈MANAGED	TBC	Head of Telesales	IT System Planning
TS-07	P4	Average ticket size	Telesales	FINANCIAL	KPI	◈MANAGED	TBC	Head of Telesales	IT System Planning
TS-08	P2	QA / compliance call score	Telesales	INTERNAL PROCESS	KPI	○UNMEASURED	≥ 90% (inferred)	Head of Telesales	IT System Development
TS-09	P3	FPD5+ on telesales-originated vintage	Telesales	INTERNAL PROCESS	KRI	◇MANUAL	≤ 4%	Head of Telesales	IT System Planning
TS-10	P4	Agent productivity (VND per agent)	Telesales	PEOPLE & LEARNING	KPI	◈MANAGED	TBC	Head of Telesales	IT System Planning
TS-11	P4	Agent attrition (collaborator vs labour)	Telesales	PEOPLE & LEARNING	KRI	◇MANUAL	bands TBC	Head of Telesales	HR Systems Administrator
TS-12	P4	Average handling time	Telesales	INTERNAL PROCESS	KPI	◈MANAGED	TBC	Head of Telesales	IT System Development

Page 6 of 6 · 25 per page. Filters live in the URL, so this view is a link you can send — which is how “the 101 metrics with no agreed target” becomes a conversation rather than a screenshot.