Redstrata Knowledge Base

Paul Miles — CLM Taxonomy Governance Dashboard (Interactive Wireframe)

3 min read

Paul Miles — CLM Taxonomy Governance Dashboard (Interactive Wireframe)

Tag: S-2026-07-04-paul-clm-taxonomy-dashboard Type: own-writing Author(s): Paul Miles (Red Strata), with AI agent Date of source: 2026-07-04 Date ingested: 2026-07-04 Authority weight: own-writing. Raw file: /_raw_sources/S-2026-07-04-paul-clm-taxonomy-dashboard.md (Proposed vs Actual Solution record); deliverables at _ClaudeWorkspace/11 CLM Taxonomy Dashboard/.

What it claims

An interactive dashboard and UI wireframe for Financial Services organisations to manage and govern their CLM data taxonomy, built to sell the concept to Business Data Owners, Business Users and Credit Risk teams. Design decisions (approved by Paul 2026-07-04):

  • Single-file HTML wireframe (CLM_Taxonomy_Dashboard.html, no external dependencies), Teams-native light (Fluent-style) styling chosen over the Midnight Executive navy palette. The same file is the Teams-publishable artefact: hosted in SharePoint next to the Excel source and pinned as a Teams channel tab.
  • Seed data is the 201-term CLM Industry Business Glossary (Excel, T-06 column model) converted to embedded JSON — glossary content is real industry-reference material; workflow status, owners, versions, dates, DQ results and lineage examples are illustrative demo overlays, flagged by an in-UI banner.
  • Views: Home dashboard (KPIs, stage progress across 18 lifecycle stages, completeness heatmap mirroring the Completeness Scorecard); Business Glossary browser (search, stage/category/tier/status/asset-class filters, term detail drawer with governance block, CSV export); Governance & Workflow (6-step Harvest → Draft → SME Review → Owner Approval → Publish → Change control flow mirroring the Confluence + Comala pattern; ownership register; pending-approvals queue); Regulator Evidence (coverage by regulatory family across 16 anchored regulations, approvals log, working CSV evidence-pack export); roadmap tabs for Metadata / Lineage / Data Quality badged as wireframe extensions; persona toggle (Business Data Owner / Business User / Credit Risk).
  • Glossary-first, taxonomy-next: the priority use of the data glossary comes first; metadata, attribute-level lineage (ECB RDARR framing) and DQ are shown as roadmap extensions attaching to approved terms.
  • Production path (diagrammed in CLM_Taxonomy_Dashboard_DataFlow.svg, not built): scripted Excel→JSON publish per approved baseline or Power Automate / Graph API refresh; full product path per the Taxonomy Knowledge Tool HLD v0.2 thin-portal + federation model — the wireframe is the front-of-house demonstration of that portal.
  • Industry UI patterns emulated from Collibra / Alation / Purview / Atlan: glossary browse + stewardship, workflow status, ownership registers, audit/evidence views.

Notable quotes

None — own-writing.

What’s speculative vs. asserted

  • Asserted (sourced): the delivered file set and capabilities; the 201-term / 16-regulation seed content; the approved design options (full glossary seed; Teams-native light styling); the Confluence + Comala workflow mirroring; the SharePoint + Teams-tab publishing route.
  • Speculative / presentation device: all governance overlay data (statuses, owners, versions, dates, approval trails), DQ results and the PD lineage example are illustrative demo data; the completeness heatmap percentages are indicative; approval write-back and PDF evidence pack are stubs. The production refresh options are design intentions, not implementations.

Topics this feeds

Open questions raised

  • Whether the first client demo should read the Excel live via Microsoft Graph or keep the scripted publish-per-baseline step.
  • Whether the persona views should become role-based access (RBAC) in the production portal rather than a toggle.
  • Which client branding/palette to apply when the wireframe is shown beyond internal use.

Graph View

Backlinks

Recently updated

See 113 more →