Tabular and Chart DI

In SBI PO Prelims and Mains, five Data Interpretation questions can decide whether you clear the section cutoff or miss it by a single mark. The candidates who get all five right are rarely the fastest calculators — they are the fastest readers. They scan the table in 20 seconds, lock in the row-and-column logic, then attack the questions. Let us learn the discipline they use.

Definition: Tabular Data Interpretation (DI) is a set of questions based on data arranged in rows and columns, sometimes with totals, sub-totals, percentages, or multiple categories like years, products and cities.

Definition: A row typically lists one entity (a year, a city, a product line) and a column lists one attribute (revenue, units sold, share). The intersection is a single data cell.

The first 20 seconds — read the table, not the question

Counter-intuitively, the very first action when a tabular DI set appears is not to read all the data, and not to read the question yet. The first action is to read the table header and column titles for about 20 seconds with three specific goals:

1. What does each row represent? Years? Cities? Products? Branches?
2. What does each column represent? Absolute numbers, percentages, ratios? In thousands, lakhs or crores?
3. Are totals or averages given, or must they be derived?

Once you know these three things, you have a mental map of the table. Now, and only now, read the first question. Always return to the table for each new question — never re-read the whole table top to bottom.

Why it matters

SBI PO 2023 Mains had a DI set where Column 3 was labelled "% growth from previous year" while Column 2 was in absolute crores. Candidates who missed the unit confusion treated 12% as 12 crores and lost all five questions. The cost of misreading a header is the entire set — five marks plus four wasted minutes. Reading slowly for 20 seconds saves four minutes downstream.

Row vs column logic — which way do you read?

A row-wise question asks you to compare different attributes of the same entity. A column-wise question asks you to compare the same attribute across entities.

Examples:

• "Total revenue of City A across all four products" → row-wise read along City A.
• "Total revenue from Product 2 across all five cities" → column-wise read along Product 2.
• "Which product had the highest sales in 2023?" → column-wise along year 2023.
• "What is the average sale of Product 1 over five years?" → column-wise along Product 1.

A test mark on each question — "row?" or "col?" — saves seconds of re-orientation, especially when the question is phrased in convoluted English.

The absolute vs percentage trap

The single most common SBI PO trap is mixing absolute values with percentages. The exam shows two columns side by side: Column A = "Revenue (crores)", Column B = "% share of branch in total". A careless candidate might add Column B values across branches expecting them to give total revenue. Wrong — Column B sums to 100, not to the total revenue.

Before any computation, ask:

• Is this number an absolute quantity (rupees, kg, units)?
• Is it a percentage (always relative to a base — what is the base?)
• Is it a ratio (compared to which other quantity?)

Reading the question first — for the second pass

Once you have the table map, read the first question carefully and only then return to the relevant cells. Underline three classes of keywords:

• Quantifiers: "at least", "at most", "exactly", "approximately"
• Multiplicity tags: "respectively", "in the same order"
• Base words: "more than", "less than", "from", "compared to" — these decide which number is the denominator

Without underlining, the brain glides over "respectively" and you swap two answers. With underlining, you mechanically check that your final answer matches the order asked.

Percentage problems — picking the right base

The most-tested trap: picking the wrong base for percentage comparison.

• "A is what percent more than B" → base is B. Use (A - B) / B × 100.
• "A is what percent of B" → base is B. Use A / B × 100.
• "Increase from previous year" → base is previous year, not current.
• "Decrease over the base year" → base is first year of the series.

The wrong choice of base typically changes the answer by 10 to 30 percentage points, and the wrong option will be a distractor in the choices.

Worked example

Question: A table shows revenue of four companies in 2022 and 2023 in crores. Company P: 80 → 100. The question asks, "By what percent did the revenue of Company P increase from 2022 to 2023?"

Solution:
Step 1: Identify the base year — the year before the change is 2022, so the base is 80.
Step 2: Compute the change: 100 - 80 = 20.
Step 3: Compute the percentage: 20 / 80 × 100 = 25%.
Step 4: Double-check the direction: revenue went up from 80 to 100, so the percentage should be positive, which it is.
Conclusion: Revenue of Company P increased by 25%.

A common wrong move is to divide by 100 (the new year), which gives 20%. This is the kind of error SBI PO loves to plant as a distractor.

The five-linked-questions strategy

Tabular DI in SBI PO is almost always a five-question set built on one table. The trick: most questions reuse the same row sums or column sums. After computing the total of each row and the total of each column the first time you need them, jot them in the margin of the paper. The next four questions usually re-use those totals, and you do not recompute. This cuts the total time per set from 6 minutes to 3 minutes.

For ratio comparisons, when two ratios look similar (say 13/7 vs 19/11), cross-multiply mentally — 13 × 11 = 143 and 19 × 7 = 133 — and the bigger product gives the bigger ratio. This is faster than dividing.

Real-world example

A bank manager looking at a quarterly branch-performance report uses exactly the same logic — scanning headers for units (lakhs vs crores), reading row totals for branch performance, column totals for product-line performance, and flagging the row with the largest percentage growth. The DI section is essentially a bank manager's reading test, compressed to 60 seconds per question.

Common misconception

The most common misconception is that mental calculation speed is the bottleneck, so candidates spend coaching-class months drilling multiplication tables. In reality, the bottleneck is reading: misreading "thousand" as "lakh", confusing "more than" with "of", or applying a row percentage to a column total. Speed maths helps, but slow careful reading + medium-speed arithmetic beats fast careless reading + fast arithmetic every time.

