Project Charter Template Example

Standard Operating Procedure: Project Charter Initiation

Document ID: SOP-PM-001
Effective Date: 2023-10-27
Version: 1.0.4
Review Cadence: Annual

---

1. Executive Summary & Purpose

This procedure mandates the uniform development and authorization of a Project Charter. The purpose is to provide a formal document that authorizes the existence of a project, defines its strategic alignment, establishes boundaries, and grants the Project Manager authority to deploy organizational resources.

2. Scope & Prerequisites

• Scope: Applicable to all capital projects, cross-departmental initiatives, and process engineering tasks.
• Software Requirements: Template Registry Charter Template (.docx), Confluence/Jira Project Space.
• Prerequisites: Completed Project Request Form (PRF) and documented Business Case/Feasibility Study.
• PPE/Physical Tools: N/A (Digital documentation environment).

3. Roles & Responsibilities (RACI)

---

4. Step-by-Step Procedure

Phase I: Preparation

• Verify the Business Case is signed off by Finance.
• Identify and interview key stakeholders to confirm operational constraints.
• Establish "SMART" objectives (Specific, Measurable, Achievable, Relevant, Time-bound).

Phase II: Drafting

• Define the Problem Statement: Explicitly state the gap between the current and future state.
• Define Scope Boundaries: Enumerate "In-Scope" vs. "Out-of-Scope" items to prevent scope creep.
• Develop the Milestone Schedule: Identify critical path milestones (High-level).
• Define Success Metrics: List KPIs (e.g., ROI target, timeline reduction, quality benchmarks).

Phase III: Validation & Authorization

• Conduct a peer review with the Project Management Office (PMO).
• Submit for final approval to the Project Sponsor.
• Archive the signed Charter in the central Registry and notify the Stakeholder register.

---

5. Quality Assurance & Pro-Tips

Best Practices

• The 80/20 Rule: 80% of project failure is caused by ambiguous scope. Spend 80% of your effort in the "Out-of-Scope" section of the charter.
• Living Documents: A charter is not a static tombstone; revise it only if the project’s fundamental strategic alignment shifts.

Common Pitfalls

• Lack of Sponsor Engagement: If the sponsor doesn't sign, the project has no authority. Do not commence without a wet or digital signature.
• Gold Plating: Ensure objectives are tied strictly to business value; avoid unnecessary complexity.

Metric Thresholds

• Time-to-Approve: Goal is <10 business days from draft submission to signature.
• Scope Accuracy: Variance between original Charter scope and Closeout scope should be <15%.

---

6. Frequently Asked Questions (FAQ)

Q: At what point do I stop drafting and start executing?
A: Execution begins only after the Project Sponsor provides formal signature. Commencement prior to this constitutes an unauthorized project.

Q: What if stakeholders disagree on the scope?
A: Escalate to the Steering Committee immediately. The Charter is the arbiter of scope; if agreement cannot be reached at the PM level, the project is technically unfeasible.

Q: Is the Budget Estimate in the charter binding?
A: The charter provides a "High-Level Order of Magnitude" (ROM) estimate (±25%). A detailed budget occurs during the Planning Phase, not the Initiation Phase.

---

Authorized by: Julian Vance, Chief Architect, Template Registry.