SNAP Mocks: What to Track After Every Test

Mock tests are weirdly emotional.

One day you finish a SNAP mock and you feel like, okay, I am built for this exam. Next mock you get humbled so hard you start questioning your whole prep plan, your coaching, your calculator skills, and probably your life choices too.

But here’s the thing. The mock score is not the main output.

The real output is what you track after the test. That tracking is what turns “I am giving mocks” into actual improvement.

So in this post, I am going to share a simple but detailed checklist of what to track after every SNAP mock, how to review it, and what patterns to watch for. You do not need fancy spreadsheets. But you do need consistency.

Why “just giving mocks” does not work for SNAP

SNAP is a speed exam. 60 minutes, 60 questions. And the paper loves pushing you into rushing, guessing, and silly mistakes.

So if you only track the final score, you miss the reasons behind it:

• Did you lose marks because you were slow or because you made wrong choices?

• Did you attempt too many with low accuracy?

• Did you waste time in a “trap” quant set?

• Did you panic in the first 10 minutes and never recovered?

Your improvement comes from these answers, not from the percentile screenshot.

In addition to preparing for SNAP, it's also beneficial to consider other entrance exams like the ISB BAT or the IIMB Test. Each of these exams has its own unique challenges and preparation strategies that can complement your overall study plan.

First rule: Track in two layers (Score layer and Process layer)

After every mock, track:

1. Score layer: What happened in terms of marks, attempts, accuracy.

2. Process layer: Why it happened. What you did, what you missed, what you should repeat.

If you only do layer 1, you will keep repeating the same errors with different scores.

The 15 things to track after every SNAP mock (non negotiable)

1. Overall score, attempts, accuracy (basic, but do it properly)

Write down:

• Total score

• Total attempts

• Total correct

• Total wrong

• Accuracy percentage

Accuracy matters a lot because SNAP can punish random attempts. You need to know your “safe attempt zone” where score rises without accuracy collapsing.

A simple accuracy formula:

• Accuracy = Correct / Attempted

Also track your net score trend. Some people increase attempts and feel productive but score stays flat because wrong answers rise too.

2. Section wise score split (and not just “I am weak in QA”)

SNAP typically has:

• General English

• Analytical and Logical Reasoning

• Quantitative, Data Interpretation and Data Sufficiency

After each mock, note for each section:

• Score

• Attempts

• Correct

• Wrong

• Accuracy

• Time spent (more on time below)

This tells you if the problem is content, speed, or selection.

3. Time spent per section (actual, not imagined)

Most students think they spent “around 20 minutes in LR” but the reality is often 28 minutes.

If your mock platform shows time spent per section, record it. If not, roughly estimate with a timer next time, or mark checkpoints like:

• At 15 minutes remaining, where was I?

• At 30 minutes remaining, where was I?

Your time split is basically your strategy in action. If it is inconsistent, your scores will be inconsistent too.

4. Time spent on the first 10 questions

This one sounds minor but it is huge.

SNAP mocks often go bad because you spend too long settling in. Track:

• How many questions you attempted in the first 10 minutes

• How many were correct

If the first 10 minutes are slow, you end up chasing time later. That is when silly mistakes and guesses start.

Goal is not to rush blindly. Goal is to start clean and confident.

5. Question selection errors (the silent score killer)

After the mock, identify questions that fall into these buckets:

• Should have attempted but skipped

• Should have skipped but attempted

• Attempted too late (spent time early on hard ones, then missed easy ones later)

This is different from “I got it wrong.” It is about your decision making.

In SNAP, decision making is a skill.

6. The “time sink” questions (where you lost minutes)

Every mock has 2 to 5 questions that eat time.

Track any question where you spent more than:

• 90 seconds in English

• 120 seconds in LR

• 150 seconds in QA/DI

(These are not fixed laws, just practical benchmarks.)

Write down the question number and topic. Over a few mocks, you will see patterns like:

• “I always overspend time in DI tables.”

• “I get stuck in assumption questions.”

• “I keep trying to brute force arrangement puzzles.”

Patterns are gold. They tell you what to fix.

7. Accuracy by difficulty level (easy vs medium vs hard)

If your mock analysis shows difficulty tags, use them.

Track:

• Easy attempted vs easy accuracy

• Medium attempted vs medium accuracy

• Hard attempted vs hard accuracy

Many students have a painful pattern: they miss easy questions and still attempt hard ones. That is a strategy problem, not an intelligence problem.

A SNAP topper mindset is boring but effective: Secure easy marks. Then medium. Hard is optional.

8. Topic wise performance (micro level)

You do not need to track 50 topics. Keep it simple. A small list that covers SNAP well.

Example topics to track:

Quant

• Arithmetic (percentages, ratio, SI/CI, averages)

• Algebra (linear, quadratic, inequalities)

• Numbers (divisibility, remainders)

• Modern math (P&C, probability basics)

• DI (tables, bar charts, caselets)

LR

• Arrangements

• Series and patterns

• Syllogisms

• Venn diagrams

• Clocks, calendars, coding decoding

• Direction sense