Choosing your DI sets

In SBI PO Mains, four DI sets are usually offered and only the best three are attempted. The smart strategy: in the first minute, glance at all four sets and pick three based on which table layouts look the cleanest. A clean table — one with simple headers, no nested categories, fewer than five columns — is almost always faster than a complicated multi-tier one with footnotes.

:::compare

Question phrasing	Base for percentage
"A is what % of B"	B
"A is what % more than B"	B
"A is what % less than B"	B
"Increase from year X to year Y"	year X (the earlier one)
"Compared to base year"	the base year given in the problem
:::

:::keypoints

• Read the table headers and units for 20 seconds before any question.
• Always read the question first, then return to the table — never read the whole table top to bottom.
• Distinguish row-wise vs column-wise questions and tag each one.
• Beware mixing absolute values with percentages or ratios.
• Underline keywords: "at least", "exactly", "respectively", "more than".
• Pick the correct base for percentage problems — usually the earlier or referenced quantity.
• Save row and column totals in the margin; SBI DI sets reuse them across the five questions.
  :::

:::memory
RUSH — Row or column? Units clear? Save the totals! Highlight the keywords. Do all four before you compute.
:::

:::recap

• Spend 20 seconds mapping the table before reading any question.
• Match the percentage base to the language of the question.
• Reuse computed row and column totals across the five linked questions.
• Slow, careful reading beats fast careless reading in DI.
  :::

In SBI PO, Data Interpretation is rarely about hard arithmetic — it is about doing easy arithmetic at speed, under pressure, with a forest of numbers in front of you. The aspirants who clear the sectional cut-off are not the ones who calculate the most accurately; they are the ones who recognise the calculation at a glance and convert it into a mental shortcut. This lesson builds that recognition layer.

Definition: A percentage is simply a fraction whose denominator is 100. Saying "37.5%" is exactly the same as saying "3 out of 8", which is exactly the same as saying "0.375".

Definition: A ratio a : b is a comparison of two quantities, mathematically equal to the fraction a/b. Comparing two ratios is therefore comparing two fractions.

Why memorising fraction-to-percent conversions matters

A typical SBI PO tabular DI set asks five questions like "By what percent did Branch B's sales increase from 2022 to 2023?" or "What is the ratio of male to female employees across all four cities?" Almost every such question hides one of these structures:

• a fraction of the form 1/n where n is small
• a percentage that maps back to a small fraction
• a comparison of two fractions

If you have already locked the small-fraction table into long-term memory, you skip the entire division step. The brain reads "12.5%" and instantly substitutes "1/8". You then multiply or divide using that 1/8, which is far faster and far less error-prone than punching 12.5 into mental arithmetic.

The fractions worth memorising cold:

• 1/2 = 50%
• 1/3 ≈ 33.33%
• 1/4 = 25%
• 1/5 = 20%
• 1/6 ≈ 16.67%
• 1/7 ≈ 14.28%
• 1/8 = 12.5%
• 1/9 ≈ 11.11%
• 1/10 = 10%
• 1/11 ≈ 9.09%
• 1/12 ≈ 8.33%

And the eighths and other useful multiples:

• 3/8 = 37.5%, 5/8 = 62.5%, 7/8 = 87.5%
• 2/3 ≈ 66.67%, 4/3 ≈ 133.33%
• 5/6 ≈ 83.33%
• 1/16 = 6.25%, 3/16 = 18.75%

Drill these until the response is automatic. A two-second recognition saves you twenty seconds across a DI set, which is the difference between attempting the last set and leaving it blank.

The core percentage formulae you will reuse

Every DI question is one of four patterns. Lock the formulae.

Pattern 1 — Percentage of a number: X% of Y = (X/100) × Y. Convert X% to its fraction whenever possible. 25% of 480 is not 0.25 × 480; it is 480/4 = 120, in one step.

Pattern 2 — What percent is X of Y: Answer is (X/Y) × 100. The trick: cancel before you multiply. 84 out of 240 is 84/240 = 7/20 = 35%.

Pattern 3 — Percentage change: ((New − Old) / Old) × 100. Always divide by the OLD value, never the new one. This is the single most common sign error in DI.

Pattern 4 — Reverse calculation (unitary method): If 12% of a quantity equals 96, then 1% = 8, so 100% = 800. This is faster than dividing 96/0.12 — you simply divide by 12 and multiply by 100.

Comparing ratios by cross-multiplication

You will often be asked which of two cities has a higher male-to-female ratio, or which year had a higher profit-to-revenue fraction. Do not convert each ratio to a decimal — that is two divisions, and decimals invite arithmetic slips.

Use cross-multiplication. To compare a/b with c/d (with b, d > 0):

• Compute a × d and b × c
• The fraction whose numerator-side product is larger is the larger fraction

Worked illustration: compare 7/12 with 9/16. Cross products: 7 × 16 = 112 and 12 × 9 = 108. Since 112 > 108, we conclude 7/12 > 9/16. No decimals, no division, just two small multiplications.

Why it works: multiplying both sides of a/b vs c/d by the positive number bd preserves the inequality, giving ad vs bc.

Approximation: your secret weapon in SBI PO

