IBPS RRB GBO common mistakes
IBPS RRB GBO · Understand the traps and how to avoid them.
In Reasoning, starting with the first puzzle on the screen - usually the 8-variable floor-plus-flat or month-year arrangement - and spending 8-10 minutes on it before touching the rest of the section.
Puzzles look impressive and candidates believe 'the first one is meant to be done', plus the printed/on-screen order creates an implicit instruction to go top to bottom. Under exam pressure, sunk cost keeps them adding 'one more clue' instead of leaving.
What to do instead
Use a 3-minute scanning pass: read every puzzle's first two lines and tag it A (fewer variables, direct clues), B (doable after elimination), C (too many 'not'/'either-or' clues). Solve only A puzzles in the first 10 minutes, then B. Never open a puzzle without first noting how many attributes and how many definite ('is', 'exactly') clues it has.
Ignoring the 30-40 one-line Reasoning items (inequality, direction sense, blood relation, order-ranking, alphabet series, coded inequality) and treating Reasoning as 'puzzle + syllogism only'.
These items are scattered and easy to skip when candidates are mentally braced for heavy puzzles; also candidates over-fear possibility-based syllogisms and skip the whole cluster.
What to do instead
Bank these as a fixed 8-10 minute block. Practise inequality and direction sense until each is under 35 seconds, and learn the standard possibility rules (all-not, some-not, complementary pairs) so syllogism becomes a rule application rather than a guess. Target 12-15 marks from this block alone before touching any arrangement.
Doing Data Interpretation and simplification with full long division and written multiplication instead of approximating and using the answer options.
School habit - candidates were trained to compute exactly and distrust estimation. With no rough-paper shortcut habits and 40 questions in a shared 45-minute prelims window, exact arithmetic silently eats 60-90 seconds per question.
What to do instead
Memorise the fraction-to-percentage table (1/6 to 1/15, 1/16 to 1/20), squares to 30, cubes to 15, and the 5%, 10%, 15%, 20% multipliers. For every DI question, compute only to the first two significant digits and eliminate options that differ visibly. Drill 10 DI sets with a 'no full division' rule until it feels natural.
Treating number series, approximation and quadratic comparison as 'easy but slow' items and letting them consume 12-15 minutes of the Quant section.
These questions feel safe, so candidates linger to be sure of accuracy; without a per-item stopwatch they do not notice each one taking 70-90 seconds instead of 30.
What to do instead
Set a hard 15-minute ceiling for the 'quick wins' block (approx 5, series 5, quadratic 5) and practise with a visible lap timer. Learn the standard series patterns (difference, ratio, square/cube ±, double-difference, alternating) and the factorisation shortcut for quadratics so each item is a pattern match, not a search.
Attempting the paper in strict printed order and refusing to leave a stuck question, so a single DI set or arrangement burns 10 minutes of the 45-minute prelims clock.
Candidates rehearse content but not strategy; the screen order feels authoritative and leaving a half-solved question feels like waste, so loss-aversion overrides arithmetic common sense.
What to do instead
Fix an attempt order in advance from mock evidence (e.g., one-line Reasoning → quick-win Quant → 2 easy puzzles → 2 easy DI sets → fill). Apply a 45-second rule: if you cannot see the method, mark and move on permanently. Rehearse this order in at least 8 full timed mocks so it becomes automatic.
Marking every unattempted question in the last minute on the assumption that one-fourth negative marking is trivially small.
Candidates underestimate the drag because they never compute the expectation: with five options, four blind guesses give roughly +1 and -1, so blind guessing on 20 questions is a coin-toss over 20 marks, not a free option.
What to do instead
Operate a two-tier guessing rule. Tier 1: if two options are eliminated, the expected value turns positive - attempt it. Tier 2: no elimination - leave it blank. Track 'educated guess' accuracy in a log; if it falls below 30% over two mocks, tighten Tier 1 to three eliminated options.
Preparing General/Banking Awareness by memorising static history (RBI founded 1935, first bank, nationalisation years) and ignoring the last six months of policy, schemes, appointments and budget numbers.
Static compilations are easy to buy and easy to feel productive with, while current affairs require monthly upkeep. Many candidates also stop updating awareness once prelims are over and never restart for mains.
What to do instead
Split awareness 70:30 in favour of the current cycle. Maintain a one-page monthly sheet: RBI repo/reverse repo/CRR/SLR and MSF numbers from each policy statement, key appointments and their organisations, new schemes and their launch amounts, budget allocations for agriculture and MSME (relevant to rural banks), and RBI circular headlines. Revise the six-month sheet weekly at a fixed slot.
Reading the full English/Hindi passage word by word before looking at the questions, spending 8-10 minutes on one RC set.
Exam-hall anxiety makes candidates seek 'comprehension' first; also school reading habits reward linear reading, but the section rewards targeted retrieval. With 40 questions for 40 marks in the mains paper, one slow passage costs an entire grammar cluster.
What to do instead
Read the questions first, note the keyword and question type, then scan only the relevant paragraph. Also clear grammar and vocabulary items (error spotting, fillers, cloze, synonyms) before RC - they are faster marks. If your paper offers a choice of English or Hindi, sit at least four full mocks in the language you will actually select; do not choose Hindi on comfort alone if all your practice has been in English.
Treating Computer Knowledge as a low-weight afterthought and not revising it at all until the week before the mains.
Twenty marks looks minor next to Reasoning and Quant, so it gets dropped from the study plan; candidates also assume everyday phone and social-media use covers the syllabus.
What to do instead
Block two hours a week from the start. Cover only the syllabus-shaped topics: generations and basic architecture, input/output devices, memory units and hierarchy, Windows and MS Office basics, shortcut keys, networking terms and topologies, internet and email protocols, DBMS basics, and cyber security terms (phishing, firewall, malware types). Finish with 15 topic-wise quizzes of 20 questions each; the section is usually finishable in 10-12 minutes in the exam.
Taking mocks but only checking the score, never reviewing the paper to classify errors as concept gaps, calculation slips, misread questions or time loss.
Score-checking gives an emotional hit and feels like progress; full analysis takes 90 minutes and exposes uncomfortable patterns. Because prelims cut-offs are state-wise and shift each cycle, a raw score alone tells a candidate almost nothing about readiness.
What to do instead
For every mock, log each wrong or left question in one of four buckets and note the seconds spent. Rebuild a 20-question 'repeat offenders' set from bucket 1 and 2 and re-solve it after 48 hours. Track three numbers per mock rather than the score: attempts, accuracy percentage and time per section; target 88-92% accuracy on attempted questions and fix the weakest section before increasing attempts.