Focusing on content makes sense. It's the obvious first step in GMAT® prep.
But once you do know the material, a lot of score loss comes from something else. You do the right work — and then lose track of it mid-problem. You solve for the wrong variable. You miss a keyword buried in the question stem. You talk yourself back into an answer you already eliminated.
These aren't knowledge gaps. They're execution errors. And one of the biggest levers for improving execution on the GMAT® is your scratch work.
Think of it as leaving breadcrumbs for yourself. Every note you write down is one less thing your working memory has to hold under pressure. And the GMAT® puts a lot of pressure on working memory.
This helps in every section. Not because writing is magic — because it lowers how much you're asking your brain to juggle at once.
Let's walk through what to write down in each section.
Quant: Write What's Given and What's Asked
One of the most common sources of missed quant questions isn't a content gap. It's losing track of what the question is asking or what information you've been given.
You start solving. You do three lines of math. You get an answer. And it's wrong — not because you couldn't do the math, but because you solved for the wrong variable or forgot a constraint that was sitting right there in the problem.
Before you start any calculation, write down two things:
What's given. What's asked.
Write the given information on the left side of your scratch paper. Write what the question is asking on the right. Then start the math.
This habit keeps you anchored to the big picture. It makes it much harder to solve for the wrong thing, because you've already written down the right thing.
If your issue is computation errors instead of direction errors, the fix follows the same principle. Write out every step. You don't need to be perfect — even we still make computation errors during practice. The goal is catching bad numbers as they happen, before they cascade through the whole problem.
A lot of students worry that writing more will slow them down. That's a fair concern. But here's the thing: re-deriving a value you already computed because you can't find it? That's slow. Re-reading a problem because the target drifted? That's slow. Writing more down front usually saves time overall.
Understanding how the scoring algorithm works helps here too. It's okay to invest more time in questions you know how to do, as long as you're giving up on the ones that are too hard for you. The net effect is usually faster, not slower.
Reading Comprehension: Light Notes on Main Ideas
The biggest scratch work mistake on RC is treating it like a college lecture. You try 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 of transcribing details, write the main idea of each paragraph as you read. One short phrase per paragraph is usually enough. This helps you process the structure of the passage without getting lost in the weeds.
When a question asks about something specific, you'll know which section to go back to. That's the whole point — not to have every detail memorized, but to have a map of where things live.
If you're taking zero notes and getting lost in long passages, try adding main-idea notes. If you're taking exhaustive notes and running out of time, try scaling back to just the big picture. Most students err on the side of too many notes, not too few.
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. By the time you're evaluating option E, the conclusion may have drifted. You think you remember what the argument was saying, but you're working with a fuzzy version of it.
Write down the main conclusion once you find 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. It takes two seconds and it prevents a very common CR error.
Verbal: Track Elimination
For every verbal question, write A, B, C, D, E on your scratch paper. Track your elimination as you go.
A simple plus or minus next to each letter is enough. Plus means it's still in contention. Minus means it's out.
This saves you from re-reasoning through options you already eliminated. Even 5 to 10 seconds saved per question adds up over a 45-minute section. And more importantly, it prevents you from talking yourself back into a wrong answer you already crossed off.
Data Insights: Capture Every Keyword
DI combines the challenges of verbal and quant, so the scratch work recommendations from both sections apply here. 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.
FAQ
Does writing more down really save time on the GMAT®?
For most students, yes. The time you spend writing is smaller than the time you spend re-reading problems, re-deriving values, or re-reasoning through eliminated answer choices. The net effect is usually faster, not slower.
What if I'm already running out of time?
If you're running out of time, the issue is almost never writing too much. It's usually spending too long on questions you should be letting go of. Better scratch work helps you make faster decisions about which questions to invest in and which to skip.
Should I take notes on Reading Comprehension or just read carefully?
Take light notes — main ideas only. Reading carefully without notes can work on short passages, but long passages are where students get lost. A few words per paragraph gives you a map without slowing you down.
How much should I write for Data Insights questions?
Write every keyword from the question stem and record every intermediate calculation result. DI questions punish you for missing small details, so err on the side of capturing more.
How long does it take to build these scratch work habits?
Give it a few practice sessions. These habits might feel unnatural at first, especially if you're used to doing most of your work in your head. But after a few hours of conditioning, most students find that writing more down makes everything feel easier, not harder.
Want to learn even more?
We covered this topic in depth on the podcast — this episode walks through scratch work strategy for every section, with examples from real practice questions.
If you're also working through score plateaus, the way you review your practice tests matters as much as the tests themselves. Our guide to reviewing GMAT® practice tests shows you how to audit your scratch work after each exam.