You might assume that the section with the fewest questions on the GMAT should be manageable. On paper, 20 questions does not sound scary.
But anyone who has taken even one full-length mock knows the reality.
Getting to question 15 itself is a task. Finishing it comfortably is a luxury.
In this post, I want to break down pacing for DI across question types, and more importantly, what pacing realistically needs to look like if you want to attempt all questions comfortably.
First, what are we even dealing with? A typical DI section looks something like this:
- DS: 6-7
- Graphics and Tables: 5-6
- TPA: 3-4
- MSR: 3-6
Now instead of thinking 20 questions, think:
Quote:
“Where is my time actually going?”
Because it’s not evenly distributed.
Scenario 1: One MSR set (the nicer version)Let’s say you get one MSR set, my time prediction would look like -
- DS: 7 × 1.5 min -> ~11 min
- Graphics and Tables: 6 × 2 min -> 12 min
- TPA: 4 × 3 min -> 12 min
- MSR: 3 questions -> ~8 min
(3 min reading + 5 min solving)
You’re already at ~43 minutes.
Which means you have... ~2 minutes of buffer for the entire section.
Two.
Not per question. Total.
So yeah, that "let me just take a minute extra here" attitude heavily backfires.
Scenario 2: Two MSR sets (the scenario most of us wish to avoid)Now let’s say you get two MSR sets.
- DS: 6 × 1.5 -> 9 min
- Graphics and Tables: 5 × 2 -> 10 min
- TPA: 3 × 3 -> 9 min
- MSR: 6 questions -> ~16 min
Total ~44 minutes.
Buffer left? ~1 minute.
At this point, even your coffee break is longer than your margin for error.
The real takeawayIf you want to attempt all 20 questions comfortably, you need to benchmark how much time you are spending on each question type.
Not rigidly to the second, but close enough.
A small fluctuation here or there is fine. One question may take 30 seconds extra. Another may be quicker. That is normal. But the overall balance has to hold.
If you mindfully spend an extra minute on one question, you need to recover that minute somewhere soon after. If you do not, the section starts slipping without you even realizing it. And once you are above 4 minutes on any one question, you have usually lost more than time. You have lost control and flow.
That is when DI starts punishing you.
Knowing when to guess is a pacing skillNobody likes guessing. Feels like giving up.
But here’s the smarter way to look at it:
If after ~1 minute you feel:
Quote:
“This will take another 2–3 mins to crack properly”
...you should seriously consider guessing.
Because those 2–3 minutes are not free. They are being stolen from future questions. And what’s worse?
Spending 5 minutes,
still guessing, and then rushing the next 2 questions.
That’s a double loss.
What helped me mentallyI used to tell myself:
Quote:
“This is probably an experimental question anyway.”
No idea if it was true. But it helped me move on without emotional damage. Highly recommend for peace of mind.
Granular ways to save time across DI question types There are many micro strategies students use to save time. I have covered some of them in my other DI posts, but here is a quick summary.
1. Table questionsDo not stare at the whole table. Identify which column needs sorting and use that to narrow the search quickly. A lot of time is wasted because students scan horizontally without a plan.
2. Graphs and chartsFirst understand the broad trend. Then check the dropdowns or answer options early. Very often, one option is much easier to validate than the others, which means you can limit the scope of the work instead of fully solving the whole thing from scratch.
3. MSRWhen reading the tabs, do not try to memorize everything like you would in RC.
Your goal is simpler: know what information exists where, understand the general trend, and roughly map which tab is likely to help with which question.
That way, when the actual questions come, you know where to go instead of rereading the whole set again.
4. TPAAfter reading the argument, go to the option table early. Use it to eliminate clearly irrelevant choices first. Then test the remaining ones against the relationships or equations you formed. Trying to brute force every option from the beginning often wastes too much time.
5. DSBe disciplined and go step by step. Use the answer framework properly rather than mentally jumping to a conclusion based on your own assumptions.
Sometimes students think skipping steps will make them faster. In reality, it usually causes back and forth thinking, second guessing, and rework. And that often takes twice as long as doing it properly in the first place.
The one mistake that cuts across all DI typesMissing constraints.This is where a lot of wrong answers come from.
Not because the math was hard. Not because the reasoning was impossible. But because one condition, one qualifier, or one restriction was missed.
And the painful part is that these questions often do not even feel difficult when reviewed later. They just expose sloppy reading under pressure.
Note: Do not rush so much that you stop respecting constraints.
At the end of the day, DI pacing isn’t about moving quickly on every question.
It is about staying within a time budget by question type, recognizing early when a question is becoming too expensive, and protecting enough time to give yourself a fair shot at all 20 questions.
A lot of students think DI is hard because the data is messy. Sometimes that is true. But a lot of the time, DI feels hard because the pacing has already gone wrong by question 5 or 6, and the rest of the section is just damage control.
If you can learn to benchmark your timing, recover lost minutes quickly, and guess without guilt when needed, DI becomes much more manageable than it first appears.