In SBI PO Mains, the answer options for DI are spaced widely enough that rounding intermediate values to two significant figures is almost always safe. If a question asks for 23.7% of 4,872, you can confidently compute 24% of 4,900 ≈ 1,176 and pick the closest option. The full computation 0.237 × 4,872 = 1,154.66 sits inside the same option range.

A safe approximation discipline:

• Round percentages to the nearest 0.5% or whole number
• Round large numbers to two or three significant figures
• Track the direction of your rounding so you know whether your answer is slightly high or slightly low
• Reserve exact calculation for questions where two options are within 1% of each other

Why it matters: The exam is timed at roughly 36 seconds per question. Exact calculation simply does not fit. The students who clear sectional cut-offs treat approximation as the default and exact arithmetic as the exception.

Real-world example

Real-world example: A typical SBI PO table shows that Branch A's loan disbursal was 4,250 crores in 2022 and 5,100 crores in 2023. The question asks for the percentage increase. Mentally: change = 850, original = 4,250. The fraction 850/4,250 simplifies to 850/4,250 = 1/5 = 20%. Done in under five seconds because you recognised that 850 × 5 = 4,250.

Common misconception

Common misconception: Many aspirants compute percentage change as (New − Old) / New, especially when "new" appears earlier in the sentence. This is wrong. The denominator is always the BASE, which is the original value you are comparing against. If revenue moves from 100 to 120, that is a 20% rise (20/100), not a 16.67% rise (20/120). The wrong denominator turns a positive trap into a negative score.

Question: A village has 3,500 voters. Of these, 14.28% supported Party X. How many voters is that?

Solution:
Step 1: Recognise 14.28% as the fraction 1/7.
Step 2: Compute 3,500 × (1/7) = 500.
Conclusion: 500 voters supported Party X. No division needed — pattern recognition turned a 14.28% multiplication into a single division by 7.

:::compare

Need to	Use	Why
Find X% of Y	Convert X% to fraction, then multiply	Avoids decimal arithmetic
Find what % X is of Y	(X/Y) × 100, cancel first	Cancellation gives clean ratios
Find % change	(Change / Original) × 100	Always divide by base
Reverse a percentage	Unitary method	One division, one multiplication
Compare two ratios	Cross-multiply	No decimals, fewer mistakes
:::

:::keypoints

• Memorise 1/n percentages for n = 2 to 12; recognition is the engine of DI speed.
• For "X is what % of Y", cancel the fraction X/Y first, then multiply by 100.
• Percentage change always divides by the OLD value, never the new.
• The unitary method (1% = …) is the fastest reverse-calculation technique.
• To compare a/b and c/d, compare a × d with b × c.
• In SBI PO, two-significant-figure approximation is safe inside the option spacing.
• The exam rewards pattern recognition, not pure calculation strength.
  :::

:::memory
FRAC-PROP: Find the Recognisable And Convert — then Pick the Right base, Optimise by cancelling, Predict using approximation.
:::

:::recap

• Convert common percentages to fractions on sight; this saves the most time.
• Always anchor percentage change to the original quantity.
• Cross-multiplication beats decimal conversion for ratio comparisons.
• Approximation is a strategy, not a shortcut — use it consciously.
  :::

In SBI PO Prelims and Mains, every DI set is a set — usually 5 to 6 questions stacked on the same table or chart. Aspirants who treat each question independently end up reading the same numbers six times. Aspirants who pre-process the table once and treat the six questions as variations of one calculation finish the entire set in half the time. This lesson shows that "pre-process once, reuse everywhere" technique on a multi-column table of employees and gender percentages.

Definition: Tabular Data Interpretation (Tabular DI) is a category of DI questions where data is presented in a rectangular table — rows are entities (departments, products, branches) and columns are attributes (totals, percentages, ratios). Questions test percentage, ratio, average, and difference calculations across rows or columns.

Definition: Pre-processing in DI means computing all the obvious derived quantities — absolute counts, totals, gender splits, averages — once at the start of the set, even before reading the actual questions. The numbers are then plugged into each question without recomputing.

Anatomy of the set

The source table gives employees in 5 departments and the percentage that are female in each. A representative row says — Department A: 250 total employees, 40% female. That single row has three useful numbers buried inside it:

• Total = 250
• Female = 40% of 250 = 100
• Male = 250 − 100 = 150

If a question later asks "male in Dept A as a fraction of total male across all departments," you already have the 150. If it asks "ratio of male in A to female in B," you again already have the 150. The 12-minute set becomes a 6-minute set.

Doing the worked example end to end

Following the source: Dept A — 250 total, 40% female.

Step-by-step margin notes (write these down on the OMR rough sheet):

• Dept A: Total 250, Female 100, Male 150.
• Continue for B, C, D, E — say total female across all five departments is given as 520.

If the question now is "Female in A as percentage of total female across all departments":

Female in A / Total female × 100 = 100 / 520 × 100 = 19.23%.

That single calculation took 5 seconds because the 100 was already pre-computed. If you had to first read "40% of 250" all over again, set up the multiplication, and only then divide by 520, you would have spent 30 seconds for the same answer.

The structural insight — questions are linked

Across SBI PO papers, the six questions of a DI set rarely test six unrelated calculations. Typically:

