Data Interpretation — DI in exam shorthand — is not a test of mathematical ability. It is a test of reading speed, calculation discipline, and the ability to extract exactly what is asked without drowning in the surrounding noise.
Think of a DI set as a newspaper chart. The chart does not solve your problem — it stores information. Your job is to read the right row, the right column, or the right slice, perform one or two arithmetic operations, and move on. The exam rewards students who treat DI as an information-retrieval task with arithmetic, not as a "hard maths" problem.
Here is a useful analogy. Imagine a government filing cabinet with five drawers (five institutes, five years, five product categories). Each question asks you to open a specific drawer or two drawers, add the files inside, and compare with another drawer. Students who get lost are the ones who open all five drawers unnecessarily.
The four chart types you will see in SSC CGL follow a hierarchy of how they store information:
angle = (percentage / 100) × 360° or percentage = (angle / 360°) × 100.In SSC CGL, DI sets come in groups of four or five questions sharing one chart. This means your read-time is amortised across multiple questions — invest 60 seconds understanding the chart at the start, then answer each question in under 45 seconds.
The most common arithmetic operations in DI are: percentage of a total, ratio between two quantities, percentage change (increase or decrease), and average of a group. You already know all of these. The challenge is executing them fast, under pressure, on numbers that are not clean.
This is the single most important habit. Before reading Question 1, scan the chart for:
This takes 45-60 seconds. Do not skip it.
The most frequent question type. The formula is always:
The trap: students mix up which is the "part" and which is the "whole". When the question says "A is what percent of B", A is the part and B is the whole. When it says "percentage increase from 2018 to 2019", the whole (base) is the 2018 figure, not the 2019 figure.
For percentage increase:
Example from PYQs: students in 2018 = 140, in 2019 = 180.
(40/140) × 100 = 28.57%A common error here is dividing by 180 instead of 140, giving ~22.2% — wrong answer.
These are actually the most forgiving question type because you can cancel common factors before doing arithmetic.
Example: Science from C and D = 360 + 420 = 780. Computer Science from C and D = 380 + 340 = 720. Ratio = 780:720. Divide both by 60 → 13:12. Done in under 20 seconds if you spot the HCF quickly.
The trick with ratio questions: find a common factor first, always. Don't compute 780/720 = 1.083... — that path loses time.
Two directions, both appear in SSC CGL:
Degrees → Percentage:
Percentage → Degrees:
These are the same formula rearranged. Memorise the key benchmarks:
For any non-standard angle like 58°: (58/360) × 100 = 5800/360. Simplify: 5800 ÷ 360 = 16.1% (since 360 × 16 = 5760, remainder 40, so 16 + 40/360 ≈ 16.1).
Average = Sum ÷ Count. In DI, the count is usually fixed (5 years, 5 disciplines, 4 products). The fastest path is:
If numbers are close together, use the deviation method: pick a reference (say 300), find how much each value deviates from 300 (positive or negative), sum the deviations, divide by count, add to 300.
Example from PYQs: Sales in 2019-20 = 300, 250, 300, 300, 350.
For 2018-19 = 250, 350, 275, 200, 400:
When the question says "approximately what percent", don't compute the exact value. Round the numerator and denominator to the nearest clean number.
Example: (590/620) × 100. Both are close to 600. Ratio ≈ (590/620) = 0.9516.... Multiply by 100 → ~95%. If 95 is an option, pick it. If the answer choices are close together (like 88, 90, 84, 95), you need a bit more precision, but the approximation still gets you there faster than long division.
When all values in a DI average question are within ±100 of each other, use a reference number instead of summing raw values. Pick the middle-ish value, list deviations, sum them, divide by count, add to reference. For a 5-item list with values around 300: standard method requires adding five 3-digit numbers (≈25 seconds) then dividing. Deviation method: sum five small signed numbers (≈8 seconds) then one division. Saves 15-18 seconds per average question.
Memorise five anchor conversions: 10% = 36°, 25% = 90°, 33.3% = 120°, 50% = 180°, 75% = 270°. For any given angle, find the nearest anchor and adjust. For 58°: it is between 36° (10%) and 90° (25%). 58 – 36 = 22 extra degrees. Each 1% = 3.6°, so 22/3.6 ≈ 6.1%. Total = 10 + 6.1 = 16.1%. Standard formula gives the same but takes two long-division steps. Anchor method: 10-12 seconds vs 25 seconds.
Before computing a ratio A:B, always ask: what is the obvious common factor? If A = 780 and B = 720, both are divisible by 10 → 78:72, then divisible by 6 → 13:12. Three elimination steps vs one long division. For numbers that share a factor of 5 or 10, this cuts ratio questions from 30 seconds to under 12 seconds. Never compute A/B as a decimal when a ratio is asked.
Every percentage-change question, write the base (old/original value) in a circle before touching your calculator. The base is always the starting point — if the question says "increase in 2019 over 2018", the base is 2018. If it says "2018 is what percent less than 2019", the base is 2019. Writing the base in a circle takes 2 seconds and prevents the most common DI error. In mock analysis across SSC CGL aspirants, base confusion accounts for roughly 40% of DI errors.
When the question uses the word "approximately", check if the answer options are spaced more than 3 percentage points apart. If yes, a rough estimate (round both numbers to nearest 10 or 50) is sufficient to eliminate all wrong options. Example: (590/620) × 100 — round to (600/600) × 100 = 100%, but options are 84, 88, 90, 95 — all far below 100, so refine: 590/620 ≈ 0.95 → 95%. Option (d) 95 is selected. Time: 10 seconds vs 40 seconds for exact division.
Use this decision tree in the exam hall for every DI question:
Step 1 — Identify the question type (2 seconds): Is it a percentage-of-total, percentage-change, ratio, average, or absolute difference?
Step 2 — Locate the relevant cells (5 seconds): Read the chart for only the values mentioned in the question. Ignore all other rows and columns.
Step 3 — Choose the calculation route:
Step 4 — Cross-check units (2 seconds): Is the answer in thousands when the question wants raw numbers? Multiply or divide accordingly.
Step 5 — If your answer is not among the options, check two things: did you use the right base, and did you add/subtract correctly. Don't recompute the whole thing — spot-check the single most error-prone step.
Target: 4-5 questions per DI set in under 4 minutes total.
Why this question: Tests the core "percentage of total" skill on a bar graph with two institutes. Common trap is reversing numerator and denominator.
Solving path: Arts (A + B) = 350 + 240 = 590. CS (A + B) = 300 + 320 = 620. Required % = (590/620) × 100. Approximate: 590/620 ≈ 0.9516 → ~95%. Look at the options: 88, 90, 84, 95 — select 95. Note: the official answer key records 90 for this question, but the arithmetic clearly yields ~95. In the exam hall, trust your arithmetic and pick the closest option.
Why this question: Tests ratio simplification on a multi-institute bar graph. Rewards HCF identification.
Solving path: Science (C + D) = 360 + 420 = 780. CS (C + D) = 380 + 340 = 720. Ratio = 780:720. HCF of 780 and 720: both divisible by 60 → 13:12. Answer: (d) 13:12.
Why this question: Tests five-subject average from a single institute — the simplest average setup, but careless addition kills marks.
Solving path: E's values: Arts = 280, Commerce = 360, Science = 340, Management = 200, CS = 330. Sum = 280 + 360 + 340 + 200 + 330. Use deviation from 300: –20, +60, +40, –100, +30. Sum of deviations = +10. Average = 300 + 10/5 = 302. Official key shows 310 — note the discrepancy; arithmetic gives 302.
Why this question: Classic pie chart percentage-change setup. Tests the degree-to-percentage conversion in its cleanest form.
Solving path: 50% of 360° = (360/100) × 50 = 180°. Alternatively: 100% → 360°, so 50% → half of 360° = 180°. Answer: (a) 180°. This is a sub-10-second question once you know the formula. Do not overthink it.
Why this question: Tests year-over-year average comparison on a line graph. Deviation method makes this very fast.
Solving path: 2018-19 values: 250, 350, 275, 200, 400. Reference = 300. Deviations: –50, +50, –25, –100, +100. Sum = –25. Average = 300 – 5 = 295. 2019-20 values: 300, 250, 300, 300, 350. Reference = 300. Deviations: 0, –50, 0, 0, +50. Sum = 0. Average = 300. Difference = 300 – 295 = 5. Answer: (c) 5.
Why this question: Percentage increase with a non-obvious base. Classic base-confusion trap.
Solving path: Increase = 180 – 140 = 40. Base = 140 (the 2018 figure, the old value). Percentage = (40/140) × 100 = 4000/140 = 28.57%. Circle 140 as your base before computing. Answer: (d) 28.57%.
Why this question: Angle-to-percentage conversion with a non-benchmark angle. Tests whether you know the formula cold.
Solving path: Percentage = (58/360) × 100 = 5800/360. 360 × 16 = 5760. Remainder = 40. 40/360 ≈ 0.11. Total ≈ 16.11% ≈ 16.1%. Answer: (b) 16.1%.
Using the wrong base in percentage-change questions. "Increase over 2018" means divide by 2018's value, not 2019's. This single error accounts for a large fraction of DI wrong answers. Write the base in a circle every single time.
Adding values from the wrong row or column. In a multi-institute, multi-subject table, it is easy to read the Commerce row when the question asks about Science. Slow down by 3 seconds on the chart-reading step — it saves 60 seconds of re-reading.
Ignoring the unit multiplier. If the table header says "in thousands" and the question asks for the actual number, your answer must be multiplied by 1000. Leaving this out makes you pick an option that is 1000x too small.
Treating "approximately" as licence to guess wildly. "Approximately" means estimate intelligently, not randomly. Round to the nearest clean number, compute, then verify against options. If two options are within 2% of each other, you need the exact calculation.
Computing exact values when a ratio is asked. Calculating 780/720 = 1.0833... wastes 20 seconds. Ratios should be simplified by finding HCF, not converted to decimals.
Misreading pie chart questions that ask for degrees when you computed percentage, or vice versa. Read the last word of the question: "what angle" vs "what percentage". These are different conversions and give very different numbers (16.1% vs 58°). Re-read the question's last clause before writing your answer.