GMAT Focus Table Analysis is the item family inside the Data Insights section that rewards a particular kind of literacy: the ability to look at a structured grid of numbers or labels, decide what the question is really asking, and operate on the table without rebuilding it from memory. The format is unfamiliar to many candidates because it sits between the verbal and quantitative halves of the test, but the underlying skill is older than the GMAT itself: disciplined table reading. The Data Insights section contains roughly twenty scored items drawn from five official families, and Table Analysis is one of the two pure-data-literacy families, the other being Graphic Interpretation. A candidate who treats the table as scenery will lose time; a candidate who treats it as a workspace will pick up the points that other test-takers leave behind.
The mechanics are short. A prompt introduces a table with three to five columns and a comparable number of rows, then asks a single multi-part question, usually a two-part or three-part multiple-choice stem, occasionally a single-select statement. The table is sortable, filterable, and clickable on the official platform, which is why preparation strategy for this family is largely about decisions, not about arithmetic. Most candidates reading this will already have the arithmetic; the gap is the decision layer above it. The article that follows breaks that layer into five archetypes, explains the pacing envelope, names the prompt words that change everything, and shows how scoring on Table Analysis interacts with the rest of the Data Insights section.
The five table archetypes you will actually see on test day
Most Table Analysis prompts are not as varied as they feel. In a working set of practice items, the same five shapes keep reappearing, and once you can name the shape you are halfway through the item. Naming is not a gimmick. It tells you which columns matter, which rows to ignore, and whether the answer lives in a single cell or in a comparison between rows. I would group the prompts into five working archetypes, and I would drill each one until the recognition is automatic.
Archetype 1: the maximum-or-minimum hunt
The prompt names a category, asks which row wins, and the table is small enough that you can read it whole. These items look easy and they are easy, but they are the ones that test discipline. Candidates who skim lose them to misaligned columns. The right move is to identify the column, scan the values, and lock the answer before clicking. Do not over-sort; the table is already short.
Archetype 2: the threshold filter
The prompt gives a numeric cut-off and asks how many rows meet it, or which row meets it, or what is true of the rows that meet it. The right tool here is the filter function, not the sort function. Sorting by the relevant column puts the rows in order but does not tell you which cross a threshold. Filtering does. Candidates who sort when they should filter waste ten to fifteen seconds per item, and over a stack of Table Analysis items the cost compounds.
Archetype 3: the rank-order question
The prompt asks for first, second, or third place under some constraint, and the trick is that the constraint forces a secondary sort. A candidate looking only at the primary column will pick the right row only by accident. The working method is to identify the secondary key, sort on it, and then read the ranking on the primary key. Rank-order questions are where a two-step mental model pays off, and they are the items where sorting earns its keep.
Archetype 4: the conditional change
The prompt says, in effect: if a value in the table were changed, what would happen to a downstream answer. These are reasoning items, not retrieval items. The right approach is to identify the dependency chain, simulate the change mentally on the row in question, and answer the conditional without rebuilding the table. Conditional-change items reward candidates who read the table as a model rather than as a picture.
Archetype 5: the comparison pair
The prompt names two rows and asks which is larger, smaller, or different, often on a derived metric that the table does not display. The right move is to find both rows, isolate the relevant columns, and do the small piece of arithmetic the question implies. The arithmetic is rarely harder than subtraction or a ratio, but it must be done on the two rows in question, not on the table as a whole.
Sorting versus filtering: the decision that controls your pacing
The single biggest decision in Table Analysis is whether to sort the table or to filter it, and the wrong choice is the most common reason candidates run out of time on Data Insights. The two tools look interchangeable, and on a small table they behave similarly, but on a busy twelve-row table they are very different operations. Sorting reorganises the table; filtering hides the rows that do not match. The prompt word decides which is correct, and the rule is simple enough to memorise: if the question asks about a single row or the order of rows, sort. If the question asks about which rows meet a condition, filter.
For most candidates, the temptation is to sort first and ask questions later. Sort feels productive. The rows are in a new order, the screen has changed, and the brain registers motion as progress. But sorting costs roughly four to six seconds, and if the prompt is a threshold question, the sort has not removed the rows that fail the threshold. The candidate then has to scan every row again. That is twenty seconds wasted on a fifty-second item, and the GMAT Focus scoring algorithm does not forgive the leak.
Filtering, by contrast, hides the rows that are not relevant, which means the surviving rows are exactly the rows the question is about. On a threshold item, a single filter leaves the candidate with a table that has shrunk from twelve rows to four. Reading the four is faster than reading the twelve, and the chance of selecting the wrong row drops to near zero. The cost of a filter is roughly three seconds, and it pays for itself the moment the prompt mentions a value, a range, or a condition.
There is a third option that the better candidates learn to use: no tool at all. On prompts that name a specific row by index or by label, the candidate should read the table once, identify the row, and answer. Sorting or filtering such a prompt is a form of procrastination. The table already has the answer; the tool only adds noise. Knowing when to do nothing is part of the preparation strategy for this family, and it is the move that separates the 645 scorer from the 755 scorer.
Practical pacing target: aim to spend no more than fifty seconds on a typical Table Analysis item, and no more than seventy on the hardest third. If you find yourself on an item past seventy seconds with no clear path, the right move is to mark the most defensible answer, flag the item, and return after the section. The Data Insights section does not penalise an unanswered item, but it does penalise candidates who let one prompt eat the time that two later prompts needed.
Reading the prompt word: the small vocabulary that changes the answer
Table Analysis prompts are short, usually one or two sentences, and almost every important word is load-bearing. The candidate who treats the prompt as prose loses items to a single word. The candidate who treats the prompt as a list of operations wins them. The vocabulary below is the working set I drill with students, and I would argue that mastering these ten words is more useful than any amount of practice with the table itself.
- Most: a maximum question. Sort descending on the relevant column, read the top row, confirm the answer.
- Least: a minimum question. Sort ascending, read the top row of the new order.
- At least: a threshold filter. The answer is a count of rows that meet or exceed the value, not a single row.
- At most: a threshold filter in the opposite direction. Again, a count, not a single row.
- Which of the following is true: an inference question. The answer is a statement that holds for the table as a whole, not a value from a row.
- If ... were ...: a conditional change. The candidate simulates the change, does not re-sort the table.
- Greater than / less than: a comparison pair. Identify both rows, isolate the columns, do the arithmetic.
- Approximately: a permission slip. The candidate does not need an exact value, only a defensible estimate, which means rough arithmetic is acceptable.
- How many: a count. Filter rather than sort, and read the surviving row count, not the value of any single row.
- Which row: a single-row retrieval. Read the table once, find the row, confirm against the prompt, answer.
The list is short on purpose. The Data Insights section is built on operational vocabulary, and Table Analysis is the most operational of the five families. A candidate who can name the operation in the first three seconds of the prompt is ahead of the candidate who is still parsing the sentence. The parsing happens anyway, but naming the operation makes it visible, and visible processes are faster processes.
Two-part and three-part prompts: how the stem changes the work
Most Table Analysis items are two-part or three-part multiple-choice stems, which means the candidate answers two or three sub-questions about the same table. The structure is efficient: one table, one read, two or three answers. The mistake candidates make is treating each sub-prompt as a separate item, which doubles or triples the table-reading cost. The right approach is to read the table once with the full prompt in mind, identify the columns and rows that the sub-prompts share, and only drill down on the parts of the table that differ between the sub-prompts.
Two-part prompts almost always share a row or a column. The first sub-prompt might ask for the row with the maximum value of column A, and the second might ask for the value of column B in the same row. The candidate who finds the row for sub-prompt one already has the answer to sub-prompt two. The table does not need to be re-read. The eye moves from the row in column A to the same row in column B, and the second answer is a single glance.
Three-part prompts add a third dimension. A common shape is: identify the row that meets condition A, confirm it meets condition B, and select the value of condition C in that row. The candidate should write the row identifier down, mentally, before answering. Writing the identifier prevents the third sub-prompt from drifting to a different row, which is the most common error on three-part items. The error rate on three-part prompts is higher than on two-part prompts not because the items are harder but because candidates lose the row identifier between sub-prompts.