Lesson Plan Template for Three Term

Standard Operating Procedure: Academic Term Planning Architecture

Document ID: TR-ED-PLAN-003
Effective Date: 2023-10-27
Version: 1.0.0
Review Cadence: Annual (Q3)

1. Executive Summary & Purpose

This document establishes the standardized framework for designing a 3-Term Academic Lesson Plan. The purpose is to ensure pedagogical alignment, curriculum continuity, and objective-based progression across a tri-semester structure. This SOP mandates a modular approach to content deployment to mitigate "curriculum drift" and ensure adherence to institutional learning outcomes.

2. Scope & Prerequisites

• Scope: Applicable to all instructional designers and faculty members developing modular course content for three-term environments.
• Tools/Software: Template Registry Unified Schema (TRUS), Learning Management System (LMS) API, Spreadsheet processor (Excel/Google Sheets), Markdown editor.
• Prerequisites: Completed Course Syllabus, Approved Learning Objectives (Bloom’s Taxonomy), and Assessment Weighting Schema.

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase I: Macro-Structural Mapping

• Define the critical path: Identify term start/end dates and non-instructional days (holidays/breaks).
• Map high-level Learning Objectives (LOs) across the three terms (e.g., Term 1: Foundational, Term 2: Applied, Term 3: Synthetic).
• Establish assessment milestones (Mid-terms/Finals) to ensure load balancing.

Phase II: Modular Content Decomposition

• Segment the syllabus into 12-week blocks (or standard term duration).
• Assign specific "Units of Competency" to each term.
• Ensure vertical alignment: Verify that Term 1 content is a prerequisite requirement for Term 2.
• Audit for "Bloom’s Creep": Ensure cognitive load increases predictably from Term 1 to Term 3.

Phase III: Template Deployment (TRUS Protocol)

• Populate the Three-Term Template with the following metadata:
  • Week Number/Day.
  • Topic/Theme.
  • Required Instructional Resources (Links/Assets).
  • Formative Assessment trigger.
  • Summative Assessment weighting.
• Validate cross-reference links between Terms 1, 2, and 3.

5. Quality Assurance & Pro-Tips

• QA Thresholds:
  • Zero-deviation in assessment weight across cohorts.
  • Minimum 15% overlap in concepts between final week of Term N and first week of Term N+1 for context retention.
• Pro-Tips:
  • The Rule of Three: Never assign a high-stakes assessment in the final week of a term if it requires feedback loops from earlier in that same term.
  • The Buffer Buffer: Always insert a 48-hour "administrative float" period at the end of each term for grading calibration.
• Common Pitfalls: Overloading Term 3 with "capstone" projects without accounting for cumulative fatigue. Front-load complexity; back-load synthesis.

6. Frequently Asked Questions (FAQ)

Q: How do we handle unexpected curriculum delays (e.g., inclement weather)?
A: Always build a "Flex Week" into the middle of each term. If unused, this week pivots to elective review or enrichment material. Do not sacrifice Term 3 content to compensate for Term 1 delays.

Q: Is it acceptable to modify the template during the term?
A: No. Structural deviations require an ECN (Engineering Change Notice) signed by the Department Head. Tactical adjustments (resource swapping) are permitted via the "Live Syllabus" addendum.

Julian Vance
Chief Architect, Template Registry