GMAT Focus Table Analysis is the item family inside the Data Insights section that gives candidates a sortable spreadsheet and asks them to extract, sort, filter, or compute across rows and columns. On the GMAT Focus Edition, each Table Analysis item is interactive: the test-taker sees roughly 20–25 rows of structured data and a short prompt, and the on-screen tools allow column sorting, partial-match search, and row selection. The section contributes to a separate 60–90 score band on the enhanced score report, and because every prompt is anchored in real business or research data, the cognitive demand is closer to working-actor judgement than to abstract mathematics. This article walks through the recurring table architectures, the question types, the pacing maths, and the error patterns that most often cost candidates the half-point increments on the band.
What a Table Analysis stimulus actually is
The stimulus is not a passage. It is a working spreadsheet with column headers, units, and roughly 20–25 data rows. The data are drawn from five recurring domains: online retail orders, financial statements or transaction logs, subscription or membership records, university admissions or enrolment data, and healthcare or operational metrics. Reading the full table from top to bottom is a trap. The header row tells you the column architecture, the units, and the sort state of each column (an arrow appears next to a column header when it is sorted ascending or descending), and that is enough orientation to begin triaging the question.
Each row carries enough information to be self-contained, which means that you do not need to read across multiple rows to understand a single record. This is the single biggest cognitive relief the item family offers: you are not synthesising a narrative, you are locating facts under a column header. Practise reading the table the way a database analyst reads a query result — header, then targeted rows.
Two display states matter. The default rendering shows the table with a fixed column order; a small arrow next to a header indicates it is sorted. Candidates can re-sort any column alphabetically or numerically in either direction by clicking the header, and they can perform a partial text match in any column. The interface supports multi-step operations: sort, then filter, then sort again, then identify a target row. The question prompt will sometimes require exactly that sequence.
The five table architectures that recur across items
Almost every Table Analysis stimulus falls into one of five structural shapes, and recognising the shape is half the work because the shape predicts which columns matter and which can be ignored.
- Transaction log shape. A row is a single order, booking, or transaction, and columns include an ID, a date, a category, a customer or vendor code, a quantity, a price, and a status. The question is almost always about filtering by date range or status and then aggregating.
- Hierarchical reference shape. A row is a parent record (a customer, a product, a country) with sub-attributes such as region, tier, segment, or sign-up channel. The question is about selecting rows whose attributes match a multi-criteria filter.
- Time-series cross-section shape. Columns are time periods (months, quarters, years) and rows are entities (products, regions, accounts). The question is about ranking, change between columns, or extreme values in a column.
- Two-entity join shape. Two stacked sub-tables share a key column, and the question requires linking row A in the top block to row B in the bottom block. Sorts and filters are usually applied to one block first.
- Wide attribute shape. Each row has 8–10 columns of mixed categorical and numerical attributes, and the question is an exclusion query (which rows fail at least one of N criteria).
Once a candidate has classified the architecture, the search and sort moves are largely pre-determined. A transaction log almost always wants a date range sort and a status filter; a time-series cross-section almost always wants a column sort to find the top or bottom entry; a wide attribute shape almost always wants partial-text filters in two or more categorical columns. Train yourself to label the architecture inside the first 15 seconds.
The four question types, with worked examples
The prompt families cluster into four types, and each type maps to a specific sequence of interface actions.
Type 1: locate a specific row
The question names a unique entity (an order number, a customer name, a product code) and asks for an attribute value. The fastest path is a partial-text filter on the identifier column, which collapses the 20–25 rows to one or two, then a visual read of the target column. In practice this is the lowest-cognitive-load item in the section, and candidates should finish it in well under two minutes.
Type 2: rank and select
The question asks which of several named entities has the highest or lowest value in a particular column, or asks the candidate to order a list of named entities by a chosen metric. The move is to filter on the named entities (which usually leaves 4–6 rows), then sort the remaining set by the target column, then read the ordered list. The most common error here is forgetting that the sort direction must match the question's superlative.
Type 3: aggregate over a filtered subset
The question asks for a sum, average, count, or ratio over rows that meet two or three criteria. The efficient sequence is to apply the filters in order of selectivity (most restrictive first), confirm the row count visually, and then read the relevant values column by column. A frequent mistake is to filter on a categorical column that has multiple plausible matches; always re-read the prompt after the first filter to confirm the row set is what the question requires.
Type 4: comparative or change-based
The question asks for a difference, ratio, or percentage change between two values in the same row, or between the same metric in two time-period columns across all rows. These items look arithmetic-heavy, but the cognitive load lives in the row identification, not the computation. Filter, sort, identify the two values, then compute on paper or in your head.
A 2-minute workflow for the section
Top scorers do not read the table, then read the question, then act. They interleave. Here is a workflow that has held up across cohorts I have tutored, calibrated to a 2-minute budget per item.
- 0:00–0:10 — read the prompt in full. Note the question type, the named entities, the target column, the direction of the answer (highest, lowest, exclude), and the number of criteria. A candidate who skips this step pays for it in mis-sorting.
- 0:10–0:25 — scan the header row. Identify the column types, the units, and the current sort state. This is the moment to classify the architecture from the list above.
- 0:25–0:40 — apply the first filter. Choose the most selective criterion (a unique identifier, a single category, a narrow date range). Use partial-text match to keep the filter fast.
- 0:40–0:55 — sort the filtered set. Sort the target column in the direction implied by the question. Confirm the row count visually.
- 0:55–1:30 — read and compute. Read the value, perform any arithmetic, and form the answer. For multi-step questions (Type 3 or Type 4), loop back to step 3 with the next criterion.
- 1:30–2:00 — sanity check. Re-read the prompt. Verify the row count, the sort direction, the column being aggregated, and the direction of the answer. Lock it in.
The budget is tight, and most candidates overrun it on the second pass of a Type 3 or Type 4 prompt. A practical rule: if you have not located the answer row by the 1:00 mark, abandon the second filter and guess from a partial read. The expected-value calculus on a 2-minute item with a 5-option multiple choice does not reward exhaustive search.
How Table Analysis differs from Graphics Interpretation
Both item families live in Data Insights, but the cognitive demand is asymmetric. Graphics Interpretation hands you a static chart and a dropdown-based answer mechanic that often requires you to mentally model a ratio. Table Analysis hands you a manipulable spreadsheet and an open-ended numeric or partial-credit answer. The implications for preparation strategy are concrete.
| Dimension | Graphics Interpretation | Table Analysis |
|---|---|---|
| Stimulus control | Static; candidate cannot alter the chart | Interactive; candidate sorts, filters, searches |
| Answer format | Multiple choice (dropdown) | Numeric entry or partial-credit statement |
| Primary skill | Visual estimation and ratio reasoning | Database-style triage and row selection |
| Arithmetic load | Light, often mental | Moderate, often requires written computation |
| Time budget per item | ~2.5 minutes | ~2 minutes |
| Most common error | Misreading the chart's scale or axis | Filtering on the wrong column or sort direction |
Candidates who are strong on Graphics Interpretation often struggle here because they treat the table as a passage to be read. Candidates who are weak on Graphics Interpretation often score well on Table Analysis because the tool-driven interface offloads the visual decoding. Train the two skills with separate drills; do not assume cross-transfer.
Common pitfalls and how to avoid them
After grading several hundred Table Analysis items, the failure modes cluster into a small number of repeatable patterns. Knowing them in advance is a meaningful score protector.
- Sort-direction drift. The question asks for the smallest value; the candidate sorts ascending, then misreads the bottom row as the answer. Habit: before clicking sort, verbalise the direction implied by the question.
- Filter on the wrong column. Two columns have similar-looking categorical values (e.g., 'Region' and 'Country'). The candidate filters on the broader column, gets 12 rows instead of 2, and overruns the budget. Habit: read column headers in full, not by abbreviation.
- Forgetting the sort arrow is sticky. After a sort, a re-filter does not preserve the sort. The candidate re-sorts only on the second or third pass and loses 30 seconds. Habit: re-confirm sort direction after every filter.
- Misreading partial-text match. A partial-text filter on 'North' returns both 'North-East' and 'North-West'. Habit: after a filter, eyeball the row set to confirm the match is exclusive.
- Arithmetic slip on Type 4. The candidate correctly identifies the two values but miscomputes the percentage change. Habit: write the two values down on the notepad before computing; do not compute from memory.
- Over-confidence on Type 1. The candidate spends 30 seconds reading the table before applying the filter. Habit: trust the filter; the table is a database, not a story.
Notice that almost none of these pitfalls are about reading comprehension. They are about workflow discipline. That is the central coaching message for this item family: a candidate who masters the interface, classifies the architecture in 15 seconds, and respects the 2-minute budget will outperform a candidate with stronger raw data literacy who treats the table as a passage.
Preparation strategy: drills that actually transfer
Generic Data Insights practice is insufficient for Table Analysis because the manipulable interface is the skill. Here is a four-week drill plan that mirrors how top-scorer candidates build the workflow above into reflex.
Week one is interface fluency. Spend 30 minutes a day on a real or simulated Table Analysis interface with the goal of completing the sort-filter-read sequence without thinking about the mouse path. Build a personal shortcut for the partial-text filter box, for the sort arrow, and for the row counter. If the platform you are using does not have an authentic interactive engine, build a minimal mock in a spreadsheet: 20 rows, five columns, one filterable text field, and a clickable sort arrow. The goal is to make the moves automatic.
Week two is architecture classification. Pull 20 practice items, time-box yourself to 15 seconds per stimulus, and label each one as transaction log, hierarchical reference, time-series cross-section, two-entity join, or wide attribute. Once you can classify in 15 seconds, the rest of the workflow is pre-loaded. Candidates who reach this milestone report a 20–30 second reduction in time-on-item by the end of the week.
Week three is question-type isolation. Drill each of the four question types separately, 10 items per type, two minutes per item. Time yourself strictly. After each set, review not the answers but the move sequences: did you sort before filtering, did you re-confirm the sort direction, did you write down values for Type 4 items. The review is on process, not on correctness.
Week four is mixed practice under timed conditions. Mix Table Analysis with the other three Data Insights item families in the official 45-minute section ratio and practise the section as a whole. The goal is to internalise when to skip a Table Analysis item and come back to it. A defensible skip rule: if you have spent 2:30 on a single Table Analysis prompt without isolating the answer row, mark it and move on; the expected value of a guess is materially higher than the cost of the overrun on the rest of the section.
Scoring implications on the enhanced score report
Table Analysis items live inside the Data Insights band, which spans 60–90 on the GMAT Focus. Because the band is narrow, every item moves the score in increments that candidates feel acutely. A reliable working number is that 2–3 items in Table Analysis correspond to a one-point move on the band, though the actual mapping is not item-linear. The implication is not to chase a count target but to protect the items you can finish cleanly. A candidate who converts 8 of 10 Table Analysis items reliably is in a stronger position than a candidate who gambles on 9 and converts 7.
The enhanced score report also surfaces per-item timing and difficulty indicators, and Table Analysis items tend to cluster in the medium-difficulty band of Data Insights. That makes the item family a productive place to bank points: medium difficulty with high time-cost, so disciplined candidates who respect the 2-minute workflow can bank the medium items and free up time for the harder Graphics Interpretation and Two-Part Analysis items that follow.
For candidates who are running a multi-attempt preparation strategy, Table Analysis is also the item family where week-over-week improvement is easiest to measure objectively. A candidate who moves from 60% conversion at 3 minutes per item to 85% conversion at 2 minutes per item is clearly trending, and that trend is visible in the per-item timing data on the report. Use it as a leading indicator for section readiness, not just a final score.
Putting it together: a closing checklist
Table Analysis rewards triage. Read the prompt before the table, classify the architecture in 15 seconds, apply the most selective filter first, sort in the direction the question implies, read the value, and lock the answer before the 2-minute mark. Train the interface until the moves are reflex, isolate the four question types in dedicated drills, and then practise mixed sections with a strict skip rule at 2:30. Candidates who build this workflow consistently score in the upper portion of the 60–90 Data Insights band, and the same workflow transfers to consulting case interviews and to any data-heavy professional setting where the underlying skill is the same: locate the right row, fast.
TestPrep İstanbul's Table Analysis diagnostic drill is a natural starting point for candidates building the 2-minute workflow from scratch and for those retakers looking to convert medium-difficulty items into banked points on the Data Insights band.