The 12-Day Fraction Calendar vs. the Number-Line Gap
Ms. Okafor teaches fourth grade at a K–5 school with 24 students: 5 receive special education services in reading and math, 4 are English learners at WIDA level 3, and 2 have behavior intervention plans. The district pacing calendar allots 12 instructional days to the fraction unit, and the grade-level team gives a common unit test on day 13. Her pre-assessment shows 18 of 24 students cannot order fractions with unlike denominators, 9 still judge fraction size by the numerator alone, and only 6 can place 3/4 accurately on a number line. The pacing calendar's next unit, decimals, assumes number-line fluency. The principal has asked teams not to fall behind the calendar, and Ms. Okafor's grade-level colleagues plan to follow it exactly.
1. Using the pre-assessment evidence, decide what Ms. Okafor should prioritize across the 12 days and what she should cut or compress. Name one risk of your choice and what evidence would make you revise it.
Read the worked answer
Decision: Spend days 1–7 on fraction magnitude and the number line, days 8–11 on equivalence and ordering with unlike denominators, and day 12 on a short review aligned to the common test's item stems. Defer formal addition and subtraction of unlike denominators to a re-entry point in the decimal unit or small-group time.
Reasoning from evidence: Nine students still use numerator-only reasoning. That is a magnitude misconception, and more ordering worksheets will not dislodge it - only comparing lengths or positions on a line will. Eighteen of 24 cannot order unlike denominators, so the number line, not the algorithm, is the highest-leverage target. It is also the stated prerequisite for decimals, which means the calendar's own logic supports spending time there rather than racing to the algorithm.
Risk: The day-13 common test will include unlike-denominator computation, and her class will underperform on those items, which is visible to colleagues and the principal. Mitigation: tell the team in advance which items fall outside her class's sequence, and bank that data as a pre-teach before the grade-level re-assessment.
What would change the call: if the day-4 checkpoint shows 20 or more students correctly placing and comparing benchmark fractions on a number line, the magnitude gap is smaller than the pre-assessment suggested and she can pull unlike-denominator computation back into days 8–11.
2. Identify two checkpoints she should build into the unit, what evidence at each would trigger a change of plan, and how she would use the 5 students with IEPs and 4 English learners as a design constraint rather than an afterthought.
Read the worked answer
Checkpoint 1 (end of day 4): a 4-item number-line card sort given as an exit ticket. Trigger: if fewer than 18 of 24 place 3/4 and 5/8 correctly, she does not move to equivalence on day 5 - she adds a day of benchmark comparison and pushes ordering to day 9. If more than 22 are correct, she compresses days 5–7 by one day and regains time.
Checkpoint 2 (end of day 8): students explain in writing why 2/3 is greater than 3/5 without common denominators. Trigger: if fewer than 15 give a magnitude-based reason, the ordering algorithm is being applied without understanding and the day-12 review becomes a re-teach of comparison rather than test practice.
Design constraint, not afterthought: the 4 English learners need the comparison language (greater than, less than, closer to one-half) pre-taught with visuals before it is used in discussion, or their exit-ticket scores will measure vocabulary rather than fraction sense and corrupt both checkpoints. The 5 students with IEPs should have the number-line work as their core objective with reduced item counts, not a parallel easier topic - otherwise the checkpoint data will show success that does not transfer to the ordering task. Both groups' checkpoint performance should be disaggregated before she decides the day-9 plan, since a class average can hide a subgroup that has not moved.