A principal decides the school should "do something about AI." A workshop is booked, a speaker talks for two hours, staff nod, and by the following week the notes are forgotten. The problem isn't the speaker. Professional development that isn't tied to a teacher's own lessons rarely changes what happens on Monday. AI is no different. The good news is that a school can run something more effective itself, with no budget, in six short weeks.
First, a sense of the wider picture, so you can tell staff why this is worth their time. Pakistan's National AI Policy, approved by the Federal Cabinet at the end of July 2025 and coordinated by the Ministry of IT and Telecommunication, includes train-the-trainer schemes and plans to integrate AI curricula with education authorities, and in a recent programme, UNESCO and Pakistan's National Commission for UNESCO trained 150 teachers, 25 head teachers, and 25 education coordinators from federal schools between September and December 2025 in tools including Khanmigo, MagicSchool, and Teach AI, with an emphasis on ethical classroom integration. Those programmes reach a limited number of schools, and most staff will get no such training unless their own school provides it.
What should the content be? UNESCO's AI competency framework for teachers is a good guide. It covers five areas, a human-centred mindset, the ethics of AI, AI foundations and applications, AI pedagogy, and AI for professional learning, across three levels: Acquire, Deepen, and Create. For a school starting out, the aim is simply to move every teacher from zero to Acquire, meaning they understand what these tools do, where they fail, and what the school's rules are, and to give interested teachers a route towards Deepen.
There's also evidence that guidance matters more than access. In the NFER trial ChatGPT in lesson preparation, 259 science teachers in 68 English schools who used ChatGPT alongside a guide on using it effectively saved around 25 minutes a week in preparation on average, compared with teachers who didn't use it, with no noticeable difference in resource quality. It was a UK trial in one subject, so it can't be transferred wholesale, but the design point holds: teachers didn't just get a tool, they got a structured way to use it.
Here is a six-week plan built on 40-minute slots. Week one, the ground rules: read your school's AI policy together, agree the data rule (no student-identifying information in general tools), and agree that every AI draft is reviewed by a teacher. If you don't have a policy yet, our post on a one-page school AI policy gives a draft. Week two, hands-on: each teacher generates a plan or worksheet for something they're teaching next week, using a real tool, and brings it back.
Week three is the most valuable session: review in pairs. Swap outputs, check them against the syllabus's learning outcomes, and list every problem: a wrong fact, a stiff Urdu sentence, an example that doesn't suit your students. Teachers quickly learn where AI fails, which is the best protection against over-trusting it. Week four, adapt: teachers edit their drafts and teach the lesson. Week five, reflect: what worked, what took longer than expected, what would you change? Week six, share and decide: each teacher shows one thing they'd recommend and one they'd avoid, and the school agrees what to keep, tighten, or drop.
A few practical notes make the difference. Keep it in subject or year-group teams so examples are relevant. Have the principal or a senior teacher take part as a learner, not an observer, because people follow what leaders do. Nominate one or two enthusiasts as peer helpers, but don't make them the only people who know. Record two or three concrete outcomes, such as minutes saved on a weekly plan or number of errors caught in review, so you can tell whether the effort paid off. And repeat a shorter version each term, since tools change quickly.
If you'd like a tool to practise on, Muallim is one option, and worth an honest description. Muallim is built by DIGIT Pakistan for teachers and school admins, not students, and we don't offer a training programme or certification. The Lesson Planner, the Worksheet Builder, and Quiz & Assessment are available on a Free plan capped by usage, so staff can try them without a purchase, and every result opens in an editor, which supports the review habit this plan is built on. For schools with several staff, the Admin Dashboard lets an admin invite teachers with time-limited links and assign their classes and subjects. Any tool that supports review-before-use would serve the same purpose; the process matters more than the product.
Start small. Book the first 40 minutes at your next staff meeting, ask each teacher to bring one lesson they're planning, and treat the first session as an experiment. By week six you'll have a school that knows its own rules, has seen AI's mistakes for itself, and has a handful of teachers who can help others, which is a better return than any single talk.
| Week | Focus | What teachers do |
|---|---|---|
| 1 | Ground rules | Read the school AI policy; agree the data rule and the review-before-use rule. |
| 2 | Hands-on | Generate a plan or worksheet for next week's lesson with a real tool. |
| 3 | Review in pairs | Swap outputs, check against learning outcomes, and list every problem found. |
| 4 | Adapt | Edit the draft to fit the class and teach the lesson. |
| 5 | Reflect | Discuss what worked, what took longer, and what to change. |
| 6 | Share and decide | Each teacher recommends one practice and one to avoid; the school agrees what to keep. |