Governance program launch SOP

Purpose

Stand up a governance body — a software governance council, an ITAM steering group, or an AI governance board — that makes real, enforceable decisions from its first meeting, instead of becoming a rubber stamp or a bottleneck nobody trusts.

Scope

Applies whenever a new governance body is proposed, and whenever an existing one is relaunched because its charter, membership, or decision rights no longer match how decisions actually get made.

Roles

• Sponsor — the executive who controls the relevant budget, is accountable for the program, and signs the charter. No sponsor means no enforcement.
• Chair — runs meetings, owns the standing agenda, and is the tie-break of last resort below the sponsor.
• Secretary / triage owner — screens intake against the thresholds, keeps the decision log, and confirms actions from prior meetings are closed before the next one.
• Voting members — the 5 to 9 people who decide on items that reach the body, drawn from the functions the charter names.
• Consulted members — non-voting roles whose input is sought on relevant items but who do not hold a vote.

Frequency

Monthly meetings. The charter, membership, and decision rights are reviewed yearly, or immediately if the body starts rubber-stamping items or items start bypassing it.

Steps

1. Agree the problem statement in one sentence: what goes wrong today without this body XW-003
2. Name an executive sponsor with budget authority XW-027
3. Write down decision rights and the thresholds that route an item to the body versus a named role XW-027
4. Name 5 to 9 voting members, drawn from the functions the charter's scope requires XW-004
5. Put an intake form and a named triage owner live, so only exceptions and above-threshold items reach the meeting XW-027
6. Agree procurement enforcement, and settle any overlap with adjacent bodies (for example an architecture or change board) in writing XW-027
7. Set the cadence, standing agenda, and decision log XW-025
8. Write down the escalation and tie-break path XW-027
9. Define success measures and a baseline to measure them from XW-025
10. Get the charter approved by the sponsor and publish it XW-020
11. Hold the first metrics review at day 90 XW-025

Evidence to retain

• The approved charter, including decision rights, thresholds, and membership.
• The intake log and triage decisions.
• The meeting decision log, dated and tied to the standing agenda.
• The success-measure baseline and each subsequent metrics review.
• The sponsor's charter approval and any later re-approval.

Design the intake log, decision log, and metrics review so each is a direct by-product of running the body, not something rebuilt after the fact when an auditor or a new sponsor asks what it decided and why.

Related

• **Governance framework crosswalk** (crosswalk) — supplies the framework rows this program's charter and decision rights map to.
• **ITAM maturity check** (itam-maturity) — its governance area score depends on this program's charter, sponsor, and decision rights being in place.
• **Application rationalization** (rationalization) — brings its consolidate/retain/retire recommendations to this body for decisions above threshold.
• **AI system intake and risk tiering** (ai-intake) — routes high-risk and prohibited-practice findings to this body for the sponsor and legal decision it flags.
• **Access review pack** (access-review) — reports its exceptions to the sponsor and owner roles this program names.