Treat CGL preparation as discrimination training: for each subject, identify the concepts that look interchangeable, learn the rule that separates them, and tag every practice mistake as concept, calculation, reading, or time. The tag distribution, reviewed weekly, tells you exactly what to study next.
Percentage Change vs Percentage Point Change in Quant Questions
A percentage change multiplies the base value; a percentage-point change is a plain subtraction between two percentages. Deciding which one a question asks for prevents choosing an option built on the wrong operation.
The signal is in the wording. 'Sales increase by 20%' means the new figure is 1.2 times the old one. 'The share of urban voters rises from 40% to 55%' is a rise of 15 percentage points — the shares themselves are not multiplied. Consecutive percentage changes compound: a 25% rise followed by a 20% fall gives 1.25 × 0.80 = 1.00, no net change at all. Keep fraction equivalents such as 1/4 for 25% and 1/5 for 20% handy, because they turn these multiplications into single-step fraction cancels.
Scenario: a salary rises 25%, then the new salary falls 20%. The tempting choice is a net 5% rise, because 25 − 20 = 5. The better decision is to multiply: 1.25 × 0.80 = 1.00, so the salary is exactly back where it started. If a base salary of 40,000 is given, 40,000 → 50,000 → 40,000 confirms it in seconds. This matters because both answers — 'no change' and '5% up' — can sit side by side in a set of options, and the multiplicative route takes barely longer once the fraction equivalents are automatic.
Valid Conclusions vs Possible Conclusions in Reasoning Syllogisms
A valid conclusion must hold in every diagram that fits the statements; a possible conclusion needs only one such diagram. Treating these as the same test — in either direction — produces avoidable wrong picks.
Draw, don't debate. For 'some' statements, sketch at least two arrangements, because 'some A are B' is compatible with all A being B as well as with partial overlap. Then test each option against every diagram: if an option fails in even one diagram, it is not a valid conclusion; if it survives in at least one, it qualifies as a possible conclusion. Writing the two diagrams takes seconds and removes the guesswork that comes from reasoning verbally about 'some' and 'all'.
Take: 'Some pens are books. All books are pages.' 'Some pens are pages' is valid — the overlapping pens sit inside books, hence inside pages. 'Some pages are pens' is valid too, the same overlap read backwards; the reversed wording is the trap, since the overlap itself does not change direction. 'All pages are books' is not supported. 'Some pens are not pages' is a possible conclusion: place one pen outside the books in a second diagram. Label each option valid, possible, or impossible before choosing.
Error Spotting vs Sentence Improvement in the English Section
Error spotting asks you to locate the faulty part of a sentence; sentence improvement asks you to pick the best replacement for a highlighted part. The same grammar rules, but different decision steps.
For spotting, check one function at a time: subject–verb agreement, tense sequence, preposition choice, pronoun case, then parallelism. In 'One of my friend live nearby', a sentence can hold more than one fault, but the structured check finds them separately — 'friends' for the plural after 'one of', 'lives' for agreement. Naming the rule out loud when you review each item matters as much as the fix itself, because the label is what transfers to the next sentence you meet.
For improvement, an option can be grammatical on its own and still wrong in context. Given the highlighted phrase 'since five years' in 'He has been working here since five years', the option 'for five years' repairs the duration marker without touching anything else. An option that rewrites the whole clause, however correct it reads alone, goes too far. The decision rule: identify the fault first, then choose the option that fixes exactly that fault — never the longest or most elegant rewrite.
Exact Computation vs Estimation in Data Interpretation Sets
Data interpretation differs from pure quant because the dataset is the given. Before computing, classify the question: exact value, comparison between entries, or approximate share. Each class earns a different method.
Make classification a deliberate triage step you practice on every set. For exact-value questions with small figures, do the full arithmetic. For comparison-type items, train yourself to compare differences or ratios between entries instead of computing both completely — try an exercise where you rank five entries by ratio alone, then verify by computing, and note how often the ranking holds. Share questions reduce to one division: a 108° sector of a pie chart is 108/360 = 30% of the total, no total required. Spending the first few seconds of each question on this classify-first habit replaces the default of computing every number you see on the page.
Scenario: a pie chart shows four expenditure sectors in degrees, with a total of 24,000 given, and asks for the share of the largest sector, 144°. The plausible mistake is converting every sector to rupees — 24,000 × (degree/360) four times — before dividing the largest by the total. The better decision: 144/360 = 40% directly; the stated total is not needed at all. This matters inside a set, because the seconds saved on one question become available for the harder items that follow it in the same passage.
Static Facts vs Current-Affairs Recall in General Awareness
Static facts change rarely and are organized in structures — rivers and tributaries, constitutional articles, historical timelines. Current events carry dates and associations that decay faster, so the two need different review spacing.
Build static facts as chains rather than isolated cards: each river with its tributaries and the states it crosses, each constitutional article beside the principle it embodies. Chains give you multiple retrieval routes — remembering one state can lead to its river, its dam, and its neighboring facts. Review static chains on a widening schedule; a fact recalled correctly three times at increasing gaps needs far less attention than one you keep re-reading on the page without ever testing yourself on it.
For current events, record each item as event plus date plus anchor: the scheme launched, the location, the ministry involved. The anchor is the static hook — a new dam project links back to its river and state from your static chains, so the two stacks reinforce each other instead of competing for attention. Consolidate monthly into a single dated list rather than collecting daily clippings that are never revisited; one consolidated pass per month outperforms scattered fragments.
Computer Knowledge Terms That Look Interchangeable
Computer knowledge questions test recognition of definitions, and the difficulty sits in near-synonyms: memory versus storage, RAM versus ROM, system versus application software. Contrast lists beat alphabetical glossaries here.
Write each pair as a one-line discriminator plus an example. RAM is volatile working space — an unsaved document disappears on power-off; ROM is non-volatile start-up instructions. Memory holds what the processor is using right now; storage holds files whether the machine is on or not. System software runs the machine; application software performs user tasks. A two-column table with the discriminator written in the middle row makes the difference visible at a single glance.
Reinforce the contrasts with labeled pictures you make yourself: one diagram splitting 'volatile — clears on power-off' from 'non-volatile — persists', with RAM, cache, and open files on the first side and SSD, hard disk, and ROM on the other. Then quiz in term-only form — cover one column and recall the discriminator from the term alone. The exam presents the terms, not your table, so your retrieval must run in that direction.
A Four-Week Practice Cycle With an Error-Tag Rubric
Rotate subjects across the week, then close each cycle by tagging every wrong answer as concept, calculation, reading, or time. The tag distribution — not the raw score — decides next week's emphasis.
A four-week cycle: in week one, study one paired-concept topic per subject and finish a short set on it the same day. Week two shifts to mixed sets with a data-interpretation emphasis, applying the classify-before-computing habit. Week three adds timed full-section sets, which is when the tag 'time' starts to carry real information. Week four repeats only the pairs your tags flagged, then re-tests them. Repeat the cycle with fresh material; the structure stays, the content changes.
After every set, tag each error and total the four categories. The rubric below gives learning milestones for closing a cycle — they describe study progress, not a predicted exam result. When a milestone is missed, spend one more cycle on that element rather than moving forward; when all are met, raise the difficulty of the material rather than the number of sets.
- Concept errors fall below a third of all tagged errors before you move to timed sets.
- In data interpretation, at least half of share-type questions are answered from a single division without touching the stated total.
- Every tagged reading error corresponds to a grammar or vocabulary rule you can name aloud.
- Time-tagged errors cluster in one identifiable section, which becomes week four's repeat topic.
- Readiness check: you can state the discriminator for every concept pair in the table below from memory, without looking.
| Concept pair | Where it appears | Core difference | Quick decision rule |
|---|---|---|---|
| Percentage change vs percentage point | Quantitative Aptitude | Multiplicative vs additive | Multiply consecutive changes; subtract only when both values are percentages |
| Valid vs possible conclusion | Reasoning (syllogisms) | True in every diagram vs at least one diagram | Reject an option only if no diagram supports it |
| Error spotting vs sentence improvement | English | Locate the fault vs replace the highlighted phrase | For improvement, fix only the highlighted fault |
| Exact vs estimated DI answer | Data Interpretation and Analysis | Computed value vs ranked or approximate share | Compare and classify before you calculate |
| Memory vs storage | Computer Knowledge | Working space vs permanent files | Ask: does the data survive a power-off? |
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.
