GMAT Table Analysis: Complete Strategy Guide
Quick Takeaways
- Strategy: Sort first — always. Manual scanning is the slowest and most error-prone approach.
- Format: One table prompt. Three separate True/False statements. No partial credit.
- Process: Re-sort the relevant column for each of the 3 statements independently.
- Trap: Always test ALL rows for a conditional — one counterexample makes the whole statement False.
- Time target: 2 minutes total for all 3 statements, approximately 35 seconds per statement.
What Is Table Analysis?
Table Analysis questions, unique to the GMAT Data Insights section, present you with a sortable spreadsheet-style table and three binary statements. Your task is to evaluate each statement as True or False (or Yes/No, or Inferable/Not Inferable, depending on the specific question framing) based solely on the data in the table. All three statements must be answered correctly to receive credit — there is no partial score.
The table is interactive: you can sort any column in ascending or descending order at will. This sort function is not a convenience feature — it is the central tool around which the entire Table Analysis strategy is built. Students who do not use it systematically average 30–45 additional seconds per statement, which almost guarantees running over the 2-minute time target.
The Sort-First Strategy: Why Scanning Never Works
Manually scanning a 6–10 row table for patterns is slow and unreliable because the human eye does not efficiently compare values across unsorted rows. When a statement asks 'does column A increase as column B increases?', scanning an unsorted table requires tracking two values simultaneously across every row — a process that takes 30–60 seconds and is prone to missed outliers. Sorting column B first reduces the same task to a 10-second left-to-right glance at whether column A values are trending upward.
The fundamental principle: Every statement in a Table Analysis question is designed to be answered efficiently by sorting a specific column. Identifying which column to sort is the analytical work; reading the answer once sorted is trivial. Spend your 35 seconds on column selection, not on scanning.
The 4-Step Process for Every Table Analysis Question
- Orient (15 seconds). Before reading any statements, spend 15 seconds understanding the table structure. What does each column represent? What are the units? Are any columns ratios, percentages, or absolute values? This orientation eliminates unit-confusion errors on the statements that follow.
- Read the statement precisely (5 seconds). Read only the first statement. Identify the key variable or comparison it requires. Underline or note the specific claim.
- Sort the relevant column (5 seconds). Determine which column, sorted in which direction, will most efficiently reveal whether the statement is true. Sort it. For correlation statements, you may need to sort one column and observe another simultaneously.
- Evaluate and record (10–15 seconds). Based on the sorted data, determine the answer. For conditional statements ('all rows where X is true also have Y'), scan all rows meeting condition X — not just the first few. Record your answer and move to the next statement. Re-sort as needed for each new statement.
Statement Types and the Right Sorting Approach for Each
GMAT Table Analysis statements cluster into five recurring types. Recognising the type from the statement's phrasing tells you immediately which column to sort.
| Statement Type | Example Phrasing | Optimal Sorting Approach |
|---|---|---|
| Extremes (highest / lowest) | 'The region with the highest revenue...' | Sort the relevant column descending. The answer is the top row. |
| Median or ranking | 'The median value of column X is greater than Y' | Sort column X ascending. With n rows, the median is the (n+1)/2 th value. |
| Correlation | 'As column A increases, column B generally increases' | Sort column A. Observe column B's trend across the sorted rows. |
| Conditional (all / every / whenever) | 'Every row where X > 5 also has Y > 10' | Sort column X. Identify all rows satisfying the condition. Check column Y for every one of them — not just the first few. |
| Aggregate (sum / average / count) | 'The average of column Z is above 50' | Sort column Z for a rough visual check; use the calculator for precise averages if the values are not round numbers. |
Five Common Traps and How to Avoid Them
- Not re-sorting between statements. The table retains its sort order from the previous statement. If you sorted by Revenue for statement 1, the table is still sorted by Revenue when you read statement 2. Always actively ask whether a new sort is needed before evaluating the next statement.
- Testing only the first few rows of a conditional. When a statement says 'all rows where X is true also satisfy Y', you must check every row where X is true — not just the top two or three. The GMAT regularly places a single counterexample in the fourth or fifth row specifically to catch students who stop checking early.
- Confusing 'must be true' with 'could be true'. These have different logical standards. 'Must be true' requires support from the data for every possible case. 'Could be true' requires only that the data is consistent with the statement — it does not need to be proven. One counterexample kills 'must be true'. 'Could be true' is False only if the data explicitly contradicts it.
- Misreading units. If one column is in millions and another is in thousands, a comparison between them requires unit normalisation. Read column headers carefully during the orientation step.
- Over-relying on the calculator. The DI calculator is available but slow to reach for on straightforward comparisons. Use it for precise aggregate calculations (exact averages of many values) but not for visual-trend or ranking questions where sorting provides the answer directly.
Worked Example: Evaluating Three Statements Against Real Data
The table below presents regional sales data for five business units. Use the 4-step process to evaluate each of the three statements.
| Region | Revenue ($M) | Market Share (%) | YoY Growth (%) | Headcount |
|---|---|---|---|---|
| East | 11.2 | 38 | +18 | 142 |
| North | 8.4 | 28 | +12 | 98 |
| South | 5.9 | 20 | +3 | 74 |
| West | 3.8 | 13 | -7 | 61 |
| Central | 0.4 | 1 | +1 | 12 |
Evaluate these three statements as True or False:
- 'The region with the highest revenue also has the highest market share.' → Sort Revenue descending: East ($11.2M) is #1. Sort Market Share descending: East (38%) is also #1. Both extremes belong to East. True.
- 'Every region that grew year-over-year had a market share above 10%.' → Sort YoY Growth: positive regions are East (+18%), North (+12%), South (+3%), Central (+1%). Now check each region's market share: East 38% ✓, North 28% ✓, South 20% ✓, Central 1% ✗. Central grew but has only 1% market share. A single counterexample makes the universal statement False. (The trap: three of four positive-growth regions have above 10% market share — checking only East, North, and South would produce the wrong answer.)
- 'The median revenue across all five regions is greater than $5M.' → Sort Revenue ascending: Central $0.4M, West $3.8M, South $5.9M, North $8.4M, East $11.2M. Five data points — median is the 3rd value = South at $5.9M. $5.9M > $5M. True.
Key lesson from statement 2: The Central region — the smallest, easiest to overlook row — is the counterexample that makes the statement False. The GMAT consistently places counterexamples in the least prominent rows. Never stop checking after the first few rows of a conditional statement.
Time Management for Table Analysis
Table Analysis questions should take approximately 2 minutes for all three statements combined — roughly 15 seconds on orientation and 35–40 seconds per statement. This is achievable if you use the sort function for every statement. Students who scan instead of sorting typically spend 70–90 seconds on statements that should take 35 seconds, often running over 3 minutes on a single question.
| Time | Activity |
|---|---|
| 0:00 – 0:15 | Orient — read column headers, understand units, note what data is available. |
| 0:15 – 0:50 | Statement 1 — read, identify column to sort, sort it, evaluate. |
| 0:50 – 1:25 | Statement 2 — re-read statement, determine if new sort needed, sort, evaluate. |
| 1:25 – 2:00 | Statement 3 — same process. Final 10 seconds for any uncertain statement. |
The most effective practice for Table Analysis uses a live interactive sortable interface rather than static table screenshots. The physical act of reaching for the sort column and executing it is a separate skill from the analytical judgment of which column to sort — and it degrades under exam pressure if it has not been practised. OpenPrep's Table Analysis questions use a fully interactive sortable table that mirrors the exact test interface, so the sort function is already muscle memory before test day.
Error tracking for TA: Table Analysis errors cluster into two categories: analytical errors (choosing the wrong column to sort, failing to test all rows of a conditional) and interface errors (forgetting to re-sort, misreading a column header). These require different remediation. Analytical errors need more practice with statement-type recognition. Interface errors need more practice with live sortable tables under time pressure.