Math // Data & Statistics

Reading tables

Complete, read, and interpret information in tables, including timetables

Ages
9 to 10
Type
Method
Builds on
2 topics
Leads to
2 topics
Standards
1 code

Quick check

Can the learner read a timetable — like a train or bus timetable — to find out when a journey leaves, arrives, and how long it takes?

Ask this to see whether the topic is secure.

Topic // Mastery

What mastery looks like

What a learner can do once this topic is secure.
  • Read a bus timetable to find the departure time for a particular stop
  • Complete a two-way table from given data about favourite sports by gender
  • Calculate how long a train journey takes using a timetable

Topic // Map

Where this fits

What to learn first and what this topic opens up, with the reason for each link. Required links come first.
  • RequiredMust come first
  • HelpfulHelps, but not essential

Before this

2 topics

You are here

Reading tables

Ages 9 to 10 // Method

Leads to

2 topics
  • Data & Statistics // Ages 11 to 13

    Frequency tables extend KS2 table interpretation to grouped numerical data

  • English // Reading Comprehension // Ages 10 to 11

    Cross-subject: drawing on information from multiple print/digital sources benefits from the ability to read and interpret tables

Topic // Research-informed

Teaching notes

From the Marble Skill Taxonomy. These notes have not been validated in classrooms, so treat them as a starting point for your own judgement.

The approach

For ages 9-10, teach children to read and complete real information tables — bus/train timetables and two-way tables (e.g. favourite sport by gender) — and to solve one- and two-step problems: find a departure time, compute a journey duration, complete a missing cell, compare two values. Two difficulties carry the teaching: tracking a value to the correct ROW×COLUMN intersection (dense grids invite off-by-one reading), and computing time DURATIONS by counting on in minutes across the hour rather than subtracting clock readings as if they were base-10 decimals. Keep every table anchored in an authentic purpose (catch the bus, plan the journey) so the numbers mean something.

Common misconceptions

  • Reading time as a decimal number: giving a journey duration as 0.70 or '2.23 hours' by subtracting or reading clock digits as base-10 rather than counting minutes in base-60
  • Reading off a single value when a difference or duration is asked ('how many more', 'how much longer') instead of computing it
  • Off-by-one-row/column reading: taking the value from an adjacent service or stop in a dense grid
  • In a two-way table, confusing a row/column TOTAL (a margin) with a single cell, or double-counting when categories overlap

Useful representations

  • A real bus/train timetable grid (services in columns, stops in rows) — the canonical structure for this age
  • A two-way table (e.g. sport × gender) with row and column totals shown
  • An empty number line or clock face for counting on the minutes of a duration across the hour
  • A finger/ruler trace from row and column to their intersection cell

Teaching practices

  • Track every value to the ROW×COLUMN intersection explicitly — finger on the row, finger on the column, meet in the middle — to defeat off-by-one-row/column reading in dense timetables
  • Teach durations by COUNTING ON in minutes across the hour (10:50 → 11:00 is 10 min, → 11:20 is another 20, so 30 min), using an empty number line or clock face — never by subtracting clock readings as if decimals
  • Confront the time-as-decimal habit head-on: when a child says a journey takes 0.70 or 2.23 hours, use an analogue clock to show 60 minutes in an hour so the digits after the colon are seen as minutes, not tenths
  • Underline the question words ('how long', 'how many more', 'how much later') so children compute the DIFFERENCE/DURATION asked for rather than reading a single value off the table
  • Read two-way tables by naming what each cell, row total and column total MEANS ('this cell is girls who chose football; this end number is all the girls') before doing any arithmetic
  • Anchor tables in an authentic task — catch the 8:40 bus, work out if you make the connection — so reading is purposeful rather than mechanical

Activities to try

  1. 1

    Live timetable with intersection highlighting

    Why it works: Reading tables is a doing skill on a 2D grid: values live at a row×column intersection, and time durations are counted in minutes across the hour, not subtracted as decimals.

    1. Use a real bus/train timetable (often services in columns and stops in rows, but check the headings because layouts vary) to find when a named service reaches a named stop.
    2. Track the stop-row with one finger and the service-column with the other, meeting at the intersecting cell. If a screen model is available, tapping a row and column can light up ONLY the intersecting cell so the off-by-one habit has nowhere to hide.
    3. Find a journey duration by counting on in minutes across the hour: 10:50 → 11:00 is 10 minutes, → 11:20 is another 20, so 30 minutes. If a duration tool is available, drag a marker along a minute-track and watch it tick across the hour.
    4. State out loud why you cannot simply subtract 11:20 − 10:50 and call it 0.70 — the digits after the colon are minutes out of 60, not tenths of an hour.
  2. 2

    Confront time-as-decimal with an analogue clock

    Why it works: The digits after the colon are minutes out of 60, not tenths of an hour, so durations must be counted in minutes, not read as decimals.

    1. When a journey duration has been found by subtracting clock times as if they were decimals (e.g. 11:20 − 10:50 written as 0.70, or '70 minutes'), look at an analogue clock and state how many minutes are in one hour (60).
    2. Find the correct duration in minutes by counting on from the start time to the end time across the hour on the clock face or an empty number line (e.g. 10:50 → 11:00 → 11:20 = 30 minutes).
    3. Try a journey that crosses the hour in the other direction too — e.g. a train leaving at 14:45 with a 40-minute journey: when does it arrive?
    4. Combine a lookup with a forward duration: if the next service is 25 minutes later than the one shown (say it leaves at 10:50), count on to find its departure time rather than adding digits.
  3. 3

    Complete and interpret a two-way table

    Why it works: A cell, a row total and a column total mean different things; 'how many more' asks for a difference between two values, not a single read-off.

    1. Before any arithmetic, name what each cell, row total and column total MEANS (e.g. 'this cell is girls who chose football; this end number is all the girls').
    2. Complete a missing cell in a two-way table of favourite sport by gender from the given data, checking the filled cell against its row and column totals. If a screen model is available, row and column totals can update live so a filled cell can be checked against its margins.
    3. Answer a 'how many more' question — underline the question words, point to BOTH values, and show the subtraction.
    4. Contrast with a plain 'how many' question so the difference between reading one value and computing a difference is explicit.

Topic // Standards

Curriculum standards

Codes for the curriculum statements this topic maps to. Each publisher owns its standard text.
The national curriculum in England: Key stages 1 and 2 framework document
Ma5/5.1b

Math // Data & Statistics