"Multilingual" undersells how linguistically layered a Pakistani classroom actually is. Urdu is the national language and the medium of instruction in a large share of schools, but it sits alongside English-medium instruction in many private and higher-tier schools, and alongside Punjabi, Sindhi, Pashto, Balochi, Saraiki, and other regional and provincial languages that students speak at home and sometimes at school, depending on province and school type. Any resource claiming to solve "multilingual teaching in Pakistan" with one language pair is quietly narrowing the actual problem.
For a teacher, this shows up as a practical, everyday juggling act: a textbook in English, instruction happening in Urdu or a regional language depending on the classroom, and parent communication in whatever mix of Urdu, Roman Urdu, and English a specific family is most comfortable with. None of that is unusual or a sign of a poorly run classroom — it's simply the linguistic reality most Pakistani teachers already navigate without a name for it.
Regional-language teaching tools specifically — resources built to generate or support content in Punjabi, Sindhi, Pashto, or Balochi directly — remain a genuinely underserved category in Pakistani ed-tech. Most tools, including general AI chat tools, handle these languages far less reliably than Urdu or English, often defaulting to a rough translation rather than native, fluent generation, if they attempt them at all.
What actually varies by province and school type is worth being specific about rather than treating "Pakistan" as one linguistic bloc. Sindh runs meaningful Sindhi-medium instruction alongside Urdu and English in public schools. KPK classrooms often blend Urdu instruction with Pashto spoken support, especially in earlier grades. Balochistan's linguistic landscape includes Balochi, Brahui, and Pashto alongside Urdu. A resource built only around Urdu and English, without acknowledging this, is quietly assuming a Punjab- or Islamabad-centric classroom as the default rather than the genuinely varied reality across provinces.
For a teacher working in one of these more linguistically layered classrooms today, the practical workaround most fall back on is manual: translating or adapting Urdu or English material into the regional language themselves, in the moment, drawing on their own bilingual or trilingual fluency. That's real, valuable skilled labor that current tools — general or specialized — don't meaningfully reduce yet, and it's worth naming as unpaid, uncounted work rather than assuming it happens for free.
It's worth being direct about where Muallim actually stands in this picture, rather than implying broader coverage than what's real: the Lesson Planner, the Worksheet Builder, and Quiz & Assessment, built by DIGIT Pakistan, generate in English, Urdu, and Roman Urdu — not Punjabi, Sindhi, Pashto, Balochi, or other regional languages. That's a real, current scope limit, not a detail to gloss over for a broader-sounding pitch.
For a genuinely multilingual classroom that needs support beyond English and Urdu specifically, the honest options today are narrower: general AI chat tools with uneven regional-language quality, human-translated materials from provincial textbook boards where they exist, or a teacher's own bilingual or trilingual fluency doing the actual translation work in the moment, unaided by any tool. None of that is a satisfying answer, and it's worth saying so plainly rather than papering over the gap.
A practical middle ground some multilingual classrooms already use: generate the underlying content — the SLOs, the activity structure — in English or Urdu using whatever tool is available, then have the teacher do the final regional-language translation themselves for the specific parts students need in their home language, rather than expecting any tool to produce fluent Punjabi or Pashto from scratch. It's more manual than a fully native generator would be, but it's a genuinely workable interim approach today, and one worth adopting deliberately rather than reinventing it from scratch each time the need comes up.
Why Urdu and Roman Urdu got built first, rather than starting with a broader but shallower set of languages: they cover the largest single share of Pakistani classroom communication that wasn't already well served by existing tools, and building them properly — natively generated, not translated — took real, focused effort rather than a quick pass across many languages at once. A separate post on this Journal covers that decision in more depth.
Whether regional-language generation is a realistic future direction is an honest open question, not a roadmap commitment being made here — it depends on real demand from teachers actually asking for it, the same feedback loop that shapes everything else on the roadmap, not a decision made in isolation from what teachers actually report needing — worth watching the Features page over time rather than assuming either way based on this post alone. For now, the most useful thing this post can do is name the actual gap accurately, rather than let a general "multilingual" claim imply more than what any current tool, Muallim included, actually delivers.