• Q1 — pure percentage (e.g., Females in B as % of total in B).
• Q2 — ratio (e.g., Males in A : Females in C).
• Q3 — difference (e.g., Difference between males in A and females in D).
• Q4 — average (e.g., Average number of females across departments).
• Q5 — percentage between rows (e.g., Females in A as % of total female).
• Q6 — combined / "what if" question (e.g., If 20% of females in B resign, new ratio of males to females in B).

Every one of those questions reuses the same per-department male and female counts. So the rational strategy is — build a tiny grid of (Department, Total, Female, Male) once. Three columns, five rows — fifteen numbers. After that, every question is a one-line plug-in.

Common time leaks

Three habits drain the most time in tabular DI:

• Recomputing the absolute female count for the same department in three different questions.
• Reading the question stem from scratch instead of scanning for the "what is being asked" phrase first.
• Doing multiplications like 40% of 250 the long way (250 × 40 / 100) instead of using "10% of 250 = 25, so 40% = 100" — a 3-second mental hop.

Why it matters: SBI PO's DI section gives 30 minutes for 30 questions, typically organised as five sets of six. If you can shave 5 to 6 minutes by pre-processing each set, you bank time for Quant and Reasoning where every extra minute is worth half a mark. Pre-processing is also the foundation for caselet DI, pie-bar combinations, and missing data DI — all SBI Mains staples.

Real-world example: A branch manager at SBI reviewing monthly KPIs across five product lines does exactly this — total customers, conversion percentage, ticket size — and writes the absolute conversions next to each row before even looking at the questions head office sent. Without this pre-processing, comparing product lines on the fly takes hours; with it, the same review takes minutes. The DI section is testing this real banking skill.

Common misconception: Many students assume "pre-processing wastes time at the start of a set." In reality, computing five percentages takes about 60 to 90 seconds and saves 5 to 6 minutes downstream because every question reuses those exact five numbers. The break-even point is around question 2 — after that, every saved question is pure profit.

Question: Dept A has 250 total employees, 40% of whom are female. If the total number of females across all 5 departments is 520, what is the female count in A as a percentage of the total female count?
Solution:
Step 1: Compute the absolute female count in Dept A. Female in A = 40% of 250 = 0.40 × 250 = 100. (Mental shortcut: 10% of 250 is 25, so 40% is 100.)
Step 2: Compute males in A for any later question: Male in A = 250 − 100 = 150.
Step 3: Compute the required percentage: (Female in A / Total female) × 100 = (100 / 520) × 100.
Step 4: 100/520 = 5/26 ≈ 0.1923, so the percentage = 19.23%.
Conclusion: Females in Dept A form approximately 19.23% of the total females across all departments. Critically, the 100 and 150 are now logged on your rough sheet for the rest of the set.

:::compare

Strategy	Time per question	Mental load	Error rate
Read and compute each Q from scratch	90–120 s	High (re-reading stems)	Higher (recalculation errors)
Pre-process all rows first, then answer	30–50 s	Low (single lookup)	Lower (one careful pass)
Skim and skip without pre-processing	60–80 s	Medium	Highest (no anchor numbers)
:::

:::keypoints

• Treat a DI set as one problem with six views, not six separate problems.
• Pre-process every row at the start — write Total, Female, Male in a margin grid.
• Use percentage shortcuts: 10%, 25%, 50% as anchors, then scale.
• Linked questions reuse the same absolute counts, so pre-processing pays back from Q2 onwards.
• The biggest time leak is re-reading the table; the second is recomputing the same percentages.
• A typical 6-question set goes from ~12 minutes to ~6 minutes with this method.
• Use the same template for caselet DI and pie-chart sets — pre-process, then plug.
  :::

:::memory
"Pre-process, then plug." Or remember the SBI PO mantra — "Margin Grid first, Maths later." If your rough sheet doesn't show three numbers per row before you answer Q2, you've already lost the time race.
:::

:::recap

• Pre-processing each row of a tabular DI set saves about half the total time.
• Compute Total, Female, and Male absolute counts once, then reuse for all six questions.
• Use percentage anchors (10%, 25%, 50%) for mental calculation speed.
• The same technique transfers to caselet, pie, and bar-graph DI sets.
  :::

Bar graphs show discrete comparisons; line graphs emphasise TREND over time. First read the axis scale and unit — SBI PO loves dual-axis charts where one series is in Rs cr and another in %. For stacked/grouped bars, each segment is a separate value; total = sum of segments. For line charts, a STEEPER slope means a larger change, not a larger value. Common question types: difference between two bars, ratio of two points, average over a period, percentage growth between two years. Speed habit: estimate from the gridlines first to eliminate 2 distant options, then compute precisely only between the 2 close ones. Watch for 'between' (exclusive) vs 'from-to' (inclusive) in period questions.

Bar graphs and line charts in SBI PO papers are not really tests of mathematics — they are tests of formula discipline under time pressure. A typical DI set throws five questions in eight minutes, and the only thing standing between you and a clean +5 is the muscle memory of half a dozen averaging and difference formulas. Master them once, and DI becomes scoring territory.

Definition: The average (arithmetic mean) of n values is the sum of the values divided by n.

Definition: Percentage growth from a starting value to an ending value measures the change as a percentage of the starting value.

The Core Formulas, One by One

1. Average Over n Periods

Average = (sum of all values) / n.

If a line chart shows sales in 5 years — say ₹120, ₹150, ₹180, ₹200, ₹250 crore — the average is (120 + 150 + 180 + 200 + 250) / 5 = 900 / 5 = ₹180 crore. Read all five gridlines carefully, add, divide. Do not mentally "guess" the average from the shape of the line.

