Most schools "do" teacher training the same way: a workshop in the summer holidays, a guest speaker once a term, and a certificate filed away. The teacher returns to the same classroom, teaches the same way, and nothing changes. The problem is not the training — it is the absence of a professional development plan for teachers that connects training to a real goal, a real classroom, and a real review of whether anything improved.
A professional development plan (PDP) is a simple one-page document: a teacher's development goal for the year, the activities that will build that skill, the support the school will provide, and how progress will be checked. It turns training from an event into a process. This guide gives Pakistani schools a practical template and the yearly cycle that makes it work.
Why Random Workshops Do Not Work
A workshop without a goal is entertainment. A teacher attends a session on "21st-century skills", enjoys it, and returns to a timetable with no time to apply anything, no one to discuss it with, and no follow-up. Within a month, the handout is in a drawer and the teaching is unchanged. Research on teacher development is consistent on this point: isolated training events rarely change classroom practice. What changes practice is sustained, focused work on a specific skill, with feedback and time to practise.
A development plan fixes this by starting from the classroom, not the catalogue. Instead of asking "which workshop should we send teachers to?", the school asks "what does this teacher need to get better at, and what is the best way to build that skill?" Sometimes the answer is a workshop. Often it is cheaper and better: observing a colleague, co-planning a unit, reading one good book, or trying a new technique with a mentor's feedback. A PDP makes those choices deliberate.
Development plans also solve a fairness problem. In many schools, training goes to whoever shouts loudest or whoever the principal likes. A PDP process gives every teacher a plan, a voice in choosing their goal, and a record of what the school invested in them — which matters when promotion and retention decisions come around. A development plan works best when the school also supports new teachers from day one — see our guide on first-day tips for teachers.
Anatomy of a Good Development Plan
A PDP should fit on one page and contain six sections. 1. Teacher and context: name, subject, classes taught, years of experience. 2. Self-assessment: two or three sentences from the teacher on their strengths and the area they most want to improve. 3. Development goal: one clear goal for the year (see below). 4. Activities: three to five specific activities with dates — not "attend training" but "attend the March workshop on questioning techniques, then try two new questioning routines in Class 7." 5. Support needed: what the school provides — time, funding, a mentor, cover for an observation. 6. Review: how progress will be checked, and when — typically a mid-year conversation and an end-of-year review.
Keep the form simple. A four-page form with rating scales will be filled in hurriedly and filed unread. A one-page form with honest sentences gets used. The principal or coordinator should discuss each plan with the teacher individually for fifteen minutes — that conversation is where the plan becomes real, because the teacher hears that the school takes their development seriously.
Store PDPs centrally and digitally — a shared folder or the school management system — so they are not lost when a coordinator changes. A school that can show every teacher's development record is also a school that can show parents and inspectors that it invests in its staff.
Goal Setting: One Goal, Done Well
The most common PDP mistake is too many goals. A teacher with five development goals has none. One goal per year — or two at most — forces focus. Good goals are specific and classroom-observable: "use formative assessment in every lesson" is vague; "use exit tickets in every Class 8 maths lesson and adjust the next lesson based on the results" is a goal you can actually see and measure.
Good goals also connect to real school priorities. For classroom techniques worth building into a goal, see our class participation ideas. If the school's priority is improving English writing in middle school, English teachers' PDP goals should serve that priority. If board exam results in science are weak, science teachers' goals should address it. Individual goals that serve a shared school priority multiply the impact of development spending.
Let teachers choose within the priority. A teacher who picks their own goal owns it; a teacher handed a goal resents it. The coordinator's job is to steer the choice toward something ambitious but achievable, and to check that the goal is about student learning, not just teacher activity. "Complete a diploma" is an activity; "use the diploma's assessment techniques to improve Class 9 test scores" is a learning goal. For ideas on choosing the right training, look at the techniques teachers actually use daily — for example, our guide on group work management.
Goal Formula
CPD Hours: What Counts and How Much
How much development is enough? A reasonable target for a Pakistani school is 30-40 hours of structured CPD per teacher per year — roughly one focused day per term plus ongoing smaller activities. That is achievable without pulling teachers out of class for weeks. What counts as CPD should be broad: workshops and courses, yes, but also peer observation, co-planning, mentoring (as mentor or mentee), action research in one's own classroom, structured reading with a written reflection, and presenting a technique to colleagues.
Track hours honestly but simply. A shared log — date, activity, hours, and one sentence on what was learned — is enough. The point of counting is not bureaucracy; it is making sure development is spread across the year and across all staff, not concentrated in a few keen teachers while others get nothing. Review the logs at mid-year: if a teacher has zero hours by December, the plan has stalled and the coordinator should intervene.
Note that some boards and school networks in Pakistan are increasingly asking for evidence of teacher CPD, and Cambridge-affiliated schools have formal CPD expectations. A maintained PDP and CPD log puts the school ahead of such requirements rather than scrambling to document training after the fact.
Funding Development on a School Budget
Development does not need a large budget — but it does need a budget line. Set aside a small, explicit amount per teacher per year, even if it is only a few thousand rupees. The discipline of a budget line matters more than the amount: it means development is planned rather than begged for each time.
Spend smart. Free and low-cost options are plentiful: in-house sessions led by your own strong teachers, peer observation cycles, online courses from reputable providers, and school-cluster sharing — three nearby schools splitting the cost of one trainer. Reserve paid external courses for the goals where they genuinely add value, and when a teacher attends an external course, require them to present a 20-minute summary to colleagues within two weeks. One teacher's course then develops ten teachers, and the presenter consolidates their own learning by teaching it.
Finally, close the loop. At year end, each teacher writes a short reflection: what did I set out to learn, what did I do, what changed in my classroom, what is next? The principal reviews the PDPs as a set, and the pattern across them becomes next year's school development plan. That is the difference between training as an expense and development as an investment: the first disappears into a drawer, the second compounds year after year.
AI Help: Muse AI
Muse AI is Meta's personal AI assistant, available in the Muse app. It can help you draft a one-page professional development plan template, turn a vague training idea into a specific classroom goal, or brainstorm CPD activities that fit your school's budget and timetable.
Join Muse with invite code LTGSWD — in the Muse app, go to Settings > Redeem token and enter the code.
Disclosure: LTGSWD is the author's Muse invite code.