Ask ten aspirants how many mocks they have taken and you will hear numbers like 60, 100 or 150. Ask them what changed in their preparation because of those mocks and the room goes quiet. A mock test is not a workout that makes you stronger by itself. It is a measuring instrument, and an instrument is only useful if somebody reads it and acts on the reading.
This post gives you a planning framework for the last 90 days before a competitive exam: how many sectional tests and full-length mocks to schedule, in what order, how to read a score report line by line, how to keep a mistake log, how to sort errors into three types, when to re-attempt a paper, how to treat rank against score, and the decision rules for changing your strategy.
One important note before we begin. Every scorecard in this article is an invented illustration. The numbers are made up to show you how to think, not to show you what students score or what any exam demands. The schedule and thresholds are planning suggestions, not official guidance. Always check the latest notification of your exam for the real pattern, marking scheme and timing.
Why the cycle matters more than the count
The useful unit of preparation is not one mock. It is one loop: take the test, analyse it, fix the causes of lost marks, and test again. A mock that is taken and not analysed is a loop that was never closed. It gave you a number and nothing else.
That is why fewer, well-analysed mocks usually beat a large number of rushed ones. If a full mock takes one hour and a proper analysis takes at least as long, then taking one mock every day means you are either skipping analysis or neglecting study. Neither is a good trade.
A rough rule to plan around (our suggestion): budget analysis time at least equal to test time, and expect about one and a half times the test time in the first few weeks, when your error log is new and every mistake needs a written reason.
Keep this loop in mind through the rest of the post. Every schedule, every table and every decision rule below exists to make that loop faster and more honest.
The illustrative paper used in this post
To keep the arithmetic easy to follow, all worked examples use one made-up pattern. It resembles many tier-1 style papers, but it is not a claim about any specific exam.
- Four sections of 25 questions each: Reasoning, General Awareness, Quantitative Aptitude, English. Total 100 questions.
- 2 marks for a correct answer, 0.5 marks deducted for a wrong answer, no marks for an unattempted question. Maximum 200.
- 60 minutes for the whole paper.
If your exam has different marks, sections or negative marking, redo the arithmetic with your own numbers. The method does not change.
One piece of arithmetic is worth doing right now because it drives attempt decisions. With 2 marks for right and 0.5 for wrong, the expected gain from answering a question is 2p minus 0.5(1 minus p), where p is your chance of being right. That equals 2.5p minus 0.5, which is positive only when p is above 0.2, or 20 percent. A pure guess among four options has p of 0.25, giving a tiny gain of 0.125 marks. If you can eliminate one option, p is about one-third and the gain is about 0.33 marks. So in this illustrative scheme, educated guesses pay a little and blind guesses pay almost nothing. Your exam may penalise differently, so recompute.
The 90-day plan in three phases
Ninety days is about twelve and a half weeks. The plan below uses twelve weeks and leaves the extra days as buffer for illness, travel or a bad week. It moves from many small tests to fewer, larger simulations.
Phase 1: weeks 1 to 4, sectional and topic tests first
In the early weeks your knowledge has gaps, and a full-length mock mostly tells you what you already suspect. Sectional tests are better value here because they are short, so you can take several, analyse them quickly, and tie each result to a topic you are studying that week.
Take one full-length mock in week 1 as a diagnostic. Do not worry about the score. Its job is to produce your first mistake log and your first time-per-section reading. Then take a second and third full mock in weeks 3 and 4 to check that your sectional work is carrying over to the whole paper.
A good ratio for this phase: about three to four sectional tests for every full mock.
Phase 2: weeks 5 to 8, build stamina and a section strategy
Now move to one or two full mocks a week. This is where you settle your section order, your time budget per section and your skipping policy. Keep two or three sectionals a week, aimed only at the topics your log says are still weak. Add one re-attempt session per week (more on that later).
A starting time budget for our illustrative 60-minute paper, as a planning suggestion: Reasoning 14 minutes, General Awareness 8 minutes, Quantitative Aptitude 20 minutes, English 18 minutes. That adds up to 60. Adjust it after two or three mocks based on where you actually gain marks per minute.
Phase 3: weeks 9 to 12, simulate the real exam
Here the full-length mock takes over. Take two to three a week, at the same time of day as your exam, on a similar device, with no pauses. Sectionals shrink to occasional repair work. The analysis becomes sharper because you are now looking for patterns across many papers, not single mistakes.
Across all three phases, the plan below totals 19 full-length mocks and 28 sectional tests, which is 47 tests in 84 days. Treat this as a ceiling for someone with enough time to analyse every test. If you have less time, cut tests, never analysis.
A sample 12-week mock schedule
This table is a planning suggestion, not an official or proven schedule. Use it as a template and adjust to your exam date, your work or college hours and your own error log.
| Week | Phase | Full mocks | Sectional tests | Re-attempt session | Main focus |
|---|---|---|---|---|---|
| 1 | Foundation | 1 (diagnostic) | 3 | No | Baseline score, first mistake log |
| 2 | Foundation | 0 | 4 | No | Weakest section, topic drills |
| 3 | Foundation | 1 | 4 | No | Check carry-over to full paper |
| 4 | Foundation | 1 | 3 | Yes | First re-attempt of wrong questions |
| 5 | Build | 1 | 3 | Yes | Fix section order and time budget |
| 6 | Build | 2 | 3 | Yes | Skipping policy, attempt rate |
| 7 | Build | 2 | 2 | Yes | Cut silly errors |
| 8 | Build | 2 | 2 | Yes | Mid-plan review of all rules |
| 9 | Simulate | 2 | 2 | Yes | Exam-time slot, full routine |
| 10 | Simulate | 2 | 1 | Yes | Stability of the 3-mock average |
| 11 | Final fortnight begins | 3 | 1 | Yes | Repair only what the log flags |
| 12 | Final fortnight | 2 | 0 | Light | Revision, rest, logistics |
Check the totals: full mocks 1+0+1+1+1+2+2+2+2+2+3+2 = 19. Sectional tests 3+4+4+3+3+3+2+2+2+1+1+0 = 28. If you start late, drop weeks from Phase 1, not from Phase 3. The simulation weeks are the hardest to replace.
The final fortnight routine
The last 14 days are not for learning new syllabus. They are for stabilising what you already have. This is a suggested routine, to be adapted to your exam date.
- Days 14 to 8 before the exam: three to four full mocks, every second day, at your exam slot. On the days in between, re-attempt the wrong and skipped questions from the previous mock and update the mistake log. No new topics unless your log shows a large, specific gap.
- Days 7 to 4: one or two full mocks and one short sectional on your weakest section. Spend most of the time reading your mistake log and your formula, rule and fact notes.
- Day 3: your last full mock. Treat the score as information, not a verdict. A bad result here is not a reason to panic; it is a list of things to check once more.
- Day 2: no mock. Read the mistake log, especially the silly-error column, and your short revision notes. Prepare documents, admit card details and travel plan.
- Day 1: light revision for an hour or two, early dinner and proper sleep. Do not take a mock the day before. A poor score the night before gives you nothing to fix and a lot to worry about.
Also rehearse the small things on mock days: how you will start each section, when you will check the clock, when you will mark a question for review, and what you will eat and drink beforehand. By the final week these should be habits, not decisions.
How to read a score report: four numbers per section
A score report can look like a wall of figures. Most of its value comes from four numbers per section: attempts, accuracy, time and marks lost. Here is a full illustration.
Illustration 1 (invented scorecard, Mock 5 of a made-up aspirant):
| Section | Attempted | Correct | Wrong | Score | Accuracy | Time used |
|---|---|---|---|---|---|---|
| Reasoning | 23 | 18 | 5 | 33.5 | 78% | 14 min |
| General Awareness | 18 | 12 | 6 | 21.0 | 67% | 8 min |
| Quantitative Aptitude | 15 | 10 | 5 | 17.5 | 67% | 22 min |
| English | 24 | 17 | 7 | 30.5 | 71% | 16 min |
| Total | 80 | 57 | 23 | 102.5 | 71% | 60 min |
Verify the maths so you can do it on your own reports. Reasoning: 18 times 2 is 36, minus 5 times 0.5 which is 2.5, gives 33.5. Total: 57 times 2 is 114, minus 23 times 0.5 which is 11.5, gives 102.5. Accuracy is correct answers divided by attempted answers, so 57 divided by 80 is 71.25 percent.
Now read it in layers.
Attempts. This aspirant attempted 80 of 100 questions. Quantitative Aptitude is the outlier: only 15 of 25 attempted, so ten questions were left blank. The other three sections have 18 to 24 attempts.
Accuracy. Overall accuracy of 71 percent is middling. With 0.5 negative marking, each wrong answer costs 2.5 marks compared with a correct one (2 marks not earned plus 0.5 deducted). Twenty-three wrong answers mean 57.5 marks lost to wrong answers alone.
Marks per minute. Divide each section score by the minutes spent. Reasoning: 33.5 over 14 is about 2.4. General Awareness: 21 over 8 is about 2.6. English: 30.5 over 16 is about 1.9. Quantitative Aptitude: 17.5 over 22 is about 0.8. Overall: 102.5 over 60 is about 1.7.
The headline finding is clear. Quantitative Aptitude eats the most time and returns the least marks. That is the first thing to investigate. The next section shows how.
Time per section and per question
Section-level time tells you where minutes go. Question-level time tells you why. Many platforms show time spent per question; if yours does, make a habit of bucketing it.
Illustration 2 (invented): Quantitative Aptitude in Mock 5, bucketed by time per attempted question.
| Time spent on the question | Questions | Correct | Wrong | Approx. minutes used |
|---|---|---|---|---|
| Under 60 seconds | 5 | 5 | 0 | 4 |
| 60 to 120 seconds | 6 | 4 | 2 | 9 |
| Over 120 seconds | 4 | 1 | 3 | 9 |
| Total attempted | 15 | 10 | 5 | 22 |
Look at the last row of the body. Four questions took roughly nine minutes, which is about 41 percent of the section time, and they produced one correct answer and three wrong ones. Net marks from those four: 2 minus 1.5 equals 0.5. Meanwhile, the five fast questions were all right.
The ten unattempted questions were not studied in this table, but suppose the aspirant reviews them after the test and finds six were within reach, each solvable in about 90 seconds. Six questions at 90 seconds is nine minutes, the same time the four long questions consumed. If answered at the accuracy seen in the 60 to 120 second bucket (4 out of 6), that is around 4 correct and 2 wrong: 8 minus 1 equals 7 marks, against 0.5 marks from the sink questions. This is a thought experiment on invented numbers, but the logic is real: time spent past a certain point on a single question usually has a poor return.
The fix is a rule, not more studying: set a hard cap per question (for example, if you are not clearly on the way to the answer at 90 seconds, mark it and move on) and plan a second pass for marked questions if time remains. Test the rule across the next three mocks and see whether Quantitative Aptitude marks per minute rise.
General Awareness shows the opposite pattern. At 8 minutes, it is the fastest section, and time is not the constraint. You either know the fact or you do not. Seven questions were left blank and six answered wrongly, so the lever there is knowledge, not speed.
Topic-wise errors: where the marks actually sit
Section totals hide the topic that is hurting you. After three or four mocks, pool your results by topic. A small spreadsheet is enough.
Illustration 3 (invented): Quantitative Aptitude pooled over three mocks, 75 questions asked.
| Topic | Asked | Attempted | Correct | Attempt rate | Accuracy |
|---|---|---|---|---|---|
| Arithmetic (percentage, profit, ratio, time and work) | 30 | 26 | 21 | 87% | 81% |
| Geometry | 15 | 7 | 3 | 47% | 43% |
| Algebra | 12 | 9 | 7 | 75% | 78% |
| Mensuration | 8 | 5 | 3 | 63% | 60% |
| Trigonometry | 6 | 2 | 1 | 33% | 50% |
| Number system | 4 | 4 | 3 | 100% | 75% |
| Total | 75 | 53 | 38 | 71% | 72% |
Check: attempted 26+7+9+5+2+4 = 53; correct 21+3+7+3+1+3 = 38; 38 divided by 53 is about 72 percent.
Now compare the topics. Arithmetic is strong on both counts and gets the most questions, so it is not the problem. Geometry is the standout gap: 15 questions asked, only 7 attempted and 3 correct. Those 15 questions carried 30 marks across the three mocks, and the aspirant collected 6 of them, a gap of 24 marks, or about 8 per mock. That is a ceiling, not a target, because nobody converts every question. Still, it shows where an hour of study is most likely to pay off.
Use two columns together, never one. A topic with a low attempt rate and low accuracy (Geometry) needs concept work. A topic with a high attempt rate and low accuracy needs a check on method or silly errors. A topic with a low attempt rate and high accuracy (Trigonometry here, though on a tiny sample of 2 attempts) means you may be skipping questions you could solve. Be careful with small samples; two questions is a hint, not a pattern.
A mistake-log template you can copy
The mistake log is the single most useful document in your preparation. It turns scattered errors into patterns. Keep it in a spreadsheet or a notebook. Log every wrong question, and every unattempted question you could have solved.
| Column | What to write |
|---|---|
| Date and mock ID | For example, Mock 5, 14 March |
| Section and question number | Quant, Q12 |
| Topic and sub-topic | Geometry, circle and tangent |
| Error type | C (concept gap), S (silly), T (time pressure) |
| What went wrong | One honest line, not a vague one |
| Correct rule or method | Write the working or rule in your own words |
| Fix action | What you will do, with a date |
| Re-test date and result | Fill after the re-attempt |
Three invented sample rows, to show the level of detail:
| Mock and Q | Topic | Type | What went wrong | Fix action |
|---|---|---|---|---|
| M5, Reasoning Q7 | Syllogism | S | Read the conclusion as "all" when the statement said "some" | Underline the quantifier word before choosing |
| M5, Quant Q18 | Geometry, circles | C | Did not recall the tangent-radius relationship | Revise the circle theorems and do 10 practice questions |
| M5, Quant Q22 | Percentage change | T | Spent over two minutes on a long calculation, then guessed | Mark and move at 90 seconds; return in second pass |
Rules for keeping it useful. Write the reason in plain words: "careless" is not a reason, "misread the quantifier" is. Review the log weekly, not only after each mock, because patterns appear across mocks. And keep it short enough that you will actually reread it in the final fortnight.
The three-column error taxonomy
Every lost mark falls into one of three buckets. The fix for each bucket is different, which is why you must sort before you act.
- Concept gap: you did not know the rule, fact, formula or method. More attempts will not fix it. Study the topic, then practise it in a sectional.
- Silly error: you knew it, and still got it wrong. Misreading, a sign slip, wrong option bubbled, a calculation slip. The fix is process: a reading routine, a quick check, a habit of writing steps.
- Time pressure: you could have solved it with more time, or you rushed because you overspent elsewhere. The fix is strategy: question caps, section order, skipping policy.
Borderline cases exist. A good test: if you could solve the same question calmly in two minutes right now, it was not a concept gap. If you still cannot solve it, it is.
Illustration 4 (invented): sorting the 23 wrong answers from Mock 5.
| Section | Concept gap | Silly error | Time pressure | Total wrong |
|---|---|---|---|---|
| Reasoning | 1 | 3 | 1 | 5 |
| General Awareness | 4 | 1 | 1 | 6 |
| Quantitative Aptitude | 2 | 1 | 2 | 5 |
| English | 4 | 2 | 1 | 7 |
| Total | 11 | 7 | 5 | 23 |
At 2.5 marks lost per wrong answer, concept gaps cost 11 times 2.5, which is 27.5 marks. Silly errors cost 7 times 2.5, which is 17.5 marks. Time-pressure errors cost 5 times 2.5, which is 12.5 marks. Together that is 57.5, matching the earlier figure.
What does this say? Concept gaps are the largest bucket (48 percent of wrong answers), and they sit mostly in General Awareness and English. Those need topic study. But look at silly errors: 17.5 marks, concentrated in Reasoning, with no new study required. Fixing them costs only a habit change, so they are the cheapest marks on the page. Time-pressure errors are the smallest bucket among wrong answers, but note that the Quantitative Aptitude time problem also shows up as ten blank questions, which this table does not capture. Always add your unattempted-but-solvable questions to the time-pressure column in your own log.
A sensible action list from this single scorecard, as an illustration of how to turn analysis into decisions:
- Add a one-line quantifier check to every Reasoning question, and track whether Reasoning silly errors fall below two in the next three mocks.
- Put the four General Awareness concept gaps and four English concept gaps into the revision plan with dates.
- Apply a 90-second cap in Quantitative Aptitude for the next three mocks.
- Schedule a Geometry block this week, based on the topic-wise table.
Re-attempting mocks the right way
A re-attempt is not a way to raise your score. If you retake an entire paper you have already seen, the score is inflated by memory and tells you nothing about the real exam. It has value only if you use it to test whether your fixes worked.
The method that works better: after 10 to 14 days, re-attempt only the questions you got wrong or skipped, without looking at the earlier solution. Record how many you now solve correctly and how many still fail.
Illustration 5 (invented): an aspirant scored 88 in Mock 3. In that paper, 34 questions were wrong or unattempted. Fourteen days later, a re-attempt of just those 34 gives 22 correct. That is 22 out of 34, about 65 percent. It means the fixes have worked for about two out of three problem questions. The other 12 go back into the log, this time tagged as repeat errors, and they get priority in the next study block.
If the re-attempt rate is low, say below half, the original analysis was probably too shallow. You wrote down the answer but not the method. Go back to the log and write the working in your own words.
A full-paper re-attempt is acceptable once, three to four weeks later, mostly to practise a different section order or timing plan on familiar questions. Do not quote that score as your level.
Rank versus score: which one to trust
Score and rank answer different questions. Your score tells you how you did against the paper. Your rank or percentile tells you how you did against the people who took that paper on that platform that week. Each can mislead on its own.
Illustration 6 (invented): two mocks, one aspirant.
| Mock | Score (out of 200) | Rank | Test takers | Approx. percentile |
|---|---|---|---|---|
| X | 110 | 4,200 | 31,000 | 86.5 |
| Y | 96 | 2,100 | 18,000 | 88.3 |
Percentile here is (1 minus rank divided by takers) times 100. For X, 4,200 divided by 31,000 is 0.135, so about 86.5. For Y, 2,100 divided by 18,000 is 0.117, so about 88.3.
The score fell by 14 marks from X to Y, and yet the standing improved. A likely reason is that paper Y was harder or the cohort differed. The reverse also happens: a higher score with a lower percentile may mean an easier paper or a stronger crowd.
How to use this in practice:
- Track your own score trend with a three-mock average to judge improvement.
- Use rank or percentile as a rough sense of position, mainly when the number of test takers is large and consistent. A rank among a few hundred people is a weak signal.
- Never compare ranks across platforms. Different cohorts and different difficulty make them incomparable.
- Do not read a single mock rank as a prediction of the real result. Real exams may have different difficulty, shifts and normalisation rules. Check the latest notification for how your exam handles that.
The three-mock average. Single scores are noisy because paper difficulty varies. Smooth them out.
| Mock | Score | Average of last 3 |
|---|---|---|
| FM1 | 84 | - |
| FM2 | 90 | - |
| FM3 | 88 | 87.3 |
| FM4 | 97 | 91.7 |
| FM5 | 102.5 | 95.8 |
| FM6 | 99 | 99.5 |
| FM7 | 104 | 101.8 |
| FM8 | 108.5 | 103.8 |
This is invented data. Notice that FM6 dipped by 3.5 marks from FM5, which can feel alarming, but the three-mock average still rose from 95.8 to 99.5. Judging on the dip would have triggered a pointless change of strategy. The average moved from 87.3 to 103.8 over six steps, a gain of about 16.5 marks, which is the real story.
Avoiding mock fatigue
Mock fatigue is what happens when tests pile up faster than your brain can process them. You stop analysing, you start guessing in the second half, and the score becomes a source of dread rather than information.
Warning signs: you skip the analysis because you are tired; you feel dread before starting; your accuracy drops in the last 20 minutes of every mock; you open the result page and close it without reading; you take another mock to feel better about the last one.
What helps:
- Cap the number per week. Even in Phase 3, three full mocks is a lot. Two with proper analysis can beat three without it.
- Keep one fixed rest day each week with no test and no new study.
- Alternate test days and repair days. A mock day followed by a re-attempt day is easier to sustain than mock after mock.
- Review before you test. Spend ten minutes on the mistake log before the mock. It keeps the previous lessons in mind.
- Set a process goal instead of a score goal. For example, "no more than two silly errors in Reasoning" is within your control, while "score 110" is not.
- Take a lighter week if signs persist. Replace two mocks with sectionals and extra revision. A short step back costs less than weeks of low-quality testing.
Decision rules: when to change your strategy
Without rules, you will either change strategy after every bad mock or never change it at all. Decide the triggers in advance. The thresholds below are our planning suggestions for the illustrative 200-mark paper; scale them to your own exam.
- Judge on three mocks, not one. Do not alter your approach because of a single score. Wait until the three-mock average tells you something.
- Plateau rule. If your three-mock average has not risen by about 3 to 5 marks across the last four mocks, something in the routine must change. Look at the error taxonomy to decide what. As an invented example, five mocks scoring 101, 99, 103, 100 and 102 average exactly 101, with a range of just 4 marks. That is a plateau. Changing the analysis habit, the time budget or the study focus is warranted.
- Silly-error rule. If silly errors account for more than about a quarter to a third of your marks lost to wrong answers (in Illustration 4 it was 17.5 of 57.5, roughly 30 percent), prioritise process fixes: slower reading, step writing, a final check routine. More study will not help.
- Concept-gap rule. If concept gaps are around half of lost marks or more, pause full mocks for a week. Return to topic study and sectionals, then resume mocks.
- Time-pressure rule. If time pressure dominates, or a section has many blank questions you could have solved, work on timed sectionals, question caps and section order before anything else.
- Attempts and accuracy rule. If attempts are low and accuracy is high (for instance, above 85 percent), raise your attempts gradually in steps of two or three questions per section. If attempts are high and accuracy is low (for instance, below 70 percent with negative marking), cut attempts and focus on question selection. Recompute the break-even accuracy for your exam's negative marking, as shown earlier.
- Re-attempt rule. If fewer than half of your previous mistakes are solved at re-attempt, change how you analyse, not how many mocks you take.
- Last-fortnight rule. Within the final 14 days, change nothing big. Fine-tune the time budget by a minute or two at most. New strategies tested this late tend to cost more than they give.
FAQs
How many full-length mocks should I take in 90 days? There is no official number. The sample table in this post totals 19 full mocks and 28 sectionals as a planning ceiling for someone who can analyse every test. If you have less time, take fewer and analyse each properly.
Should I start with sectional tests or full mocks? Take one full mock first as a diagnostic, then lean on sectional and topic tests for the first four weeks or so. Move to more full mocks as your topic coverage improves.
How long should analysis take? At least as long as the test itself, and often about one and a half times the test duration in the early weeks. If analysis takes you ten minutes, you are probably only checking answers, not causes.
What is a good accuracy percentage? It depends on your exam's negative marking and your target score. In the illustrative scheme in this post, accuracy above 20 percent has positive expected value for an individual question, but the real aim is to raise accuracy while keeping attempts high. Track your own trend instead of chasing a fixed number.
Is rank more important than score? Neither alone. Use the three-mock average of your score to measure your own progress and rank or percentile as a rough indicator of position. Both depend on paper difficulty and the cohort, so do not treat either as a prediction.
Should I re-attempt the whole mock? Mostly no. Re-attempt only the wrong and skipped questions after 10 to 14 days to see whether your fixes worked. A whole-paper re-attempt, if you do one, should be weeks later and its score should not be treated as your current level.
What should I do if my score drops suddenly? Check the paper's difficulty, your time per section and the error taxonomy before changing anything. A single dip, as in the three-mock-average example, may just be noise. If the average also falls over three or four mocks, apply the decision rules above.
How do I know if I have mock fatigue? Common signs are skipping analysis, rising dread before tests, falling accuracy in the second half of every paper and taking mocks only to feel better. Reduce the weekly count, add a rest day and lean on sectionals for a week.
Should I take a mock the day before the exam? We suggest not. Take your last full mock about three days before, use the last two days for the mistake log and light revision, and rest properly.
Do these numbers apply to my exam? Not directly. All scorecards here are invented illustrations built on a made-up pattern. Check your exam's latest notification for the actual number of questions, marks, negative marking and time, and redo the arithmetic with those figures.
Putting it into practice
Start this week with three things: print or open the mistake-log template, pick a section time budget for your next mock, and decide in advance which of the decision rules will trigger a change. Then let the loop run: test, analyse, fix, retest.
To work through the plan, practise with full-length mocks and sectional tests on Pareeksha, and use the section-wise results to fill in your own version of the tables in this post. Your own scorecards, read honestly, will tell you more than any number of mocks taken and forgotten.
Comments (0)
No comments yet. Be the first to share your thoughts.