A useful lesson study template gives the team a shared question, a plan for collecting relevant evidence, and a place to compare expectations with what actually happened. The packet below is a filled planning example with blank observation and conclusion fields. It prepares a cycle; it does not report a completed classroom study.
Start with a question observers can follow
Lesson study brings a team through studying, planning, teaching and observing a research lesson, then reflecting on the evidence. The Lesson Study Group describes one team member teaching while others record student thinking and learning, followed by discussion of those records. What Is Lesson Study?
For this original example, use research question RS01:
When we ask learners to show how their counts account for all items, what reasoning does their explanation make visible?
The proposed task uses eight paper tokens and two trays. Learners place one token in each tray per complete round and make as many complete equal rounds as possible. Four rounds produce four tokens in each tray, using all eight.
Confirm the actual class, relevant curriculum, materials, schedule and observation permissions before using the plan. The small task makes the protocol easy to inspect; it does not establish suitability for a particular class.
Predict reasoning without filling in the results
Write possible explanations before the lesson so observers know what to watch for. Keep their status visible.
| Planning ID | Anticipated explanation—not an actual student quote | What the team would investigate |
|---|---|---|
| P01 | “Four because half of eight.” | Does the learner connect four in each tray to all eight tokens, or only state a remembered result? |
| P02 | “Three each and two left.” | Does the learner recognize that the two remaining tokens permit one more complete round? |
Three in each tray accounts for six tokens. Two remain, so another round is possible. That arithmetic identifies a question for observation; it does not tell you why a particular learner would stop early.
The proposed teacher prompt is: “How does your arrangement account for all eight?” The team's hypothesis is that this question may elicit more explicit counting reasoning. Leave the finding blank until there is evidence to examine.
The Lesson Study Group treats the research lesson plan as a hypothesis and recommends collecting evidence relevant to its phases and goals, including observations, written work and lesson documentation. Focus the Data Collection
Assign coverage before the lesson
Use role IDs while the actual people are still unconfirmed. Agree on permitted case identifiers and work references under the school's record rules.
The proposed research-lesson flow is: present the eight-token task; allow an initial arrangement and explanation; ask the proposed prompt; invite a further explanation; then retain the permitted work references for debrief. Set actual timings with the team rather than inventing observation timestamps in advance.
| Proposed role | Coverage linked to RS01 |
|---|---|
| T01: teacher | Present the task; ask the proposed prompt; make the timing and wording available to observers. |
| O01: observer | Record initial arrangements and explanations, with time and task context. |
| O02: observer | Record explanations after the prompt, exact words or visible actions, work references and any additional support. |
| R01: debrief facilitator | Keep evidence, interpretation and revision proposals separate in the later discussion. |
Arrange coverage so the same permitted cases can be connected across phases. If that connection is missing, record the gap rather than treating unrelated before-and-after comments as one learner's change. Confirm whether one person can hold more than one role without leaving required evidence unobserved.
Keep the observation log blank until observation
Use this original record structure for each event:
| Time | Permitted case ID | Phase | Exact observed words or action | Work reference | Teacher prompt or other support | Separate interpretation |
|---|---|---|---|---|---|---|
Record what you can substantiate before interpreting it. An arrangement with three tokens in each tray and two aside is observable. “Does not understand equal sharing” is an interpretation requiring more evidence.
Do not paste P01 or P02 into the log as if a learner said it. If no response was captured, distinguish “no response observed” from “observer missed this phase.” Neither automatically establishes failure. Preserve unexpected reasoning and cases that challenge the team's hypothesis.
Debrief toward a defensible next question
The team's discussion should follow the evidence rather than rate the teacher. Complete these rows only after reviewing actual records:
| Debrief field | Entry |
|---|---|
| What initial reasoning was recorded? Include evidence references. | |
| What reasoning was recorded after the prompt for connected cases? | |
| How did actual reasoning compare with P01, P02 or an unanticipated approach? | |
| Which contrary cases, missing observations or additional supports limit interpretation? | |
| What can the team reasonably conclude about RS01? What remains uncertain? | |
| What revision is proposed, based on which evidence, for which next-cycle question? |
A different explanation after a prompt is worth investigating. One before-and-after case alone does not establish that the prompt caused learning. A partner's explanation, a rearranged display or unrecorded support could also matter. Keep that limitation beside the proposed revision.
For example, if actual records eventually show that learners count the two remaining tokens but do not connect them to another round, the team could propose testing a more explicit “one in each tray” demonstration. That is a conditional revision idea, not a finding from this unrun example. The next cycle would need its own question and evidence plan.
Copy this prompt to prepare your packet
Create one complete, self-contained US-English HTML companion for “RS01 • lesson study protocol”. Return the full HTML document, with inline CSS and any JavaScript needed for the local interactions. Use the original scenario, named records, numbers and expected cases below.
Design the page for this task: use clearly labeled input or source records, a readable result or worked example, and an adjacent explanation of the evidence. Use a restrained visual hierarchy, left-aligned text, readable tables or stacked records, and a responsive layout at 720px and 360px. Provide meaningful labeled controls for Add one complete round; Show 3-round case; Reset tokens; Initial reasoning / O01; After prompt / O02; Evidence discussion / R01; Prepare text; Select text. Use keyboard-accessible native controls and visible focus. Keep the complete content readable without an external dependency.
The following brief supplies the substantive content and constraints. Native-format requests describe the material to represent or copy manually; this HTML must not pretend to create DOCX, XLSX, PDF, PPTX, H5P or another native file, run Python/Flask/Django/Snowflake/Power BI, connect a live service, send messages, or perform an authorized real-world action. Where the task requires a native source, actual observation or separate approval, retain that requirement and leave unsupplied evidence blank.
Create an original lesson study planning packet in US English. Produce a readable document, not a teacher evaluation rubric or a report of completed research.
Use research question RS01: “When we ask learners to show how their counts account for all items, what reasoning does their explanation make visible?”
Use eight paper tokens and two trays. Place one token in each tray per complete round; make as many complete equal rounds as possible. The task key is four in each tray. Three in each tray leaves two tokens, enough for another complete round.
Label P01 “four because half of eight” and P02 “three each and two left” as anticipated explanations, never actual student quotes. State the proposed prompt “How does your arrangement account for all eight?” as a hypothesis that may elicit reasoning, not a proven intervention.
Include a cycle brief; research-lesson flow; anticipated-thinking table; and proposed coverage for T01 teaching, O01 initial explanations, O02 explanations after the prompt, and R01 debrief facilitation. Connect observation coverage across phases for the same permitted cases. Mark actual people, class, curriculum, permissions, permitted case IDs, materials and schedule TO CONFIRM.
Provide blank actual-record fields for time, permitted case ID, phase, exact observed words/action, work reference, teacher prompt or other support, and separate interpretation. Do not invent observations, names, results or completed findings.
Provide a blank debrief matrix comparing actual evidence with predictions, including unexpected reasoning, contrary cases, absent responses, coverage gaps and additional supports. Explain that before-and-after differences alone do not prove causation and no captured response does not automatically mean failure. Keep conclusions blank. Link each future revision proposal to evidence references and a next-cycle question. Do not rate teacher quality or declare the cycle complete.
COMPLETE AUTHORED SCENARIO AND EXPECTED CASES
The following is the supplied reading/teaching/calculation record to represent in the companion. Preserve its particular content, examples, source references and unknowns. Wording about a future native implementation refers to that native task, not permission to omit this HTML companion.
# Lesson Study Template: Connect a Research Question to Classroom Evidence
Your team has a lesson ready, but the observation sheet still says “engagement” and “understanding.” Afterward, one observer may remember busy hands while another remembers a quiet student. Neither note tells you how a learner reasoned or which part of the lesson deserves another look.
A useful lesson study template gives the team a shared question, a plan for collecting relevant evidence, and a place to compare expectations with what actually happened. The packet below is a filled planning example with blank observation and conclusion fields. It prepares a cycle; it does not report a completed classroom study.
## Start with a question observers can follow
Lesson study brings a team through studying, planning, teaching and observing a research lesson, then reflecting on the evidence. The Lesson Study Group describes one team member teaching while others record student thinking and learning, followed by discussion of those records. [What Is Lesson Study?](https://lessonresearch.net/about-lesson-study/what-is-lesson-study-2/)
For this original example, use research question **RS01**:
> When we ask learners to show how their counts account for all items, what reasoning does their explanation make visible?
The proposed task uses eight paper tokens and two trays. Learners place one token in each tray per complete round and make as many complete equal rounds as possible. Four rounds produce four tokens in each tray, using all eight.
Confirm the actual class, relevant curriculum, materials, schedule and observation permissions before using the plan. The small task makes the protocol easy to inspect; it does not establish suitability for a particular class.
## Predict reasoning without filling in the results
Write possible explanations before the lesson so observers know what to watch for. Keep their status visible.
| Planning ID | Anticipated explanation—not an actual student quote | What the team would investigate |
| --- | --- | --- |
| P01 | “Four because half of eight.” | Does the learner connect four in each tray to all eight tokens, or only state a remembered result? |
| P02 | “Three each and two left.” | Does the learner recognize that the two remaining tokens permit one more complete round? |
Three in each tray accounts for six tokens. Two remain, so another round is possible. That arithmetic identifies a question for observation; it does not tell you why a particular learner would stop early.
The proposed teacher prompt is: **“How does your arrangement account for all eight?”** The team's hypothesis is that this question may elicit more explicit counting reasoning. Leave the finding blank until there is evidence to examine.
The Lesson Study Group treats the research lesson plan as a hypothesis and recommends collecting evidence relevant to its phases and goals, including observations, written work and lesson documentation. [Focus the Data Collection](https://lessonresearch.net/plan-step/focus-data-collection/)
## Assign coverage before the lesson
Use role IDs while the actual people are still unconfirmed. Agree on permitted case identifiers and work references under the school's record rules.
The proposed research-lesson flow is: present the eight-token task; allow an initial arrangement and explanation; ask the proposed prompt; invite a further explanation; then retain the permitted work references for debrief. Set actual timings with the team rather than inventing observation timestamps in advance.
| Proposed role | Coverage linked to RS01 |
| --- | --- |
| T01: teacher | Present the task; ask the proposed prompt; make the timing and wording available to observers. |
| O01: observer | Record initial arrangements and explanations, with time and task context. |
| O02: observer | Record explanations after the prompt, exact words or visible actions, work references and any additional support. |
| R01: debrief facilitator | Keep evidence, interpretation and revision proposals separate in the later discussion. |
Arrange coverage so the same permitted cases can be connected across phases. If that connection is missing, record the gap rather than treating unrelated before-and-after comments as one learner's change. Confirm whether one person can hold more than one role without leaving required evidence unobserved.
## Keep the observation log blank until observation
Use this original record structure for each event:
| Time | Permitted case ID | Phase | Exact observed words or action | Work reference | Teacher prompt or other support | Separate interpretation |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |
Record what you can substantiate before interpreting it. An arrangement with three tokens in each tray and two aside is observable. “Does not understand equal sharing” is an interpretation requiring more evidence.
Do not paste P01 or P02 into the log as if a learner said it. If no response was captured, distinguish “no response observed” from “observer missed this phase.” Neither automatically establishes failure. Preserve unexpected reasoning and cases that challenge the team's hypothesis.
## Debrief toward a defensible next question
The team's discussion should follow the evidence rather than rate the teacher. Complete these rows only after reviewing actual records:
| Debrief field | Entry |
| --- | --- |
| What initial reasoning was recorded? Include evidence references. | |
| What reasoning was recorded after the prompt for connected cases? | |
| How did actual reasoning compare with P01, P02 or an unanticipated approach? | |
| Which contrary cases, missing observations or additional supports limit interpretation? | |
| What can the team reasonably conclude about RS01? What remains uncertain? | |
| What revision is proposed, based on which evidence, for which next-cycle question? | |
A different explanation after a prompt is worth investigating. One before-and-after case alone does not establish that the prompt caused learning. A partner's explanation, a rearranged display or unrecorded support could also matter. Keep that limitation beside the proposed revision.
For example, if actual records eventually show that learners count the two remaining tokens but do not connect them to another round, the team could propose testing a more explicit “one in each tray” demonstration. That is a conditional revision idea, not a finding from this unrun example. The next cycle would need its own question and evidence plan.
Implement the local companion rather than returning a text-only plan. Preserve every numerical fixture and the distinction between illustrative expectations and actual evidence. Any native-runtime or classroom tests mentioned above remain tests to perform in the proper environment; do not mark them passed. Keep edits and practice responses in this open page only, without claiming persistent storage. Provide invalid/missing-input feedback and reset behavior that agree with this specific brief. Do not claim accessibility certification, learning gains, real approvals or test results that were not observed.
Review the protocol together
Keep the school's lesson plan and permitted actual records as the authoritative materials; the review does not collect observations or establish findings.
Bring the team back to the evidence references before deciding what to change in the next cycle.