Project Charter Template WORD Pmi

Standard Operating Procedure: Project Charter Standardization

Document ID: SOP-TR-PMO-001
Effective Date: October 26, 2023
Version: 1.2.0
Review Cadence: Annual

1. Executive Summary & Purpose

This SOP dictates the standardized workflow for generating, vetting, and archiving a Project Charter based on Project Management Institute (PMI) standards. The purpose is to establish formal project authorization, define high-level boundaries, and secure executive sponsorship to ensure organizational alignment and resource allocation.

2. Scope & Prerequisites

• Scope: All projects initiated under the Template Registry governance framework.
• Required Tools: MS Word (v.2019+), Microsoft SharePoint/Teams (Version Control), Adobe Acrobat (for sign-off).
• Prerequisites: Completed Business Case, identified Project Sponsor, and preliminary budget estimate.
• PPE: N/A (Digital environment).

3. Roles & Responsibilities (RACI Matrix)

4. Step-by-Step Procedure

Phase I: Preparation & Data Gathering

• Retrieve the official TR_PMI_Charter_Template.docx from the Global Repository.
• Secure Business Case documentation for reference.
• Schedule a scoping session with the identified Project Sponsor.

Phase II: Drafting the Charter

• Define Purpose: Draft the high-level business need and strategic alignment.
• Establish Objectives: Define SMART (Specific, Measurable, Achievable, Relevant, Time-bound) goals.
• Outline Scope: Document in-scope deliverables and explicitly state out-of-scope exclusions.
• Identify Stakeholders: Populate the preliminary stakeholder register.
• Define Constraints & Assumptions: List known dependencies and external risk factors.

Phase III: Review & Sign-Off

• Perform a peer review against the PMI PMBOK standard.
• Submit draft to Sponsor for markup and revision.
• Secure electronic signature (DocuSign/Adobe Sign) from the Sponsor.
• Archive the finalized version in the designated SharePoint library.

5. Quality Assurance & Pro-Tips

Best Practices

• The "So What" Test: If an objective doesn't directly map to a business value, strike it.
• Granularity: Do not include a Work Breakdown Structure (WBS) in the charter; save that for the Project Management Plan.
• Living Document: While the Charter is the "constitution," treat the Assumption Log as a dynamic document throughout the project lifecycle.

Common Pitfalls

• Scope Creep: Failing to explicitly list what is not included.
• Ambiguous Authority: Not clearly defining the Project Manager’s decision-making limits within the charter.

Metric Thresholds

• Approval Time: Standard approval cycle must not exceed 5 business days.
• Alignment Score: 100% of charter objectives must map to at least one organizational strategy pillar.

6. Frequently Asked Questions

Q: Does the charter need to be updated if the budget changes by 5%?
A: No. Minor variances are managed via the Change Control Board (CCB). The Charter only requires formal re-approval if the project scope, timeline, or strategic objective undergoes a fundamental shift.

Q: Can I modify the Microsoft Word template formatting?
A: Style headers and brand identity markers must remain static to ensure compliance. You may add appendices for technical requirements, but the core PMI fields are non-negotiable.

Authorized By:
Julian Vance
Chief Architect, Template Registry