2. Required Value for a New Average

If you already have n values with a known sum and you want the (n+1)-th value to make a target average:

Required value = (new average × new count) − current sum.

Question: The average score of 5 students in a test is 72. What score must a 6th student get so that the average rises to 75?
Solution:
Step 1: Current sum = 5 × 72 = 360.
Step 2: New total needed = 6 × 75 = 450.
Step 3: Required value = 450 − 360 = 90.
Conclusion: The 6th student must score 90.

This single formula handles dozens of DI variants — "average rises by 2," "new candidate brings the average down by 1," "what was the missing year's value," and so on.

3. Percentage Growth Over Several Years

Across a multi-year line chart, percentage growth from year 1 to year N is:

% growth = (valueN − value1) / value1 × 100.

This is NOT the sum of the yearly growth percentages. Year-on-year percentages compound, they do not add. Three years of 10% growth each give an overall growth of 33.1%, not 30%. SBI PO regularly traps students with the "add the yearly percentages" mistake.

Question: A company's revenue rose from ₹400 crore in 2018 to ₹540 crore in 2022. What is the percentage growth over the period?
Solution:
Step 1: Difference = 540 − 400 = 140.
Step 2: % growth = 140 / 400 × 100 = 35%.
Conclusion: 35% growth over the period.

4. "Overall Ratio" Across Two Series

If you have two series (say "exports" and "imports") tracked over five years and the question asks for the overall ratio of exports to imports across all five years, do not average the yearly ratios. Instead:

• Sum the export figures.
• Sum the import figures.
• Divide.

Overall ratio = (Σ exports) : (Σ imports).

This is because the ratio is a weighted average, and only summing-then-dividing weights each year correctly.

5. CAGR Shortcut (Rare in Prelims)

CAGR — Compound Annual Growth Rate — is the constant rate at which a value would have grown each year to reach its final value:

CAGR = (Final/Initial)^(1/n) − 1, where n is the number of years.

A handy shortcut: if a quantity doubles in n years, total growth is 100% and CAGR ≈ 72 / n % (the "Rule of 72"). For Prelims, plain percentage growth is usually enough — CAGR shows up mostly in Mains-level questions on financial growth.

6. Difference Questions Across Years

For "by how much did X exceed Y in year Z," just subtract directly from the gridline readings:

Difference = (X reading) − (Y reading).

Watch the units. If the y-axis says "₹ in crore," report the answer in crore. If two series share the y-axis, you can read both off the same scale; if they have different y-axes (a left axis and a right axis), apply each scale separately.

7. The Mixed-Unit Trap (Bar + Line on One Chart)

This is SBI PO's favourite trap. A chart shows a bar for total revenue (in ₹ crore, absolute number) and a line for the percentage of revenue coming from a single product, year by year. To get the actual revenue of that product in any year:

Actual value of the % series = (% reading) × (corresponding total).

Question: In 2022, total revenue = ₹800 crore (bar reading). The line shows that 35% came from product A. What was the absolute revenue of product A in 2022?
Solution:
Step 1: Identify the bar value: ₹800 crore.
Step 2: Identify the line value: 35%.
Step 3: Actual = 35% × 800 = 0.35 × 800 = ₹280 crore.
Conclusion: ₹280 crore.

If you forget this multiplication and just compare percentages across years, you can get the entire question set wrong.

Why It Matters

Why it matters: DI carries 30–35 marks out of 60 in SBI PO Prelims's Quant section and around 50 marks in Mains. Bar–line combinations and "with percentage" charts are the most common chart formats. Mastering the seven formulas above can give you a 90%+ accuracy at full speed — and DI is where toppers separate themselves from the pack.

Real-World Example

Real-world example: When the RBI publishes the Annual Report, it shows a bar for total agricultural credit each year and a line for the share of small and marginal farmers in it. To answer "by how much did credit to small farmers rise from 2018 to 2023," you would multiply each year's bar by the corresponding line's % and then subtract. The trick is exactly the SBI PO "mixed-unit" formula.

Common Misconception

Common misconception: Many candidates add the yearly percentage growth figures across a multi-year span: "5% + 8% + 12% = 25%." This is wrong because percentages of different base values cannot be added. Always use (final − initial)/initial × 100 over the whole stretch.

Another slip: averaging ratios. If the export-to-import ratios over three years are 2:3, 3:4 and 4:5, the overall ratio is not the average of these ratios. Sum the exports, sum the imports, then take the ratio.

A third slip: forgetting which series the question is about. Highlight the relevant series with a thumbnail symbol on the rough sheet before computing.

Speed Tactics

When the timer is ticking, the order of operations matters. Read the question stem first, then look only at the data you need. If three years are mentioned in the stem, ignore the remaining four. Use approximation where the options are widely spaced — for example, 35% of 783 ≈ 35% of 800 = 280, and if the nearest options are 240 and 290 you have your answer without exact arithmetic.

:::compare

Need	Wrong shortcut	Correct formula
Average over n years	Eyeball the middle of the line	Sum / n
Value needed for new average	Just add the new value	(new avg × new count) − current sum
Multi-year % growth	Sum of yearly %s	(final − initial) / initial × 100
Overall ratio of two series	Average the yearly ratios	Sum each series, then divide
Actual value when % line + total bar	Use only the % reading	% × corresponding total
:::

