Anisha has done MBA in Marketing from NMIMS And Executive Management(PMNO) from Harvard Business School. She has been instrumental in growing CATKing Digital with her experience with Marico and Henkel in the past.
Taking a Mock Test is Easy. Most Students Stop at the Score. Here Is What to Do Instead.
The average GRE aspirant takes 4-6 mock tests before their real exam. Almost all of them spend 3 hours taking the test and 10 minutes looking at the score. This is exactly backwards.
The test itself teaches you nothing. The analysis after the test is where score improvement happens. A student who takes 3 mocks and analyses each one for 90 minutes will almost always outperform a student who takes 8 mocks and spends 10 minutes reviewing each one.
This guide gives you a complete, section-by-section mock analysis system - including a ready-to-use error log template, Verbal and Quant diagnostic frameworks, and a decision guide for when you are ready to book your real exam.
The Core Principle
The 80/20 rule of GRE prep: 80% of your score improvement comes from 20% of your effort - specifically, the effort you spend understanding WHY you got a question wrong, not just THAT you got it wrong. Analysis time should be at minimum equal to test time. For high-impact sessions, it should be double.
Why Mock Analysis Matters More Than Taking More Mocks
Most students respond to a low mock score by booking another mock immediately. This is the wrong instinct. Here is why:
|
Approach |
What Happens |
Score Outcome |
|
Take mock |
Same errors repeat. No concept gaps fixed. Timing issues persist. |
Score plateaus or improves only 2-3 points over multiple tests |
|
Take mock |
Specific error categories are identified and addressed. Concept gaps closed. Time strategy adjusted. |
Score jumps 5-12 points between mocks with focused remediation |
The GRE's section-adaptive format makes this even more important. Your Section 1 performance determines the difficulty ceiling of Section 2. Repeating the same patterns - rushing Section 1, misreading Quantitative Comparison questions, skipping RC passages - without diagnosing them first means you keep hitting the same ceiling.
Step 1 - Check for External Disruptions Before Analysing Anything
Before diving into question-level analysis, assess whether your mock score accurately reflects your real ability. The following factors can significantly inflate or deflate a home mock score:
|
Disruption |
Effect on Score |
What to Do |
|
Paused the test mid-section |
Inflates score - more thinking time than real exam allows |
Note it, discount the section score by 3-5 points for planning purposes |
|
Skipped AWA entirely |
AWA score is invalid - may also affect concentration for next sections |
Always attempt AWA even in mocks - it builds the full test stamina required |
|
Phone calls or interruptions |
May inflate or deflate depending on timing - disrupts concentration |
Log the disruption and the question you were on - flag those questions in analysis |
|
Took longer breaks than allowed |
Inflates score - real exam allows one optional break of ~1 minute |
Redo that section under strict time conditions if score is a key decision point |
|
Internet connectivity issues |
Can skew timing data - artificially slow down or speed up question pacing |
Discount timing data from affected sections for that mock |
Step 2 - Section-Level Overview: Find Your Biggest Drop
Before looking at individual questions, get a 60-second top-level view of your performance across sections. This tells you where to spend the most analysis time.
• Total score and combined percentile - is this above, at, or below your target?
• Section accuracy: Verbal Section 1 vs Section 2, Quant Section 1 vs Section 2
• Skipped questions per section - skips indicate time pressure or confidence issues, not just knowledge gaps
• Average time per question per section - are you faster in one section? Slower in another?
Section-Adaptive Interpretation
Key signal to look for: If your Section 2 accuracy is significantly lower than Section 1 in the same subject, you likely received the harder Section 2 (which means Section 1 went well). This is actually a good sign - your Section 2 difficulty was elevated. Do not panic at a lower Section 2 raw score; look at the scaled score instead. Conversely, if Section 1 and Section 2 have similar accuracy and similar difficulty, your Section 1 performance may have been inconsistent - look more carefully at Section 1 errors.
Step 3 - The Error Log Template (Use This for Every Mock)
This is the most important tool in your mock analysis process. Every wrong answer and every skipped question goes into this log. The act of categorising the error forces you to understand why you got it wrong - which is the only way to prevent the same error next time.
The 4 Error Types - Choose One for Every Wrong Answer:
|
Error Type |
Definition |
Example |
Fix |
|
Concept Gap |
You did not know the underlying concept, formula, or vocabulary required to answer the question correctly |
Got a permutations question wrong because you do not know the nPr formula |
Study the concept from scratch. Do 10 practice questions on that specific concept before moving on. |
|
Calculation / Careless Error |
You knew the concept and the approach, but made an arithmetic, algebraic, or reading error in execution |
Knew the method for a percentage problem but multiplied instead of divided in the last step |
Slow down at the execution step. Write every intermediate step. Check your final answer against a quick estimate. |
|
Misread Question |
You read the question incorrectly - misidentified the question type, missed a qualifier, or answered a different question than was asked |
Answered 'which must be true' when the question asked 'which could be true' |
Circle or underline the key qualifier in every question before solving. Re-read the question after solving before selecting the answer. |
|
Time Error (Rushed) |
You knew or likely knew the answer but ran out of time or rushed and selected incorrectly under pressure |
Got an RC question wrong after spending 30 seconds on a passage that needed 2 minutes |
Flag this question type for pacing practice. Build a timed drill specifically for this section. Practice the skip-and-return strategy. |
Step 4 - Verbal Error Analysis: Diagnosing the Real Cause
Verbal errors are the most misdiagnosed errors in GRE prep. Most students assume every verbal error is a vocabulary problem. This is rarely true. Here is the correct diagnostic breakdown:
Text Completion (TC) and Sentence Equivalence (SE) Error Diagnosis:
|
Symptom |
Actual Cause |
Diagnostic Test |
Fix |
|
Got TC wrong even though you knew all the words |
Logic error - you did not read the sentence direction (contrast, continuation, causation) before evaluating options |
Re-read the question without looking at options. Predict what the blank should mean. Then check options. |
Practice 'predict before you peek' - always determine the blank's meaning from sentence logic before reading choices. |
|
Got TC wrong because you didn't know a word |
Vocabulary gap - specific high-frequency GRE word not in your active vocabulary |
Look up the word. Is it in CatKing's high-frequency list? |
Add to the error vocabulary list. Study the word in 3 different contexts. Review in 3 days using spaced repetition. |
|
Got SE wrong even though both blanks seemed right |
Missed the SE rule - both words must create the same meaning in the sentence, not just both make grammatical sense |
Re-read SE instructions. The two correct answers must be interchangeable AND produce similar sentences. |
Practice 10 SE questions focusing only on the 'same meaning' test. Eliminate options that work individually but diverge in meaning. |
|
Consistently wrong on 2-blank and 3-blank TC |
Attempting all blanks simultaneously instead of filling easiest blank first |
Identify which blank has the most context clues in the sentence. Fill that one first. |
Practice the 'easiest blank first' technique. In 3-blank TC, there is almost always one blank with stronger context than the others. |
Reading Comprehension (RC) Error Diagnosis:
|
Symptom |
Actual Cause |
Fix |
|
Wrong on 'main idea' or 'primary purpose' questions |
Reading the passage for details instead of structure. Missing the author's central argument. |
Read the first sentence of each paragraph only, then answer main idea questions. Details are distractors for main-idea Qs. |
|
Wrong on 'inference' questions - chose a stated fact instead |
Confusing what the passage says (explicit) with what the passage implies (inference). Inference Qs require you to go one step beyond the text. |
For every inference answer, ask: 'Is this directly stated, or must I conclude it from what is stated?' Only the latter is correct. |
|
Wrong on 'tone' or 'author attitude' questions |
Missing tone-signal words - GRE passages use subtle language to indicate the author's position (e.g., 'arguably', 'purportedly', 'overlooks the fact that'). |
Circle every tone word in the passage before answering attitude questions. Build a list of GRE tone vocabulary. |
|
Consistently wrong on long-passage Qs but correct on short-passage Qs |
Active reading fatigue - concentration drops on longer passages without a structured reading approach. |
Use the 'paragraph topic sentence' method: read only the first sentence of each paragraph for structure, then read the specific paragraph the question refers to. |
|
Wrong after spending a lot of time on passage |
Over-reading - trying to understand every word instead of reading for argument structure. |
Time yourself: max 3 minutes for a short passage, 4-5 minutes for long passage. Any more is over-reading. |
Step 5 - Quant Error Analysis: Concept, Calculation, or Misread?
Unlike Verbal, Quant errors fall into three very distinct categories - and each requires a completely different fix. Misidentifying the error type leads to the wrong remediation.
|
Error Type |
How to Identify It |
What It Means |
The Right Fix |
|
Concept Gap |
After seeing the solution, you still don't understand the method or formula used. |
You have not yet learned or retained this specific concept. This is a knowledge gap, not a practice gap. |
Study the concept from the textbook level - not by doing more questions. Watch a video explanation. Then do 5 questions on that concept specifically. Do not move on until you can solve it without looking at the solution. |
|
Calculation / Careless Error |
After seeing the solution, you say 'I knew that - I just made a silly mistake.' The method was correct, the arithmetic was wrong. |
You have the knowledge. The problem is execution speed and accuracy - often caused by rushing or skipping steps. |
Slow down on the execution step specifically. Write every step on scratch paper. Develop a habit of checking your final answer against a quick estimation (e.g., 'the answer should be around 50 - my answer of 52 is plausible'). |
|
Misread Question |
After seeing the solution, you realise you answered a slightly different question - missed a negative sign, misread 'integer' as 'whole number', or confused 'least' with 'greatest'. |
You are not reading carefully enough before solving. Often caused by time pressure. |
Circle the key terms in every Quant question before solving: the variable being asked for, any qualifiers (integer, positive, not equal to zero), and the question verb (find, minimise, maximise, which must be true). This takes 5 seconds and prevents this entire error category. |
|
Wrong Strategy / Approach |
After seeing the solution, you understand the answer, but your approach was longer or more complex than necessary. |
You solved correctly but inefficiently - this is a time drain that causes downstream problems. |
Learn the shortcut or pattern-recognition approach for this question type. GRE Quant rewards elegant shortcuts over brute-force algebra. Study the specific question type (QC, DI, word problems) for pattern recognition. |
Quantitative Comparison (QC)
The Most Commonly Misanalysed Question Type
QC questions generate the highest rate of avoidable errors among Indian students. The most common cause is not testing edge cases.
• For every QC question you got wrong: did you test x = 0, x = 1, and x = negative before selecting your answer?
• If Quantity A > Quantity B for x = 2 but Quantity A < Quantity B for x = -1, the answer is always D (cannot be determined) - not A or B.
• The most common QC error: testing only positive integers and selecting A or B without checking whether negatives or fractions change the relationship.
Realistic Score Improvement - What to Expect Week by Week
One of the most demoralising experiences in GRE prep is improving 2 points after 3 weeks of hard work and feeling like nothing is happening. Understanding realistic improvement curves prevents this.
|
Starting Score |
6-Week Realistic Gain |
12-Week Realistic Gain |
Primary Driver |
Biggest Risk |
|
Below 295 |
10 – 18 points |
18 – 28 points |
Quant fundamentals - biggest gains come fastest from rebuilding math basics |
Studying everything broadly instead of targeting Quant first |
|
295 – 305 |
7 – 12 points |
12 – 20 points |
Error log discipline - identifying repeating error types and fixing them systematically |
Continuing to take mocks without deep analysis between them |
|
306 – 314 |
5 – 8 points |
8 – 14 points |
Section 1 strategy + error type precision - most gains come from fixing the same 3–4 error patterns |
Spending time on content you already know vs fixing specific weak spots |
|
315 – 322 |
3 – 6 points |
4 – 8 points |
Precision and timing - small gains from eliminating careless errors and improving pacing |
Trying to cover too many new topics instead of perfecting high-frequency patterns |
|
323 – 330 |
1 – 3 points |
2 – 5 points |
Near-ceiling performance - gains come from rare question types and maximum consistency |
The marginal gain may not justify extended prep - evaluate whether score already meets your target |
What This Table Actually Means For You
The most important thing this table tells you: if you are in the 295–314 range, the gains are achievable but ONLY through disciplined error analysis. More mocks without analysis will not get you there. Students in this range who implement the error log system consistently move 8–14 points in 12 weeks. Students who just keep taking mocks typically move 2–4 points.
When Should You Book Your Real GRE? A Decision Framework
This is one of the most common questions students ask - and the answer should be data-driven, not calendar-driven. Use this framework:
|
Question |
If YES |
If NO |
|
Have you taken at least 3 full-length mocks under real test conditions (timed, no breaks, AWA attempted)? |
You have enough data to make a reliable decision. Continue. |
Take at least 3 mocks before booking. One or two data points are not enough to predict your real exam score. |
|
Are your last 3 mock scores within 5 points of each other (consistent band)? |
Your score has stabilised - this is a reliable indicator of your current ceiling. Compare this band to your target. |
High variance means your performance is still inconsistent. Do another 2 mocks after a focused analysis sprint before deciding. |
|
Is your consistent mock score at or above your target program's competitive range? |
Book the real exam within 2–3 weeks. Your score is ready. Waiting longer risks score erosion from fatigue. |
Identify the gap. Is it 3–5 points? A targeted 3-week sprint may close it. Is it 8+ points? You need a full prep cycle extension. |
|
Are your most recent mocks done using ETS PowerPrep or PowerPrep Plus? |
Your benchmarks are the most reliable possible. Third-party mock scores can be 5–10 points off in either direction. |
Replace your most recent benchmark with a PowerPrep test before making the booking decision. Third-party scores are not reliable enough to base this decision on. |
|
Have you analysed your last 2 mocks fully using an error log? |
You have extracted the maximum learning from your mock data. You are ready to commit to a test date. |
Do not book yet. Untanalysed mocks are wasted mocks. Complete the analysis first - you may identify a fixable issue that changes your timeline. |
When "Not Ready" is actually fear
The sunk cost trap: Many students delay booking their real exam because they feel 'not ready yet'. This is often fear, not data. If your PowerPrep scores are consistently in your target range across 3+ tests and your error log shows no new error categories emerging in the last 2 weeks - you are ready. Additional prep time at this point produces diminishing returns.
Frequently Asked Questions (FAQs)
Q1. How long should I spend analysing a GRE mock test?
At minimum, your analysis time should equal your test time - which means at least 2 hours of analysis for a full GRE mock. For maximum improvement, analysis time should be double the test time. The analysis session should include: checking for disruptions, reviewing section-level accuracy, logging every wrong answer in the error log, diagnosing the error type for each question, and building a specific action item list before your next study session.
Q2. How many GRE mock tests should I take before the real exam?
Most students benefit from 4 to 6 full-length mock tests. The first two (ideally ETS PowerPrep I and II) establish your baseline and final benchmark. The middle tests (Manhattan, Magoosh, or CatKing mocks) are practice tests for learning and error identification. More than 6–8 mocks without analysis between them produces diminishing returns and can cause test fatigue. Quality of analysis matters more than quantity of tests taken.
Q3. What is the best GRE mock test for accuracy?
ETS PowerPrep tests (both the two free tests and the three paid PowerPrep Plus tests) are the most accurate GRE mock tests available because they use real retired GRE questions and the actual ETS scoring algorithm. Third-party mocks from Manhattan Prep, Magoosh, and Kaplan are useful for practice but can vary by 5–10 points from your real exam score in either direction. Always use a PowerPrep test as your final benchmark before booking your real exam.
Q4. What should I do after a low GRE mock score?
Do not rebook another mock immediately. Instead: complete a full error log analysis of the low-scoring mock to identify whether the drop was caused by concept gaps, careless errors, time management failures, or external disruptions. This analysis will tell you exactly what to work on. Then do 1–2 weeks of targeted remediation on the identified error categories before taking your next mock. Taking another mock without this analysis step will likely produce a similar result.
Q5. How do I improve my GRE Verbal score from mock tests?
First, diagnose whether your Verbal errors are vocabulary-based, inference-based, or time-based - these require completely different fixes. Vocabulary errors require building contextual word knowledge from a high-frequency list. Inference errors require practising RC question types specifically. Time errors require pacing drills. Most students make the mistake of studying vocabulary when their real problem is inference or pacing. Use the Verbal error diagnosis table in this article to identify your actual error pattern before starting remediation.
Q6. How do I improve my GRE Quant score from mock tests?
The most important step is distinguishing concept errors from calculation errors. Concept errors require studying the underlying topic from scratch. Calculation errors require slowing down on execution and writing every step explicitly. Both are common but require opposite remediation approaches - more practice does not fix concept gaps, and slower execution does not fix knowledge gaps. The error log template in this article will help you categorise each Quant error correctly so you fix the right problem.
Q7. Is a CatKing mock test reliable for predicting my GRE score?
CatKing's diagnostic mock is designed to give you a section-wise performance baseline and identify your error patterns - it is most useful as a diagnostic tool and study-progress tracker. For the most accurate prediction of your real GRE score, use ETS PowerPrep tests as your primary benchmark, and compare your CatKing diagnostic result to your PowerPrep scores to calibrate the gap.
Comments are disabled for now