Project Charter Template Slide

SOP: Project Charter Slide Development (TR-STD-042)

1. Executive Summary & Purpose

This procedure defines the standardized production of the "Project Charter Slide"—a single-page executive summary designed to align stakeholders, define scope, and secure resource allocation. The objective is to distill complex project intent into a high-signal, zero-latency visual artifact.

2. Scope & Prerequisites

• Scope: Applicable to all internal and client-facing projects managed within Template Registry.
• Prerequisites:
  • Approved Project Business Case.
  • Access to the Standardized Corporate Slide Library.
  • Required Software: Microsoft PowerPoint (v.365) or Google Slides (Template Registry Master Theme).
  • Hardware: Enterprise-grade workstation with dual-monitor configuration recommended.

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase 1: Data Synthesis

• Collate the project title, budget ceiling, and top-level timeline.
• Identify three (3) critical success factors (CSFs) using SMART criteria.
• List primary stakeholders and their specific influence/interest levels.

Phase 2: Slide Architecture

• Apply the Template Registry Master Theme (16:9 aspect ratio).
• Ensure the Header contains: Project Name, Sponsor, and Status (e.g., Green/Yellow/Red).
• Populate the Core Quadrants:
  • Top-Left: Problem Statement (The "Why").
  • Top-Right: Objective/Scope (The "What").
  • Bottom-Left: Key Milestones/Timeline (The "When").
  • Bottom-Right: Resource/Budget (The "How").

Phase 3: Review & Finalization

• Conduct a peer review against the 10-point readability check (font size >12pt, contrast ratio >4.5:1).
• Obtain Sponsor sign-off via digital signature.
• Export as "Final_Charter_[YYYY-MM-DD].pdf" and archive in the Registry repository.

5. Quality Assurance & Pro-Tips

• The 5-Second Rule: If a stakeholder cannot discern the project’s goal within 5 seconds of scanning the slide, the copy is too dense.
• Metric Thresholds: Budget variance must be documented if >5%; schedule variance must be documented if >10%.
• Pro-Tip: Use a "RAG" (Red-Amber-Green) indicator for status, but avoid using red text for project success criteria to prevent psychological bias toward "negative" indicators.
• Common Pitfall: Over-populating the "Scope" section with task lists rather than strategic outcomes. Keep it outcome-focused.

6. Frequently Asked Questions (FAQ)

Q: Should I include risk management details on the charter slide? A: Only include top-tier, show-stopper risks (High Impact/High Probability). Minor risks belong in the Project Management Plan (PMP), not the high-level charter.

Q: How should I handle overflow content? A: Never shrink font size below 12pt. If the content does not fit, it is a signal that the project scope is insufficiently defined or requires a secondary technical annex. Do not compromise the one-page constraint.

Q: Is it acceptable to use custom graphics? A: Only use official Template Registry iconography. Consistency reduces cognitive load for executives reviewing multiple projects.

End of Document Authorized by: Julian Vance, Chief Architect