Reusable governance objects

A forum is a decision mechanism, not a recurring meeting.

Each pattern below states the mandate, delegated scope and escalation boundary needed to keep governance fast and accountable. Adapt the pattern; do not copy a committee calendar without its authority model.

Monthly and event-driven

Cloud Steering Committee

Resolve enterprise priorities, investment constraints and material cross-domain escalations.

Chair: Technology executive or delegated cloud sponsor
Decision scope: Strategy, material investment, risk posture and unresolved escalations
Participants: Cloud Governance · Finance · Security · Business technology leadership
Escalation: Enterprise technology or executive committee
Watch for: Reviewing routine technical changes that belong to delegated authorities.

Fortnightly and event-driven

Cloud Design Authority

Decide material architecture deviations and evolve reusable technical patterns.

Chair: Lead Cloud Architect
Decision scope: Architecture patterns, exceptions, technical debt and design guardrails
Participants: Architecture · Security & Assurance · Platform Engineering · Operations
Escalation: Cloud Steering Committee for risk or investment decisions
Watch for: Becoming a mandatory review board for every low-risk engineering change.

Monthly

Cloud Service Portfolio Forum

Govern service admission, lifecycle, ownership, performance and retirement.

Chair: Cloud Service Portfolio Lead
Decision scope: Catalogue admission, service investment, lifecycle state and improvement priority
Participants: Service owners · Platform Engineering · Operations · Consumer representatives
Escalation: Cloud Steering Committee for investment conflicts
Watch for: Maintaining a catalogue without accountable service owners or usage evidence.

Monthly and triggered by material exceptions

Cloud Risk & Assurance Forum

Route control interpretation, evidence gaps, exceptions and risk acceptance to the right authority.

Chair: Cloud Security & Assurance Lead
Decision scope: Control interpretation, assurance priority and delegated exception decisions
Participants: Security · Risk · Privacy · Architecture · Cloud Governance
Escalation: Enterprise risk owner or formal risk-acceptance authority
Watch for: Letting the forum accept risk outside its formally delegated mandate.

Monthly

Cloud Economics Forum

Translate cost, usage and value signals into accountable optimization decisions.

Chair: FinOps Lead
Decision scope: Optimization commitments, allocation policy, anomaly escalation and forecast actions
Participants: Finance · Service owners · Engineering · Business product owners
Escalation: Cloud Steering Committee for investment or business-priority conflicts
Watch for: Publishing cost reports without named decision owners or follow-through.

Event-driven

Operational Readiness Review

Confirm that a new or changed service can enter operations with explicit acceptance.

Chair: Service Transition Lead
Decision scope: Readiness acceptance, conditions, deferred debt and launch escalation
Participants: Platform Engineering · Cloud Operations · Service Management · Security
Escalation: Service owner, then Cloud Steering Committee for unresolved material risk
Watch for: Treating document delivery as operational acceptance without evidence.

Link forums to governed decisions.

Create reusable forum objects once, then assign decisions by identifier so cadence, chair and escalation cannot drift across diagrams.

Open the forum map