IBPS RRB Law Officer common mistakes
IBPS RRB Law Officer · Understand the traps and how to avoid them.
Attempting every Professional Knowledge question in sequence without regard to time, so the last 15–20 questions are left blank when the section timer expires.
Candidates treat the 40-question professional knowledge section as a knowledge test rather than a timed test; because many questions are long statutory scenarios, each one feels worth finishing, and there is no practised pacing rule. The section often carries more marks per question, so blanks are doubly costly.
What to do instead
Adopt a two-pass rule: first pass answers only questions solvable in under 45 seconds, marking the rest; second pass spends the remaining time on flagged items. Practise with a hard stop at 30 seconds per question in mocks and record how many marks the second pass recovers.
Answering contract-law questions from general memory of 'what seems fair' instead of identifying the exact statutory provision, e.g. treating a minor's agreement as voidable rather than void, or confusing coercion with undue influence.
The Indian Contract Act concepts are taught at a high level in law school, and candidates rely on intuition where the section tests precise section-level distinctions and consequences (void vs voidable vs unenforceable, damages vs specific performance).
What to do instead
Build a one-page comparison grid for the high-yield pairs: void/voidable/illegal, coercion/undue influence/fraud/misrepresentation, condition/warranty, indemnity/guarantee, bailment/pledge. For each, note the defining section, the remedy, and one worked example, and revise the grid weekly rather than rereading the Act.
Confusing SARFAESI, DRT and IBC remedies - for example saying a secured creditor must always approach the DRT first, or that SARFAESI applies to unsecured creditors or to agricultural land.
The three regimes overlap in purpose but differ in trigger, forum, thresholds and exclusions; coaching summaries often compress them into one 'recovery' topic, so candidates blur the 60-day notice under Section 13(2), the Section 13(4) measures, the Section 17 appeal to the DRT, and the Section 14 magistrate route.
What to do instead
Make a three-column table (SARFAESI / DRT / IBC) covering: who may invoke, minimum default, notice period, forum, appeal route, exclusions, and effect on possession. Attach the specific section numbers to each cell and test yourself by writing the sequence from demand notice to possession from memory.
Skipping or rushing the General Awareness (banking and financial sector) section on the assumption that current affairs cannot be prepared, then losing easy marks on static banking items like RBI functions, monetary policy tools, and regulator mandates.
Candidates conflate 'general awareness' with unpredictable news and under-invest in the static core, which is actually the most reliably repeated content; they also read news passively without converting it into exam-style facts (who, what rate, which regulator, which Act).
What to do instead
Split preparation: a daily 15-minute current-affairs log limited to banking/finance/regulatory items with a one-line 'exam fact' each, plus a fixed static list (RBI Act provisions, CRR/SLR/Repo/Reverse Repo/MSF, SEBI and NABARD roles, key committees, financial inclusion schemes). Revise the static list on a spaced schedule and quiz it weekly.
In Reasoning, spending several minutes on one puzzle or seating-arrangement set and thereby losing the ability to attempt the easier independent questions later in the section.
Puzzle sets are visually engaging and create sunk-cost pressure - having drawn the grid, candidates feel compelled to finish. Sectional timing means the cost is invisible until the section ends.
What to do instead
Set a 90-second decision gate per puzzle set: if the arrangement has not begun to resolve, abandon it and return only after all standalone questions are done. In mocks, log time per set and compute marks-per-minute to confirm which set types to skip by default.
In Quantitative Aptitude, attempting data interpretation or arithmetic word problems with full written calculation instead of approximation, and misreading what is asked (e.g. percentage decrease vs increase, 'approximately' vs exact).
School habits of exact computation persist, and DI sets are designed with numbers that reward estimation and ratio reasoning; candidates also skim the question stem after reading a long table.
What to do instead
Drill approximation deliberately: percentage-to-fraction conversions, squares to 30, and ratio shortcuts, with a rule of no long division in DI. Before computing, underline the exact quantity requested and its unit. Time-box each DI set and check answers only after the set is complete.
In English Language, choosing an option because it 'sounds right' in cloze and error-spotting questions, without checking subject–verb agreement, preposition collocation, or whether the sentence needs a grammatical (not meaning-based) correction.
The section rewards precise grammar rules, but candidates rely on fluency intuition; exam distractors are built to sound plausible, especially in 'improve the underlined part' and 'find the error' items.
What to do instead
Maintain an error log of rules actually missed (articles, prepositions after specific verbs, parallelism, tense sequencing) and revise it before each mock. For each wrong answer, write the rule violated and one corrected sentence; do not move on until the rule is named.
Treating Computer Knowledge as a general-literacy section and skipping preparation for banking-specific computing: core banking solution concepts, CBS/IFSC/NEFT/RTGS/UPI distinctions, digital signature and PKI basics, and cyber-security terms.
Candidates assume computer questions are only about MS Office and hardware, so they do not study the payment-system and information-security vocabulary that the banking context makes likely; terminology like RTGS vs NEFT settlement timing is commonly confused.
What to do instead
Prepare a focused glossary of 60–80 banking-technology terms with one-line definitions and distinguishing features (NEFT vs RTGS vs IMPS vs UPI; firewall vs antivirus; phishing vs pharming; digital signature vs e-sign). Test recall with flashcards rather than reading notes.
In Constitutional and Administrative Law, answering from general civics knowledge and ignoring the exact article, writ, or doctrine - e.g. mixing up Articles 32 and 226, or the grounds for issuing certiorari versus prohibition.
The topic overlaps heavily with school civics, creating false confidence; the professional paper tests article-level precision, landmark-case principles, and the difference between constitutional and statutory remedies.
What to do instead
Build an article-and-writ matrix: Article 32 vs 226 (scope, territorial reach, alternative remedy), the five writs with their distinct triggers and targets, and key doctrines (basic structure, pleasure doctrine, natural justice). Attach one landmark case name to each row and revise by covering the answers and reconstructing the table.
In Labour and Industrial Law, applying the wrong statute - for example answering a retrenchment or standing-orders question under the Factories Act, or citing the Industrial Disputes Act for a wage-payment issue governed by the Code on Wages.
Labour law is a patchwork of overlapping statutes, and recent codification changed which provisions apply; candidates learn topics by theme ('wages', 'dismissal') without anchoring each theme to its governing Act and threshold.
What to do instead
Organise revision by statute, not theme: for each Act/code, list applicability thresholds (number of workers), key definitions, the authority (labour court, tribunal, inspector), and remedies. Then create a 'which Act applies' quiz using short fact patterns, and note where the new codes replace the old Acts.