50 Teacher Observation Feedback Examples (Organized by Framework Domain)

A useful teacher observation feedback example does three things: it names specific evidence from the lesson, ties that evidence to a framework domain, and points toward one clear next step. The 50 examples below are grouped by the areas principals actually score - classroom environment, instruction, questioning, engagement, planning, and assessment - and mapped to the Danielson Framework, T-TESS, and Marzano so you can adapt them to your rubric.

What makes a teacher observation feedback example useful?

The strongest feedback statements read like a camera, not a verdict. They describe what the teacher and students actually did, then connect it to the rubric. Research backs this up: a 2022 study on classroom observation feedback found that teachers judged feedback as useful when it was specific and clearly tied to their practice, and discounted it when the standards felt too broad or disconnected from the lesson they taught.

That is why a comment like "great job with engagement" rarely changes anything, while "when you asked students to restate a peer's idea before adding their own, six more students entered the discussion" gives a teacher something concrete to repeat. Four habits separate the second kind from the first:

1. Lead with evidence, not judgment. Describe what happened before you label it. The label without the evidence is just an opinion.
2. Name the domain. Tie the evidence to a specific rubric domain so the teacher knows which part of their practice it speaks to.
3. Pair the strength with a next step. A strength a teacher can repeat plus one move they can try next is worth more than a paragraph of praise.
4. Keep it to two or three points. Covering the whole rubric dilutes the message. Depth on one thing beats a checklist of ten.

For the note-taking habits that make this kind of evidence easier to capture, see writing better observation notes.

How are these examples mapped to framework domains?

Frameworks use different words, but they observe the same territory. The six groups below cross-walk to the major rubrics so you can lift an example and drop it into your own language:

• Classroom environment maps to Danielson Domain 2: Learning Environments, T-TESS Learning Environment, and Marzano Conditions for Learning.
• Instruction and delivery maps to Danielson Domain 3: Learning Experiences, T-TESS Instruction, and Marzano Standards-Based Instruction.
• Questioning and discussion lives inside the instruction domains of all three frameworks and is where the highest rating levels are usually decided.
• Student engagement and ownership is the evidence that separates Proficient from Distinguished in Danielson and Accomplished from Distinguished in T-TESS.
• Planning and preparation maps to Danielson Domain 1, T-TESS Planning, and Marzano Standards-Based Planning.
• Assessment and feedback to students appears across the instruction and planning domains in every rubric.

These mappings follow the published rubrics from the Danielson Group and Teach for Texas. The examples below are written as the strength and evidence half of a feedback note. Further down, we show how to extend any of them into a growth move and a next step a teacher can act on.

Classroom environment feedback examples

These speak to Danielson Domain 2, the T-TESS Learning Environment domain, and Marzano's Conditions for Learning.

• When a student gave a wrong answer, you asked "Tell me how you got there" - the student kept working instead of shutting down.
• Lab materials were staged at each table before students arrived, so the transition into group work took under a minute.
• You referenced your posted norms by name ("Remember, we build on each other's ideas") rather than just leaving them on the wall.
• You used proximity to redirect two off-task students without interrupting instruction or naming them in front of the class.
• Students moved from the carpet to their desks using a routine they clearly knew - no verbal directions were needed.
• Every student was greeted by name at the door, and you referenced a prior conversation with one of them.
• When the noise level rose during partner work, your quiet signal reset the room in about five seconds.
• Student work was displayed with rubrics attached, so students could see what proficient work looks like.

Instruction and delivery feedback examples

These speak to Danielson Domain 3, the T-TESS Instruction domain, and Marzano's Standards-Based Instruction.

• You opened with the lesson objective and returned to it twice, so by the end students could name what they were learning and why.
• Your model of the two-step equation included a think-aloud, so students heard the reasoning, not just the steps.
• You checked for understanding with a quick thumbs-up signal, then re-taught to the third of the class who were unsure.
• The lesson built from a concrete example to an abstract rule, which matched where most students were in their thinking.
• You connected today's text to the novel students read last month, helping them see the theme carry across both.
• Your directions for the station rotation were given once, clearly, and posted - students self-managed the rotation for 20 minutes.
• When students finished early, you had an extension task ready that deepened the work rather than just keeping them busy.
• You named the strategy students were practicing ("We're using context clues") so they could transfer it to new texts later.
• Your pacing left time for a three-minute summary, so the lesson closed cleanly instead of being cut off by the bell.

Questioning and discussion feedback examples

Questioning sits inside the instruction domain of every framework and is often where the top rating levels are won or lost.

• You asked "What evidence in the text supports that?" and waited - the pause gave a quieter student time to raise a hand.
• After a correct answer, you asked "Can someone build on that?" which turned one response into a three-student exchange.
• Your questions moved from recall ("What happened?") to analysis ("Why did the author choose that ending?") within the same discussion.
• You used several seconds of wait time instead of calling on the first hand, which widened participation noticeably.
• When a student disagreed with a peer, you had them respond directly to each other rather than back through you.
• You charted students' competing claims on the board, making the disagreement visible and worth resolving.
• A cold-call was softened with "I'll come back to you" for a student who wasn't ready, so the question still landed.
• You asked students to restate a classmate's idea in their own words before adding their own, which kept them listening.

Student engagement and ownership feedback examples

This is the evidence that separates the top two rating levels in most rubrics - the shift toward student ownership is explicit in the 2022 Danielson edition and in T-TESS.