:::keypoints

• Average = sum / n; required value to hit a target average = (new avg × new count) − current sum.
• Percentage growth over a span is computed from the start and end values, NOT by adding yearly percentages.
• For an overall ratio across years, sum each series first, then divide — never average the ratios.
• CAGR uses the n-th root formula; the Rule of 72 estimates doubling time.
• For mixed bar-and-line charts where one is absolute and one is %, multiply % by the matching absolute value.
• Read questions before reading data; pick only the years and series you need.
• Approximation and option-elimination beat exact arithmetic when time is short.
  :::

:::memory
"Sum, Divide, Done" — for averages. "Final minus Initial, over Initial" — for % growth. "Bar times Line" — whenever one series is a percentage of another.
:::

:::recap

• Six core formulas cover almost every bar/line DI question in SBI PO.
• Percentages of different bases never add; ratios across years never average.
• For combined charts, the % series is meaningless without the matching absolute total.
• Speed comes from formula reflex + approximation + option elimination, not from heavy arithmetic.
  :::

Dual-series line charts look harmless on the screen, but in the SBI PO data interpretation section they decide who finishes the set in two minutes and who burns five. The single habit that separates the two groups is simple: never read profit; always compute it once, write it down, then read it.

Definition: A dual-series line chart is a graph with two lines drawn on the same axes — here, one for Revenue and one for Expenditure — across the same time periods (years). The vertical gap between the two lines at any year is the Profit for that year.

Definition: Profit in DI is simply Revenue minus Expenditure. If Expenditure is larger than Revenue, the result is a Loss (a negative profit). All "profit growth", "profit ratio", "average profit" and "highest profit year" questions ultimately read from a single derived row: profit per year.

Reading the chart the smart way

Most aspirants make one expensive mistake: they treat each sub-question as a fresh problem and re-read the chart from scratch. The chart in this lesson plots Revenue and Expenditure (in Rs crore) for four years — 2021, 2022, 2023, 2024. Before solving anything, build a tiny mental table.

For 2021, Revenue = 120 and Expenditure = 90, so Profit = 30. For 2022, Revenue = 150 and Expenditure = 100, so Profit = 50. Once you have written "30, 50, …" above each year's point on the rough sheet, every question downstream becomes a lookup, not a calculation. This is the same idea as memoising a function — pay once, reuse many times.

The two question types you must separate

SBI PO setters love to interleave two superficially similar percentage questions, and students confuse them under stress.

Type A — Percentage change in profit between two years. The base is the earlier year's profit. From 2021 to 2022, profit grew from 30 to 50, so the percentage increase = (50 − 30)/30 × 100 = 20/30 × 100 = 66.67%. Notice the base: it is 30 (the previous year), not 50 and not the revenue.

Type B — Profit as a percentage of revenue (profit margin) in a single year. The base is that year's revenue. For 2022, profit margin = 50/150 × 100 = 33.33%. The base is revenue, not the previous profit.

Why it matters: One careless swap of base — using revenue when the question wants previous profit, or vice versa — is enough to land on a wrong option that the setter has deliberately placed in the answer choices as a trap.

Why pre-computing profit saves the set

Real-world example: Think of an SBI branch manager getting monthly numbers from head office. She does not recompute "what was March's profit?" every time someone asks; she keeps a one-line summary above each month. That is exactly the discipline an SBI PO aspirant must build in the DI section. With profit pre-computed:

• "Average profit over the four years" → just add the four numbers and divide by 4.
• "Year with highest profit" → glance at the row.
• "Ratio of profit in 2023 to 2024" → write the two numbers directly.

Each of these would otherwise demand reading two points off the chart and subtracting — about 8–10 seconds saved per sub-question, which is huge when a single caselet has 5 sub-questions.

Common misconception: "If revenue rises, profit must rise." Wrong. Profit depends on the gap between the two lines, not on either line alone. A year with higher revenue can have lower profit if expenditure rose faster. Always look at the vertical gap, never at one line in isolation.

Question: From the chart, Revenue in 2021 = 120 and 2022 = 150 (Rs cr), Expenditure in 2021 = 90 and 2022 = 100 (Rs cr). Find (a) the percentage increase in profit from 2021 to 2022 and (b) the profit as a percentage of revenue in 2022.

Solution:
Step 1: Compute profit for each year. Profit 2021 = 120 − 90 = 30. Profit 2022 = 150 − 100 = 50.
Step 2: For (a), the base is profit of 2021. Percentage increase = (50 − 30)/30 × 100.
Step 3: 20/30 = 2/3 = 0.6667, so the answer is 66.67%.
Step 4: For (b), the base is revenue of 2022 = 150. Profit margin = 50/150 × 100.
Step 5: 50/150 = 1/3 = 0.3333, so the answer is 33.33%.
Conclusion: (a) 66.67% increase in profit; (b) 33.33% profit margin in 2022. Different bases, very different answers — that is the entire point of the lesson.

:::compare

Quantity asked	Formula	Base (denominator)	2022 value
Profit	Revenue − Expenditure	—	50
% change in profit (2021→2022)	(P₂ − P₁)/P₁ × 100	Previous year profit (30)	66.67%
Profit margin in 2022	Profit / Revenue × 100	Same-year revenue (150)	33.33%
Expenditure as % of revenue	Expenditure / Revenue × 100	Same-year revenue (150)	66.67%
:::

