Mock tests and analysis for IBPS PO

In bank exams, question selection decides results. Two candidates with the same knowledge can finish a prelims mock ten marks apart, because one spent seven minutes on a puzzle that never settled and the other spent those minutes on three easy questions at the end of the section. Nobody learns that from a book. You learn it from mocks, and only if you analyse them properly.

A mock taken and not analysed is mostly wasted. It tells you a score, which you already half-knew, and nothing about why. This guide is about using mocks as a diagnostic tool: when to take them, how many, and exactly what to do in the forty minutes after.

Types of mocks, and when to use each

Topic tests teach. Sectional tests build speed. Full mocks teach selection and stamina. You need all three, in that order.

How many?

These are ceilings, not targets. If you cannot analyse a mock properly, take fewer. Thirty mocks analysed well beat sixty taken and forgotten.

Exam-like conditions

• Same time of day as your likely slot.
• Full screen, no phone, no breaks, a rough sheet and pen as in the exam hall.
• Sectional timers on. Never pause a mock because a question is interesting.
• For mains mocks, do the descriptive at the end, typed, while tired. That is how it will feel on the day.

A 40-minute analysis

1. Scores by section (2 minutes). Note them in your log, with accuracy.
2. Wrong answers (10 minutes). For each, write why it was wrong: concept, calculation, misreading or guess.
3. Skipped questions (10 minutes). Solve them now, untimed. Which were actually easy? This is usually where the biggest gains are.
4. Time sinks (8 minutes). Which questions or sets took more than about two minutes? Were they worth it?
5. Three actions (10 minutes). Write three specific changes for the next mock and add weak topics to your practice list.

Classify every error

After ten mocks, count the categories. If most errors are misreading or guesses, you do not need more study; you need calmer habits.

A worked analysis

Suppose, in one prelims mock, an aspirant's reasoning section went like this: 24 questions attempted, 20 right, 4 wrong. With reasoning at about 8/7 of a mark per question and a penalty of about 2/7:

• Score: (20 × 8/7) − (4 × 2/7) = 160/7 − 8/7 = 152/7 ≈ 21.71

The analysis finds:

• Two wrong answers came from one puzzle, where a clue was misread early.
• One wrong answer was a misread inequality.
• One was a guess with no option eliminated.
• Three skipped questions (a direction question, a coding question and a syllogism) turned out to be easy. The aspirant ran out of time because seven minutes went into a puzzle that was abandoned unsolved.

Now the "what if". Suppose those seven minutes had gone to the three easy questions, all answered correctly, and the blind guess had been skipped:

• Right: 20 + 3 = 23. Wrong: 4 − 1 = 3.
• Score: (23 × 8/7) − (3 × 2/7) = 184/7 − 6/7 = 178/7 ≈ 25.43

That is about 3.7 marks from the same knowledge, just better selection. Across three sections, gains like this decide whether a candidate clears.

Lessons mocks teach

• Which question types you should always attempt first.
• Which puzzle types you solve fastest (floor, box, linear or circular seating).
• Which DI formats suit you and which to leave.
• Where you over-invest time, and how long you can safely give a puzzle before moving on.
• How your accuracy changes when you push attempts.

A mock log

Add a column for your lowest section margin if you are tracking sectional cut-offs. Read the log every Sunday. Patterns show up over weeks, not in one mock.

Previous papers

• Memory-based papers from recent cycles show the real level and style.
• Solve them in timed conditions; they are often better calibration than an easy mock.
• Do not memorise them. Questions rarely repeat; question types do.

Choosing a mock series

• One main series is enough; add a second only for extra mains practice.
• Look for sectional timers, an interface close to the real exam, and detailed solutions.
• Prefer a series with many test-takers, so the percentile means something.
• Do not judge a series by whether it makes you feel good. An honest, slightly harder series prepares you better.

One wrong question, analysed properly

Writing the real reason in one line is what turns a mock into learning. "Silly mistake" is not a reason.

When scores are low or flat

• Mock series differ in difficulty. Compare your percentile and your own trend, not raw marks.
• If scores are flat for two weeks, take fewer mocks and spend more time on analysis and weak topics.
• If one section drags your total down, switch to sectional tests in that section for a week.
• A bad mock close to the exam is information, not a verdict. Analyse it and move on.

What to do next

• Take your next mock at your likely exam time, with sectional timers on.
• Spend 40 minutes on the analysis steps above and classify every error.
• Start the mock log, and read it every Sunday.
• Use the prelims strategy to set a minute plan for each section, and apply it in the next mock.