Reading Tables and Charts

One-sentence summary

Tables and charts display the data we collect in an organised way so we can read the information inside it more easily; to read them correctly we pay attention to rows, columns, axes and scale.

Why does it matter?

In the previous lesson we collected and cleaned data. But when all we have is a long list of numbers, it is hard to answer the question, “What is going on here?” This is exactly where tables and charts come in: they make the same data visible.

AI tools also work by reading data and finding patterns inside it. Before we trust a result an AI gives us, we need to be able to read the data that result is based on. Learning to read tables and charts helps us understand our own experiments and also helps us notice whether the charts other people (and AI tools) show us are honest or misleading.

Short definition: A table is an arrangement that places data into rows and columns. A chart shows the same data using shapes, lengths or lines.

Reading a table: rows and columns

A table is made of two basic parts:

• Row: A line that runs horizontally, from left to right. It usually describes one “thing” (one day, one student, one measurement).
• Column: A line that runs vertically, from top to bottom. It usually describes one “feature” (a date, a temperature, a count).

The first row is often the header row, and it tells us what each column means.

Example: A one-week reading log

The table below shows how many pages of a book a student read over five days.

| Day       | Pages read |
|-----------|------------|
| Monday    | 12         |
| Tuesday   | 8          |
| Wednesday | 15         |
| Thursday  | 0          |
| Friday    | 20         |

Reading this table, we can see:

• Header row: “Day” and “Pages read.” It tells us what each column is.
• Reading a row: In the “Wednesday” row, the page count is 15.
• Reading a column: Looking down the “Pages read” column, the largest value is 20 (Friday).
• Zero is a value: Thursday’s 0 pages does not mean the data is missing; it means nothing was read that day.

Example: Classroom temperature readings

We can build the same layout for a different topic. A class measured its morning and midday temperature:

| Day       | Morning (°C) | Midday (°C) |
|-----------|--------------|-------------|
| Monday    | 19           | 23          |
| Tuesday   | 18           | 24          |
| Wednesday | 20           | 22          |

Here there are two separate columns for two different measurements. Reading a row shows one day’s morning and midday values together. Reading a column lets us compare the morning values across all the days.

Chart types: bar and line

A table organises numbers; a chart turns them into a shape you can notice at a glance. We start with two basic chart types.

Bar chart

A bar chart shows each value as the height of a bar. The taller the bar, the bigger the value. It is ideal for comparing separate things.

If we draw the reading log above as a bar chart:

Pages read
20 |                        ████
15 |            ████        ████
10 | ████       ████        ████
 5 | ████  ███  ████        ████
 0 | ████  ███  ████   __   ████
   | Mon   Tue  Wed    Thu  Fri

By looking at the bar heights, we understand at a glance that the most reading happened on Friday and the least on Thursday.

Line chart

A line chart joins points with a line to show how a value changes over time. It is ideal for seeing rises, falls and ups and downs.

If we picture the midday classroom temperatures as a line chart, we can follow how the line goes up and down from day to day. A bar chart answers the question “which is bigger?” better, while a line chart answers “how is it changing?” better.

Axes, labels and scale

Reading any chart correctly depends on three parts:

• Axis: The two edges of the chart. The horizontal axis (left to right) usually shows *what we are measuring* (days, names), and the vertical axis (bottom to top) usually shows *how much there is* (pages, degrees).
• Label: The name of the axes and the chart. Without labels we cannot know what the numbers mean.
• Scale: The spacing between the numbers on the vertical axis. It should go up in equal steps, like 0, 5, 10, 15.

Before reading a chart, it is a good habit to always look at the labels and the scale first.

Drawing conclusions and watching for misleading charts

Drawing a conclusion from a chart

After reading a chart, we can draw a conclusion from it. Looking at the reading-log chart, we can say: “Reading dropped on Thursday and reached its highest point on Friday.” This is an honest observation based on the data.

But we must be careful. A chart only tells us the data it shows; it does not tell us why. We do not know why Thursday was 0; maybe there was a test that day. A chart shows “what” happened; we investigate the “why” ourselves. Guessing beyond the data means saying something the data never told us.

Watching for misleading charts

The same correct data can look completely different if the scale is changed. The most common tricks are:

