Most "lesson plan template" searches turn up an English header row — Subject, Class, Topic, SLOs, Activities, Homework — with the expectation that a teacher fills it in and translates the wording themselves if the classroom runs in Urdu. That's usable, but it skips the actual question an Urdu-medium teacher is asking: not "what are the section headers" but "what does a plan that's genuinely written in Urdu, not translated into it, look like once it's filled in."
Here's the template itself, the same structure Pakistani teachers already use on paper, with the headers given in both languages since a plan often gets referenced by a coordinator or head teacher who expects the English labels even in an Urdu-medium school: مضمون / Subject, جماعت / Class, موضوع / Topic or Chapter, تعلیمی مقاصد (SLOs) / Learning Outcomes, سرگرمیاں / Activities, گھر کا کام / Homework. Copy that header row directly — it's the same shape whether it ends up handwritten, typed in a Word document, or generated.
The part a bare template can't give you is the phrasing inside each section, and that's where translation and native Urdu genuinely diverge. An SLO like "identify the main characters in the story" translates literally into something a bit stiff — کہانی کے مرکزی کرداروں کی شناخت کریں — where a teacher writing the same outcome directly in Urdu for their own class would more naturally phrase it as کہانی کے اہم کرداروں کو پہچانیں. Neither is wrong, but only one reads like something a teacher would actually say out loud in class, and that gap between technically-correct and naturally-phrased is exactly what a blank template can't fix by itself.
The same issue shows up in the Activities section more than anywhere else, since that's the part meant to be read aloud or handed to students directly. "Students will read the passage and answer the following questions" translates word-for-word into an instruction that sounds like a manual; a teacher phrasing the same instruction fresh in Urdu tends to write something shorter and more direct — یہ عبارت پڑھیں اور دیے گئے سوالات کے جواب دیں — the kind of line a teacher would genuinely say to a class rather than one that reads like it passed through a translator.
Roman Urdu is worth including as a third option in the same template, not a lesser fallback — it's the format a homework line or parent note in the Homework section usually ends up in anyway, especially for anything sent over WhatsApp. "Parhy gaye sabaq ka khulasa likhein" fits the same Homework field as the Urdu-script or English version; which one goes in the actual plan depends on who's reading it, not on which is somehow the "correct" choice.
The Lesson Planner fills in exactly this template — the same six-section structure above — with the SLOs, activities, and homework written directly in whichever of English, Urdu, or Roman Urdu is chosen for that generation, not translated after the fact from an English draft. Board is selected alongside class and subject (Punjab, FBISE, Sindh, KPK, or SNC-style planning), so the SLOs it fills in are scoped to that curriculum rather than generic.
Worth being direct about the honest use of a free template versus a free generation: copying the header structure above costs nothing and works with any tool, including a plain Word document. What a generator adds isn't the template shape — it's skipping the phrasing step described above, since the Urdu or Roman Urdu wording comes out already written in the natural, spoken register rather than needing that translation pass done by hand afterward.
This is still a beta product, and the honest caveat that applies everywhere else on this Journal applies here too: a generated plan is a draft a teacher reviews and edits before it goes anywhere, not a finished document meant to be handed out unchanged. The template above, filled in by hand or by the Lesson Planner, is a starting point either way — the review step is where a teacher's own judgment about their specific class still does the real work.