Writing one lesson plan the night before is the most expensive way to plan. You pay the start-up cost five times a week, you make each decision without seeing the shape of the week, and you write the Ways Forward box when you are too tired to act on it.
This is a routine for planning a full week of ILAW lessons in about an hour, in one sitting. It is built around a simple observation: the parts of a lesson plan that take the longest are the parts that repeat, and repetition is cheapest when batched. If the format is new to you, our complete ILAW lesson plan guide covers what belongs in each box.
The 10-second answer: Plan the whole week in one block, in four passes. Competencies for all five days first, then assessments, then learning experiences, then learner context last. Doing the same box five times in a row is far faster than doing four different boxes five separate times.
Why batching beats nightly planning
Every time you sit down to plan, you spend the first few minutes reloading context: which competency comes next, what happened in the last session, where the class actually is. That reload costs roughly the same whether you then write one plan or five.
Five nightly sessions means paying that cost five times. It also means you cannot see the week as a shape. You discover on Wednesday that three heavy assessment lessons landed on consecutive days, and by then the only fix is to teach them anyway.
Planning the week together lets you make three decisions you simply cannot make one night at a time: where the heavy lesson goes, which day carries the assessment you will need time to check, and which lesson arc should span two sessions rather than being crushed into one.
The four passes
The routine works because each pass keeps you in one kind of thinking. Curriculum thinking, then assessment thinking, then teaching thinking, then your own class.
Pass one: competencies and the shape of the week (10 minutes)
List the competencies for all five sessions. Then mark each one with its cognitive demand: recall, application, or analysis and above. This takes a minute per lesson and it tells you where the week is heavy.
Now arrange. A lesson at the analysis level needs discussion time, so it belongs on your longest period, not the one shortened by a flag ceremony. Two heavy lessons back to back will exhaust both you and the class, so separate them with an application lesson where learners work more and you talk less.
This is also the pass where you decide which learning genuinely needs two sessions. Deciding that now is planning. Discovering it on the day is improvising.
Pass two: assessments, all five at once (15 minutes)
Write the assessment before the activities. This feels backwards and it is the single change that improves plans the most, because every activity you then design has a target to aim at.
For each day, write the exact task and the scoring rule. Three exit-slip items with points, or a performance with three criteria. Writing all five in a row makes the checking load visible, and that visibility is the point: if Tuesday and Wednesday both produce a stack of paragraphs to score, move one.
Keep the verb honest against the competency, which is the discipline covered in writing ILAW intentions that match the competency code. If the competency says evaluate, the exit slip cannot be a matching type.
For performance tasks, the rubric is the scoring rule, and reusing one rubric across a week of similar tasks is legitimate and saves real time. Our rubric guide has a sample to adapt.
Pass three: learning experiences (20 minutes)
Now write the middle of each lesson, working backwards from the assessment you just wrote. Four minutes per lesson is enough when the target is already fixed.
For each session, write the opener, what you will model, what learners practise, and one specific thing you will look for while circulating. That last item is what separates a plan from a list of activities, and it is what makes Ways Forward writable at the end of the lesson rather than invented afterwards.
Check the timing against the real period, not the timetable. The segment breakdowns in fitting an ILAW lesson into 50 or 60 minutes give you a distribution that survives contact with an actual class.
Pass four: learner context (10 minutes)
Last, and never skipped. Go through the five plans and add the sentence that could only have been written about your section this week.
Some of it is known in advance: the learners who joined late, the ones who read below grade level, the section that meets last period. Some of it comes from last week’s evidence, which is why this pass sits at the end, after you have looked at what the week’s assessments will produce.
A context that would fit any class in the country is not context. That test is covered in more detail in the Intentions guide linked above, and it is the thing observers notice fastest.
The Friday review that makes next week faster
Ten minutes on Friday, with the week’s exit slips in front of you. You are answering one question: which competencies need a second pass?
Sort each lesson’s evidence into three piles. Learners who have it, learners who have part of it, and learners who do not. The middle pile drives next week’s openers. The third pile drives your remediation grouping, which is easier to run when it is planned rather than improvised.
Write the answer straight into next week’s pass-one list. That is the whole loop: Friday’s evidence becomes Monday’s opener, and the Ways Forward box stops being a paragraph nobody reads.
A realistic first-week timetable
| Pass | Time | Output |
|---|---|---|
| Competencies and week shape | 10 min | Five competencies, ordered, with the two-session arc identified |
| Assessments | 15 min | Five tasks with scoring rules, checking load balanced |
| Learning experiences | 20 min | Five narratives with a look-for in each |
| Learner context | 10 min | Five specific sentences |
| Formatting and submission | 5 min | Plans in the required template |
An hour, honestly. Your first attempt will take ninety minutes, because pass two is unfamiliar. By the third week it settles.
Where the hour usually goes wrong
- Starting with activities. Without a target, activity design expands without limit. Write the assessment first.
- Perfecting Monday. Five adequate plans beat one polished plan and four rushed ones. Work in passes across all five, never one plan to completion.
- Formatting while writing. Get the thinking down as plain text, format at the end in one go.
- Skipping the Friday review. Without it, next week’s plans are guesses, and the remediation you promised never gets scheduled.
- Planning on the same evening as checking. Different work, different energy. Separate them.
Where a tool actually helps
Be precise about which part of the hour a tool can take. It cannot write your learner context, and it should not write your Ways Forward, because both depend on evidence only you hold. What it can do is remove the blank page and the formatting.
Skoolari’s DepEd mode takes a competency and topic and returns a complete ILAW plan in the official structure, with assessment items that match the stated intention. Used inside this routine, it collapses passes two and three into a review-and-edit job, which is where most of the hour goes. The plans are listed on our pricing page.
Two cautions. Declare AI use in the plan, as the MATATAG guidelines require. And read every generated assessment item before it reaches learners, because generated items fail in specific, predictable ways, which we cover in what AI gets wrong when writing test items. Our wider review of AI tools for Filipino teachers gives the honest picture of which jobs are worth handing over.
When the week includes a quarterly exam
Exam weeks break the routine, and they need their own version. The exam is not planned in an hour, it is blueprinted with a table of specifications so the weighting matches what you actually taught, and ideally checked in advance by pilot testing it before it reaches learners.
Plan the exam a week ahead, then use your normal hour for the four teaching days around it. And keep the grading week itself separate: the encoding and submission load has its own sequence, which we lay out in the quarterly grading week checklist.
Starting this week
Pick a single block of time, protect it, and do only pass one and pass two the first week. Those two passes are where the value concentrates, and they are enough to change how the week feels. Add passes three and four when the first two stop taking effort.
The measure of success is not a thicker folder of plans. It is Friday afternoon, when you know exactly which learners need what on Monday, and it takes you ten minutes to decide instead of an evening.