Time management on the GMAT Focus Data Insights section is not a single skill but a layered protocol: a per-item time box, a per-pass triage plan, and a small set of rescue moves for the prompts that overrun. The section presents 20 questions inside 45 minutes, drawn from five item families — Data Sufficiency, Multi-Source Reasoning, Table Analysis, Graphics Interpretation, and Two-Part Analysis. Because the prompts range from a quick two-statement check to a 350-word integrated scenario, the average of 135 seconds per question is almost useless as a planning number. A working pacing protocol has to start with the section's structural facts and end with the moment a student decides to let an item go.
What the section actually gives you, minute by minute
The Data Insights section of the GMAT Focus is built around 20 items and a 45-minute clock. That produces the widely quoted 2 minutes 15 seconds per item, which I would actively discourage students from treating as a target. Two reasons. First, the five item families do not consume time symmetrically. A two-statement Data Sufficiency item can be dispatched in 60 to 90 seconds by a student who has the stem pattern catalogued, while an integrated Multi-Source Reasoning prompt with three tabs and a layered question routinely eats 3 to 4 minutes. Second, the test is adaptive, so the second batch of ten items is calibrated to the way you handled the first ten. Running out of clock at item 18 costs you the easiest two items on the test, not the hardest.
In practical terms I ask students to plan the section as a budget rather than a pace. The 45 minutes becomes 40 minutes of work plus a 5-minute safety margin, with the safety margin itself split into two reserves: a 2-minute late-section reserve for items 16 through 20, and a 3-minute end-of-section reserve that you only spend when the late reserve has been exhausted. That single reframe — "this is a budget, not a pace" — changes how the section feels, because it gives the student a place to put recovered time when a Data Sufficiency item falls in 70 seconds and a place to draw on when a Two-Part Analysis runs hot.
Why the average is a trap
The 2:15 average is a retrospective number, not a prescriptive one. It is what your watch will read if the section went well. It is also what your watch will read if the section went badly and you skipped the last three items. The two outcomes are not equivalent, but the average hides the difference. A pacing protocol has to behave well in both cases, and that means accepting that the last three items of the section are the most expensive items on the test in terms of scoring efficiency. A student who reaches item 18 with four minutes left and a partially built Table Analysis answer is, in my experience, a student who has spent those four minutes badly. The right move at that point is rarely to push the Table Analysis through. It is to triage item 18 as a guess, finish 19 and 20 with whatever time the rest of the section returns, and live with the cost.
The five item families, ranked by per-item time cost
Before a student can build a per-item time box, they need a realistic mental model of what each family costs. I rank the five families by typical per-item time on a prepared student, not on a novice, because pacing protocols are designed for prepared students, and novices have a different problem (they need to learn the families before they can pace them).
| Item family | Typical time, prepared student | Dominant time sink | Pacing implication |
|---|---|---|---|
| Data Sufficiency | 70 to 110 seconds | Re-reading the stem after the answer choices | Strict two-pass: classify, then evaluate |
| Multi-Source Reasoning | 150 to 240 seconds | Switching cost between three tabs | Read question first, then build a fact list |
| Table Analysis | 120 to 180 seconds | Off-by-one column reads | Mark column headers, then re-mark |
| Graphics Interpretation | 120 to 180 seconds | Unit or axis confusion | Underline the units before any math |
| Two-Part Analysis | 150 to 220 seconds | Forgetting the parts must be answered jointly | Treat as one question with two boxes |
These ranges are not promises. A Two-Part Analysis on a clean algebra system can fall inside 110 seconds; a Data Sufficiency item with three nested conditions can run to 140 seconds. The point of the table is not to lock the student into a number per family but to break the assumption that all 20 items are equivalent units. They are not. A pacing protocol that spends 150 seconds on every Data Sufficiency item and 100 seconds on every Two-Part Analysis item is leaking time on roughly half the section.
A two-pass architecture for the whole section
The single most useful pacing structure I teach is a two-pass architecture. Pass 1 covers items 1 through 14 and runs to a hard clock of 32 minutes. Pass 2 covers items 15 through 20 and runs to the section's natural close at 45 minutes. The boundary at item 14 is not magical, but it is convenient: it leaves the last six items, which include the section's hardest material under the adaptive algorithm, in a second pass that the student enters with a clear picture of remaining time.
How to behave inside Pass 1
Pass 1 is where the budget is earned. Three rules govern it. First, no item in Pass 1 is allowed to consume more than 3 minutes of clock. If a student is still reading the third tab of a Multi-Source Reasoning prompt at the 2:40 mark, the item is marked and skipped. Second, every Data Sufficiency item in Pass 1 is treated as a two-pass item internally: a 30-second classification pass that identifies the stem type, followed by a 60 to 80-second evaluation pass. Third, the student writes down the wall-clock time at the end of item 5, item 10, and item 14. Those three timestamps are the section's pacing dashboard. If the item 10 timestamp is later than 20 minutes, the student is in deficit and needs to start skipping aggressively. If the item 14 timestamp is earlier than 32 minutes, the student has a surplus to deploy in Pass 2.
How to behave inside Pass 2
Pass 2 is where the budget is spent. The student enters Pass 2 with a known clock, a known position, and a known level of difficulty on the test. The two most common failure modes here are: pushing too hard on the first one or two items of Pass 2 and burning the late reserve; or, conversely, treating the last six items as a slow read because the clock feels comfortable. A useful rule of thumb: the items in Pass 2 are worth the same per-item time as Pass 1, but they are also the items most likely to overrun, so the student should pre-commit to a 4-minute per-item ceiling and a guess threshold at 4:30. Items that breach 4:30 in Pass 2 are guessed, marked, and moved past. The late reserve is reserved for genuine emergencies, not for ordinary overruns.
Per-item time boxes that actually fit the family
A per-item time box is only useful if the student has a believable internal model of what the family costs. Below is the working set I give to students at the start of a Data Insights cycle, calibrated for a candidate aiming at DI 78 or higher.