• An axis that does not start at zero: If the vertical axis starts at 18 instead of 0, tiny differences look huge.
• An unequal scale: If the steps (0, 5, 100, 105) are irregular, the bars become deceptive.
• Missing labels: If an axis has no name, the chart can be twisted to mean anything.
• Too much decoration: 3D, colourful, moving graphics can hide the real numbers.

If a chart is trying to convince you of a conclusion very quickly, stop and look at the axes. An honest chart shows the data as it is, without exaggerating.

Hands-on practice

We can read tables by hand, but a computer can do the job for us quickly. The Python program below keeps the reading log in a list of dictionaries and works out the total, the average and the highest day. We are not training any AI model here; we are simply counting the data honestly.

# Weekly reading log (cleaned data)
log = [
    {"day": "Monday", "pages": 12},
    {"day": "Tuesday", "pages": 8},
    {"day": "Wednesday", "pages": 15},
    {"day": "Thursday", "pages": 0},
    {"day": "Friday", "pages": 20},
]

pages = [entry["pages"] for entry in log]
total = sum(pages)
average = total / len(pages)

# Find the day with the most reading
best = max(log, key=lambda entry: entry["pages"])

print("Total pages:", total)
print("Daily average:", average)
print("Most reading:", best["day"], "-", best["pages"], "pages")

This program prints:

Total pages: 55
Daily average: 11.0
Most reading: Friday - 20 pages

In your own attempt, change the numbers and watch how the average changes. For example, if you make Thursday 10 instead of 0, how does the average change?

Common mistakes

Treating the header row as data

The first row of a table usually holds the column names. If we count it as a measurement, the result comes out wrong.

Judging without reading the axis

A bar looking tall does not mean anything on its own. Does the scale start at 0, and what is the unit? A conclusion drawn before looking at the axis is misleading.

Choosing the wrong chart type

Showing change over time with a bar chart, or comparing separate things with a line chart, makes reading harder. Pick the chart that fits the question.

Confusing “what” with “why”

A chart can show that a value dropped, but it does not show why. The reason should be investigated by looking at the data, not made up.

Safety note

• Protect personal data. When you make a table or chart, do not use personal information such as your friends’ names, addresses or phone numbers. Show measurements with anonymous labels like “Student 1, Student 2.”
• Be careful with online tools. Do not upload personal information about yourself or others into websites or AI tools that draw charts or analyse data. Use these tools with an adult nearby and follow the platform’s age rules.
• Question the AI. AI is a tool that finds patterns in data; it is not conscious and it can be wrong. The chart or result it gives is only as good as the data behind it. If the data is incomplete or biased, the result will be wrong too. Always verify important results with your own eyes.

Lesson summary

• A table places data into rows and columns; the first row is usually the header row.
• A bar chart is good for comparing separate things, and a line chart is good for showing change over time.
• To read a chart correctly, we should look at the axes, labels and scale first.
• A chart shows “what” happened; finding out “why” is up to us.
• A chart with a tampered scale or labels can make even correct data look misleading.

Check questions

1. What is the difference between a row and a column in a table?
2. Which chart type is better for comparing separate things (for example, the page counts of different days)?
3. What do the “axis”, “label” and “scale” of a chart do?
4. Name two situations that can make a chart “misleading”.
5. In the reading log above, what is the total number of pages read, and on which day was the most read?

Answers

1. A row runs horizontally and usually describes one thing (a day, a person); a column runs vertically and usually describes one feature (a date, a count).
2. A bar chart is better for comparing separate things.
3. The axis is the two edges of the chart and shows what/how much we are measuring; the label is the name of the axes and the chart; the scale shows the equal steps in which the numbers on the vertical axis increase.
4. Examples: the vertical axis not starting at 0, the scale steps not being equal, a missing axis label, or too much decoration.
5. The total is 12 + 8 + 15 + 0 + 20 = 55 pages; the most was read on Friday, 20 pages.

Source and verification note

For “Reading Tables and Charts”, verification focuses on whether the relationship between Reading a table: rows and columns and Example: Classroom temperature readings remains consistent across examples. Datasets in this module are small and educational; real personal data should not be used. An AI result should be evaluated not only for accuracy but also for data balance, error distribution and explainability.

Next lesson

What Is a Pattern?