Separated data model
Classes are reusable teaching groups. Weekly periods live in schedules. Lessons inherit timing from the slot they belong to — no dates baked into class names.
Schools, classes, weekly periods, units, and lessons stay as separate layers — so the AI never has to guess what Monday Period 2 actually means. Plan in minutes, teach with confidence, and let next term's plans learn from this term's reflections.
LessonToolkit keeps course identity, timetable placement, and lesson generation in separate layers — so each one stays clean and honest about what it actually represents.
Classes are reusable teaching groups. Weekly periods live in schedules. Lessons inherit timing from the slot they belong to — no dates baked into class names.
Recurring periods, day-of-week logic, and optional A/B rotations sit at the centre of planning instead of being smuggled into class titles.
Class size, supports, room setup and behaviour notes flow into every prompt — without making you re-explain them lesson after lesson.
Unit plans, daily lessons, teaching mode, and post-lesson reflections all stay connected to the same school and schedule model.
School first, then classes, then recurring schedule slots, then units and lessons. Every layer adds context the next one can rely on — no spreadsheets, no copy-paste, no naming hacks.
Sign in to get startedCreate the school record and timezone so classes and schedule data have a consistent home.
Add courses like “Algebra I” or “Year 9 Science” once — without mixing in period identifiers.
Use schedules to link each class to the right weekday, time range, and optional rotation key.
Build unit arcs, place lessons on the calendar, and let timetable-aware slots drive the daily agenda.
LessonToolkit ships with a provider-agnostic generator. Pick a default, set a fallback, and switch any time without losing prompts, units, or feedback.
Use school records, reusable class profiles, and weekly schedules as separate layers — so the rest of the system can reason correctly.