Lesson Plan Template for Google Slides

SOP-TR-EDU-004: Standardized Google Slides Lesson Plan Architecture

---

1. Document Control Block

---

2. Executive Summary & Purpose

This document establishes the institutional standard for designing, deploying, and maintaining high-fidelity lesson plan templates within the Google Slides ecosystem. The purpose is to minimize cognitive load for educators while ensuring pedagogical consistency, structural modularity, and cross-platform accessibility.

---

3. Scope & Prerequisites

• Scope: Applies to all instructional design staff and educators utilizing Template Registry assets.
• Software Requirements: Google Workspace (Slides, Drive), current stable browser (Chrome/Edge/Firefox).
• Hardware: Any device with an active internet connection capable of executing Google Apps Script (if advanced automation is required).
• PPE: N/A (Digital environment).

---

4. Roles & Responsibilities (RACI)

---

5. Step-by-Step Procedure

Phase I: Structural Setup

• Initialize a new Google Slide deck with a 16:9 aspect ratio.
• Configure the Slide Master (View > Theme Builder) to establish global typography and color palettes.
• Define the base layout architecture: Title, Objectives, Direct Instruction, Guided Practice, and Assessment.

Phase II: Component Injection

• Insert placeholders for interactive elements (e.g., text boxes with standardized prompt text).
• Integrate external links using the "Link" feature (Ctrl+K) for supplementary resources.
• Deploy "Slide Numbers" and "Footer" branding on all master slides.

Phase III: Optimization & Deployment

• Apply "Locking" mechanisms for background elements to prevent accidental editing by end-users.
• Export as a "Template" by updating the URL suffix from /edit to /template/preview.
• Store the master template in a read-only repository folder.

---

6. Quality Assurance & Pro-Tips

Quality Assurance Metrics:

• Load Time: < 3 seconds on standard fiber connections.
• Accessibility: Must pass Google Slides "Accessibility Check" (Alt-text on all images).
• Consistency: Zero deviation from brand style guide (Hex codes, font weights).

Pro-Tips:

• The 10/20/30 Rule: Use no more than 10 slides, spend no more than 20 minutes (per section), and use nothing smaller than 30-point font.
• Versioning: Always utilize the "Version History" feature; name your iterations clearly to avoid catastrophic data loss during template updates.
• Master Slides: Never place content directly on individual slides if it is meant to be repeatable. Always place repetitive design elements in the Theme Builder.

---

7. Frequently Asked Questions

Q: How do I prevent users from changing the slide background? A: Use the "Theme Builder" to set the background. Assets applied at the Master level cannot be edited by the user in the standard edit view.

Q: Should I use Google Slides or Google Docs for lesson planning? A: Use Google Slides for real-time delivery and high-impact visual pedagogy. Use Google Docs only if the primary goal is long-form documentation or archival reporting.

Q: How do I update a template that is already in use by multiple teachers? A: Do not edit the deployed file. Create a new version, publish it, and share the new link. Breaking change management requires strict communication protocols to prevent workflow disruption.

---

End of SOP Julian Vance Chief Architect, Template Registry