SOP: USASK Lesson Plan Template Standardization

STANDARD OPERATING PROCEDURE: USASK LESSON PLAN TEMPLATE STANDARDIZATION

Document ID: SOP-TR-USASK-7042
Effective Date: October 24, 2023
Version: 2.1.0
Review Cadence: Annual
Owner: Julian Vance, Chief Architect, Template Registry

---

1. EXECUTIVE SUMMARY & PURPOSE

This Standard Operating Procedure (SOP) defines the institutional baseline for authoring, validating, and deploying lesson plan templates aligned with the University of Saskatchewan (USask) pedagogical framework. The intent of this document is to eliminate instructional variance, enforce curricular alignment with Saskatchewan Ministry of Education and institutional competencies, and provide a repeatable engineering lifecycle for educational artifacts within the Template Registry.

---

2. SCOPE & PREREQUISITES

2.1 Scope

This SOP applies to all instructional designers, curriculum architects, faculty developers, and registry maintainers producing lesson plan artifacts intended for deployment within USask-affiliated programs.

2.2 Prerequisites & Tools

• Access to the Template Registry repository (Authorized contributor status).
• Markdown / LaTeX authoring environment or enterprise word processor (Microsoft Word / Google Docs with institutional USask styling macros).
• Familiarity with Backward Design (Wiggins & McTighe) and USask Indigenous engagement protocols (Truth and Reconciliation Commission Calls to Action 62 & 63).
• Software: Git, Pandoc (for format conversion), Linter tools for accessibility (WCAG 2.1 AA compliance).

---

3. ROLES & RESPONSIBILITIES

The following RACI matrix dictates operational ownership across the lesson plan template lifecycle:

---

4. STEP-BY-STEP PROCEDURE

Phase 1: Metadata Initialization & Structural Setup

• 1.1 Clone the latest template repository from the Template Registry using git clone https://registry.usask.ca/templates/lesson-plan.git.
• 1.2 Initialize the document header with institutional metadata: Course Code, Instructor of Record, Term, and Module/Unit Number.
• 1.3 Verify that the document version tag matches semantic versioning standards (e.g., v2.1.0).

Phase 2: Curricular & Learning Outcome Alignment (Backward Design)

• 2.1 Define measurable Learning Objectives (LOs) utilizing Bloom’s Taxonomy action verbs.
• 2.2 Map each LO directly to programmatic competencies and provincial curriculum standards where applicable.
• 2.3 Integrate Indigenous ways of knowing, historical perspectives, or land acknowledgments into the foundational rationale of the lesson block.

Phase 3: Instructional Sequencing & Timing Architecture

• 3.1 Partition the instructional period into rigid temporal blocks:
  • Hook / Anticipatory Set (0–10% of time): Engagement metric initialization.
  • Core Instruction / Modeling (40–50% of time): Didactic delivery and scaffolded transfer.
  • Guided & Independent Practice (30–40% of time): Application vectors.
  • Closure & Formative Assessment (10% of time): Exit tickets, synthesis.
• 3.2 Define explicit learner-to-content and learner-to-learner interaction modalities (Synchronous/Asynchronous/Blended).

Phase 4: Assessment & Accessibility Validation

• 4.1 Attach formative and summative assessment rubrics containing clear, non-ambiguous grading criteria.
• 4.2 Execute an accessibility sweep: verify color contrast ratios exceed 4.5:1, ensure all structural headings utilize proper semantic tags (H1 through H4), and provide alt-text for all pedagogical diagrams.
• 4.3 Submit the finalized draft to the template linter pipeline: npm run lint:usask-template.

---

5. QUALITY ASSURANCE & PRO-TIPS

5.1 Best Practices

• Atomic Modularization: Keep learning activities modular so they can be hot-swapped across different syllabus iterations without breaking structural integrity.
• Explicit Differentiation: Always define explicit accommodation pathways for diverse learners (Universal Design for Learning - UDL framework).

5.2 Common Pitfalls

• Time Inflation: Allocating more content than can physically be delivered in the prescribed temporal blocks. Always pad transition times by 5%.
• Vague Objectives: Using unmeasurable verbs like "understand" or "learn" instead of "analyze," "construct," or "evaluate."

5.3 Metric Thresholds

• Accessibility Score: Must achieve 100% pass rate on automated WCAG 2.1 AA audits.
• Alignment Completeness: 100% of Learning Objectives must map to at least one measurable assessment mechanism.

---

6. FREQUENTLY ASKED QUESTIONS (FAQ)

Q1: How do I handle updates to the foundational USask template schema?
A: Template updates are pushed quarterly by the Chief Architect. Pull the latest release branch (git pull origin main), run make update-schema, and resolve any breaking merge conflicts in your local metadata headers.

Q2: Are interdisciplinary lesson plans required to reference multiple departmental standards?
A: Yes. If a lesson intersects multiple domains (e.g., Engineering and Indigenous Studies), the metadata block must declare dual-mapping arrays in the YAML front matter to satisfy QA compliance metrics.