Project Charter Document Prepared At

Standard Operating Procedure: Project Charter Preparation

Template Registry Engineering Standards

1. Document Control Block

2. Executive Summary & Purpose

The purpose of this SOP is to standardize the formal initiation of all internal and client-facing projects. A Project Charter acts as the primary governing document, granting the Project Manager (PM) the authority to utilize organizational resources. Compliance with this process ensures alignment between project objectives and corporate strategy, mitigates scope creep, and establishes baseline KPIs.

3. Scope & Prerequisites

• Scope: Applies to all projects with a budget exceeding $50k or a duration exceeding 30 business days.
• Prerequisites:
  • Approved Project Request Form (PRF-01).
  • Access to the Template Registry Enterprise Project Management (EPM) Suite.
  • Access to the centralized Document Repository (SharePoint/Confluence).
  • Required Stakeholder Matrix (identified via CRM data).

4. Roles & Responsibilities (RACI)

5. Step-by-Step Procedure

Phase 1: Contextualization

• Verify PRF-01 approval status.
• Conduct initial Stakeholder Interviews to determine critical success factors.
• Define high-level project objectives (SMART criteria).

Phase 2: Documentation Drafting

• Populate Template Registry Charter Template (TR-TMP-CH).
• Define scope boundaries (In-Scope vs. Out-of-Scope).
• Identify top 5 primary risks and associated mitigation strategies (Risk Register).
• Define high-level budget allocations and resource requirements.

Phase 3: Review & Authorization

• Circulate draft for technical review by the Engineering Lead.
• Update document based on feedback loop.
• Obtain digital signatures from the Project Sponsor and Portfolio Manager.
• Upload final document to the Master Registry and trigger "Project Active" status in the EPM.

6. Quality Assurance & Pro-Tips

• Metric Thresholds:
  • Charter approval to project kick-off cycle time: < 72 hours.
  • Scope variance at completion: < 5%.
• Pro-Tips:
  • The Rule of Three: If you cannot define the project's purpose in three sentences or less, the project is not sufficiently defined.
  • Constraint Prioritization: Always force a decision between Cost, Time, and Quality during the chartering phase. You cannot optimize all three simultaneously.
• Common Pitfalls:
  • Failing to define "Out-of-Scope" items explicitly, leading to uncontrolled feature creep.
  • Inadequate identification of secondary stakeholders (e.g., Compliance, Legal).

7. Frequently Asked Questions

Q: What if the Project Sponsor refuses to sign the charter? A: Do not initiate project activities. The charter is your authority to spend. Without a signature, the PM lacks legal and financial protection to utilize organizational resources. Escalate to the PMO Steering Committee.

Q: Can the charter be modified after the project has started? A: The charter is a static document. If scope changes fundamentally alter the original objectives, a "Charter Amendment" must be drafted, reviewed, and signed by the original signatories.