PrepShorts · Study sheet · Class 6 Mathematics · Chapter 4, Data Handling and Presentation
Chapter 4 · Data Handling and Presentation
Tally marks and frequency: organising data so it can be read
This video could not be loaded. Reload the page to try again.
Sign in with Google9 min.
Keep your place in this chapter — sign in, it’s free.Sign in
A tally mark is not a tidier numeral. It is the notation you need when the data is walking past you and will not wait — one stroke, no reading, no crossing out. And the crossing stroke on every fifth is not decoration: it is what lets the record be read later without being counted again.
The idea
A tally stroke is not a lazy way of writing a numeral — it is the one notation that works when the data is still arriving and you get no second pass. Bundling the strokes in fives is what makes such a record readable without recounting it, and the number it finally yields has its own name, frequency, because it answers "how many of these" rather than "how much". Organising is therefore not tidying: it is the step that converts a record into something a question can be asked of, and each way of organising settles what you can still ask. Sorting the shoe sizes keeps all twenty-seven measures and loses only the order they arrived in; the frequency table keeps the counts and loses who chose what.
What you should be able to do
- Record a running count using tally marks, bundling every fifth stroke
- Read a bundled tally group as a number without recounting the strokes
- Complete a frequency table from tally marks and state each frequency
- Define frequency as the count of occurrences of a value or category
- Explain what a frequency table can be used for and what it can no longer tell you, using the book's own sweets question
- Arrange a set of measures in ascending order and read off the largest, the smallest, and how many take a given value
- Answer "how many are greater than 4?" from ordered data and say why the ordering made it quick
- Choose between an ordered list and a frequency table for a given question, and justify the choice
Words to know
| Term | Definition in one line | First introduced |
|---|---|---|
| tally mark | one stroke standing for one observation, with every fifth stroke drawn across the previous four | printed in this chapter, p.76 |
| frequency | the count of how many times a value, measure or observation occurs | printed in this chapter, defined on p.77 |
| frequency distribution table | a table listing each category or value beside its frequency | printed in this chapter, p.95 |
| ascending order | arranged from smallest to largest | printed in this chapter, p.77 |
| category | one of the named groups a data value can fall into | printed in this chapter, p.83 |
| data | anything recorded about things that tells you something about them | Turning an argument into a question you can settle with data; defined p.74 |
| bundle of five | the crossed group of five tally strokes — the explanation's name for it; the book describes the crossing but gives the group no noun | an added term; not printed in this chapter |
| one-pass counting | counting things as they arrive, with no chance to go back — the explanation's name for the situation tallies are built for | an added term; not printed in this chapter |
Where people slip up
- "Tally marks are just a childish way of writing numbers." They exist for a situation numerals handle badly — a count that has to be updated while you are looking somewhere else. The crossed fifth stroke is a deliberate design feature, not decoration.
- **"A crossed bundle means five more."** The crossing stroke is the fifth. A bundle plus one loose stroke is six, not seven. This is the single most common slip when reading the printed sweets table.
- "Frequency means how often something happens in time." In this chapter it means the count of occurrences of a category or value. Nine students chose gulab jamun; nothing in that is about time.
- "Once you have the frequency table you have all the data." The book asks the killing question itself on p.77: the sweets table cannot say which child wanted which sweet. Summarising loses information — deliberately, and you should know which information you have chosen to lose.
- "Ordering the data changes it." Sorting the twenty-seven shoe sizes adds nothing and removes nothing. It only puts equal values next to each other, so the counting stops requiring you to scan the whole board each time.
- "'Larger than 4' includes 4." It does not. Fifteen students, not twenty-four, wear a size above 4 — a place where a careless read of ordered data goes wrong quietly.
- "There is one right way to organise data." The book's own Math Talk asks for other arrangements. Which organising is right depends on the question.
Ask your teacher a person
Your teacher reads this and writes back, usually within a day. For an instant answer, use Ask the video in the sidebar.
Your class sees the question and the answer. Only your teacher sees that it was you.
No questions on this topic yet.
Worked answers to this chapter’s exercises · this video explains Figure it Out · 2 Q1, Figure it Out · 2 Q2, Figure it Out · 3 Q1, Figure it Out · 3 Q2, Figure it Out · 3 Q3, Figure it Out · 3 Q4, Figure it Out · 6 Q3, Figure it Out · 6 Q4
Transcript1,276 words
A teacher wants to buy sweets for the class. Not a random assortment — the right number of each kind. So she asks everybody which sweet they would like. Five kinds are on offer. And the answers come back one at a time. Doughnut. Ice cream. Ice cream. Cookie. Brownie. Chocolate cake. Ice cream. Now she has to record those as they arrive, because thirty-eight children are not going to wait while she thinks.
Which turns out to be a genuinely different problem from counting things that sit still and let you. And it has a genuinely different solution. Suppose you try to keep running totals in numerals. Doughnut, one. Ice cream, one. Ice cream again — so cross out the one, write two. Cookie, one. Brownie, one. Chocolate cake, one. Ice cream — cross out the two, write three. You can already feel where this is going.
Every single answer means finding the right row, reading a number, crossing it out, and writing a new one. Four operations per child, on a page that is getting messier, while somebody is talking to you. And if you lose your place, you cannot go back. That child has already answered and walked off. So here is the notation, and it is beautifully simple. One stroke for one answer. That is the whole of it.
Doughnut? Draw a stroke in the doughnut row. Ice cream? Draw a stroke in the ice cream row. No reading, no crossing out, no arithmetic at all. One mark, and you are ready for the next child. But there is one more piece, and it is the clever bit. Every fifth stroke is not drawn upright. It is drawn across the other four. So the marks come in bundles of five, tied off as you go along.
And now ask why that matters, because it is certainly not decoration. Here is a row with one bundle and one loose stroke. You do not count that. You see five, and you see one, and it is six. Here is a bundle and four loose ones. Five and four. Nine. Now compare that with nine upright strokes in a row. Try to read nine strokes at a glance, and you will count them — and you will sometimes get eight.
The bundling means the record can be read without being recounted. Which is the entire reason for that crossing stroke. It buys you accuracy later, for free, at the moment of writing. Right. Your book prints the finished tallies, fills in two of the numbers, and leaves three of them for you. Doughnuts: one bundle and one loose. Six — that one is printed. Chocolate cake: one bundle and four loose. Nine — also printed.
Now the three blanks. Ice cream: two bundles and three loose. Ten and three. Thirteen. Brownies: three loose strokes and no bundle at all. Three. Cookies: one bundle and two loose. Seven. And now the table can be read in a single look. Ice cream leads, with thirteen. Before we go on, do the check that almost nobody remembers to do. Add the five numbers up. Six, plus nine, plus thirteen, plus three, plus seven.
Thirty-eight. Now — is thirty-eight the size of the class? If it is, then every child has been recorded exactly once, and you can trust the table. If it came to thirty-seven, somebody was missed. If it came to thirty-nine, somebody got two strokes. Your book does not print this sum. It is worth doing every single time, because it is the only check the table can give you. Now, the number in that last column has a name, and your book puts it in a box of its own.
Frequency. The frequency of a value is simply how many times it turned up. The frequency of chocolate cake is nine. The frequency of brownies is three. And it is worth noticing what this word is for. It answers how many of these — not how much. Nine chocolate cakes has a frequency of nine. Nine kilograms of chocolate cake does not have a frequency at all. Counting things, rather than measuring stuff. That distinction runs through the whole of data handling.
And now the question your book asks next, which is sharper than it looks. Is this table enough to hand each sweet to the child who asked for it? And no. Obviously not, the moment you say it out loud. The table says thirteen children want ice cream. It does not say which thirteen. That information was in the original list of answers — and the moment you turned it into tallies, you threw it away.
Which was the right thing to do. The teacher's job was to place an order, and for that job the table is perfect. But it is worth being precise about it. Organising data is not tidying up. Every way of organising keeps some questions answerable and closes others off. Let me show you that with a second data set, organised a different way. Twenty-seven shoe sizes, written on a board in the order they were measured.
Four, five, three, four, three, four, five, five, four, and so on, for twenty-seven numbers. Now, these are not categories. They are measurements, and measurements have an order — a five really is bigger than a four. So there is something available here that was not available with the sweets. You can sort them. Put them in ascending order, smallest first, and look what falls out straight away. Three, three, three, four, four, four, and on up to a single seven right at the end.
The smallest is three. The largest is seven. You read both off the ends without counting anything at all. How many wear size five? They are all together now, so you count one block. Ten. And how many wear larger than four? Everything to the right of the fours. Ten fives, four sixes, one seven. Fifteen. That last question would have been horrible on the unsorted list. You would have had to scan all twenty-seven and keep a running count.
On the sorted list it is one cut and one addition. So compare the two things we have just done. With the sweets we made a frequency table. Five rows, five numbers. We kept the counts, and we lost who chose what. With the shoe sizes we sorted. We still have all twenty-seven measurements — not one of them was thrown away. What we lost is the order they arrived in.
Two different organisings. Two different things given up. And that is what to take from this section. There is no neutral way to organise data. Every arrangement makes some questions easy and some questions impossible — and you want to know which, before you choose. So go and build one. Your book gives you three, and they get better as they go. One. Count the trees on your walk to school. Kinds of tree in the first column, tallies in the next.
Two. That letter count in a piece of newspaper. Five letters — and you will need the bundles, because e will run into the hundreds. Three, and this is the best of them. Roll a die thirty times and tally the six faces. Then read off which face came up most often, which least, and which ones tied. And notice that you cannot predict that table. Nobody can. Which makes it the first genuinely honest data collection in the chapter. Nobody knows the answer before you start — including your teacher.
Next time, we stop writing the counts down, and start drawing them.
Where this fits
Taken from the notes each video was made from, not from the reading order — these are the ideas this one rests on and the ones that later rest on it.
Builds on
- Turning an argument into a question you can settle with dataClass 6 · Ch 4, Data Handling and Presentation
Comes up again in
- Pictographs, and why the scale has to be statedClass 6 · Ch 4, Data Handling and Presentation
- Reading a bar graph: what length is standing forClass 6 · Ch 4, Data Handling and Presentation
- Drawing a bar graph, and choosing a scale that fitsClass 6 · Ch 4, Data Handling and Presentation