Reference — generated from the toolkit
Source of truth: toolkit/registers/client-commitment-register.md. Edit it there; this page is regenerated on build.
Client-commitment register
The Stop agenda's first question — what have we promised? — answered as one canonical register. Populated by client commitment triage; nothing pauses safely until every row carries a disposition.
Schema
| Field | Notes |
|---|---|
| ID | CC-NNNN |
| Client | account name |
| Commitment | what was promised, in the client's terms |
| Source | contract / proposal / verbal — link the evidence (SOW clause, proposal section, email, call note) |
| Contractual weight | binding / written-but-uncontracted / goodwill (drives scoring) |
| Revenue at risk | account value / premium volume exposed if missed (Commercial-validated) |
| Promised date | date given to the client; regulatory dates flagged as immovable |
| Disposition | honour / renegotiate / fold into RAPID rebuild / retire |
| Owner | named Delivery owner |
| Status | open / dispositioned / client informed / closed |
Example row
| CC-0001 | {broker} | MTA journey change for scheme {X} | contract (SOW §4) | binding | £{n}k premium | {YYYY-MM-DD} | renegotiate | {name} | dispositioned |
Rules
- Delivery-owned — Delivery owns the register and every row has a named Delivery owner; account leads feed it, they don't run it.
- Commercial view — Commercial validates revenue at risk, leads renegotiation and retirement conversations, and uses only the approved STOP comms pack wording with clients.
- Weekly review — reviewed weekly with Leadership until the undispositioned count reaches zero; a commitment not on the register doesn't exist, and a verbal promise is still a row.
- No silent drops — retire requires an explicit close-out with the client, recorded against the row.