Milestone Teachers · team planning record

Next Lesson Sprint

A four-week teaching-team record that keeps a shared instructional move, observed response, and next decision visible.

Plan one skill, try a teaching action, look at what the team observed, and decide the next move. Counts describe the learners checked in that week; they do not establish causal growth.

Privacy boundaryUse a team label, not people’s names. Do not enter student names, initials, identifiable work, or disability information. This page keeps entries only in this browser tab’s memory; it does not use local storage or send anything automatically.

Import saved JSONDraft · complete the record

DRAFT — incomplete or invalid fields are marked.

Sprint focus

Team label for example, “Grade 5/6 fractions team” Single skill one teachable focus Observable learning criterion what will count as meeting it? Teaching action the move the team will try Role responsible a role, never a person’s name Kickoff dateReview date

End-of-sprint decision

Team decisionRationale what the team saw and why this is the next move

Use this in the meetings

Kickoff prompt

“What would we be able to see or hear if a learner met this criterion, and what will each of us do during the teaching action?”

Agree on one small, observable check.
Decide when the check will happen.
Name the team role that will bring the record back.

Review prompt

“What did we notice among the learners we checked, what remains uncertain, and what teaching step best fits that evidence?”

Read session completion separately from learner response.
State the count checked before interpreting the count meeting the criterion.
Choose Continue, Adapt, or Gather more evidence—and write why.

“Load synthetic example” inserts invented Grade 5/6 fractions demonstration data only. It is not customer, classroom, or outcome evidence. Export a JSON file to resume the sprint later; importing validates this tool’s saved-record shape before replacing anything on screen.