:::keypoints

• Profit at each point = vertical gap between Revenue and Expenditure lines.
• Compute profit for every year once, write it above the chart — never recompute.
• "% increase in profit" → base is previous year's profit.
• "Profit margin" → base is same year's revenue.
• A rising revenue line does not guarantee rising profit; watch the gap.
• Loss appears when the Expenditure line crosses above Revenue.
• "Highest profit year" need not be the highest revenue year.
• Ratios of profits cancel units; do not bother converting Rs cr.
  :::

:::memory
G-P-M for dual-line charts: Gap gives profit, Previous profit is the base for change, Margin uses same-year revenue as the base. Whisper "G-P-M" before every DI caselet on line charts.
:::

:::recap

• Dual-series line chart = two quantities, one axis; the vertical gap is the story.
• Pre-compute profit per year before reading any sub-question.
• Pick the right base — previous profit for change, same-year revenue for margin.
• One pass of arithmetic, many sub-questions answered.
  :::

A pie chart's full circle = 360° = 100% of the total. Conversion: 1% = 3.6°, and 1° = 5/18 %. To find a sector's value: (sector % or sector°/360) × total. SBI PO often gives ONE pie in degrees and another in percentages, or a pie plus a table — convert everything to a common unit first. Key memory aids: 90°=25%, 45°=12.5%, 60°=16.67%, 72°=20%, 36°=10%, 120°=33.33%, 180°=50%. To find the total when one sector's value and its angle are known: total = value × 360/angle. For 'central angle of X' questions: angle = (X value/total) × 360. Always confirm whether the question wants degrees, percent, or absolute value.

Mixed (or 'combined') DI pairs a pie with a bar, table, or line — or gives two interlinked charts. The skill tested is data transfer: a value from chart 1 becomes the base for chart 2. Workflow: (1) compute the grand total from whichever chart gives absolute figures; (2) convert all sectors/series to absolute values; (3) only then answer. Trap: percentages in two different charts are taken on DIFFERENT bases — never add raw percentages across charts. For 'X in chart A as % of Y in chart B', compute both absolute values first. Time tip: in a 5-question mixed set, the first 2 minutes spent building a small absolute-value table pays back across all questions.

A pie shows a family's monthly budget of Rs 48,000 split as: Food 30%, Rent 25%, Education 20%, Savings 15%, Misc 10%. Food = 30% × 48000 = Rs 14,400. Education = 20% × 48000 = Rs 9,600. 'Central angle of Rent' = 25% × 360 = 90°. 'Rent is how much more than Misc': Rent 12,000 − Misc 4,800 = Rs 7,200, or as % = (25−10)/10 × 100 = 150% more. If a second pie splits Food into items, multiply: e.g. Vegetables = 40% of Food = 0.40 × 14,400 = Rs 5,760. Note the chained calculation — Food's value feeds the sub-pie.

Of all SBI PO Data Interpretation formats, the caselet is the one that breaks more aspirants than any chart or table. There is no diagram. There is no pre-built grid. Just a paragraph — sometimes a single dense one — that you must convert into structured numbers, often under 90 seconds of clock pressure. This lesson is about that conversion process.

Definition: A caselet DI is a data interpretation set in which information is presented as continuous prose, with numbers buried inside sentences rather than displayed as a chart or table. The aspirant must read, extract, and re-organise the data before any calculation begins.

Definition: A linking word is a verbal cue ("remaining", "twice", "one-third more than", "half of", "rest", "out of which") that signals an arithmetic or logical relationship between two quantities.

Why caselets feel harder than they are

The difficulty of a caselet is mostly organisational, not mathematical. The numbers themselves are usually simple — additions, percentages, ratios, a two-variable equation, or a Venn diagram. What kills time is re-reading the paragraph because you tried to "hold it in your head." If you spend the first 60–90 seconds tabulating, the calculations that follow are easy.

The official rule of thumb in PO coaching is brutal but correct: never attempt a caselet in your head. Underline, then table.

A four-step strategy that works in 90 seconds

1. Read once, fully, without writing. Get a feel for what is being described — is it a budget split? People in a city? Sales across days?
2. Underline every number and its label. "120 students", "20% boys", "remaining girls" — circle each pairing.
3. Build your own scaffolding. A two-column table for two-variable problems, a 3×3 grid for three-category breakdowns, or a Venn diagram for set-based caselets.
4. Watch for the linking words and translate them into equations.

Why it matters: SBI PO Mains DI has 30 marks in 45 minutes. A well-executed caselet pays the best return per minute in the entire paper, because most candidates skip them. Two solved caselets can lift a borderline score into the call-list zone.

Translating linking words into algebra

Once the data is on paper, the language becomes equations. A short reference:

• "A is 20 more than B" → A = B + 20
• "A is twice B" → A = 2B
• "Half of A is equal to B" → A/2 = B, i.e., A = 2B
• "One-third more than B" → A = B + B/3 = 4B/3
• "Remaining" or "Rest" → (Total) − (what is already assigned)
• "Out of which" → a subset relation

Worked example for the classic two-equation case:

Question: A and B together have Rs 180. A is 20 more than B. Find A and B.

Solution:
Step 1: Let B = x. Then A = x + 20 (translating "A is 20 more than B").
Step 2: A + B = 180, so (x + 20) + x = 180 → 2x = 160 → x = 80.
Step 3: B = 80, and A = 100.
Conclusion: A has Rs 100, B has Rs 80.

