GMAT Error Log Guide for Nepali Students explains how to record wrong answers, slow correct answers, lucky guesses and low-confidence decisions, then identify the first step that failed. It covers topic recognition, framework choice, data input, execution, answer-choice traps, timing, confidence, slips, prevention rules, transfer questions, weekly pattern analysis and using official practice and score-report evidence.
Information checked on 25 July 2026 against current mba.com Exam Content, Official Score Reports, Official Practice guidance and mba.com’s detailed error-analysis article. An error log is a preparation method, not an official scoring rule; adapt fields to the decisions that repeatedly limit your performance.
Key facts at a glance
| Error factor | What to record |
|---|---|
| Wrong answer | First failed decision and selected trap |
| Slow correct answer | Where excess time was spent |
| Lucky correct answer | Guess or unresolved reasoning |
| Low confidence | Evidence or method uncertainty |
| Root cause | Topic, framework, input, execution or mapping |
| Repair | Specific prevention rule and practice task |
| Transfer | Fresh question proving the repair |
Understand the purpose
An error log converts practice results into decisions about what to study next. It should reveal why performance failed, not merely list incorrect question numbers.
The goal is a repeatable repair that transfers to unfamiliar questions.
Log more than wrong answers
mba.com’s error-analysis guidance recommends including problems that took too long as well as wrong responses. Lucky correct answers also hide unstable reasoning.
Include any item whose process would be unreliable under a fresh topic or tighter timing.
Record the source
Note official product, practice exam, set and question identifier without copying copyrighted question text.
This allows later review while keeping the log concise and compliant.
Record section and question type
Use current categories: Quant Problem Solving, Verbal RC or CR, and the five Data Insights formats.
Add a useful subtopic such as ratios, inference, assumptions or table percentages.
Record the exact task
State what the question asked: value, inference, strengthen, sufficiency, comparison or another role.
Many errors begin by solving a related but different task.
Record your original answer
Save the selected choice and a brief reason before reading the explanation. This preserves the actual reasoning rather than a reconstructed story.
Also record confidence and whether the answer was bookmarked or changed.
Record time
Capture first-pass time and any review time. A slow correct answer may create later damage that accuracy alone hides.
Compare individual times with section checkpoints and the Official Score Report when available.
Find the first failed step
Do not stop at the final arithmetic slip or wrong choice. Identify the earliest decision that made the outcome likely.
Fixing the first failure often prevents several downstream errors.
Check topic recognition
Did you correctly identify the content, question type and logical task? Misclassification can make every later step efficient but irrelevant.
The repair may be broader exposure and a set of recognition cues.
Check framework choice
Did you choose an appropriate approach such as algebra, estimation, passage mapping or conclusion-gap analysis?
A familiar framework can still be inefficient or fragile for a particular structure.
Check framework recall
Did you remember the necessary steps and constraints? Missing one decision rule can produce repeated errors across a topic.
Write a short method checklist, then test it on fresh questions.
Check question-data input
Did you capture all qualifiers, units, comparison groups and conditions? Correct execution on incomplete input still gives the wrong answer.
Create a targeted reading or notation rule rather than labelling the error careless.
Check execution
Did algebra, arithmetic, evidence retrieval or source integration fail after a correct setup? Identify the exact operation.
Repair with a verification step appropriate to the error, such as sign, unit, scope or substitution.
Check answer mapping
Did the correct result get matched to the wrong option, column, unit or response part? This is common in interactive Data Insights formats.
Add a final interface and task check before submission.
Distinguish mistakes from slips
A mistake can come from a wrong concept or framework; a slip occurs when the plan was sound but execution failed.
They need different repairs: instruction and practice for one, process design and checks for the other.
Reject the label careless
“Careless” does not identify an action. Replace it with missed negative sign, skipped qualifier, wrong denominator or rushed final selection.
A precise label supports a precise prevention rule.
Record the selected trap
Explain why the wrong option was attractive: repeated passage words, right number wrong unit, reversed ratio or unsupported extreme.
Then state the feature that should eliminate it next time.
Explain the correct answer
Write why the correct choice meets the task using your own concise reasoning. Avoid copying the official explanation.
If you cannot explain it independently, the review is not complete.
Explain every rejected choice
For Verbal and close Data Insights questions, classify why each alternative fails: unsupported, reversed, irrelevant, wrong scope or wrong condition.
This trains discrimination rather than answer recognition.
Create a prevention rule
A useful rule is observable and specific: “write the denominator before percentage calculation” or “state the CR conclusion before choices.”
A vague promise to focus harder cannot be tested.
Assign a repair task
Choose the smallest practice that tests the rule: five untimed items, a method lesson, one timed set or a passage-mapping drill.
Do not respond to every error with a full-topic restart.
Use transfer questions
Solve a fresh question with the same underlying decision but different wording or topic. Transfer shows that the repair is reusable.
Delay the transfer when necessary so short-term memory of the explanation does not dominate.
Revisit logged questions
Re-solve without looking at the previous answer, then compare method and time. Mark whether the prevention rule was used.
Recognition of an old answer is weaker evidence than correct work on a fresh item.
Analyse weekly patterns
Group entries by question type, first failed step, timing, confidence and trap. Look for repeated root causes.
Prioritise high-frequency and high-impact patterns rather than the most recent mistake.
Use enough evidence
One error may be random. Build a reasonable sample before declaring a stable weakness, while still repairing serious process failures immediately.
Track whether the error rate changes after intervention.
Include strengths
Record processes that worked under difficult conditions. A strong evidence-return method or pacing recovery can transfer to weaker areas.
The log should guide maintenance as well as repair.
Use confidence calibration
Compare high, medium and low confidence with accuracy. High-confidence errors deserve special attention because the failure may be invisible during the exam.
Low-confidence correct answers may need method consolidation.
Use Official Score Report evidence
The current report provides performance by section, content domain, question type, skills, time management and review changes.
Combine those patterns with your process log to decide what a retake plan should target.
Keep the log manageable
Use structured columns and concise entries. A beautiful spreadsheet that takes longer than the practice itself will not be maintained.
Add a field only when it changes a study decision.
Recognise common logging mistakes
Common mistakes include copying explanations, logging only wrong answers, ignoring time, using vague causes and never testing the repair.
Another is collecting hundreds of entries without weekly prioritisation.
Use current official materials
Read the mba.com error-analysis guide, official Exam Content and Official Score Reports.
Use current official practice questions so the logged categories match the current exam.
Follow a seven-step error-log method
Capture the attempt; classify the task; find the first failed step; identify the trap; write a prevention rule; assign repair practice; then prove transfer.
Review patterns weekly and retire a rule only after stable improvement.
Connect preparation with applications
For business-school research and overseas application planning, visit MKS Education. For guided GMAT error analysis, explore MKS Prep.
Bring your error log and official practice report to counselling so assignments target root causes.
Frequently asked questions
Which questions belong in a GMAT error log?
Include wrong answers, slow correct answers, lucky guesses and low-confidence or fragile decisions.
What is the most important field?
Identify the first failed decision and a specific prevention rule that can be tested.
Should I copy the official explanation?
No. Explain the correct reasoning and the selected trap concisely in your own words.
How often should I review the log?
Review patterns weekly and after major timed sets or full practice exams.
How do I know an error is repaired?
Use the prevention rule successfully on fresh transfer questions under increasingly realistic timing.