RSMSSB Patwari common mistakes
RSMSSB Patwari · Understand the traps and how to avoid them.
Preparing Rajasthan GK almost entirely from Rajasthan-only sources and skipping the parts of the syllabus that connect Rajasthan to national history and geography - for example, not being able to place Rajasthan's princely states within the chronology of British paramountcy, the 1857 revolt, or the integration of the state after 1947.
Rajasthan GK feels like the biggest and most distinctive section, so candidates buy one Rajasthan-specific book, memorise lists of forts, lakes and folk deities, and never build the surrounding national timeline. Questions that ask about the Mewar–Maratha–Mughal sequence, the role of Rajasthan in 1857, or the phases of the Prajā Maṇḍal movement then feel unfamiliar even though the facts are in the same book, just in a chapter the candidate skipped.
What to do instead
Build a one-page national timeline (1707–1947–1956) and place every Rajasthan event on it: Treaty of 1818 with the British, 1857 centres at Nasirabad, Aauwa and Kota, the 1920s peasant movements, the 1948–49 stage-by-stage integration of the Matsya Union, Rajasthan Union and Greater Rajasthan. Revise Rajasthan GK through that timeline rather than as isolated lists, so each fact has a date anchor.
Treating Rajasthan current affairs as a monthly news digest to be read once, so schemes, appointments and budget figures learned in January are forgotten or overwritten by June.
Coaching PDFs and monthly magazines encourage passive reading. Candidates feel productive because they have 'covered' the month, but nothing is retrieved, so nothing sticks. Because the exam is a single paper with a heavy current-affairs component, this is one of the highest-frequency causes of lost marks.
What to do instead
Keep a single rolling register of state current affairs in fixed categories: new schemes and their launch year, boards and commissions, appointments, awards, budget allocations, sports and cultural events hosted in Rajasthan. Review the register weekly and self-test by covering the right-hand column. Before the exam, revise only the last 12 months, since most questions stay inside that window.
Answering India and world current affairs from social-media headlines without checking the institutional detail - which body elected or appointed a person, which country holds a chair, which summit produced which declaration, or what a rank or index actually measures.
Short-form news gives the name and the event but strips the institution and the number. Candidates then recognise the topic in the exam and pick an option that sounds right, which is exactly the distractor design. Questions on summits, indices, appointments and international organisations are built to punish half-knowledge.
What to do instead
For every current-affairs item you record, force three fields: who or what, which institution or country, and one number or date. For indices, note the publishing body and what is being ranked. Practise converting headlines into 'institution + number' statements, and discard any item you cannot fill in completely.
Rushing arithmetic in the numerical-ability section - doing percentage, ratio and average calculations in the head, skipping the estimation step, and losing time re-doing sums that went wrong.
The paper is long and time-pressured, so candidates try to buy time by speed. Mental arithmetic feels faster but produces silent errors, especially with unit conversions, decimal placement in percentages, and chained ratio problems. The candidate then has to redo the question, which costs more time than the careful method would have.
What to do instead
Adopt a fixed written routine: write the given values, convert units before computing, estimate the answer to one significant figure first, then compute exactly and compare with the estimate. Practise 10 questions daily under a timer using this routine until it becomes automatic. Keep a personal error log of the specific slip types you repeat.
Attempting every question in Mathematics and Basic Numeracy in sequence instead of triaging, so time is consumed by two or three long word problems and the last fifteen easy questions are never seen.
Candidates are trained to solve in order and feel uncomfortable leaving a question blank. Because difficulty is not ordered, a hard compound-interest or time-and-work problem can appear early, and the clock runs out before the straightforward simplification and average questions later in the section.
What to do instead
Do two passes. On the first pass, answer only questions you can finish in under a minute and mark the rest; on the second pass, return to marked questions with the remaining time. In mock tests, record how many marks were lost to unseen questions versus wrong answers - the unseen count is usually the bigger and more fixable loss.
Solving reasoning questions by intuition on series, coding-decoding and blood-relation puzzles, without writing out the pattern or drawing the family tree.
These questions look easy on inspection and candidates believe they can 'see' the answer. Under exam pressure, working memory overloads, the candidate mis-sequences a letter series or reverses a relation, and a question that would take twenty seconds with a diagram takes two minutes and still ends wrong.
What to do instead
Use fixed external representations: write the alphabet with position numbers at the top of your rough sheet, draw family trees with gender symbols and generation lines, and tabulate seating arrangements. For series, test differences, ratios and alternating sub-series in a set order rather than guessing. Drill one question type per session until the representation is habitual.
Ignoring non-verbal and spatial reasoning (mirror images, paper folding, embedded figures, figure series) because it feels less 'studyable' than verbal reasoning, then losing a predictable block of marks.
Candidates prefer topics where notes and formulas exist. Spatial topics require practice with visual transformations, which feels unproductive, so they are postponed and never done. These questions are typically formulaic and highly trainable, making this an avoidable loss.
What to do instead
Schedule short daily blocks of 10–15 non-verbal questions, rotating mirror and water images, paper folding and cutting, embedded figures, and figure series. Practise with a pencil and actually fold or draw rather than visualising, until the transformation rules are internalised. Track accuracy by subtype and target the weakest one.
Studying computer awareness as scattered facts - memorising shortcut keys in isolation while being unable to explain what an operating system, a browser, an IP address, or a spreadsheet formula actually does.
Computer awareness is treated as a low-priority memory section, so candidates collect lists without a mental model. Questions that ask about function, hierarchy of storage, types of software, or the purpose of a device component then defeat list-based preparation, because the options are all plausible terms the candidate has seen.
What to do instead
Build a simple layered model: hardware, operating system, application software, network, and internet services. Place every term you learn into that model, and for each term write one line on what problem it solves. Revise shortcut keys and abbreviations separately as a quick-recall list, but test yourself with 'what does this do' questions, not just 'what does this stand for'.
Taking full-length mocks without a post-mortem, so the same mistakes repeat across tests and the score plateaus.
Mocks are treated as a score to be checked rather than a diagnostic. After seeing the score, the candidate moves to the next mock or back to reading notes, and never classifies errors by cause: not known, known but misread, calculation slip, or time lost. Without classification, revision effort is spread evenly and the fixable errors survive.
What to do instead
After every mock, spend at least as long analysing as attempting. Tag each wrong and skipped question with a cause code and a domain, then compute lost marks by cause. Direct the next week's revision at the largest cause category, and re-attempt the same wrong questions after three days to confirm the fix.
Neglecting negative marking and guessing behaviour - either answering every unknown question on a hunch or leaving everything blank when unsure, with no consistent policy.
Candidates rarely decide in advance how to handle uncertainty, so behaviour varies by mood and section. Random guessing on a four-option question with a penalty for wrong answers erodes marks, while excessive caution leaves easy eliminations unused. Both patterns are common and both are correctable with a rule.
What to do instead
Adopt an explicit policy before the exam: attempt when you can eliminate at least two options, skip when you cannot eliminate any. Practise applying it in mocks and compare scores under the policy versus your natural behaviour. Also fix an order of sections and a time budget per section so the policy is applied under realistic pressure.