Plotting points in the first quadrant

Plotting and reading ordered pairs in the first quadrant is a procedure built on the coordinate convention: x before y, both counted from the origin along numbered gridlines. Secure the convention as a fixed rule of movement ('along the corridor, then up the stairs'), have children both plot given pairs and read plotted points back, then graph real data pairs (e.g. time vs distance) so each coordinate becomes a meaningful statement about a situation rather than a bare dot. Interpreting a point in context is part of the objective, not an add-on, and is what separates fluent plotting from mechanical dot-placement.

• Reversing the coordinates — plotting (a,b) as if it were (b,a), going up before across
• Counting the squares rather than the numbered gridlines, landing one place off
• Assuming one square always equals one unit and ignoring an axis scaled in twos or fives
• Treating a plotted point as just a dot, unable to say what its coordinates mean in the given scenario

• First-quadrant coordinate grid with clearly numbered axes and a marked origin
• 'Corridor then stairs' / 'along then up' movement metaphor for the x-then-y order
• Data table paired with its plotted graph (e.g. time in column 1, distance in column 2) so each row becomes a point
• Journey/time-distance line built from plotted points, linking each dot to a moment in a story

• Rehearse the x-before-y convention as a fixed sequence of movements from the origin ('across, then up') before any data work, so the ordered pair is read as a route, not two loose numbers
• Insist children count along the numbered lines/gridlines, not the squares between them, to pre-empt the off-by-one error
• Move quickly from plotting bare pairs to graphing real data pairs (time vs distance, cost vs quantity) and asking 'what does this point tell us?' so coordinates carry meaning
• Use grids whose axes are scaled in steps other than one (twos, fives) once the basic convention is secure, so children read the scale rather than assuming one-square-equals-one
• Have children both plot (given the pair, mark the point) and read (given the point, state the pair) in the same session — the two directions expose different errors