How to make a lesson plan

A lesson plan that cannot see the timetable and the holiday master will assign work on a closed day.

Schools do not fail because teachers cannot write objectives. They fail when plans live in personal drives disconnected from the class the register uses. Do this against working days on one student record, with publish gates, not a generic weekday grid. Named facts: working days, one student record, publish gates. Name the owner before the first family sees a receipt.

No. Teachers write it. Software keeps it on the class that actually meets.

Planning on a generic Monday–Friday file.
Homework due dates that ignore closures.
A scheme of work nobody can export with the class list.

Start from the published grid

The class and period already exist. The plan hangs off that, not a parallel list. Attach the plan to the class the register uses. A parallel list in a personal drive will not match the students who actually met.

For writing a lesson plan, “Start from the published grid” still has to survive a mid-year joiner and a working-day exception on one student record. Refuse this shortcut: Planning on a generic Monday–Friday file. Does software write the lesson? No. Teachers write it. Software keeps it on the class that actually meets. Named facts: working days, one student record, publish gates.

“Start from the published grid” for writing a lesson plan fails when this is skipped: The plan has to hang off the class and period that already exist on the published grid, and it has to move when the holiday master moves the day.

Drafts still need a working day and a real class. Do not publish unchecked text to families.

Start from the published grid
Planning on a generic Monday–Friday file.
Named facts: working days, one student record, publish gates.

Respect working days

If the holiday master moved the day, the plan moves or it is fiction. If the holiday master closed the day, the plan moves or it is fiction. Homework due dates have to read the same working days as attendance.

For writing a lesson plan, “Respect working days” still has to survive a mid-year joiner and a working-day exception on one student record. Refuse this shortcut: Homework due dates that ignore closures. Can AI draft a plan? Drafts still need a working day and a real class. Do not publish unchecked text to families. Named facts: working days, one student record, publish gates.

“Respect working days” for writing a lesson plan fails when this is skipped: The plan has to hang off the class and period that already exist on the published grid, and it has to move when the holiday master moves the day.

Cover is a policy on the published grid, not a second plan in chat.

Respect working days
Homework due dates that ignore closures.
Named facts: working days, one student record, publish gates.

Keep evidence retrievable

Inspection and coordinators will ask what was taught, not for a screenshot of a slide. Keep what was taught retrievable with the class, not as a screenshot of a slide. Inspection and coordinators will ask for the class, not the file name.

For writing a lesson plan, “Keep evidence retrievable” still has to survive a mid-year joiner and a working-day exception on one student record. Refuse this shortcut: A scheme of work nobody can export with the class list. What about substitutes? Cover is a policy on the published grid, not a second plan in chat. Named facts: working days, one student record, publish gates.

“Keep evidence retrievable” for writing a lesson plan fails when this is skipped: The plan has to hang off the class and period that already exist on the published grid, and it has to move when the holiday master moves the day.

No. Teachers write it. Software keeps it on the class that actually meets.

Keep evidence retrievable
A scheme of work nobody can export with the class list.
Named facts: working days, one student record, publish gates.

Do not mix schemes

IB inquiry and a national chapter list can share a teacher, not a mashed template. IB inquiry and a national chapter list can share a teacher. They cannot share a mashed template. The scheme stays on the class placement.

For writing a lesson plan, “Do not mix schemes” still has to survive a mid-year joiner and a working-day exception on one student record. Refuse this shortcut: Planning on a generic Monday–Friday file. Does software write the lesson? No. Teachers write it. Software keeps it on the class that actually meets. Named facts: working days, one student record, publish gates.

“Do not mix schemes” for writing a lesson plan fails when this is skipped: The plan has to hang off the class and period that already exist on the published grid, and it has to move when the holiday master moves the day.

Drafts still need a working day and a real class. Do not publish unchecked text to families.

Do not mix schemes
Planning on a generic Monday–Friday file.
Named facts: working days, one student record, publish gates.

How this playbook changes for a real campus

writing a lesson plan still starts from the holiday master, not a borrowed weekday grid. The plan has to hang off the class and period that already exist on the published grid, and it has to move when the holiday master moves the day.

Working days, one student record, and publish gates are the checks. Receipts have to match finance before families see a result.

Planning on a generic Monday–Friday file. Homework due dates that ignore closures. A scheme of work nobody can export with the class list. Named facts: working days, one student record, publish gates.

Drafts still need a working day and a real class. Do not publish unchecked text to families.

Start from the published grid
Named facts: working days, one student record, publish gates.
the boards the campus reports to

Where this usually breaks

Planning on a generic Monday–Friday file. Homework due dates that ignore closures. A scheme of work nobody can export with the class list.

A second spreadsheet for the real list is the usual failure. Named facts: working days, one student record, publish gates.

writing a lesson plan still fails when this is skipped: The plan has to hang off the class and period that already exist on the published grid, and it has to move when the holiday master moves the day. Saved marks stay drafts until the school publishes them.

Schoolyi keeps teaching assignments on the same calendar as attendance. Lesson artefacts should follow that class, not a side folder.

Planning on a generic Monday–Friday file.
Homework due dates that ignore closures.
A scheme of work nobody can export with the class list.

How Schoolyi fits

Schoolyi keeps teaching assignments on the same calendar as attendance. Lesson artefacts should follow that class, not a side folder.

Open /features/teaching after you can describe the awkward case for writing a lesson plan. This page is a playbook, not a feature grid. Name the owner in the demo. Named facts: working days, one student record, publish gates.

That walkthrough still uses the holiday master the school will go live on and the fee heads families can see on a receipt.

No. Teachers write it. Software keeps it on the class that actually meets.

Playbook: /how-to/write-a-lesson-plan
Product: /features/teaching
Book a demo with your awkward case, not a slide deck

Questions

Does software write the lesson? No. Teachers write it. Software keeps it on the class that actually meets.

Can AI draft a plan? Drafts still need a working day and a real class. Do not publish unchecked text to families. Named facts: working days, one student record, publish gates.

The plan has to hang off the class and period that already exist on the published grid, and it has to move when the holiday master moves the day. Named facts: working days, one student record, publish gates. Ask these before the demo.

What about substitutes? Cover is a policy on the published grid, not a second plan in chat. Named facts: working days, one student record, publish gates.

Does software write the lesson? No. Teachers write it. Software keeps it on the class that actually meets.
Can AI draft a plan? Drafts still need a working day and a real class. Do not publish unchecked text to families.
What about substitutes? Cover is a policy on the published grid, not a second plan in chat.

Bring this playbook to a demo

The plan has to hang off the class and period that already exist on the published grid, and it has to move when the holiday master moves the day. Schoolyi keeps teaching assignments on the same calendar as attendance. Lesson artefacts should follow that class, not a side folder. Named facts: working days, one student record, publish gates. Book the demo with that owner in the room.

Score statutory filing and hardware as not met unless the deployment actually has them. Publish gates still decide what families see.

Start from the published grid

Open /features/teaching
Book a demo with the awkward case
Named facts: working days, one student record, publish gates.

How to make a lesson plan