Lesson Factory · Curriculum
Build a curriculum that stays coherent as it changes.
Lesson Factory produces sequenced materials to your specifications, checks each lesson against the framework and keeps expert approval before release.
The system problem
Thousands of separate documents drift.
A curriculum lives in thousands of lesson documents. As writers change, year levels are revised and requirements move, those documents drift away from one another and from the framework they were meant to carry. Keeping them consistent by hand consumes the time of the people who should be improving them.
A shared sequence
Foundation to Year 10, sequenced across two subjects.
More than 4,000 lessons span Foundation to Year 10. The curriculum records 154 progression steps, with vocabulary introduced in sequence across the curriculum.
Inventory view
Foundation to Year 10
School-year sequence
Mathematics and English are covered in every year from Foundation to Year 10.
4,000+
Mathematics and English lessons
154
Progression steps across the curriculum
940
Vocabulary introductions sequenced
Expert review
Quality checks happen before publication.
The engine begins with the framework’s rules, drafts within those constraints, checks each output and keeps a human approval gate before publication.
01
Constraints
Framework rules, vocabulary progression, curriculum mappings and exemplars define the space in which a lesson can be written.
02
Generation
The engine drafts with knowledge of the framework, the lesson's place in sequence and the exemplars that set the standard.
03
Validation
Fidelity, vocabulary and coverage checks run before a lesson reaches a reviewer. Anything outside the rules enters review.
04
Approval
An expert reviewer approves, requests revision or regenerates a single stage while approved work remains intact.
Lesson quality record
In reviewComparing and ordering fractions
- Outcome
- AC9M4N03
- Approach
- Explicit
Approach checks
- Explicit learning intention
- New content in small steps
- Worked example before practice
- Check for understanding built in
Reviewers can approve, request revision, or regenerate one stage while the rest of the lesson remains intact.
Change without rebuilding
Update the affected parts of the library.
Lessons are tied to the outcomes they teach and to the lessons around them. When a requirement changes, the system identifies linked lessons, prerequisites and vocabulary, then limits regeneration and review to the affected material.
Descriptor diff
- partition into halves and quarters
+ partition into halves, quarters and eighths
Direct mapping
Affected lessons
Queued for regeneration
Sequence
Prerequisites
Checked for impact
Language
Vocabulary
Reviewed in sequence
Regenerate affected material. Retain approvals for unaffected lessons.
Client control
Your pedagogy, your property, your approval.
The system retains its pedagogy, its intellectual property and the final approval of every lesson, by contract and by design. The engine applies your framework under your ownership; it does not replace the expertise that governs it.
The next step
Bring the framework your system needs to carry.
We will show how your sequence, standards and review requirements can govern production and change.