A school timetable lists a teacher's periods, not their week. The gap between the two — the hours a teacher actually works versus the hours a timetable admits to — is where most of the real strain lives, and it's largely invisible precisely because nothing official measures it.
Consider what falls into that gap: lesson plans written at home on a Sunday night, not during any paid period. Worksheets and papers marked after the household has gone to sleep. Parent messages typed out on a personal phone at 9pm because that's when a parent finally replies. None of this appears on a timetable, a payslip, or a job description, and that invisibility is exactly what makes it easy for a school administration to underestimate how much of a teacher's actual week it consumes.
This invisibility carries a real cost beyond the hours themselves. Work that isn't counted is work that's easy to keep adding to — a new duty, a new report format, a new WhatsApp group to manage — because from the school's side, nothing on the visible timetable changed. The teacher absorbing it experiences a very different reality than the one the schedule describes.
Some of what makes this specifically heavier in a Pakistani context, rather than a generic "teachers are busy everywhere" observation: content frequently needs producing bilingually, in English for planning documents and Urdu or Roman Urdu for the classroom and parents, which is genuinely two jobs layered into one. Class sizes in many schools run larger than what curriculum materials assume. And resource scarcity — a shared computer, unreliable internet, no institutional template library — turns tasks that should take minutes into ones that take an evening.
None of this is a claim that naming the problem fixes it — it doesn't. But it does change what "workload" actually means when a school or a tool claims to address it: reducing the visible, scheduled part of a teacher's day changes little if the invisible, uncounted part stays exactly as heavy. A tool that shortens lesson-plan drafting time genuinely helps with one specific slice of the uncounted hours — the repetitive content-creation part — without pretending to touch class size, duty rosters, or school bureaucracy, which are different problems entirely and need different fixes.
This weight also isn't distributed evenly across a staffroom. A new teacher in their first year or two is usually building lesson plans and worksheets from nothing, every single week, with no personal archive to draw on yet — the uncounted hours are heaviest exactly when a teacher has the least experience to plan efficiently. A veteran teacher with years of saved material has usually built up enough of a personal bank to reuse and adapt rather than starting fresh, which is real, earned efficiency rather than the job itself getting lighter with tenure.
What a school can actually do about this, separate from what any individual tool can do: treat lesson-plan and worksheet archives as institutional assets rather than something each teacher rebuilds privately and takes with them when they leave. A shared, organized bank of past material — by chapter, by subject, by class — built collectively over a few terms, changes the starting point for every teacher who joins after, new or veteran, without requiring any single piece of software to do it.
Muallim, built by DIGIT Pakistan specifically after its leadership saw this gap firsthand, is scoped to that one slice deliberately: the Lesson Planner and the Worksheet Builder target the repetitive content-creation hours specifically, on a Free plan from first sign-up, not a claim to fix a teacher's whole week.
For the practical, task-by-task version of what's actually reducible and how, a separate, more tactical post on this Journal breaks it down step by step. This one is meant to do something narrower first: put a name on the part of the week that usually doesn't get one.
That naming matters beyond individual relief, too. A workload conversation that stays vague — "teachers are busy" — is easy for a school to acknowledge and then do nothing about, because there's no specific task to point at. A workload conversation that names the actual uncounted hours — Sunday-night planning, after-hours marking, late-evening parent messages — gives a school something concrete to actually respond to, whether that response is a tool, a shared resource bank, or simply adjusting what gets asked of teachers outside their scheduled hours.
It's worth teachers naming this to each other, too, not just to administration. The quiet assumption that everyone else is managing the invisible hours just fine, while you personally are falling behind, is common and usually false — most of a staffroom is carrying some version of the same uncounted weight, and saying so out loud tends to be the first step toward a school actually addressing it collectively rather than each teacher absorbing it alone.