After Telling Time: Elapsed Time and Reading a Daily Schedule

Why elapsed time is a separate skill from telling time

Reading a clock is a lookup: what does this position mean? Elapsed time is arithmetic: how far apart are these two positions? A child can read a clock perfectly and still freeze on 'if it's 3:15 now and the movie starts at 4:00, how long is the wait' — that's a subtraction problem wearing a clock costume.

Don't assume clock reading fluency means elapsed time is ready to go. Treat it as a new skill that happens to reuse a familiar tool.

Start with a number line, not the clock face

Before jumping to the dial, draw a simple line from one time to another and count the gap in easy jumps — hour by hour first, then filling in minutes. This makes the 'distance between two points' idea visible in a way the round clock face doesn't.

Once that clicks, moving back to the actual clock face and asking the same question feels like applying a known idea to a new picture, not learning from scratch.

Use a printed daily or weekly schedule

A simple printed timetable (wake-up, breakfast, school, dinner, bedtime, each with a time) gives elapsed-time practice a real context: 'how long between breakfast and school?' feels different from an abstract worksheet question.

This is also where reading a schedule becomes its own skill — scanning down a list of times to find one entry, or comparing two rows, is a different visual task than reading a single clock face.

Common mistakes and how to catch them

The most frequent error is treating clock math like base-10 math — subtracting 3:15 from 4:00 the way you'd subtract 315 from 400. Watch for this specifically and walk through why 60 minutes make an hour, not 100.

If a child consistently gets elapsed time wrong by exactly an hour, they're likely miscounting which hour mark they started from — a sign to go back to counting the gap hour by hour before adding minutes.