IBPS RRB Treasury Manager common mistakes
IBPS RRB Treasury Manager · Understand the traps and how to avoid them.
In the Reasoning section, spending more than about 60–75 seconds on a single multi-condition puzzle or seating-arrangement question instead of leaving it and returning later, so the last 8–10 questions of the section are never read.
Puzzles are presented as a single block of text and candidates feel they have 'almost solved it', so they sink time into one question that carries the same single mark as a quick syllogism or inequality item; sectional timing pressure is not rehearsed because practice is done untimed.
What to do instead
Practise with a strict sectional clock and a written rule: if a puzzle's first two conditions do not yield a fixed position within 90 seconds, mark it and move on. Build a personal order of attack (inequalities and syllogisms first, puzzles last) and drill it until it is automatic, so no question is left unread at the section's end.
Solving seating-arrangement and floor/box puzzles directly in the head or in a single messy column, then misreading one's own notation and marking the wrong option.
Under time pressure candidates skip setting up a grid or a fixed notation (e.g. A > B for 'taller than', arrows for facing direction), so when a new condition forces a rearrangement they cannot track which positions were already fixed.
What to do instead
Adopt one standard notation and always draw the frame first: a row of blanks for linear arrangements, a circle with inward/outward arrows for circular ones, a two-column table for floor puzzles. Enter each condition as a symbol or tick in the frame before answering, and verify the final arrangement against every stated condition once.
In Quantitative Aptitude, attempting every question in sequence rather than triaging, so calculation-heavy topics (time-work pipes, boats, complex data interpretation) consume the section and easy arithmetic is left undone.
Candidates equate effort with marks and are reluctant to skip, and they have not measured which question types they personally solve fastest; DI sets look short but hide three sub-questions each requiring separate computation.
What to do instead
Classify each question in the first 10 seconds as 'do now', 'do if time', or 'leave'. Do approximation, simplification, number series and quadratic comparisons first, then DI, then word problems. In mocks, record the time taken per topic and set a per-question cap (about 60 seconds for a standalone sum) that you actually enforce.
Losing marks on Data Interpretation through estimation errors, unit mismatches (lakh vs crore, percentage vs percentage points) and answering the wrong sub-question of a set.
DI is read quickly after a long calculation, and the five options are often close, so a rounding shortcut taken at the wrong step changes the answer; candidates also compute a value and then pick the option for a different quantity than the one asked.
What to do instead
For every DI set, first write down the units and the base of each percentage in the margin, and underline the exact quantity the question asks for before calculating. Use approximation only to eliminate options, and do an exact check whenever two options differ by less than about 5 per cent. Re-read the sub-question label after computing.
In the English or Hindi Language section, reading the passage first in full and then the questions, and choosing options that merely repeat words from the passage rather than answering the question asked.
School habits favour full reading, and option setters deliberately place familiar passage vocabulary in wrong options; candidates also skip the instruction line stating how many questions the passage covers.
What to do instead
Read the questions first, note the keyword each asks about, then scan the passage for those keywords and read only the surrounding two or three sentences. For inference and tone questions, reject any option that is stated literally but does not answer the question. Check the passage's question range before starting.
Treating the language section's grammar items (error spotting, fillers, sentence rearrangement) as pure instinct, without applying a checklist of subject-verb agreement, preposition collocation, tense consistency and parallel structure.
These items are quick and candidates answer them in seconds on 'what sounds right', which fails when the sentence is deliberately long or when the error is one of usage rather than obvious grammar.
What to do instead
Run a fixed four-point check on every error-spotting and filler item: verb agreement with the real subject, correct preposition after the verb or adjective, tense consistency across clauses, and parallel form in lists. For rearrangement, find the opening sentence by looking for a standalone noun phrase with no backward reference, then chain by pronouns and connectors.
In General Awareness, revising only static banking history and forgetting that a large share of questions concerns the last six to eight months: current RBI policy rates, recent monetary policy statements, appointments, schemes, budget figures and market regulators.
Old guides and coaching notes are static and easily available, while current affairs require disciplined monthly collection; candidates also assume 'banking awareness' means only definitions of CRR, SLR and negotiable instruments.
What to do instead
Maintain a one-page monthly sheet: repo rate and stance, reverse repo, MSF, bank rate, CRR, SLR, inflation and IIP prints, key appointments, new schemes and their launch amounts, and recent SEBI/RBI/IRDAI regulatory changes. Revise the last eight months' sheets weekly and test yourself only on items you can date.
Preparing Treasury and financial-market topics only at headline level - knowing that a bond's price and yield move inversely but not being able to apply duration, or confusing the call money market with the repo market and primary dealers with banks.
The treasury portion of the syllabus is specialised and candidates from a general banking background rely on one-line definitions, which cannot answer a question that asks which operation the RBI uses to inject or absorb liquidity, or what a rise in yield does to a held portfolio.
What to do instead
Build a small working model of each instrument: who issues it, tenor, whether it is a money-market or capital-market instrument, and how its price responds to a rate change. Specifically separate RBI liquidity tools (repo, reverse repo, MSF, SDF, OMO, CRR, SLR) by direction of liquidity impact, and learn duration as the approximate percentage price change for a 1 per cent yield move.
Not attempting the separate Professional Knowledge / Treasury paper's descriptive or specialised questions because the candidate prepared only for the objective Reasoning and Aptitude pattern of the preliminary stage.
Candidates prepare from the preliminary exam's pattern and under-estimate the main examination's professional-knowledge component, so they arrive without structured material on treasury operations, risk management and forex, and write vague answers.
What to do instead
Confirm the current pattern from the official notification for the cycle you are applying to, then prepare a short structured answer template for treasury topics: definition, mechanism or process, an example with numbers, and a risk or regulatory point. Practise writing four or five such answers under timed conditions so recall becomes usable prose.
Taking full-length mocks without analysing them, so the same errors (misread question, wrong unit, skipped question, guessed option) repeat across tests and the score plateaus.
Mock analysis is tedious and candidates prefer taking a fresh test, which feels productive; without a written error log there is no feedback loop, and sectional cut-offs are breached by the same one or two sections each time.
What to do instead
After every mock, spend at least as long analysing as taking it: log each wrong and skipped question with its cause in one of four categories (knowledge gap, calculation slip, misread, time), and re-solve it without looking at the solution. Review the log before the next mock and track only whether the count in your worst category is falling.