Project Charter Template WORD Doc

Standard Operating Procedure: Project Charter Generation

Template Registry Engineering Standards

---

1. Document Control Block

---

2. Executive Summary & Purpose

This procedure defines the standardized workflow for generating, populating, and versioning a Project Charter. The purpose is to ensure institutional alignment, secure executive sponsorship, and establish fixed project boundaries before resource allocation.

---

3. Scope & Prerequisites

• Scope: Applies to all projects within the Template Registry ecosystem.
• Software Requirements: Microsoft Word 365 or Word 2021+ (utilizing .docx format), SharePoint/OneDrive for version history, or enterprise-grade document management system (DMS).
• Prerequisites: Completed "Project Intake Form," defined Business Case, and identified Executive Sponsor.

---

4. Roles & Responsibilities (RACI)

---

5. Step-by-Step Procedure

Phase 1: Initiation and Setup

• Retrieve official template from the Registry Central Repository (/templates/pm/charter_v1.docx).
• Save document using standard nomenclature: YYYYMMDD_ProjectName_Charter_v1.docx.
• Confirm file properties include correct Author and Project Title metadata.

Phase 2: Content Population

• Define Executive Summary: Write a 150-word synthesis of project intent and expected ROI.
• Identify Scope Constraints: Document explicit exclusions (Out-of-Scope) to prevent scope creep.
• Define Success Metrics: Align on at least three Key Performance Indicators (KPIs) with baseline targets.
• Establish Milestone Roadmap: Populate high-level dates (Phase Gates).

Phase 3: Review and Approval

• Perform a peer review against the "Quality Assurance Checklist" (Section 6).
• Submit draft to Executive Sponsor for digital signature.
• Archive signed PDF version to the secure document repository.

---

6. Quality Assurance & Pro-Tips

• Metric Thresholds: Any project charter without a clearly defined "Success Metric" must be rejected by the Project Management Office (PMO).
• Pro-Tip (Version Control): Never use "Final_v2_RealFinal.docx." Use consistent semantic versioning (v1, v2, v3) in the filename.
• Common Pitfall: Failing to define "Out-of-Scope" items. This is the primary driver of project failure; if it is not written down, assume the stakeholder will ask for it mid-cycle.

---

7. Frequently Asked Questions

Q: Can I deviate from the template structure? A: No. Deviation requires formal request via an Engineering Change Order (ECO). The structure is designed for programmatic parsing by our portfolio dashboard tools.

Q: How do I handle missing financial data during the drafting phase? A: Use "TBD" with an attached footnote defining the expected date of data availability. Do not delay charter submission for missing non-critical metrics if the business case is otherwise sound.

---

Authorized by: Julian Vance Chief Architect, Template Registry