• Students tracked their own progress on the unit goal in their folders, and several could tell me their current score.
• During the debate, students ran the turn-taking themselves using a protocol they clearly owned.
• When you stepped back, the small-group discussion kept going for several minutes without redirection.
• A student pushed back on the prompt ("Couldn't it also mean...?") and the class took the question seriously - a sign of a safe room.
• Students self-selected their reading level for the independent task, and the choices looked appropriately matched.
• The exit ticket asked students to rate their own confidence and name one question they still had - real self-monitoring.
• Group roles were assigned and actually used, so every student had a job and no one coasted.
• Students checked their work against the success criteria before turning it in, instead of waiting for your verdict.

Planning and preparation feedback examples

These speak to Danielson Domain 1, the T-TESS Planning domain, and Marzano's Standards-Based Planning - scored from artifacts and conferences as much as from the lesson itself.

• The lesson objective was tied to a specific standard, and the activities built toward it rather than around it.
• Your warm-up surfaced a common misconception early, which let you address it before the main task.
• The task had a built-in scaffold for emerging writers and an extension for students ready to go further.
• Materials, grouping, and timing were planned in advance, which is why the 50-minute lesson had no dead time.
• The questions you planned were sequenced from concrete to abstract, showing intentional design rather than improvisation.
• Your assessment matched the objective - students were asked to do exactly what the lesson taught, not something adjacent.
• You anticipated where students would struggle in the lab and pre-positioned a checkpoint at that step.
• The plan accounted for the co-teacher's role, so both adults were teaching rather than one supervising.

Assessment and feedback examples

These appear across the instruction and planning domains in every framework and cover how the teacher gathers and acts on evidence of learning.

• Your feedback on the draft named a specific strength ("Your thesis is arguable") and one revision move, not just a grade.
• The rubric was shared before the task, so students knew what proficient looked like while they worked, not after.
• You ran a formative check halfway through and regrouped three students who needed another model.
• Students received feedback the same day, while the work was still fresh enough to act on.
• Your comments asked questions ("What made you choose this order?") that pushed revision instead of closing it down.
• The exit ticket gave you data you actually used - you named tomorrow's reteach group based on it.
• You had students apply your feedback immediately by revising one paragraph before the period ended.
• Peer feedback was structured with a protocol, so students gave specific comments instead of "looks good."
• You separated ungraded practice from the graded assessment, which lowered the stakes for risk-taking.

How do you turn an example into a next step a teacher can act on?

Each statement above is the evidence half of a feedback note. To make it coaching rather than commentary, add a growth move and a concrete next step. The pattern is strength, then growth, then next step:

1. Questioning. Strength: "You asked text-based questions and used wait time, which widened participation." Growth: build in more of these on purpose. Next step: plan two text-evidence questions in advance for tomorrow and mark where you will pause.
2. Instruction. Strength: "Your think-aloud made the reasoning visible." Growth: hand the reasoning to students. Next step: in the next lesson, model one example, then have a student narrate the second while you record their thinking.
3. Assessment. Strength: "You shared the rubric before the task." Growth: have students use it to self-assess. Next step: add a two-minute self-check against the success criteria before students submit their next piece.

Notice that each next step is small, specific, and tied to the very next lesson. That is what makes it likely to actually happen.

How many strengths and growth areas should one observation include?

Fewer than you think. The most productive post-observation conversations name one or two genuine strengths the teacher can repeat and exactly one area for growth. Covering the whole rubric in a single write-up reads as thorough but lands as noise - teachers cannot act on ten things at once, so they act on none of them. Depth on the highest-leverage move beats breadth every time.

How does Observation Copilot help write feedback like this?

Writing 50 evidence-based, domain-tagged comments by hand is the reason feedback gets delayed - and delayed feedback is feedback teachers can no longer use. Observation Copilot takes your raw observation notes, maps the evidence to the right domain in your district's framework, and drafts the strength-and-next-step language in the rubric's own terms. You review and edit, then share it the same day. It is free for individual principals, with unlimited teachers and observations.

The actual process with Observation Copilot has alleviated that time that it takes for me to go back and look at which domain it's aligned to and making sure that I'm using the correct verbiage in our rubric. It has laid it out all for me.

Frequently Asked Questions

What is an example of positive feedback for a teacher observation?

A strong positive example names specific evidence and ties it to the rubric, such as: "When you asked students to restate a peer's idea before adding their own, six more students entered the discussion - that is exactly the kind of accountable talk your framework's instruction domain is looking for." Evidence plus a domain beats general praise.

How do you give feedback after a classroom observation?

Open by asking the teacher how they thought the lesson went, then highlight one specific strength with evidence, focus on a single area for growth, and co-create one next step the teacher can try in their next lesson. Deliver it the same day, while the lesson is still fresh.

What should you avoid when writing teacher observation feedback?

Avoid vague judgments ("good engagement"), covering the entire rubric at once, and writing only about teacher actions while ignoring what students did. The most common error is leading with a label instead of the evidence behind it, which makes feedback feel subjective rather than grounded.

How many strengths and areas for growth should one observation include?

One or two strengths the teacher can repeat and a single area for growth. Teachers cannot act on a long list at once, so naming everything reduces the odds anything changes. Pick the highest-leverage move and go deep on it instead.

Should observation feedback be tied to a specific framework domain?

Yes. Tying each comment to a domain in Danielson, T-TESS, Marzano, or your local rubric tells the teacher which part of their practice the feedback addresses and keeps the conversation aligned to how they will ultimately be rated. It also makes feedback consistent across observers.

Ready to generate framework-aligned feedback from your own notes? Paste them into Observation Copilot and get a structured draft in seconds at app.observationcopilot.com.