• Critical reasoning style questions

English

• RC (short passages)

• Vocabulary and usage

• Grammar error spotting

• Sentence improvement / para jumbles

After every mock, write the topic next to every wrong question and every time sink question.

Within 5 mocks, you will know your real weak areas. Not the ones you think you have.

9. Error type classification (this changes everything)

For each wrong answer, classify it as one of these:

1. Concept gap: did not know the method/rule.

2. Process mistake: knew the concept, but applied wrong step.

3. Calculation mistake: arithmetic slip, missed negative, wrong multiplication.

4. Reading mistake: misread question, missed “not”, missed unit.

5. Guess / panic attempt: attempted without clarity due to time pressure.

This is the part most students skip. But it is the most actionable.

Because each error type needs a different fix:

• Concept gap needs revision + practice.

• Process mistake needs slow practice + error log.

• Calculation mistake needs checking habits.

• Reading mistake needs discipline and pacing.

• Guess panic needs strategy changes.

10. Your “best score potential” (score you could have scored)

This is a little painful but very useful.

Look at:

• Easy questions you got wrong

• Easy questions you skipped

• Questions you got wrong due to silly mistakes

Estimate a realistic “best score potential” for that mock if you had been calmer and cleaner.

Not a fantasy perfect score. A realistic one.

If your actual score is 32 and potential is 42, you do not need more topics right now. You need execution.

11. Attempts vs accuracy tradeoff (find your personal sweet spot)

Track across mocks:

• When you attempt 40, accuracy drops to 60 percent.

• When you attempt 34, accuracy stays at 75 percent.

That tells you the sweet spot. And that sweet spot usually shifts upward as you improve.

Your goal is not max attempts. Your goal is max score.

12. Review time spent (yes, track this too)

Mock review is part of the mock.

Track:

• How long did you review the mock?

• Did you review on the same day?

• How many wrong questions did you fully understand after review?

If you are giving 3 mocks a week but reviewing only 20 minutes each, you are basically collecting stress, not progress.

13. Your mental state notes (short, honest)

Write 2 to 3 lines after every mock:

• Was I anxious?

• Did I lose focus mid way?

• Did I rush the end?

• Did I feel sleepy, distracted, overconfident?

This sounds fluffy. It is not.

SNAP is as much about managing your head as managing your questions.

Over time, you will notice patterns like “I always mess up Mock 2 of the day” or “My evening mocks are better than morning.”

14. Strategy adherence (did you follow your plan?)

Before the mock you have a plan, maybe:

• English 12 minutes

• LR 25 minutes

• QA 23 minutes

Or maybe a different order.

After the mock, rate yourself:

• Followed strategy fully

• Partially followed

• Completely broke it

And note exactly where it broke. For example: “I entered QA too early because LR felt hard, then panicked.”

These are the moments you fix.

15. One single takeaway for the next mock

End every mock review by writing:

• One thing to stop

• One thing to continue

• One thing to start

Example:

• Stop: spending 4 minutes on DI caselets early.

• Continue: quick scanning and picking easy English questions first.

• Start: hard cap of 2 minutes on any LR question.

This keeps you improving without overcomplicating everything.

A simple mock review routine you can actually follow

Here is a clean 60 to 90 minute mock review workflow.

Step 1: Cool down (5 minutes)

Do not jump into analysis immediately. Just breathe. Drink water. Reset.

Step 2: Mark all wrong and skipped questions (10 minutes)

Create three lists:

• Wrong questions

• Skipped but easy/medium questions

• Time sink questions

Step 3: Re solve wrong questions without seeing solution (20 to 30 minutes)

This is important.

If you immediately see the solution, you get the illusion of learning.

Try again. Then check solution.

Step 4: Log errors and topics (15 minutes)

Update your error log:

• Topic

• Error type

• What to do next time

Step 5: Decide the next 2 day action plan (10 minutes)

Pick:

• 2 topics to practice

• 1 execution habit to improve (like reading carefully, time cap, skipping rule)

That is it.

What a good tracking sheet looks like (minimal, not fancy)

You can do this in Notes app, Google Sheets, or a notebook.

Columns could be:

• Mock number, date

• Overall score, attempts, accuracy

• Section wise attempts and accuracy

• Time split

• Top 3 weak topics from this mock

• Top 3 error types from this mock

• One takeaway

Keep it boring. Keep it consistent.

A quick note on coaching and mock quality

Not all mock series are equal. Some have weird difficulty swings. Some have messy solutions. Some do not match SNAP vibe.

If you are still choosing a coaching institute or deciding which mock series to trust, it helps to compare options calmly instead of buying whatever is trending.

You can use MBA Entrance Exam Guide by GOALisB to discover and compare coaching institutes by exam type, fees, and student reviews, and even book a free counseling or demo class if you are stuck deciding. It is basically made for this exact decision fatigue.

Website: https://mbaentrance.goalisb.com/

The real win: You should be able to predict your score swings

After you track 6 to 8 mocks properly, something nice happens.

You stop being surprised.

You start knowing:

• “My accuracy dropped because I chased attempts.”

