Project Charter Document Prepared at Which Level

Standard Operating Procedure: Project Charter Hierarchical Positioning

Document ID: TR-SOP-PM-004
Effective Date: 2023-10-27
Version: 1.0.0
Review Cadence: Biennial

---

1. Executive Summary & Purpose

This SOP defines the institutional standard for the hierarchical level at which a Project Charter must be authored, reviewed, and authorized. The objective is to ensure alignment between strategic intent and operational execution, preventing "scope creep" and ensuring fiscal accountability at the appropriate organizational altitude.

---

2. Scope & Prerequisites

Scope: Applicable to all projects managed under the Template Registry governance framework.
Prerequisites:

• Software: Project Portfolio Management (PPM) Suite (e.g., Jira, Asana, or Clarity).
• Documentation: Strategic Business Case (pre-cursor).
• Access: Read/Write permissions to the Enterprise Project Management Office (EPMO) directory.

---

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Procedure: Charter Authorization Levels

Project Charters are prepared at the Executive/Sponsorship Level, but managed at the Operational Level.

Phase I: Hierarchical Determination

• Assess total project budget against the Capital Expenditure (CapEx) threshold.
• Determine the project's impact: Strategic (Enterprise-wide) vs. Tactical (Department-specific).
• Map the project to the relevant governance body (Steering Committee vs. Departmental Lead).

Phase II: Drafting and Alignment

• Drafting: PM prepares the technical specs and resource estimates.
• Alignment: Sponsor reviews against the current fiscal year (FY) strategic roadmap.
• Formalization: Charter is locked at the level of the primary funding source owner.

Phase III: Execution and Sign-off

• Route document via digital signature workflow.
• Notify all "Informed" stakeholders upon final execution.
• Archive the charter in the EPMO centralized registry.

---

5. Quality Assurance & Pro-Tips

• Metric Thresholds:
  • Low Impact (<$50k): Charter authorized at the Department Head level.
  • High Impact (>$50k): Charter authorized at the C-Suite or VP level.
• Pro-Tip: Never attempt to gain signature approval from a stakeholder below the level of the budget holder. It is a fundamental error that will result in immediate audit failure.
• Common Pitfall: Drafting a charter before securing a sign-off on the underlying Business Case. The Charter is the contract, the Business Case is the justification.

---

6. Frequently Asked Questions

Q: Can a Charter be prepared by a Project Manager if the Sponsor is unavailable? A: No. The Project Manager acts as the scribe, but the content and authorization must reside with the Project Sponsor to ensure ownership of the business objectives.

Q: At what point is a Charter considered "officially active"? A: A Charter is active only after it has been signed by the designated Accountable party (Sponsor) and uploaded to the centralized project registry with a unique project ID.

Q: Does every project require a formal Charter? A: Yes. Regardless of scale, the absence of a Charter indicates a lack of definition, which leads to uncontrolled resource consumption.

---

End of Document
Authorized by: Julian Vance, Chief Architect