How to use the Lesson Reflection Generator.
Lesson reflection should use observations and learner work to choose a specific adjustment. Avoid judging the entire lesson from whether it felt busy.
Make the workflow fit your task.
Use learner responses, work and classroom observations to compare the intended learning with what happened. Identify one specific adjustment and preserve the parts that worked, avoiding a global judgment based only on lesson energy.
- What you provide
- Teacher observations and assessment outcomes.
- What you get
- Evidence-based reflection and next-lesson adjustments.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Lesson observation: most learners solved routine examples but struggled to explain their reasoning. No cause established.
Completed example
What worked: routine problem solving was successful for most learners observed. What needs attention: explanations of reasoning were difficult. Interpretation limit: the observation does not establish why. Next lesson proposal: model one explanation, then ask learners to explain a comparable problem before further practice. Evidence to collect: the explanation responses, reviewed separately from answer accuracy.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Does a busy, enthusiastic lesson necessarily show the objective was learned?
Look at the evidence learners produced. Participation and enjoyment matter, but they do not by themselves establish the intended understanding.
Why does reflection produce only broad promises to improve next time?
Choose a concrete change linked to an observed difficulty and decide how its effect will be checked.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