This page is a case gym . The Unitary method — direct and inverse proportion parent taught the two laws; here we run them through every kind of situation an exam or the real world can throw at you — including the weird "edge" cases that trip people up: zeros, a mix of both proportions in one problem, and limiting behaviour.
Intuition Read this first
Two words decide everything: direct (ratio y / x stays fixed) or inverse (product x y stays fixed). Before every example, you will forecast the direction. If your forecast and your arithmetic disagree, one of them is wrong — that clash is your safety net.
Here is the full map of cases. Every example below is tagged with the cell it fills.
Cell
Case class
What makes it tricky
A
Direct, scale up (more)
plain "value of one, then multiply"
B
Direct, scale down (fewer)
answer must come out smaller
C
Inverse, plain
product stays fixed, not ratio
D
Inverse, non-integer unit
the "value of one" is a fraction
E
Zero / degenerate input
0 workers, 0 items — what breaks?
F
Limiting behaviour
as workers → ∞ , days → ?
G
Real-world word problem
must extract which quantities pair
H
Exam twist: chain of both
direct and inverse in one problem
Cells A, B → direct. C, D → inverse. E, F → edge/limit. G, H → applied.
Worked example 4 notebooks cost ₹100. Find the cost of 9 notebooks.
Forecast: More notebooks than 4, so the answer should be more than ₹100. Guess a rough figure before reading on.
Step 1 — Direction test. More notebooks → more cost. Same direction → direct .
Why this step? The whole method branches here; guessing wrong sends every later line the wrong way.
Step 2 — Value of ONE. 4 100 = ₹25 per notebook.
Why divide? We split the total ₹100 equally across 4 notebooks to see what a single one "carries".
Step 3 — Scale to 9. 25 × 9 = ₹225 .
Why multiply? Each of the 9 notebooks carries ₹25, so we stack nine of them.
Verify: Ratio check — 4 100 = 25 and 9 225 = 25 . Both ratios equal, and ₹225 > ₹100 matches the forecast. ✓
Worked example 15 identical bricks weigh 30 kg. What do 6 bricks weigh?
Forecast: Fewer bricks (6 < 15) → the weight must come out less than 30 kg.
Step 1 — Direction test. More bricks → more weight. Same direction → direct .
Why this step? Scaling down still uses the direct law; only the final number shrinks, not the method.
Step 2 — Value of ONE. 15 30 = 2 kg per brick.
Why divide? Weight shares equally over the 15 bricks.
Step 3 — Scale to 6. 2 × 6 = 12 kg.
Verify: 15 30 = 2 = 6 12 — ratio preserved, and 12 kg < 30 kg as forecast. ✓
Common mistake "Scaling down means switch to inverse"
Wrong instinct: because the answer got smaller, some students flip to the inverse rule.
Fix: Direction of the relationship (do both move the same way?) decides direct vs inverse — not whether your particular answer is bigger or smaller. Fewer bricks weighing less is still both-move-together = direct.
Worked example 6 pumps empty a tank in 10 hours. How long for 4 pumps?
Forecast: Fewer pumps → each has to do more → longer than 10 h.
Step 1 — Direction test. More pumps → less time. Opposite directions → inverse .
Step 2 — The fixed product (name it!). 6 × 10 = 60 pump-hours — the total size of the job.
Why multiply? In inverse proportion the product stays constant, not the ratio. 60 pump-hours is the whole task no matter how we split it.
Step 3 — Solve for new time. 4 × t = 60 ⇒ t = 4 60 = 15 h.
Why divide? The same 60 pump-hours now shared among only 4 pumps, so each works longer.
Verify: 4 × 15 = 60 = original product. And 15 h > 10 h, matching the forecast. ✓
Worked example 7 machines produce a batch in 9 hours. How long for 5 machines?
Forecast: Fewer machines (5 < 7) → more than 9 h.
Step 1 — Direction test. More machines → less time → inverse .
Step 2 — Fixed product. 7 × 9 = 63 machine-hours .
Step 3 — Solve. 5 × t = 63 ⇒ t = 5 63 = 12.6 h.
Why this is fine: the "value of one" (63 machine-hours for the whole job) needn't split into a whole number of hours. 12.6 h = 12 h 36 min.
Verify: 5 × 12.6 = 63 ✓, and 12.6 > 9 as forecast. ✓
Intuition Fractions are allowed
Nothing in the law says answers must be whole. The constant (63 machine-hours) is real; how it divides among machines can be a decimal.
Worked example 5 workers dig a trench in 12 days. What happens with
0 workers ? And what does "0 days " require?
Forecast: With nobody digging, the trench is never finished. So "days" should blow up — not a normal number.
Step 1 — Direction & product. Inverse. Fixed job = 5 × 12 = 60 worker-days.
Step 2 — Set workers to 0. 0 × t = 60 .
Why this breaks: no value of t makes 0 × t = 60 , because 0 × t = 0 always. Zero workers → the equation has NO solution → the task can never be done. The unitary method flags this honestly as "impossible", not as a number.
Step 3 — Now ask: 0 days. Set t = 0 : x × 0 = 60 again has no solution . Finishing in zero time is equally impossible.
Verify: Both degenerate cases give the contradiction 0 = 60 , so both are ruled out. A correct model should refuse to produce a finite answer here. ✓
Common mistake Blindly dividing by zero
Students sometimes write t = 0 60 and call it "infinity" as if that's a valid answer. Division by zero is undefined ; the honest statement is "no finite time completes it — it never finishes." See Example 6 for the limit that gives infinity its meaning.
Worked example Same 60-worker-day trench. What happens to the number of days as workers grow
without bound (x → ∞ )? And as x → 0 + (a tiny team)?
Forecast: Loads of workers → time crashes toward almost nothing. A single sluggish helper → time balloons.
Step 1 — Write the rule. t = x 60 (days as a function of workers x ).
Why this form? Inverse proportion is x y = k , so y = k / x — this is the same y = k / x curve you meet in Linear Equations as a non -linear (reciprocal) relation.
Step 2 — Push x large. As x → ∞ , x 60 → 0 . Time shrinks toward zero but never reaches zero (Example 5 showed 0 days is impossible).
Step 3 — Push x small. As x → 0 + , x 60 → ∞ : with a whisker of a workforce, days explode toward infinity — the smooth version of Example 5's "never finishes".
Verify (spot values): x = 60 ⇒ t = 1 day; x = 120 ⇒ t = 0.5 day; x = 600 ⇒ t = 0.1 day. Falling toward 0. ✓
Worked example A recipe for 8 people needs 600 g rice and takes 45 min of cooking. You are cooking for
20 people . How much rice, and does cooking time change?
Forecast: Rice scales with people → more rice. Cooking time of a pot is set by the pot, not the head-count → probably unchanged.
Step 1 — Sort the quantities.
Rice vs people: more people → more rice → direct .
Cooking time vs people: boiling rice takes the same 45 min whether it feeds 8 or 20 (bigger pot, same simmer) → not proportional at all . This is the trap: not every pair is a proportion.
Why this step? The hardest part of word problems is deciding which quantities pair up. Extract that before touching arithmetic — see Ratio and Proportion .
Step 2 — Rice, value of one person. 8 600 = 75 g per person.
Why divide? Direct proportion → go to one first.
Step 3 — Scale to 20. 75 × 20 = 1500 g = 1.5 kg.
Step 4 — Time. Stays 45 min (independent variable, not proportional).
Verify: 8 600 = 75 = 20 1500 ✓. Time unchanged, matching forecast. ✓
Worked example 12 workers, each working 8 hours a day, build
3 houses in 20 days. How many days will 16 workers, working 6 hours a day, need to build 5 houses?
Forecast: More workers → faster (down). Fewer hours/day → slower (up). More houses → more work (up). Several forces pull in different directions, so we combine them carefully.
Step 1 — List each factor and its direction (relative to DAYS).
Workers 12 → 16 : more workers → fewer days → inverse , multiply by 16 12 .
Hours/day 8 → 6 : fewer hours → more days → inverse on hours, multiply by 6 8 .
Houses 3 → 5 : more houses → more days → direct , multiply by 3 5 .
Why this step? The "chain rule" of proportion: start from the known days and multiply one correcting ratio per changing quantity. Each ratio is written so its effect matches the up/down forecast.
Step 2 — Assemble.
t = 20 × 16 12 × 6 8 × 3 5
Why written this way? Inverse factors put the new value on the bottom (so more workers → smaller factor); direct factors put the new value on top (more houses → bigger factor).
Step 3 — Compute.
t = 20 × 0.75 × 1.3333 … × 1.6667 … = 16 × 6 × 3 20 × 12 × 8 × 5 = 288 9600 = 33. 3 days .
So t = 33 3 1 days.
Verify (total work must balance). Work = workers × hours/day × days, per house.
Old: 3 12 × 8 × 20 = 640 worker-hours per house.
New: 5 16 × 6 × 33. 3 = 5 3200 = 640 worker-hours per house. ✓ Same effort per house — the model is consistent. Connect this to Time and Work .
Mnemonic Chain-of-proportion setup
Start with the known answer. For each changing quantity ask "does this push my answer up or down ?" Up → the ratio is (bigger/smaller); down → (smaller/bigger). One ratio per quantity, all multiplied.
Recall Did we hit every cell? (cover the answers)
A Direct up ::: Ex 1 — ₹225
B Direct down ::: Ex 2 — 12 kg
C Inverse plain ::: Ex 3 — 15 h
D Inverse fractional ::: Ex 4 — 12.6 h
E Zero input ::: Ex 5 — impossible (no solution)
F Limit ::: Ex 6 — t → 0 as x → ∞
G Word problem ::: Ex 7 — 1.5 kg rice, time unchanged
H Chain of both ::: Ex 8 — 33 3 1 days
Recall One-line "why" for each edge case
Why does 0 workers give no answer? ::: 0 × t = k can never equal a positive k .
Why does the reciprocal curve never touch zero? ::: 60/ x shrinks forever but stays positive for all finite x .
Why isn't cooking time proportional to diners? ::: The pot simmers the same 45 min regardless of head-count.
Ratio and Proportion — extracting which quantities pair (Ex 7) is proportion-spotting.
Percentages — "per person" (75 g) is a unitary value, exactly like "per 100".
Speed Distance Time — Ex 3 & 6 are speed–time inverse cousins.
Time and Work — Ex 8's worker-hours balance is the master identity there.
Linear Equations — t = 60/ x is the reciprocal curve; contrast with the straight line y = k x .