Paul Miles — CLM Business Glossary Squad TOR, client-applied update
Tag: S-2026-07-12-paul-clm-glossary-squad-tor-client-update Type: own-writing Author(s): Paul Miles (Red Strata) — manual revision of the 2026-07-11 TOR Date of source: 2026-07-12 (document’s internal date line still reads 11 July 2026) Date ingested: 2026-07-12 Authority weight: high — Paul’s own record of how the TOR is actually being applied at the client; supersedes the planning-stage TOR Raw file: S-2026-07-12-paul-clm-glossary-squad-tor-client-update.md (markdown extraction of Paul’s uploaded .docx)
What it claims
The one-page CLM Business Glossary Squad Terms of Reference as applied for the client, retaining the three-section structure (Squad Objectives; Key scope items In/Out; Key considerations / dependencies) and the core design — single mastered glossary with Policy/Process/Regulatory metadata, Day 1 terms front-loaded, H2 2026 SREP commitment, 7-stage Build Kit process, fast-track governance with a 3–5 working-day SME SLA, T1–T6/D1–D8 authoring standards with C-QA, guardrails GR-01..GR-14 + GR-BA with no numeric auto-approval — with the following client-application changes vs the 2026-07-11 version:
- Escalation forum renamed throughout: the fortnightly CM Business Impact Forum replaces the CLM Design Sub-Committee slot (in-scope governance, out-of-scope fora list, governance dependency).
- SME availability assumption changed to ~5 days/week (was ~2 days/week); the re-baseline caveat sentence was removed from that bullet.
- Planning figures removed from objectives: no weeks-1–4 / ~5–6-week timings, no two-squad / ~6–7-core / per-week throughput numbers (scope remains ~500–1,000 terms); the 399-term reconciled baseline reference removed.
- Decisions pending now owned by the squad (not Paul/squad); first decision replaced by “finalise the scope of terms included based on bottom up assessment and SME input” (replacing adoption of the 399-term reconciled glossary); asset-class lead order dropped from the tier-split decision; the D9 “Source Anchored” decision removed.
- Publishing simplified to Excel → SharePoint — Confluence/Comala removed from the objective and the tooling out-of-scope bullet.
- Inconsistency sources generalised in objectives to “existing business glossary or data dictionary sources and Day 1 design” (Matrix and ODS remain named in the in-scope harvest sources).
- Regulatory alignment wording simplified to “regulatory requirements e.g. IRB” in the SREP objective (BCBS 239 attestation still listed in the out-of-scope fora).
- Header simplified: Squad A / Squad B split removed; programme titled “Credit Lifecycle Management (CLM)”; wording now “AI accelerates, squad members decide”; out-of-scope item generalised to “Glossary operating model”; prompt-portability risk qualified “for MS365 Copilot”.
Notable quotes
- “Decisions pending (squad): finalise the scope of terms included based on bottom up assessment and SME input” (§3, Decisions pending bullet)
- “the sizing model assumes Business Data SMEs at ~5 days/week” (§3, SME availability bullet)
What’s speculative vs. asserted
Asserted: the client-applied governance route (CM Business Impact Forum), scope boundaries, process, standards and controls. Planning-status: throughput and squad-count figures are explicitly retained as “planning estimates” pending the confirmed harvested term count; the ~500–1,000 term scope remains an estimate. The document does not state the reasons for the changes (e.g. why SME availability moved to ~5 days/week) — reasons are not recorded here.
Topics this feeds
- CLM Glossary Acceleration Squad — the project this TOR governs; this version supersedes the 2026-07-11 TOR as the operative framing.
Open questions raised
- The SME availability assumption (~5 days/week) differs materially from the ~2 days/week in the June 2026 squad sizing model [S-2026-06-01-paul-clm-glossary-squad]; whether the throughput/sizing model has been re-run on the new assumption is not stated.
- The 399-term reconciled-glossary adoption decision no longer appears; whether it is replaced by (or feeds into) the squad’s bottom-up scope assessment is not stated.
- The D9 “Source Anchored” decision was removed from the pending list; its status (adopted / dropped / deferred) is not stated.