CLM Transformation Programme

Updated 2026-09-11 based on S-2026-09-11-weekly-briefing — no CLM Pilot or live-engagement captures appeared in the 7-day window; the flagship engagement remains invisible in the record. Logged as a continuing capture gap in Open questions / blockers, not a change to programme substance.

Status: active Started: before 2026-03-15 (in flight at point of seeding) Last touched: 2026-09-11

Why this project exists

A retail bank in Ireland is running a Credit Lifecycle Management (CLM) Programme transforming Corporate, Capital and SME credit processes, technology, and data, taking the organisation from low to high data maturity over the period H1 2026 → end of 2029 [S-2026-03-20-paul-clm-data-taxonomy].

Current state

• A multi-workstream programme covering Credit Management (Policy and Covenants), Matrix (Tier Matrix — already live), and CLM (ODS Day 2 terms), with an Operational Data Store (ODS) as the certified system of record for the CLM UI [S-2026-03-20-paul-clm-data-taxonomy][S-2026-05-13-paul-clm-pilot-plan].
• Three sub-engagements active or in flight:
  • CLMP Data Governance and DQ Engagement — 3-month engagement, 15 tasks, 4 May – 31 July 2026 [S-2026-04-25-paul-clmp-brief].
  • CLM Pilot — Covenants and Valuations — 13 workstreams, 63 sub-activities; pilot delivery plan saved 13 May 2026 [S-2026-05-13-paul-clm-pilot-plan].
  • CLM Data Taxonomy Governance — Confluence + Comala governance for Data Glossaries (Phase 1b + Phase 2 + Phase 2b on the glidepath) [S-2026-03-20-paul-clm-data-taxonomy].
• The IRB Requirements and CLM Implications Briefing (DRAFT v0.1, 23 April 2026) is a client-facing artefact translating IRB obligations into Day 1 and Day 2 design implications [S-2026-04-29-paul-irb-clm-briefing].
• Anchored to BCBS 239 / ECB RDARR Guide May 2024 / DAMA-DMBOK v2 / DCAM v3, with target DCAM 4 at CLM R2 [S-2026-04-25-paul-clmp-brief].
• 2026 SREP Business Glossaries action must be met in H2 2026 — “a top priority” [S-2026-03-20-paul-clm-data-taxonomy].

Decisions made

• 2026-03-20 — Confluence + Comala chosen as the governance environment for Data Glossary artefacts (Excel files edited in SharePoint / Teams attached as governed versions) [S-2026-03-20-paul-clm-data-taxonomy].
• 2026-04-25 — CLMP DG & DQ Consultant Brief scoped as a 3-month engagement (not the full glidepath duration) on assumption of follow-on re-contracting; role-agnostic / generic so the Programme Director can socialise the need before recruiting; forums referenced generically rather than naming the in-flight CLM Design Sub-Committee ToR v0.1 [S-2026-04-25-paul-clmp-brief].
• 2026-04-26 — CLMP DG & DQ Delivery Plan saved at DRAFT v0.1: 15 tasks across three phases (Mobilise & Discover; Design; Socialise & Transition) [S-2026-04-25-paul-clmp-brief].
• 2026-04-29 — IRB Requirements and CLM Implications briefing DRAFT v0.1 saved with 8 named recommendations and 8 open client-confirmation questions [S-2026-04-29-paul-irb-clm-briefing].
• 2026-05-13 — CLM Pilot Delivery Plan saved covering 13 workstreams, 63 sub-activities, with parallel-run design, Power BI access pattern (role-based, row-level security), and exit-criteria scorecard ahead of R1 build [S-2026-05-13-paul-clm-pilot-plan].

Open questions / blockers

Eight client-confirmation items from the IRB briefing [S-2026-04-29-paul-irb-clm-briefing]:

1. SI vs LSI status of the bank.
2. Current IRB scope (PD / LGD coverage by portfolio).
3. Materiality threshold parameters under CDR 2018/171.
4. Model-owner mapping.
5. Use-test evidence retention policy.
6. Pillar 3 cadence and template-population responsibility.
7. JST engagement protocol.
8. Historical default-flag back-fill scope.

Plus:

• Whether the 3-month CLMP engagement will be re-contracted for follow-on phases as assumed [S-2026-04-25-paul-clmp-brief].
• Whether 2026 SREP Business Glossaries (H2 2026 deadline) will be met on time [S-2026-03-20-paul-clm-data-taxonomy].
• Forum interlock between Enterprise DG Council, ARB, DQ Forum, BCBS 239 attestation forum, and the in-flight CLM Design Sub-Committee ToR v0.1 [S-2026-04-25-paul-clmp-brief].
• 2026-09-11 (weekly briefing) — capture gap: no CLM Pilot or live-engagement notes were captured in the 7-day window to 11 Sep; the programme has been absent from the record while capture volume has been entirely inbound vendor/regulatory intelligence. Opportunity: a light habit of capturing CLM programme movement would connect the week’s “governed context via MCP” and “AI-as-operational-resilience” signals to live delivery [S-2026-09-11-weekly-briefing].
• 2026-09-18 (weekly briefing) — capture gap continues: a third consecutive week with no CLM Pilot or live-engagement captures in the 7-day window; the programme remains absent from the record while capture volume is entirely inbound vendor/regulatory intelligence. Opportunity unchanged: capturing even two or three CLM decisions or blockers would connect the week’s agent-control-plane and MCP-governed-context signals to live delivery [S-2026-09-18-weekly-briefing].

Connected wiki pages

• implements → BCBS 239 and Data Lineage — anchoring framework.
• parent-of → CLMP Data Governance and DQ Engagement — sub-engagement.
• parent-of → CLM Pilot — Covenants and Valuations — sub-engagement.
• parent-of → CLM Data Taxonomy Governance — sub-engagement.
• parent-of → IRB Requirements and CLM Implications Briefing — client-facing artefact within the programme.
• relevant-to → Service Line — Governance Framework Design — primary service line.
• relevant-to → Service Line — Programme Governance Specialist — embedding model.
• relevant-to → Service Line — Regulatory Readiness and Evidence — IRB briefing as evidence artefact.
• derived-from → S-2026-09-11-weekly-briefing — logged the 7-day capture gap for the programme [S-2026-09-11-weekly-briefing].
• relates-to:: [[EBA Supervisory Direction on AI and Governan