Choral counting with decimals, and why crossing one whole matters

Counting by tenths or hundredths uses the same accumulate-don't-erase choral counting routine as every other DotSense count track — Franke, Kazemi & Turrou's Choral Counting & Counting Collections shows that a structured, persistent record is what lets a class notice pattern instead of just reciting, and Kathy Richardson's Developing Number Concepts is why counting forward and backward from any start value (not just from zero) matters just as much with decimals as with whole numbers. But decimals carry a specific, well-documented misconception that whole-number counting never surfaces: Steinle & Stacey's longitudinal research on decimal notation found students who judge 0.45 as bigger than 0.8 — "longer is larger" thinking, applying whole-number place-value logic (45 has more digits than 8, so it must be more) to a place-value system where it doesn't hold. Watching the count move steadily through 0.7, 0.8, 0.9, 1.0, 1.1 — the tenths ticking upward one at a time, then the value itself passing straight through a whole number and continuing to grow — directly contradicts that belief, since 1.0 obviously comes right after 0.9 even though it "has fewer digits." This is exactly the reasoning CCSS 4.NF.6 and 4.NF.7 ask for: representing tenths and hundredths as decimals and comparing them by reasoning about their size, not by digit-counting, building on the tenths-to-hundredths equivalence in 4.NF.5. This tool stops at hundredths on purpose — the misconception is fully exercised there, and going further would trade clarity for a decimal place most K–3 and early intervention classrooms aren't using yet.