Design a change control board review agenda and rubric

Establish a fast, repeatable 30-minute Change Control Board agenda paired with an objective scoring rubric to approve or reject changes.

You get30-Minute Agenda Structure, CCB Evaluation Rubric and decision Thresholds and Rules

Prompt

Prompt
Act as a governance specialist for enterprise project management. Design a structured Change Control Board (CCB) meeting agenda and a quantitative review rubric to assess project scope, schedule, or budget change requests.

Rules:
- Structure the agenda for an efficient 30-minute meeting window.
- Design a scoring rubric with measurable thresholds for impact, risk, and urgency.
- Include explicit decision rules: automatic rejection criteria and clear approval thresholds.
- Focus on cross-functional alignment across schedule, cost, resources, and technical debt.

Output format:
- 30-Minute Agenda Structure (timed blocks, presenter role, and objective)
- CCB Evaluation Rubric (scoring table with dimensions: Dimension, 1 Point Low, 2 Points Medium, 3 Points High)
- Decision Thresholds and Rules (numeric thresholds for Pass, Review, or Reject, plus 3 immediate veto rules)

Example output

30-Minute Agenda Structure

  • 00:00 - 05:00 | PMO Lead: Review previous action items and confirm quorum.
  • 05:00 - 15:00 | Change Request Owner: Present change request, justification, cost, and schedule impacts.
  • 15:00 - 25:00 | Board Members: Cross-functional Q&A and rubric scoring on technical and commercial impact.
  • 25:00 - 30:00 | CCB Chair: Tabulate score, record formal decision, and assign action owners.

CCB Evaluation Rubric

Dimension1 Point (Low Impact)2 Points (Medium Impact)3 Points (High Impact)
Schedule ImpactDelays milestone by < 3 business daysDelays milestone by 4 to 10 days; critical path unchangedShiffs critical path or impacts contractual delivery date
Financial CostAbsorbed by contingency (< $5,000)Requires contingency allocation ($5,000 - $25,000)Requires executive budget expansion (> $25,000)
Resource DemandSolved with existing assigned team hoursRequires temporary resource reallocation across teamsRequires external vendor hiring or full-time staffing shifts
Operational RiskNo impact to core systems or securityMinor regression testing required across secondary systemsAlters core data schemas, compliance postures, or customer UX

Decision Thresholds and Rules

  • 4 to 6 Points: Fast-track approval by PMO lead.
  • 7 to 9 Points: Standard CCB majority vote approval.
  • 10 to 12 Points: Escalation required to Executive Steering Committee.

Immediate Veto Rules:

  • Request adds unbudgeted external software license costs without approved vendor procurement.
  • Request extends customer-facing go-live past agreed contractual freeze date.
  • Request introduces unresolved high-risk data privacy or security vulnerabilities.
Written by AI from this prompt. Your results will vary.

Use this prompt as-is in ChatGPT, Claude, or Gemini to build your CCB operating charter. You can follow up by pasting an actual project change request to see how the rubric scores it.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Project Management
Project Management

Audit a RACI chart for split accountability

Identify dangerous governance flaws, duplicate owners, and delivery bottlenecks in an existing RACI matrix. Use this before launching high-stakes projects.

Project Management

Build a RACI matrix from deliverables

Assign clear operational roles across all major project workstreams. Use to eliminate delivery confusion and establish single-point task accountability.