The thing that jumps out isn't the four questions you don't get to. It's the ones you do.
If you're working 16 and finishing with 11 or 12 right, at least four of your misses are on questions you had time for. So the timing story only explains part of the DI 77.
Worth naming too: 77 to 84 is a substantial jump. What makes it plausible is that you can already solve this material untimed.
On that untimed accuracy, though. It's good news, but it doesn't prove the concepts are solid in the way the test needs. Untimed, you can reread the prompt, start down one path, back out, open a different tab, and still land on the right answer. That covers for a lot. Under the clock you have to see what's being tested and set it up correctly on the first pass, which is a different skill.
Why that breaks down varies. Sometimes the Quant or Verbal underneath isn't automatic, so you're working out the approach instead of recognizing it. Sometimes it's process: which tab first, when to sort, when to estimate. Sometimes a few early questions eat the time the last four needed. Nerves show up too. Your own data is what tells you which.
So track DI by question type on your next few mocks, time and outcome for every question. Compare against roughly 1:30 to 2:30 for Quant-based Data Sufficiency and Table Analysis, 1:30 to 3:00 for Graphics Interpretation and Quant-based Two-Part Analysis, 1:30 to 2:30 for Verbal-based Two-Part Analysis, and for Multi-Source Reasoning, 1:00 to 2:00 on single-answer questions and 2:00 to 3:00 on three-statement ones, plus 30 to 90 seconds on the prompt itself. Wherever you're consistently long, that's the type to rebuild: relearn the approach, drill that type alone untimed until accuracy is high and the setup is routine, then layer timing back in.
Two DI-specific levers. Your Quant and Verbal foundations, since DI is largely those concepts in unfamiliar packaging. And doing less arithmetic — when the answer choices are spread out, estimate; when they're close, compute.
For the section itself, use checkpoints instead of a per-question average. Five blocks of four questions, nine minutes each. You want 36 minutes left starting question 5, 27 at question 9, 18 at question 13, and 9 at question 17.
Last thing, and you can start on it immediately alongside the rest: choose your guesses. Right now the test picks them for you, and it picks the last four. If you spot a heavy question at question 6 and guess it in 20 seconds, you've bought back two minutes for something you can actually solve. Two or three deliberate guesses beats four forced ones at the end.
This article goes deeper on DI pacing by type:
Data Insights Timing Strategy.
sri2024
Hi Community,
I'm looking for advice on improving my Data Insights (DI) score from around
DI 77 to
DI 84+.
My biggest challenge is time management. In both the official GMAT practice tests and GMAT Club mocks, I'm usually able to attempt only about
16 out of 20 questions. I often end up guessing the last four questions because I run out of time. The time pressure also causes me to make avoidable mistakes, so I typically finish with only
11–12 correct answers.
The interesting part is that when I review the mock afterward without time constraints, I'm able to solve virtually all the questions correctly. This suggests that my conceptual understanding is solid, but my execution under timed conditions is lacking.
Has anyone faced a similar plateau? What strategies, drills, or practice methods helped you improve your speed and consistency to reach
DI 84+? Any advice would be greatly appreciated.