Last updated July 07, 2026 · Reviewed by the AnvayaPrep team
Introduction
Table Analysis presents an interactive spreadsheet-like table with 8-15 rows and 4-6 columns of data, accompanied by three true/false statements that the test-taker evaluates by sorting and filtering the data. A dropdown menu above one column allows sorting in ascending or descending order, and each question requires the test-taker to decide which sorting strategy will most efficiently reveal the relevant data.
Topics in this unit include filtering tables and the sorting interface, trend analysis within tables, missing values in tabular data, ranking data, sorting tables strategically, percentages in tables, ratios in tables, table reasoning, numeric interpretation, conditional tables (evaluating statements based on rows that meet specified criteria), and filtering techniques for complex multi-condition statements.
Table Analysis questions make up approximately 15-20% of the Data Insights section and appear in sets of three true/false statements per table. Unlike passive reading questions, Table Analysis requires active interface manipulation: choosing the column to sort, reading the reorganized data, and performing arithmetic to evaluate statements. Students who practice with the actual GMAT interface or simulated interactive tables are measurably faster on test day than those who only study static screenshots.
Learning Objectives
- Identify when a filtering or sorting operation is required to answer a Table Analysis statement efficiently
- Determine the optimal column to sort for each statement within 20-30 seconds, before beginning any calculation
- Execute sorting operations to organize data (ascending or descending) and apply results to verify or refute true/false statements
- Calculate percentages, ratios, differences, and rankings from sorted table data accurately under time pressure
- Evaluate conditional statements (for example, "among rows where column A exceeds X, column B is greater than column C") by first isolating the qualifying rows through sorting
- Identify when a statement can be evaluated without sorting (for example, when the relevant data is visible without reorganization) and skip unnecessary interface steps
- Avoid common table misreading errors: using the wrong column, misidentifying the row with the maximum or minimum value, or performing arithmetic on pre-sorted rather than sorted data
High-Yield Concepts
| Task | Most Efficient Approach | Common Error |
|---|---|---|
| Find the maximum or minimum in a column | Sort that column descending or ascending; the answer is the first or last row | Reading the maximum from an unsorted table by visual scan (error-prone with large tables) |
| Identify top-N rows by a criterion | Sort by the relevant column descending; read the first N rows | Counting rows without sorting, missing ties or misidentifying which row is N-th |
| Evaluate a percentage claim | Sort by the percentage column if it is pre-computed; otherwise sort by the numerator or denominator column | Calculating percentages for all rows instead of only the rows relevant to the statement |
| Evaluate a conditional statement ("Among rows where X > Y, is Z true?") | Sort by X descending to isolate rows where X is largest; mentally filter to those where X > Y; check Z | Not isolating the qualifying subset before evaluating the sub-claim about Z |
| Rank entities by a composite metric | Compute or estimate the composite metric for the top few candidates after sorting by the most dominant variable | Attempting to compute composite metrics for all rows rather than focusing on plausible top candidates |
| Find missing values | Sort by the column with the missing value to group known values and identify gaps | Scanning the unsorted table for missing values, which is slow and error-prone |
Before sorting, read the statement carefully and identify the single most useful column to sort. Choosing the wrong column wastes one of your limited sorting operations and forces you to re-sort. The most useful column is almost always either the variable being ranked, the variable with the conditional criterion, or the variable whose maximum or minimum you need to identify.
A common error is applying a calculation to all rows in the table when the statement specifies a subset. Statements like "Among companies with revenue above $50 million, the profit margin is higher for Company A than Company B" require you to first identify which companies qualify (revenue > $50 million), then compare only those companies' margins. Performing calculations for all rows without the conditional filter leads to evaluating the wrong set of data.
Study Strategy
Practice with interactive interfaces before test day. Table Analysis is the one GMAT question type where interface fluency directly affects speed. Knowing where the dropdown is, how to click ascending versus descending, and how to read the re-sorted table quickly comes from practice, not conceptual study.
For each statement, develop a consistent 3-step process: (1) identify what the statement claims and what data is needed to verify it; (2) decide the optimal sort column and direction; (3) perform the sort, extract the relevant numbers, and determine true or false. This process prevents the common error of jumping to calculations before deciding the right sorting strategy.
Arithmetic fluency in percentages, ratios, and differences is essential because Table Analysis requires these calculations from raw data. Review percent change calculation (new minus old, divided by old) and ratio comparison (cross-multiply to avoid decimal division) so these operations are automatic.
Practice estimating when exact calculations are not needed. If a statement claims "Company A's margin is at least twice Company B's," and after sorting you see Company A's margin is 28% and Company B's is 12%, you can verify 28 > 2 x 12 without a calculator, faster than computing the exact ratio.
Common Mistakes
Sorting the wrong column: Reading the statement and choosing a related column rather than the exact variable the statement requires. Sorting "revenue" when the statement asks about "revenue growth rate" produces a table organized by absolute revenue rather than by growth, which is the relevant criterion.
Forgetting that the sort reorders all rows: After sorting by one column, all rows shift position. Students who try to "remember" a specific row's position from before sorting often look at the wrong row after sorting.
Ignoring ties: When the statement asks for "the highest" value and two rows tie, both rows must satisfy the tie condition. The statement may be false if it implies uniqueness.
Calculating when estimation suffices: For statements with wide margins (Company A's ratio is clearly 3x Company B's from visual inspection), exact calculation wastes time. Estimate quickly and confirm with one mental check.
Missing conditional filters: When a statement says "among rows where column A > threshold," evaluating all rows instead of only the qualifying subset produces incorrect results.
Exam Tips
Scan the table structure first. Before reading any statement, spend 15-20 seconds understanding what the table contains: what are the column labels, what do the rows represent, what units are used? This orientation prevents misidentification of which column is relevant for each statement.
Use the sort dropdown strategically. You can re-sort as many times as needed, but each sort takes 5-10 seconds. Plan which column is most useful for each statement before touching the interface to minimize re-sorting.
For percentage and ratio statements, determine whether the table already contains a pre-computed percentage column or whether you must calculate from raw numerator and denominator columns. If a percentage column exists, sort it directly. If not, sort by the numerator or denominator and estimate the ratio.
True/false guessing heuristic: If the statement makes a very strong claim (every row, always, never), it is slightly more likely to be false; moderate claims (some, most, in general) are more often true. Use this only as a last resort when time is short.
For the third statement in a set, you may have already organized the table usefully from the first two statements. Check whether your current sort order already reveals the relevant information before re-sorting.
The sorting-strategy checklist for Table Analysis: (1) What is the statement claiming? (2) Which column contains the relevant data? (3) Do I need the maximum, minimum, rank, or conditional subset? (4) Sort ascending (for minimum or lowest) or descending (for maximum or highest). (5) Read the relevant rows. (6) Calculate or estimate. (7) Mark True or False.
Sign up free to keep reading
Create a free AnvayaPrep account to finish this GMAT guide on Table Analysis — plus flashcards and practice questions.