How Writing Down More Improves Your GMAT® Score

What This Episode Covers

Most GMAT® prep content focuses on what to learn. This episode focuses on something just as important that almost nobody talks about: how what you write on your scratch paper affects your score.

Isaac walks through how scratch work improves performance in every section of the GMAT® — Quant, Verbal, and Data Insights. The core insight is simple but counterintuitive: the number one thing holding back most people's quant scores isn't a knowledge gap. It's missing questions they already know how to do. And better scratch work fixes a significant portion of those misses.

The advice is practical and specific. For Quant: always write what's given and what's asked. For Reading Comprehension: take light notes on main ideas, not details. For Critical Reasoning: write down the conclusion every time. For Data Insights: capture every keyword in the question. Each recommendation is designed to be implementable on your next practice set.

Key Points

Quant: Write What's Given and What's Asked

The biggest source of missed quant questions isn't content gaps — it's losing track of what the question is asking or what information you've been given. Writing both down before you start solving keeps you anchored to the big picture and makes it much harder to solve for the wrong thing.

If computation errors are your main issue instead, write out every step of your computation. You don't need to be perfect — even Isaac still makes computation errors during practice. The goal is catching them before they wreck the whole problem. When you write every step, you can spot a bad number as it happens and fix it immediately.

It might feel like writing more will slow you down too much. That's a normal concern. But understanding how the scoring algorithm works helps — it's okay to invest more time in questions you know how to do if you're giving up on the ones that are too hard for you. The net effect is usually faster overall, because you're not re-deriving things you already figured out.

Reading Comprehension: Light Notes on Main Ideas

The biggest scratch work mistake on RC is treating it like a college lecture — trying to capture every detail so you can recall it later. But the passage never disappears. You can always go back and reread a specific section when a question asks about it.

Instead, write the main idea of each paragraph (or each section of a long paragraph) as you read. This helps you process the structure of the passage without getting lost in details. When a question asks about something specific, you'll know which section to go back to.

This approach feels too fast for some people and too slow for others. If you're taking zero notes and getting lost, try adding main-idea notes. If you're taking exhaustive notes and running out of time, try scaling back to just the big picture.

Critical Reasoning: Write the Conclusion

The most common CR mistake isn't failing to identify the conclusion — it's losing track of the conclusion while working through complicated answer choices. Your short-term memory can only hold so much, and by the time you're evaluating option E, the conclusion may have drifted.

Write down the main conclusion once you find it. That's it. When you're going back and forth between two answer choices, you can reference your notes instead of trying to hold the entire argument in your head.

Verbal: Track Elimination

Write A, B, C, D, E for every verbal question and track your elimination as you go. A simple plus or minus next to each letter saves you from re-reasoning through options you already eliminated. Even 5–10 seconds saved per question adds up over a 45-minute section.

Data Insights: Capture Every Keyword

DI combines the challenges of verbal and quant, and the scratch work recommendations from both sections apply. But there's one DI-specific trap that catches a surprising number of people: missing a keyword in the question itself.

Many DI questions pack five or six keywords into a short question stem. Miss one of them and you're answering a different question than the one being asked. Write down what every DI question is asking you to find, and make sure you've captured all the keywords before you start pulling data.

For computation on DI, write down the results of your calculator work. You don't need to write every keystroke, but record the big intermediate results — especially anything with units attached. It's easy to lose track of a number you computed 30 seconds ago when you're juggling multiple tabs of data.

Key Takeaways

Writing more down in Quant is the highest-ROI habit you can build. Always write what's given and what's asked. It could fix at least half of the questions you currently know how to do but get wrong.
Write every step of your computation. You won't stop making computation errors entirely — nobody does. But you'll catch them before they ruin the problem.
RC notes are for processing, not recall. Write main ideas only. The passage stays there — go back for details when a question asks.
Write the CR conclusion every time. It prevents the most common CR mistake: losing track of the conclusion while evaluating answer choices.
Track elimination on every verbal question. A, B, C, D, E with plus/minus marks saves re-reasoning time.
Capture every keyword in DI questions. Missing one keyword in the question stem is one of the most common DI errors for students who have already mastered the content.
All of this takes practice to implement. Don't expect it to work perfectly on your next practice test. Give it a few hours of conditioning first.