Standard Operating Procedure: QCAA Unit Plan Template Architecture

Standard Operating Procedure: QCAA-Compliant Unit Plan Architecture

Document ID: SOP-TR-QCAA-8842
Effective Date: October 24, 2023
Version: 2.4.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 designing, validating, and deploying QCAA (Queensland Curriculum and Assessment Authority) compliant unit plans within the Template Registry ecosystem. The objective is to eliminate structural drift, guarantee pedagogical alignment with the Queensland Syllabus, and ensure seamless interoperability between institutional planning artifacts and external verification workflows. Compliance with this SOP is mandatory for all curriculum architects, instructional designers, and systems operators.

---

2. Scope & Prerequisites

Scope

This procedure applies to all senior and junior secondary unit plans generated, maintained, or processed through the Template Registry for QCAA-governed educational frameworks.

Prerequisites & Required Tools

• Software: Template Registry Authoring Suite (v4.2+), Enterprise Markdown/LaTeX Processor, QCAA Portal Access.
• Documentation: Current QCAA Syllabus documents, General Senior Syllabus operational guidelines, and Instrument-Specific Guides (ISGs).
• Clearances: Level 2 Curriculum Authoring Credentials.

---

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Procedure

Phase 1: Initialization & Metadata Architecture

• Initialize the unit plan repository using the designated TR-QCAA-Base-v2 template schema.
• Populate system metadata blocks including Course Name, Syllabus Version, Nominal Hours, and Author ID.
• Lock the curriculum matrix identifier against the central QCAA syllabus database.

Phase 2: Syllabus Alignment & Objectives Mapping

• Extract mandatory Unit Objectives from the authorized QCAA syllabus document.
• Map cognitive verbs (Cognitive Levels R–S) directly to the assessment instruments.
• Verify that 100% of syllabus objectives are accounted for across the teaching, learning, and assessment continuum.

Phase 3: Assessment Instrument Integration

• Anchor the Summative Assessment Instrument (IA1–IA4 or EA) to the core unit objectives.
• Embed the designated ISG criteria matrices (e.g., Knowledge and understanding, Analyzing and applying).
• Define formative checkpoint intervals to validate trajectory toward summative standards.

Phase 4: Teaching and Learning Schema Construction

• Sequence weekly learning experiences to support scaffolding of cognitive load.
• Align pedagogical strategies with differentiated learning pathways (IEPs, EAL/D, Gifted).
• Embed explicit formative assessment checkpoints matching QCAA standards.

Phase 5: Verification & Deployment

• Execute automated validation script: tr-validator --qcaa-strict --file unit_plan.md.
• Resolve all syntax errors, unmapped objectives, and metadata mismatches.
• Export final payload to the Template Registry production vault and notify institutional stakeholders.

---

5. Quality Assurance & Pro-Tips

Best Practices

• Granular Mapping: Never group distinct cognitive verbs under a single assessment objective node. Maintain atomic mapping for audit traceability.
• Iterative Linting: Run the validation linter after every structural modification to prevent error cascades during the final compliance check.

Common Pitfalls

• Cognitive Drift: Using non-syllabus verbs in assessment instruments that misalign with the prescribed cognitive level.
• Orphaned Content: Including learning activities that do not directly map to a syllabus objective or assessment requirement.

Metric Thresholds

• Syllabus Coverage: Exactly 100% (No missing, no extraneous objectives).
• Validation Errors: 0 errors permitted prior to vault commit.

---

6. Frequently Asked Questions (FAQ)

Q1: What happens if the QCAA updates an ISG mid-term?
A: Execute a delta patch using the Template Registry Patch Utility (tr-patch --update-isg). This isolates the modified criteria while preserving existing teaching and learning sequences.

Q2: How are multi-class implementations handled within the template schema?
A: Multi-class variations must branch from the master unit plan using the semantic versioning tagging system (e.g., v2.4.0-classA), ensuring cohort-specific adjustments do not compromise core compliance.

Q3: Is manual override permitted for non-standard assessment tasks?
A: No. Any deviation from standard ISG matrices requires written sign-off from the Chief Architect and a formal compliance exemption ticket logged in the Template Registry audit trail.