
Data Handling and Representation
Every question in this topic starts the same way: you're handed a messy list of raw data and asked to do something useful with it. The skill being tested isn't arithmetic — it's judgement. Can you organise the mess into a table without miscounting? Can you pick the right picture for the data type in front of you? And can you read that picture back correctly, including spotting when there's a tie for the mode or a class interval with an odd width? Examiners recycle these exact traps every year.
Overview: The Shape of This Topic
Data handling in MYP 2 is a pipeline: raw data → organised table → visual display → interpretation. Every subtopic below is one link in that chain. Get the organisation step wrong (miscount a tally, misclassify discrete vs continuous) and every step after it is wrong too, even if your arithmetic is perfect.
- Raw data is just a list — hard to spot patterns in, easy to miscount.
- Frequency tables and tally charts organise raw data into counts.
- Bar charts, line graphs and pie charts turn those counts into pictures suited to different purposes.
- Stem-and-leaf diagrams and dot plots are the middle ground: organised like a table, but no individual value is lost.
- The whole topic hinges on correctly identifying whether your data is discrete, continuous, or categorical — that single decision drives every choice after it.
The shape of the chapter
Command terms examiners use in this topic
| Command term | What it demands | AO | Mark-earning move |
|---|---|---|---|
| State / Identify | Give a short, direct answer — a value, category or feature — with no working required. | Criterion A | Naming the wrong feature (e.g. giving a frequency when asked for the value itself) forfeits the mark even if your counting was correct. |
| Construct / Complete | Build a full, correctly labelled table or diagram from raw data. | Criterion B | Missing tally marks, an unlabelled axis, or no key on a stem-and-leaf loses a mark even when your frequencies are right. |
| Calculate | Carry out an arithmetic procedure and give the numeric result. | Criterion B | Markers want to see the method (e.g. total − known values); a bare final answer with no working can lose the method mark if it's wrong. |
| Compare | State how two values or categories relate, using the data as evidence. | Criterion D | Just restating both numbers side by side without saying which is bigger and by how much/what factor earns zero. |
| Explain | Link a feature of the data to a real consequence or decision, using 'because'. | Criterion D | Describing what the table shows without saying how it helps the decision scores no marks — the causal link is the mark. |
Key point
Frequency Tables and Tally Charts
A raw list of 10, 20 or 30 responses is unreadable at a glance. A tally chart fixes that by recording one stroke per occurrence as you go through the data; a frequency table then converts those strokes into a clean count per category or value.
- Tally marks are grouped in fives: four vertical strokes, then the fifth drawn diagonally across them — this makes counting large frequencies fast and far less error-prone than counting single strokes one by one.
- For categorical data (flavours, colours) the categories are the labels themselves; for numerical data with only a few repeated values (items bought: 2,3,4,5) the values themselves become the rows.
- When numerical data has many different values (25 test scores from 34 to 95), listing every single value would need dozens of rows — instead group values into equal-width class intervals (e.g. 30–39, 40–49, …) and tally into those bands.
- Always sum the frequency column at the end and check it equals the total number of data items — this single check catches most tallying errors before you lose marks.
- Raw data
- Data exactly as collected, before any organising — usually just a list.e.g. 3, 5, 2, 5, 3, 4, 5, 3, 2, 4
- Tally mark
- A single stroke recorded for each occurrence of a value, grouped in bundles of five for fast counting.
- Frequency
- The number of times a particular value or category occurs in the data set.
- Frequency table
- A table listing each value/category alongside its frequency, built from a tally chart.
- Class interval
- An equal-width band of values (e.g. 40–49) used to group numerical data that has too many distinct values to list individually.
Worked example
Building a tally chart from scratch
Worked example
Mode from a frequency table — and the tie examiners test
Worked example
Grouped frequency table from continuous-looking data
Common mistake
Counting tally strokes one at a time instead of grouping them in bundles of five.
Consequence: Large frequencies get misread (e.g. mistaking |||||||| for 9 instead of 8) — this loses the accuracy mark even when the data was understood correctly.
Fix: Always draw the fifth stroke of every group diagonally across the previous four, then count in fives plus any leftover single strokes.
Examiner tip
Key takeaways
- Tally in groups of five, straight through the data in order — never by re-sorting first.
- A frequency table's final column total must equal the number of data items — use this as an automatic check.
- Modes and modal classes can tie — always scan every row before answering, don't stop at the first high value you meet.
- For numerical data with many distinct values, group into equal-width class intervals — but verify the last interval really is equal width before relying on it.
Bar Charts, Line Graphs and Pie Charts
Once data is organised in a frequency table, the next decision is which picture to draw — and this decision is examined directly, not just the drawing itself.
- Bar chart: separate bars with visible gaps, one per category, height equal to frequency — used to compare sizes between distinct categories.
- Line graph: points plotted and joined with straight segments, x-axis usually time or sequence — used to show a trend or change.
- Pie chart: a full circle split into sectors, each sector's angle proportional to that category's share of the total — used to show proportion of a whole, not raw counts.
- The gap between bars in a bar chart is not decorative — it signals the data is separate/categorical, unlike a histogram (continuous grouped data) where bars touch.
Bar chart of items bought
Categories on the x-axis, frequency on the y-axis, visible gaps between bars.
Line graph of a weekly trend
Points joined by straight segments show the trend across the week.
Pie chart of favourite flavours
Sector angle is proportional to each flavour's share of the 30 students surveyed.
Pie chart sector angle
The angle for one category's sector, out of the full 360° circle.
- — the count for that one category
- — the sum of all frequencies (the whole data set)
All sector angles calculated this way must add up to exactly 360° — use that as a built-in check.
The same ratio expressed as a percentage instead of an angle — often asked for alongside or instead of the angle.
Worked example
Finding a missing frequency and comparing proportions
Bar chart vs line graph vs pie chart
| Feature | Bar Chart | Line Graph | Pie Chart |
|---|---|---|---|
| Best data type | Categorical or discrete counts | Continuous data over time/sequence | Categorical parts of one whole |
| What it shows | Compares sizes between separate categories | Trend or change over time | Each category's share of the total |
| Shape/axes | Two axes; visible gaps between bars | Two axes; points joined by straight lines | No axes — a circle split into sectors |
| Common construction error | Bars drawn touching (implies continuous data) | Joining points that shouldn't be connected | Angles that don't sum to 360° |
Common mistake
Drawing bar chart bars touching each other with no gaps.
Consequence: This signals confusion between categorical/discrete data (bar chart) and continuous grouped data (histogram) — costs a construction mark even if the heights are correct.
Fix: Always leave a visible, equal gap between every bar in a bar chart; only histograms have touching bars, and histograms aren't part of this subtopic.
Key takeaways
- Bar chart = compare separate category sizes; gaps between bars are compulsory.
- Line graph = show a trend across time/sequence; only join points that are genuinely sequential.
- Pie chart = show proportion of a whole; sector angle = (frequency ÷ total) × 360°, and all angles must sum to 360°.
- 'Compare' answers need direction and magnitude ('more/less popular, by roughly how much') — not just two numbers side by side.
Stem-and-Leaf Diagrams and Dot Plots
A grouped frequency table is efficient but loses information — once 45 and 49 are both filed under '40–49' you can't get the exact values back. A stem-and-leaf diagram keeps every original value visible while still organising the data by size.
- Stem = the leading digit(s) of a number (e.g. the tens digit); leaf = the final digit.
- Every stem-and-leaf diagram needs a key, e.g. 'Key: 6|4 means 64' — without it the diagram is meaningless to anyone else.
- An ordered stem-and-leaf lists the leaves in each row from smallest to largest — this is what lets you read off the median and mode directly by counting.
- Dot plots stack one dot per data value directly above a number line — best for a smaller range of simple discrete values (like quiz scores from 4 to 9), where the tallest stack of dots is instantly visible as the mode.
- Stem
- The leading digit(s) of a data value, written once per row on the left of a stem-and-leaf diagram.
- Leaf
- The final (units) digit of a data value, written in the row matching its stem.
- Key
- A statement (e.g. '6|4 means 64') that tells the reader exactly how to interpret stem-leaf combinations.
- Ordered stem-and-leaf diagram
- A stem-and-leaf diagram where leaves in every row are arranged from smallest to largest — required for reading off median/mode directly.
- Dot plot
- A display with one dot per data value stacked above a number line, showing frequency as stack height.
Stem-and-leaf diagram of test scores
Stems are tens digits (3 to 9); leaves are ordered within each row.
Worked example
Building an ordered stem-and-leaf diagram and reading the median
Remembering stem vs leaf
Leaf = Last digit
The leaf is always just the final (units) digit of the number; everything before it — however many digits — is the stem.
Common mistake
Writing leaves in the order they appear in the raw data instead of sorting each row afterwards.
Consequence: Makes it impossible to correctly read off the median or mode by counting, and loses construction marks whenever the question specifically asks for an 'ordered' stem-and-leaf diagram.
Fix: After entering all leaves in a first pass, go back row by row and rewrite each stem's leaves in ascending order before the diagram is considered finished.
Key takeaways
- Stem-and-leaf diagrams keep every individual value visible while still organising by size — unlike a grouped frequency table.
- A key is compulsory — without it, no one (including the marker) can decode the diagram.
- Leaves must be re-sorted within each row for the diagram to count as 'ordered' and for median/mode to be read off reliably.
- Dot plots suit a small range of simple values (like quiz marks 4–9); stem-and-leaf suits larger multi-digit values (like test scores 34–95).
Choosing the Best Data Representation
Examiners regularly hand over raw data and simply ask 'which representation would you use, and why?' — this tests judgement, not drawing skill. The answer always comes down to three questions: how many categories/values are there, is the data counted or measured, and do you need to preserve every individual value or just the overall pattern?
- Few categories, comparing sizes → bar chart. Few categories, showing share of a total → pie chart.
- Data changing over time or in sequence → line graph, because joining the points reveals the trend/direction.
- Numerical data where every value still matters → stem-and-leaf diagram or dot plot, not a grouped frequency table.
- Large numerical range with too many distinct values to list → grouped frequency table, to simplify without needing to show every value.
Data situation → best representation
| Situation | Best representation | Why |
|---|---|---|
| Comparing counts across a few separate categories (e.g. favourite flavours) | Bar chart | Bars side by side make size differences easy to compare visually |
| Showing how a whole splits into parts (e.g. % share of votes) | Pie chart | Sector angle directly represents each category's share of 360° |
| Data changing over time or in sequence (e.g. temperature each day) | Line graph | Joining points shows the direction and rate of change |
| Numeric data set where every individual value still matters | Stem-and-leaf diagram or dot plot | Organises by size without losing any individual data value, unlike a frequency table |
| Large numeric range with many distinct values | Grouped frequency table | Reduces dozens of unique values into a manageable number of class intervals |
Frequently confused
| Concept A | Concept B | The distinction that matters |
|---|---|---|
| Bar chart | Pie chart | Bar chart compares actual sizes/counts between categories side by side; pie chart shows each category's share of one whole total — you cannot read an exact count off a pie chart without working backwards from angle/frequency ratios. |
| Stem-and-leaf diagram | Dot plot | Stem-and-leaf keeps multi-digit values organised by place value (good for larger numbers, e.g. 34–95); dot plot stacks a dot per value above a single number line (best for a small range of simple values, e.g. quiz scores 4–9). |
Examiner tip
Real-world application
Key takeaways
- Always name the specific data feature (category count, counted vs measured, need to preserve individual values) that justifies your chosen display.
- Bar chart ≠ pie chart: one compares sizes, the other shows proportion of a whole — they answer different questions from the same data.
- If individual data values matter, prefer stem-and-leaf/dot plot over a grouped frequency table, which discards them.
Types of Data: Discrete and Continuous
Before choosing any display, you have to classify the data correctly — and this is tested directly because it isn't as obvious as it looks. 'Test score out of 100' feels like it could be anything, but it's actually discrete, because you can't score 72.5 on a test marked in whole numbers. 'Height of a plant in cm' genuinely is continuous, since any decimal value is possible depending on how precisely you measure it.
- Quantitative data is numerical and splits into discrete (countable, separate values — 0, 1, 2, 3...) and continuous (any value within a range, limited only by measurement precision).
- Categorical (qualitative) data is non-numeric labels — nominal if there's no natural order (colours, flavours), ordinal if there is one (small/medium/large).
- The test isn't the unit of measurement — it's whether the recorded values can only be whole numbers/specific counts (discrete) or genuinely any value in between (continuous).
- Discrete data
- Numerical data that can only take specific, separate values, typically whole-number counts (e.g. number of items bought).
- Continuous data
- Numerical data that can take any value within a range, limited only by how precisely it's measured (e.g. height, time, mass).
- Categorical (qualitative) data
- Non-numeric data recorded as labels or categories, not counted or measured (e.g. favourite flavour, eye colour).
- Nominal data
- Categorical data with no natural order or ranking (e.g. flavours: chocolate, vanilla, strawberry).
- Ordinal data
- Categorical data with a natural order or ranking (e.g. sizes: small, medium, large).
Frequently confused
| Concept A | Concept B | The distinction that matters |
|---|---|---|
| Discrete | Continuous | Ask: 'could there be a value in between two consecutive data points?' If no (you could list every possible value one by one, like 0, 1, 2, 3...), it's discrete. If yes (any decimal is possible depending on measurement precision, like 1.5 seconds or 1.53 seconds), it's continuous. |
Worked example
Classifying real data from this topic's own questions
Common mistake
Calling categorical data (like flavours or colours) 'discrete'.
Consequence: 'Discrete' specifically describes numerical data with countable gaps between values — using it for non-numeric labels shows a misunderstanding of the term and loses the definition mark.
Fix: Reserve 'discrete' and 'continuous' strictly for NUMBER data. Use 'categorical' (further split into nominal or ordinal) for non-numeric labels.
Key takeaways
- Discrete = countable, separate numerical values (no value can exist in between). Continuous = measured, any value possible within a range.
- Categorical data is never called discrete or continuous — it's nominal (no order) or ordinal (has an order).
- A score 'out of 100' is discrete even though the underlying ability is continuous — this exact distinction is the most commonly tested trap in this subtopic.
- Classifying data correctly is the first step in every question on choosing a representation — get this wrong and the whole answer collapses.
Quick Reference
Data Handling and Representation — at a glance
Formulas
- Pie chart sector angle — all angles must sum to 360°
- Share of a category as a percentage of the total
Key facts
- Full circle for a pie chart
- 360°
- Tally grouping size
- 5 (four verticals + one diagonal)
- Median position for n values
- the (n+1)/2‑th value when ordered (average of two middle values if n is even)
Mnemonics
- Leaf = Last digitThe leaf is the final (units) digit; everything before it is the stem
Don't confuse
- Discrete vs Continuous: Could a value exist in between two data points? No → discrete. Yes → continuous.
- Bar chart vs Pie chart: Bar chart compares actual sizes between categories; pie chart shows proportion of one whole total.
- Stem-and-leaf vs Dot plot: Stem-and-leaf suits larger multi-digit values organised by place value; dot plot suits a small range of simple values stacked on a number line.
Command terms
- State / Identify:
- Give the value/category directly — no working needed, but the wrong feature named loses the mark
- Construct / Complete:
- Build the full table/diagram with all labels and key — missing labels lose marks even with correct numbers
- Calculate:
- Show the method (e.g. total minus knowns), not just the final number
- Compare:
- State direction and magnitude — 'A is more/less than B, by roughly X' — not just two numbers restated
- Explain:
- Give the causal 'because' link between the data feature and its real consequence
Exam checklist
- Classify the data first: counted (discrete) or measured (continuous), or categorical (nominal/ordinal)?
- Tally straight through the raw list in order, grouping strokes in fives.
- Sum the frequency column and check it equals the total number of data items.
- Check every frequency before naming 'the' mode or modal class — ties happen.
- Choose bar chart (compare categories), pie chart (proportion of a whole), line graph (trend over time), or stem-and-leaf/dot plot (preserve individual values).
- For pie charts, check all sector angles sum to exactly 360°.
- For stem-and-leaf diagrams, re-sort leaves within each row and include the key.