Redstrata Knowledge Base

CLM Pilot — Covenants and Valuations

5 min read

CLM Pilot — Covenants and Valuations

Status: active (planning) Started: 2026-05-13 (delivery plan created) Last touched: 2026-08-07 (weekly-briefing gap note)

Why this project exists

Pilot delivering covenants and valuations functionality to a small user base on the CLM Transformation Programme (Non-Retail scope: Corporate, SME, Leveraged Finance, Commercial Real Estate). Pilot design includes parallel running with the existing semi-automated process, CLM UI with a small set of alerts and events, threshold-driven borrower-level metrics, one near-real-time source via event services and one batch source, ODS as system of record for the UI, Power BI access to the ODS schema, Enterprise Borrower View over the pilot population, and full data quality and lineage end to end [S-2026-05-13-paul-clm-pilot-plan].

Current state

  • High-level activity list: 13 workstreams, 63 sub-activities [S-2026-05-13-paul-clm-pilot-plan].
  • Workbook saved as CLM_Pilot_Delivery_Plan.xlsx and .md in C:\Users\pgmil\OneDrive\Documents\_ClaudeWorkspace\03 Credit Lifecycle.

Workstreams captured:

  • WS1 Mobilisation & Governance — pilot mandate and success criteria, named user cohort, governance interlock with CLM Design Sub-Committee / DQ Forum / Steering Committee, integrated pilot plan, RAID log, reporting cadence, stakeholder comms.
  • WS2 Scope, Requirements & Use Cases — covenants and valuations user-story maps, alerts and events catalogue, borrower-level CDE metric definitions, testable acceptance criteria mapped to OKRs and SREP items, parallel-run design.
  • WS3 Data Architecture & ODS Design — extends ODS canonical model for covenant / valuation / borrower entities, confirms golden-source systems with signed data-supply contracts and DQ SLAs, aligns to Enterprise Customer Hierarchy / LEIs / Tier Matrix reference data, end-to-end lineage documented in data catalogue, ADRs for Design Sub-Committee approval.
  • WS9 Power BI / Reporting — role-based access pattern with row-level security, curated semantic model / Power BI dataset, pilot dashboards for covenants / valuations / DQ KPIs, auditable user-access approval trail.
  • WS13 Exit Criteria, Lessons Learned & Scale Decision — exit-criteria scorecard, lessons-learned workshop, scale-up recommendation paper, refreshed R1 build backlog, pilot closeout report and BAU governance handover.

Decisions made

  • 2026-05-13 — Pilot design fixed at parallel-run with existing process; CLM UI with small alerts / events catalogue; threshold-driven borrower-level metrics; ODS as system of record; one near-real-time + one batch source; Power BI consumption pattern; full data quality and lineage end to end [S-2026-05-13-paul-clm-pilot-plan].

Open questions / blockers

  • 2026-08-07 (weekly briefing) — the gap persists and the timing now sharpens it: this week shipped practice-build tooling (Business Glossary Reader v0.3, the DG explainer video) but still no CLM Pilot engagement capture, even though the CLMP DG & DQ delivery plan scheduled closeout and handover for 27–31 Jul — a window that has now passed with no closeout or handover note in the capture stream. Action: capture the Pilot / engagement closeout explicitly, doubling as structured audit-hour evidence toward the ISO 42001 Lead Auditor 300-hour requirement [S-2026-08-07-weekly-briefing].
  • Which named cohort of RMs and credit analysts will form the pilot user base.
  • Whether parallel-run divergence handling will require process changes downstream of the pilot.
  • Acceptance criteria mapped to OKRs and SREP items need to be confirmed with Steering / Design Sub-Committee.
  • 2026-07-31 (weekly briefing) — gap partly self-corrected, but only on tooling: CLM/taxonomy work returned as the single largest own-work cluster this week (Dashboard v3→v4, Taxonomy Knowledge Tool architecture, Ringer swarm) — yet still no CLM Pilot execution or client-engagement capture. The paying Pilot itself (delivery, cohort, stakeholders) remains absent from the capture stream while its surrounding tooling is richly documented. Action: one deliberate Pilot status/stakeholder note next week, doubling as structured audit-hour evidence toward the ISO 42001 Lead Auditor 300-hour requirement [S-2026-07-31-weekly-briefing].
  • 2026-07-24 (weekly briefing) — standing gap widened: CLM captures fell to zero this week — not only no pilot execution notes, but no CLM Transformation or glossary/taxonomy captures at all, a sharp reversal from the June/early-July glossary surge. The week’s capture stream was entirely practice-build, credential and vendor scanning. A single deliberate capture of live pilot progress would keep the paying engagement visible in the weekly synthesis [S-2026-07-24-weekly-briefing].
  • 2026-07-10 (weekly briefing) — standing gap: no pilot execution captures have appeared for a fourth consecutive week; the recent CLM delivery surge has been entirely glossary/taxonomy advisory. Framed as an opportunity — a single deliberate capture of live pilot progress (mobilisation, cohort selection, or a WS-level step) would restore this project’s presence in the weekly synthesis and give the “delivery-light” gap a concrete counter-signal [S-2026-07-10-weekly-briefing].
  • 2026-06-05 (weekly briefing) — corpus gap: no CLM Pilot or CLM Transformation status capture has been made for a second consecutive week (also flagged 29 May); a deliberate status note is outstanding so the largest active engagement is not under-represented in the knowledge base [S-2026-06-05-weekly-briefing].

Connected wiki pages

History

  • 2026-05-13 — 13-workstream delivery plan created.

Sources / notes

  • [

Graph View

Backlinks

Recently updated

See 113 more →