Simple Project Charter Example

SOP-PM-001: Project Charter Initialization

Document Control Block

1. Executive Summary & Purpose

This procedure defines the institutional standard for drafting a Project Charter. The purpose is to provide a unified framework for project authorization, formalizing the project’s existence, objectives, and high-level resource constraints to ensure alignment with organizational strategic goals.

2. Scope & Prerequisites

• Scope: All internal projects exceeding 40 man-hours or requiring cross-departmental resource allocation.
• Prerequisites:
  • Defined Business Case (pre-approved).
  • Access to Project Management Information System (PMIS) (e.g., Jira, Asana, or internal Template Registry portal).
  • Required software: PDF export/digital signature capability.
  • No physical PPE required; environmental setting is standard digital office.

3. Roles & Responsibilities (RACI Matrix)

4. Step-by-Step Procedure

Phase I: Charter Drafting

• Define high-level project objectives (SMART criteria).
• List key stakeholders and define preliminary constraints (budget, timeline, scope).
• Identify high-level risks and mitigation strategies.
• Populate the "Template Registry Charter Template" (v.current).

Phase II: Review & Validation

• Submit draft to assigned Project Sponsor for initial review.
• Incorporate feedback from Dept. Leads regarding resource availability.
• Verify alignment with current fiscal year KPIs.

Phase III: Final Approval & Sign-off

• Secure formal digital signature from the Project Sponsor.
• Archive the signed Charter in the central document repository.
• Notify relevant departments of project kick-off.

5. Quality Assurance & Pro-Tips

• Quality Metrics: A Charter is considered "Validated" only if it passes the Vance Triple Check:
  1. Objective is time-bound.
  2. Budget variance limit is defined (<10%).
  3. Success criteria are measurable.
• Pro-Tip: Never skip the "Out of Scope" section. Clearly defining what the project will not do is the primary defense against scope creep.
• Common Pitfall: Drafting a Charter that is too granular. Keep it high-level; the Charter is a directive, not a technical specification.

6. Frequently Asked Questions

Q: At what stage is the Charter considered "live"? A: The Charter is active the moment it is digitally signed by the Sponsor and recorded in the Registry metadata.

Q: Can a Charter be modified after approval? A: Only via a formal Change Request (CR) process. Minor editorial changes do not require a new Charter, but material changes to scope or budget require a re-signatory event.

Q: What if I don't have a formal Project Sponsor yet? A: You are in the pre-project phase. Secure a Sponsor before proceeding. Projects without an accountable Sponsor at the leadership level are unauthorized and should not be documented in the Registry.

Authorized by: Julian Vance, Chief Architect, Template Registry