Choral counting with time, and why 60 isn't 100

Counting time 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 a round one, matters here too. But time has a structural quirk none of DotSense's other choral tools do: it doesn't regroup by tens. Sixty seconds make a minute and sixty minutes make an hour — a base-60 system riding inside a track that otherwise counts by ones. Watching the seconds climb 55, 56, 57, 58, 59 and then roll the minute over to 0 (not 60) is exactly the moment a class has to notice that this "counting by ones" doesn't behave like counting by ones anywhere else in math — directly relevant to CCSS 2.MD.7 (telling and writing time to the nearest five minutes) and 3.MD.1 (telling time to the nearest minute and measuring time intervals in minutes — the foundation 3.MD.1's elapsed-time word problems build on, though that word-problem step is beyond what this counting routine does). Counting backward through that same boundary — a minute breaking back apart into 59 seconds instead of borrowing a ten — is just as informative to watch as building it forward.