Every Pakistani school does classroom observations. A principal or coordinator walks in, sits at the back with a notebook, watches for twenty minutes, and later tells the teacher "it was good" or "you need to improve discipline". The teacher nods, the notebook closes, and nothing changes. Multiply that by a hundred observations a year and a school can spend an enormous amount of leadership time producing zero improvement. The problem is not that observation fails — it is that most schools observe without a system. Good principal classroom observation feedback is a cycle: a conversation before, evidence during, an honest conversation after, and a follow-up that checks whether anything actually changed.
This guide gives principals and coordinators that cycle, designed for real Pakistani schools: large classes, mixed-ability students, teachers with heavy loads, and limited time. It covers what to observe, how to record it, how to give feedback teachers accept, and how to follow up without turning observation into surveillance.
Why Most Observations Change Nothing
Observations fail for four predictable reasons. First, they are surprise inspections. A principal who appears unannounced with a notebook triggers performance, not teaching: the teacher delivers a rehearsed show lesson, the children behave unusually well, and the observer learns nothing about the ordinary Tuesday lesson that actually matters. Second, feedback is vague. "Good class" tells a teacher nothing; "improve your questioning" tells them nothing they can act on. Third, feedback is all judgement and no evidence. When a principal says "your discipline was weak", the teacher hears an opinion and gets defensive. When the principal says "in 40 minutes, you asked 14 questions, 12 of them closed, and the same three students answered 11 of them", the teacher hears a fact — and facts are hard to argue with. Fourth, there is no follow-up. Feedback given once and never revisited is a ritual, not a development process.
The deeper problem is trust. In many schools, observation is linked — openly or quietly — to salary decisions, contract renewal, or public ranking. The moment a teacher believes an observation is a trap, the honest conversation dies. Observation must be separated, visibly, from punishment. Its purpose is improvement, and the school must say so and act so: observations feed coaching and training plans, not a blacklist. That does not mean weak teaching is ignored — it means weak teaching is handled through a documented support process, not through a surprise visit.
Set the expectation at the start of the session: every teacher is observed two to three times a term, observations are announced, feedback comes within 48 hours, and every observation ends with one agreed action. When the system is predictable and fair, teachers stop fearing it and start using it. Our earlier guide to classroom observation feedback covers the same cycle from the teacher's side; this article is the principal's playbook.
Before the Lesson: The Pre-Observation Conversation
A five-minute pre-observation conversation transforms the whole exercise. Ask the teacher three questions: What are you teaching, and what do you want students to learn by the end? What part of the lesson are you unsure about — the part you would like me to watch closely? Is there anything about the class I should know — a new student, a difficult dynamic, a child who needs support? These questions do two things. They focus the observer on what the teacher cares about, and they tell the teacher that the observation is a professional conversation, not an ambush.
Agree on the focus. A general "observe everything" observation produces general feedback. A focused observation — "watch how I check understanding during the practice phase" or "watch whether the back rows are actually working" — produces usable evidence. New teachers benefit from a broad focus on lesson structure and classroom management. Experienced teachers benefit from a narrow focus on one skill they want to sharpen. Let the teacher choose the focus at least half the time; ownership of the focus is ownership of the improvement.
Agree on logistics too: when you will arrive, where you will sit, how long you will stay (a full period is better than twenty minutes, which only shows the opening), and whether you will interact with students. A principal who helps a struggling student during an observation is no longer observing. Sit where you can see the students' faces and their work, not just the teacher's back, and stay out of the lesson.
During the Lesson: What to Observe and Record
Observe learning, not performance. A lively, confident teacher with silent, copying students is not teaching well. A quiet teacher whose students are all working, answering, and correcting their own mistakes is. Your observation notes should track evidence of learning: what students are doing minute by minute, what they produce, who participates, and who is left out. Use a simple rubric with four or five domains: lesson clarity (do students know what they are learning and why?), student engagement (how many are actively working?), questioning and checking (does the teacher check understanding, or just ask "understood?"), classroom environment (is behaviour managed calmly and consistently?), and pacing and use of time (does the lesson finish with consolidation, or run out of time?).
Record evidence, not adjectives. Instead of "poor discipline", write: "9:12 — two boys at the back talking; teacher continued without addressing it. 9:20 — four students out of their seats." Instead of "good questioning", write: "Teacher asked 8 questions; 6 were recall, 2 required explanation; 5 students answered." This discipline feels slow at first, but it is what makes feedback credible. It also protects the teacher: an evidence-based observation is a fair record, not a mood. Keep a simple tally system — questions asked, students called on, time spent on each phase — on a single sheet. A rubric this simple can be used by a coordinator, not only by the principal, which is how a school scales observation beyond one person's diary.
Also note the positives specifically. "Good board work" is useless praise. "The worked example on the board, with each step numbered, meant every student could start the practice without asking for help" is praise a teacher can repeat next week. Specific praise is not flattery; it is the other half of coaching. Teachers who hear only faults stop listening; teachers who hear their strengths named precisely start trusting the observer's judgement about weaknesses too.
The Feedback Conversation: Evidence, Not Judgement
Hold the feedback conversation within 48 hours, privately, for twenty to thirty minutes. Never give feedback in the corridor, in the staffroom, or in front of students. Start with the teacher's own reflection: "How do you think the lesson went? What would you change?" Teachers usually name their own weak spots accurately, and a self-identified weakness needs no lecture. Then share your evidence: two strengths first, each tied to specific evidence, then one or two growth areas, also tied to evidence. The ratio matters — feedback that is all criticism makes teachers defensive; feedback that is all praise teaches nothing.
Use the language of curiosity, not verdict. "I noticed the practice phase ran for six minutes and most students finished only two questions. What do you think happened there?" invites thinking. "Your pacing was bad" invites argument. Describe the effect on students, not the teacher's character: "the back rows did not get a question in the whole period" is a fact about students; "you ignore the back rows" is an accusation about the teacher. And agree on one — at most two — concrete actions before the meeting ends. "Use name cards to call on students across the room" is an action. "Improve participation" is a wish. Write the agreed action down, with a date for the follow-up.
For struggling teachers, keep the same structure but add support: a demonstration lesson by a senior teacher, a shared lesson plan, or a co-teaching session. Observation feedback is not the place for threats. If a teacher's performance is genuinely below standard after support, that is a separate process — a documented improvement plan under your teacher appraisal system, with clear expectations and timelines — not a dressing-down after an observation.
The Feedback Formula
Follow-Up: The Step That Makes It Work
Follow-up is where observation cycles usually die. The agreed action goes into a file, the term rolls on, and nobody checks. Build the follow-up into the calendar: a short revisit — fifteen minutes in the same class, two or three weeks later — focused only on the agreed action. Did the teacher use name cards? Did participation spread? A short, focused revisit tells the teacher the conversation mattered, and it gives the observer real evidence of growth. Keep a simple log: teacher, date, focus, evidence, agreed action, revisit date, revisit outcome. A school management system with staff records can hold this log so it survives a change of coordinator.
Use the pattern across the school, not just the individual. If three observations show the same weakness — say, teachers asking only recall questions, or lessons running out of time before consolidation — that is not three teachers' problem; it is a training need. The principal's termly observation summary (no names, just themes) becomes the school's training plan: a workshop on questioning, a session on pacing, a demonstration lesson by the strongest teacher. This is how observation improves a whole school instead of a single classroom.
Finally, observe the observers. Once a term, the principal should sit in on a coordinator's observation and feedback conversation, and give the coordinator the same kind of evidence-based feedback. Observation quality is a leadership skill, and it improves with the same cycle: evidence, conversation, follow-up. And handle the classroom discipline techniques that observations reveal as a school-wide conversation, not a private criticism — when every teacher uses the same calm, consistent approach, every observation gets easier.
AI Help: Muse AI
Muse AI is Meta's personal AI assistant, available in the Muse app. It can help you turn rough observation notes into a clear, evidence-based feedback script — two strengths, one or two growth areas, and one agreed action — written in calm, professional language.
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.