Let me be honest with you: when DepEd released the MATATAG Curriculum Framework, the first thing most teachers did was look for a new DLL template. We are creatures of habit, and our habits are shaped by forms and formats. Show a Filipino teacher a blank template and she will fill it perfectly. Show her a philosophical shift in educational values and she will ask: "Meron bang template?"

So here is the template thinking — and why it both helps and limits us.

What MATATAG Actually Changed in Lesson Planning

The Daily Lesson Log format looks familiar on the surface. You still have Objectives, Content, Learning Resources, Procedures, Remarks, and Reflection. But the philosophy embedded in those sections changed significantly.

Under the old K–12 framework, a lesson objective often read: "At the end of the lesson, the learners will be able to identify the parts of a plant." That is a knowledge-level objective. Identify. Name. List. Under MATATAG, the same lesson objective should read: "Learners will demonstrate understanding of plant structure by explaining how each part contributes to the plant's survival in their local environment."

The difference is not cosmetic. It changes your activity design, your assessment, and your reflection at the end of the day. MATATAG pushes teachers to plan for transfer — can the student use this knowledge in a new situation? — not just for recall.

The Procedures Section: Where Most Teachers Get Stuck

The Procedures section of the DLL has five phases under MATATAG's suggested instructional model:

Reviewing Previous Lesson / Presenting New Lesson — This is your bridge. Three to five minutes connecting yesterday to today.
Establishing Purpose — Answer "Why does this matter?" before you teach it. Authentically.
Presenting Examples / Instances — Use local, familiar contexts. A grade 4 math lesson about fractions hits differently when you use lechon portions versus abstract pie charts.
Discussing New Concepts — Guided discovery, not lecture. Ask more than you tell.
Developing Mastery / Application — Students produce something: a diagram, a written explanation, a demonstrated skill.

The most common mistake I see in DLL observations is teachers who write beautiful procedures but then teach a completely different lesson because the real class dynamics took over. Your DLL should be a flexible script, not a rigid performance rubric.

How AI Lesson Planners Changed My Prep Time

I started using an AI lesson planner about five months ago. Specifically, DepEd Me's Lesson Planner tool. The first time I used it, I typed in my MELC code, my grade level, and a note about my class context (rural school, limited gadgets, most students are hands-on learners). It generated a complete DLL in about 90 seconds.

Was it perfect? No. But it was a great draft. It had all five procedures sketched out with real activity suggestions. I spent 20 minutes adjusting it to fit my specific students — replacing one example with a local one, shortening an activity that would have taken too long, adding a reflection question I liked better than the one generated.

That 20 minutes replaced what used to be a 90-minute Sunday evening ritual. Over the course of one school year, I calculated that I reclaimed nearly 80 hours of prep time. I used those hours to actually observe other teachers, read professional development materials, and, yes, sleep earlier on school nights.

The Reflection Section: The Most Overlooked Part of Your DLL

Here is the section almost every teacher writes last and writes the least: the Reflection. Yet it is arguably the most important part of the DLL for your own professional growth.

MATATAG's DLL format asks you to reflect on two things: what worked, and what needs adjustment. Simple questions, but powerful if you take them seriously. The teachers I know who improve fastest year over year are the ones who write honest, specific reflections — not "Students were engaged" but "The pair-sharing activity in Step 4 took too long. Next time, limit it to 5 minutes and provide a sentence frame for lower-proficiency students."

Your DLL is not just a compliance document. It is a professional journal. Treat it that way and it becomes one of the most valuable tools you have.