Paul Miles — Master Glossary Change Request Process (T-07 form & T-08 register)

Tag: S-2026-07-10-paul-glossary-cr-process Type: own-writing Author(s): AI agent (Claude, Cowork) for Paul / Red Strata Date of source: 2026-07-10 Date ingested: 2026-07-10 Authority weight: medium — an operational process record derived strictly from the governed Build Kit v1.2 Stage 7 artefacts (P-07, change-governance.md, Squad Operating Procedures §11/§12/§13, T-06) plus the squad fast-track governance SLAs; it packages existing controls into an intake layer rather than creating new rules. The ≤2-working-day triage SLA and the T-07/T-08 numbering are new proposals pending squad confirmation. Raw file: S-2026-07-10-paul-glossary-cr-process.md

What it claims

Records the delivery of the Master Glossary Change Request process (2026-07-10), a user-facing intake and tracking layer over Build Kit Stage 7 answering Paul’s brief for a very simple CR process covering additions, changes, retirements and other cases for one or many terms, with minimal requester input and Excel-list attachment for bulk.

Deliverables (all in 09 Taxonomy Tool\Glossary CR Process\): a 3-slide B&W process deck + md record (Glossary_Change_Request_Process.pptx/.md), T-07 Change Request Form (requester-facing Excel: Guide, CR Form with yellow input cells / dropdowns / worked example, Lists) and T-08 Change Request Register (squad-side 22-column log with About sheet and a formula-driven status summary, recalc-verified), plus an approach & work-breakdown record.

Process shape: five steps — Raise (requester, T-07) → Log & triage (Data Steward, ≤2 working days, CR-nnn in T-08) → Assess & draft (DS + AI under P-07 to the definition-quality.md / source-authority.md standards; manual fallback M-07) → Decide (SME / Definition Owner at the squad’s existing 3–5-working-day fast-track SLA; + Regulatory/Risk SME for regulatory-tagged terms; disputes to the standing fortnightly CLM Design Sub-Committee slot) → Apply & close (T-06 Entry Version +1, Change Request Ref linked, prior values preserved, rolled into the next baseline with a delta report). CR statuses: Submitted → Triaged → In Assessment → Awaiting Decision → Approved / Rejected → Applied & Closed.

Minimal-input design: four required fields per term (Change Type Add/Change/Retire/Other · Term Name · Proposed Definition / Change · Reason); Term ID/BCK, source reference, superseding term and notes optional. Single and bulk share one Change-List sheet (one row per term), or the requester attaches their own Excel list with at least the four minimum columns. Squad-side data (CR IDs, impact, approvals, versions, baselines) deliberately kept off the user form.

Routing rule of note: a large set of NEW terms backed by source documents is re-routed at triage as an incremental source batch through Stages 1–5 under GR-14, not term-by-term CRs; bulk changes/retirements are processed as one Bulk CR under GR-BA review discipline (100% of reg/policy-tagged rows; ≥10% sample of uniform low-risk rows).

Controls: no new roles, forums, statuses (on T-06) or tooling; reuses GR-01 (humans approve), GR-11 (never delete — retire with history), GR-12 (version stamps), GR-13 (source authority), GR-BA, GR-14 and the change-governance.md escalation triggers.

Notable quotes

“The gap was user intake and tracking; minimal fields maximise adoption.” (Approach record, §3.)

What’s speculative vs. asserted

• Asserted (grounded in kit artefacts): Stage 7 already defines CR handling (P-07 tasks, CR-nnn, baseline/delta model, escalation triggers); T-06 carries Change Request Ref / Entry Version / Baseline Version fields; the 3–5-working-day approval SLA and fortnightly committee slot are the squad’s existing fast-track governance; GR-14 incremental batching is the kit’s own design for new-term waves.
• Speculative / proposals pending squad confirmation: the ≤2-working-day triage SLA; the T-07/T-08 template numbering (could clash if the master kit later mints its own); the “squad mailbox / SharePoint CR folder” submission channel (placeholder); the six CR tracking statuses (T-08-internal only).

Topics this feeds

• CLM Glossary Acceleration Squad — supplies the Stage 7 CR intake form, register and user-facing process the squad operates post-baseline.

Open questions raised

• Confirmation of the actual submission channel (squad mailbox vs SharePoint CR folder) and the triage SLA.
• Whether T-07/T-08 are adopted into the master kit’s templates folder (and the MS365 Copilot edition regenerated to match) or remain a sibling Glossary CR Process\ folder.