Project Charter Template Google Slides

Standard Operating Procedure: Google Slides Project Charter Deployment

Document ID: SOP-TR-ENG-084
Effective Date: October 24, 2023
Version: 2.1.0
Review Cadence: Semi-Annual
Author: Julian Vance, Chief Architect, Template Registry

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional-grade engineering lifecycle for generating, validating, and publishing Project Charter artifacts within Google Slides. The intent is to eliminate variance in cross-functional project initialization, enforce strict metadata compliance, and ensure structural integrity across all Template Registry technical deployments. Adherence to this protocol is mandatory for all engineering and product management teams.

---

2. Scope & Prerequisites

2.1 Scope

This document governs the creation of Project Charters utilizing Google Slides within the Template Registry ecosystem. It applies to all internal initiatives, client-facing deliverables, and open-source infrastructure programs.

2.2 Prerequisites & Environment

• Software: Google Workspace Enterprise Tier (latest stable release of Chrome or Chromium-based browsers).
• Access Control: Level 3 Write/Edit permissions within the designated organizational Template Repository Shared Drive.
• Master Artifacts: Access to the TR-CORE-CHARTER-MASTER-v2.1 slide deck template.
• Required Inputs: Approved Project Brief, Resource Allocation Matrix, and High-Level Milestone Schedule.

---

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Procedure

Phase 1: Artifact Initialization & Namespace Governance

• Navigate to the authorized Template Registry Shared Drive folder: Shared Drives/TR-Engineering/Templates/Charters/.
• Locate the canonical master artifact (TR-CORE-CHARTER-MASTER-v2.1).
• Execute a programmatic copy via the Google Workspace interface: Right-click $\rightarrow$ Make a copy $\rightarrow$ Entire presentation.
• Rename the newly instantiated file immediately using strict semantic versioning and naming convention: [YYYYMMDD]-[ProjectCode]-Project-Charter-v1.0.
• Move the newly created file to the active project workspace directory (Shared Drives/TR-Engineering/Active-Projects/[ProjectCode]/).

Phase 2: Metadata & Core Parameter Injection

• Navigate to Slide 1 (Title Slide) and update the primary token fields: {{Project Name}}, {{Project Code}}, and {{Lead Engineer/PM}}.
• Access File $\rightarrow$ Page setup and verify the aspect ratio is locked to widescreen 16:9 (Dimensions: 10 inches x 5.63 inches) to prevent layout corruption during projection.
• Update the Master Slide metadata footer: Input the current ISO 8601 date (YYYY-MM-DD) and current document version index (v1.0).
• Verify corporate typography compliance: Ensure all headings utilize Inter (Bold) and body text utilizes Inter (Regular) per Template Registry design tokens.

Phase 3: Structural Content Population

• Slide 2 (Executive Summary): Populate the high-level objective statement. Constraint: Maximum 75 words; utilize bulleted architecture constraints rather than paragraph blocks.
• Slide 3 (Scope Boundaries): Define explicit In-Scope and Out-of-Scope deliverables using the binary comparison table layout.
• Slide 4 (Milestone Schedule): Insert phase gates (Phase 0 through Phase 4) mapped against absolute calendar quarters, utilizing the native Timeline element.
• Slide 5 (Resource Allocation & RACI): Map core project stakeholders to operational swimlanes. Ensure zero single-points-of-failure in accountability vectors.

Phase 4: Validation, Access Control, & Publishing

• Execute an end-to-end visual inspection check for contrast ratios, text overflow, and alignment anomalies using the grid tool (View $\rightarrow$ Show grid).
• Configure document access permissions: Set organization-wide access to View mode; restrict Edit mode strictly to the designated Project Manager and Chief Architect.
• Generate a static PDF backup artifact: Select File $\rightarrow$ Download $\rightarrow$ PDF Document (.pdf) and archive it in the project's immutable audit directory.
• Copy the live Google Slides URI and log it into the central Template Registry Index database.

---

5. Quality Assurance & Pro-Tips

5.1 Best Practices

• Atomic Updates: Never modify the master template (TR-CORE-CHARTER-MASTER) directly; always instantiate a clone for project-specific usage.
• Color Token Integrity: Restrict all custom callouts to the Template Registry authorized palette (Primary: #0F172A, Accent: #3B82F6, Warning: #EF4444).
• Version Control: If structural modifications occur post-approval, increment the minor version index (e.g., v1.1) and log the delta in the revision history slide (Slide 2).

5.2 Common Pitfalls

• Layout Drift: Avoid importing external fonts or using unapproved text scaling, which causes line-wrapping failures across different operating systems.
• Permission Leaks: Ensure "Editors can change permissions and share" is explicitly unchecked before distributing links to external stakeholders.

5.3 Metric Thresholds

• Deployment Velocity: Total instantiation and population time must not exceed 45 operational minutes.
• Compliance Rate: 100% adherence to typography, color tokenization, and structural slide sequencing.

---

6. Frequently Asked Questions (FAQ)

Q: What should I do if the master template layout is accidentally overwritten?
A: Immediately halt modifications. Access File $\rightarrow$ Version history $\rightarrow$ See version history, locate the last known clean state timestamp managed by the Chief Architect, and select Restore this version. Report the incident to the Governance Board.

Q: Can external non-Google Workspace collaborators edit the project charter directly?
A: No. External collaborators must be granted Comment access only. If direct input is required, export the document to an isolated staging copy, collect edits, and manually migrate approved changes into the canonical workspace file.