• “This mock went bad because I lost 10 minutes on two LR questions.”

• “I am missing easy English grammar ones. That is free marks.”

That is when your prep becomes stable. And SNAP rewards stability.

Keep giving mocks, sure. But more importantly, keep tracking what the mock is trying to tell you. That is the whole game.

FAQs (Frequently Asked Questions)

Why is just giving SNAP mock tests not enough for effective preparation?

Simply taking SNAP mock tests without analyzing them doesn't lead to improvement because the exam is a speed test that challenges your accuracy, time management, and decision-making. Tracking only the final score misses critical insights like whether you lost marks due to rushing, guessing, or poor question selection. Effective preparation requires understanding these reasons behind your score to make targeted improvements.

What are the two layers I should track after every SNAP mock test?

You should track two key layers: 1) The Score Layer, which includes marks obtained, number of attempts, and accuracy; and 2) The Process Layer, which examines why those results occurred — what strategies you used, mistakes made, and what to repeat or avoid. Tracking both layers ensures you don't just see your score but also understand and improve your test-taking process.

What specific metrics should I record in the 'score layer' after a SNAP mock?

In the score layer, record your total score, total attempts, number of correct and wrong answers, and calculate your accuracy percentage (Accuracy = Correct / Attempted). Also monitor your net score trend over multiple mocks to identify if increasing attempts is genuinely improving your score or just increasing wrong answers.

How important is tracking time spent on each section during SNAP mocks?

Tracking actual time spent per section (General English; Analytical & Logical Reasoning; Quantitative & DI) is crucial because SNAP demands precise time management. Many students misjudge their time allocation leading to rushed guesses or missed questions. Recording exact time helps assess whether content knowledge or speed is the problem and allows you to adjust your strategy accordingly.

What are 'time sink' questions and why should I track them?

'Time sink' questions are those where you spend excessive time beyond practical benchmarks (e.g., over 90 seconds in English or 150 seconds in Quant). Identifying these questions helps reveal patterns such as consistently spending too long on particular topics or question types. Recognizing these patterns enables you to target weaknesses and improve efficiency during the exam.

How can tracking question selection errors improve my SNAP mock performance?

Question selection errors involve attempting questions that should have been skipped or skipping ones that should have been attempted, as well as attempting difficult questions too late in the test. Since decision-making is a critical skill in SNAP due to its speed nature, analyzing these errors helps refine your strategy to maximize scoring potential by focusing on easier questions first and avoiding traps.

{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Why is just giving SNAP mock tests not enough for effective preparation?","acceptedAnswer":{"@type":"Answer","text":"Simply taking SNAP mock tests without analyzing them doesn't lead to improvement because the exam is a speed test that challenges your accuracy, time management, and decision-making. Tracking only the final score misses critical insights like whether you lost marks due to rushing, guessing, or poor question selection. Effective preparation requires understanding these reasons behind your score to make targeted improvements."}},{"@type":"Question","name":"What are the two layers I should track after every SNAP mock test?","acceptedAnswer":{"@type":"Answer","text":"You should track two key layers: 1) The Score Layer, which includes marks obtained, number of attempts, and accuracy; and 2) The Process Layer, which examines why those results occurred — what strategies you used, mistakes made, and what to repeat or avoid. Tracking both layers ensures you don't just see your score but also understand and improve your test-taking process."}},{"@type":"Question","name":"What specific metrics should I record in the 'score layer' after a SNAP mock?","acceptedAnswer":{"@type":"Answer","text":"In the score layer, record your total score, total attempts, number of correct and wrong answers, and calculate your accuracy percentage (Accuracy = Correct / Attempted). Also monitor your net score trend over multiple mocks to identify if increasing attempts is genuinely improving your score or just increasing wrong answers."}},{"@type":"Question","name":"How important is tracking time spent on each section during SNAP mocks?","acceptedAnswer":{"@type":"Answer","text":"Tracking actual time spent per section (General English; Analytical & Logical Reasoning; Quantitative & DI) is crucial because SNAP demands precise time management. Many students misjudge their time allocation leading to rushed guesses or missed questions. Recording exact time helps assess whether content knowledge or speed is the problem and allows you to adjust your strategy accordingly."}},{"@type":"Question","name":"What are 'time sink' questions and why should I track them?","acceptedAnswer":{"@type":"Answer","text":"'Time sink' questions are those where you spend excessive time beyond practical benchmarks (e.g., over 90 seconds in English or 150 seconds in Quant). Identifying these questions helps reveal patterns such as consistently spending too long on particular topics or question types. Recognizing these patterns enables you to target weaknesses and improve efficiency during the exam."}},{"@type":"Question","name":"How can tracking question selection errors improve my SNAP mock performance?","acceptedAnswer":{"@type":"Answer","text":"Question selection errors involve attempting questions that should have been skipped or skipping ones that should have been attempted, as well as attempting difficult questions too late in the test. Since decision-making is a critical skill in SNAP due to its speed nature, analyzing these errors helps refine your strategy to maximize scoring potential by focusing on easier questions first and avoiding traps."}}]}