That is a six-line algebra problem hidden inside a paragraph. The skill is spotting it, not solving it.

Set-based caselets — the Venn diagram trick

When the paragraph mentions categories like "people who like tea / coffee / both / neither," draw a two-set Venn the moment you start reading. Use these formulas:

• n(A ∪ B) = n(A) + n(B) − n(A ∩ B)
• "At least one" = n(A ∪ B) — the union
• "Exactly one" = n(A) + n(B) − 2·n(A ∩ B) — union minus the overlap counted twice
• "Neither" = Total − n(A ∪ B)
• "Only A" = n(A) − n(A ∩ B)

For three-set problems, expand to:
n(A ∪ B ∪ C) = n(A) + n(B) + n(C) − n(A ∩ B) − n(B ∩ C) − n(A ∩ C) + n(A ∩ B ∩ C).

Real-world example: A bank's caselet might say "Out of 500 customers visiting Branch X on Monday, 280 used the ATM, 200 used internet banking, 60 used both, and the rest used neither." A Venn instantly tells you: only-ATM = 220, only-internet = 140, both = 60, neither = 500 − 420 = 80.

:::compare

Phrase in caselet	What you write on paper
"Remaining 40%"	(100% − already-assigned %)
"Twice as many men as women"	M = 2W
"30 more than"	A = B + 30
"Half of A"	A/2
"At least one of X or Y"	n(X ∪ Y)
"Exactly one of X or Y"	n(X) + n(Y) − 2 n(X ∩ Y)
"Neither X nor Y"	Total − n(X ∪ Y)
:::

Common misconception

Common misconception: Many aspirants believe that the trick to caselets is "speed reading." It is not. The trick is slow reading — once, with underlining — followed by fast tabulating. Speed reading makes you miss the linking words, which is exactly where the marks are.

Another common error is mixing up "at least one" with "exactly one." Read both phrases as: at-least-one = union, exactly-one = union − both-region. If you draw the Venn, the diagram itself reminds you which region you are being asked about.

Putting it all together — a SBI PO style mini-caselet

Question: In a society of 1,200 residents, 60% own a car. Of the car-owners, one-third also own a two-wheeler. Among the non-car-owners, 75% own a two-wheeler. How many residents own neither a car nor a two-wheeler?

Solution:
Step 1: Car owners = 60% of 1200 = 720. Non-car owners = 480.
Step 2: Car owners with a two-wheeler = (1/3) × 720 = 240.
Step 3: Non-car owners with a two-wheeler = 75% of 480 = 360. Non-car owners without a two-wheeler = 480 − 360 = 120.
Step 4: Residents owning neither = the 120 non-car owners without a two-wheeler.
Conclusion: 120 residents own neither.

Notice how every sentence in the caselet became one row of arithmetic — that is the conversion habit you are training.

:::keypoints

• Caselet DI = prose, no chart. Hardest format because YOU build the structure.
• Step 1 — read once fully. Step 2 — underline numbers. Step 3 — table or Venn. Step 4 — equations.
• "Remaining / rest" = Total − assigned. "Twice", "half", "one-third more" are all algebra.
• For sets: at-least-one = union, exactly-one = union − both, neither = total − union.
• n(A ∪ B) = n(A) + n(B) − n(A ∩ B) is the only formula you need for two-set caselets.
• 90 seconds of tabulating saves 3 re-reads. Never attempt in head.
• Two solved caselets often decide an SBI PO call list.
  :::

:::memory
"R-U-T-E" — Read once, Underline numbers, Table or Venn, Equation.
For sets: "At-Least = Add minus Both; Exactly = Add minus Twice-Both."
:::

:::recap

• A caselet is just a paragraph in disguise — a table, a Venn, or a pair of equations waiting to be drawn.
• The slow first read with underlining is the speed gain, not the loss.
• Master the linking-word translations and the Venn formulas; the arithmetic is easy.
• In SBI PO, caselets reward the patient — pick them when others skip them.
  :::

For heavy calculation DI use successive-percentage netting: a rise of a% then b% gives net = a + b + (ab/100). E.g. +10% then +20% = 10+20+2 = +32%. A +20% then −20% = −4% (never zero). For fraction-of-fraction, multiply fractions before touching the base: 3/5 of 2/3 of 900 = (3/5 × 2/3) × 900 = 2/5 × 900 = 360. Digit-sum / first-digit approximation eliminates wrong options fast in 'find approximate value' questions. For ratios that must sum to a total, scale the ratio: if A:B:C = 2:3:5 and total = 4000, each part = 4000/10 = 400, so A=800, B=1200, C=2000. Always reuse the 'one-part value' across the whole question.

Caselet: 'A shop sold 540 items on Day 1. On Day 2 sales rose by 1/3. On Day 3 sales were 90 fewer than Day 2.' Day 2 = 540 × (1 + 1/3) = 540 × 4/3 = 720. Day 3 = 720 − 90 = 630. Total 3-day sales = 540 + 720 + 630 = 1890. 'Day 3 as % of total' = 630/1890 × 100 = 33.33%. 'Average daily sales' = 1890/3 = 630. The discipline: write Day1, Day2, Day3 in a column the moment you read each clause — by the time you finish the paragraph the table is done and every sub-question is a lookup, exactly the SBI PO time-saving habit.