Project Charter Template Microsoft

Standard Operating Procedure: Microsoft-Ecosystem Project Charter Deployment

Document ID: SOP-TR-PM-042
Effective Date: October 24, 2023
Version: 3.2.0
Review Cadence: Annual
Owner: Julian Vance, Chief Architect, Template Registry

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional engineering standard for instantiating, governing, and maintaining Project Charters within the Microsoft enterprise ecosystem (SharePoint, Teams, Word, and Planner). The objective is to eliminate drift in project initiation, enforce strict governance guardrails, and ensure cross-functional alignment by leveraging standardized Microsoft templates. Adherence to this SOP is mandatory for all project initialization sequences across Template Registry operations.

---

2. Scope & Prerequisites

2.1 Scope

This procedure applies to all internal and client-facing projects managed within the Template Registry portfolio. It covers the lifecycle from initial charter drafting to governance sign-off and repository archiving.

2.2 Prerequisites & Environment

• Software/Licensing: Microsoft 365 Enterprise E5/G5 license including SharePoint Online, Microsoft Teams, Word Online (v16.0+), and Planner.
• Access Rights: Project Manager (PM) permissions to the designated SharePoint Project Hub and Microsoft Teams workspace.
• Artifacts: Approved Template Registry Master Project Charter .dotx or SharePoint Modern Page template.
• PPE/Safety: Not applicable (Digital Operations).

---

3. Roles & Responsibilities

---

4. Step-by-Step Procedure

Phase 1: Repository Provisioning & Environment Setup

• 1.1 Navigate to the Template Registry Enterprise SharePoint Hub (https://templateregistry.sharepoint.com/sites/PMO).
• 1.2 Verify active Microsoft Teams workspace connectivity for the target project (naming convention: PRJ-[YY]-[Code]-[ProjectName]).
• 1.3 Create a dedicated sub-folder directory within the SharePoint Document Library matching the structure: /01_Charter/Approved/.

Phase 2: Template Instantiation & Parameterization

• 2.1 Download the current Master Project Charter template (TR_Enterprise_Charter_v3.2.dotx) from the Template Registry repository.
• 2.2 Open the template in Microsoft Word (Desktop App preferred to maintain XML schema integrity).
• 2.3 Update the Document Properties (Title, Author, Company) via File > Info > Properties to align with project metadata.
• 2.4 Populate Section 1 (Executive Summary) and Section 2 (Business Case) using data extracted from the approved Project Request Form.
• 2.5 Define measurable success criteria in Section 3 utilizing SMART (Specific, Measurable, Achievable, Relevant, Time-bound) parameters.

Phase 3: Scope, Milestones, and Risk Matrix Configuration

• 3.1 Input explicit In-Scope and Out-of-Scope boundaries in Section 4 to prevent scope creep.
• 3.2 Construct the high-level milestone schedule in Section 5, mapping deliverables directly to the enterprise fiscal calendar.
• 3.3 Populate the Risk Matrix (Section 6) with a minimum of three (3) critical operational risks, assigning initial Probability and Impact scores (Scale 1–5).
• 3.4 Export the completed document to PDF format using the naming convention: PRJ-[YY]-[Code]_Project_Charter_v1.0.pdf.

Phase 4: Approval Workflow & Microsoft Teams Integration

• 4.1 Upload the finalized PDF to the /01_Charter/Approved/ SharePoint directory.
• 4.2 Initiate a formal approval flow utilizing Power Automate / Microsoft Approvals targeting the Project Sponsor and Chief Architect.
• 4.3 Upon digital signature verification, move the artifact status to "Baseline-Locked" in SharePoint metadata.
• 4.4 Pin the approved charter link to the General Channel tab in the project's Microsoft Teams workspace for organizational visibility.

---

5. Quality Assurance & Pro-Tips

5.1 Best Practices

• Version Control: Never overwrite existing baselines; increment minor versions (v1.1) for post-approval edits and major versions (v2.0) for structural re-baselining.
• Metadata Tagging: Ensure SharePoint columns (Project Code, Sponsor, Lifecycle Phase) are populated immediately upon upload to ensure automated indexing by enterprise search.

5.2 Common Pitfalls to Avoid

• Pitfall: Hardcoding milestone dates instead of linking them to the master Microsoft Project / Planner schedule. Correction: Use dynamic table links or plain text placeholders referencing the live schedule ID.
• Pitfall: Failing to define out-of-scope items explicitly. Correction: Every charter must contain at least three explicitly bounded out-of-scope statements.

5.3 Metric Thresholds

• Deployment SLA: Charter instantiation and baseline approval must be completed within five (5) business days of project kickoff.
• Compliance Audit: 100% of active projects must maintain a signed, baseline-locked charter in the designated SharePoint repository.

---

6. Frequently Asked Questions (FAQ)

Q: What should I do if the Project Sponsor rejects the charter during Phase 4 review?
A: Document the rejection feedback directly within the Microsoft Approvals comment thread. Revert the document status to draft, make the required adjustments, increment the minor version number (e.g., v1.0 to v1.1), and re-initiate the approval workflow.

Q: Can I use a local copy of the Word template instead of downloading the master from the repository?
A: No. To ensure compliance with evolving enterprise metadata schemas and styling updates, you must always pull the active master template directly from the Template Registry SharePoint repository immediately prior to drafting.

Q: How are scope changes handled after the charter has achieved "Baseline-Locked" status?
A: Any post-baseline scope modification requires the submission of a formal Change Request (CR) via the Microsoft Teams PMO channel, which must be approved by the Change Control Board (CCB) before the charter document is updated to a major version (v2.0).