Table Analysis: SORT Before You Think
Picture it. It is 9:40 on a Tuesday night. You worked a full day, you put the kids to bed, and now you are staring at a table with eight rows and five columns. The first statement asks about the median. So you start running your finger down the screen, hunting for the middle number, losing your place, starting over. Two minutes later you have an answer you only half trust.
Here is my verdict: that is NOT a math problem. That is a sorting problem you chose to solve by hand. The test hands you a sort button and most people never touch it.
What Table Analysis actually is
Integrated Reasoning (IR) is the first of the three sections on the Executive Assessment. You get 12 questions in 30 minutes. Table Analysis is one of its question types. You see a table of data, and above it is a menu that lets you sort the table by any column. Sorting just means putting the rows in order, smallest to largest, by the column you pick. Below the table you get a few statements, and for each one you make a two-way call, such as Yes or No, or True or False.
Now do the math on the clock. 30 minutes for 12 questions is 2.5 minutes per question on average. I'll bet your last Table Analysis took MORE than that. Go check your notes. And if you don't have notes, that is its own problem, and we'll get to it.
Also remember how the score works. Each section is scored 0 to 20, and all three count the same toward your 100 to 200 total. IR is worth exactly as much as Quant. That is why Integrated Reasoning is NOT the warm-up act, no matter how many people treat it like one. You can confirm the structure on GMAC's assessment structure page.
The one rule: find the column, then sort
Every Table Analysis statement leans on one column more than the others. Words like highest, lowest, median, fewer than and at least are flags. Each one is telling you which column to put in order. Sort that column FIRST, then think. When the rows are in order, the highest is on top or bottom, the median sits in the middle, and a cutoff like "fewer than 13" becomes a clean line in the list.
Stop reading for a second. Think about the last time you searched a messy spreadsheet at work. Did you scan 200 rows by eye, or did you click the column header? You clicked. You already know how to do this. You just forget to do it when the timer is running.
Why people skip the sort
It feels slower. Clicking a menu feels like a detour when you can "just look." But looking is where the time goes. With an unsorted table, every statement means scanning every row, and every scan is a chance to skip one. A sort costs you a click. A missed row costs you the statement.
The same idea runs through the rest of IR. On charts, you read the axes first before you judge a single bar. On Multi-Source Reasoning, you stop reading every tab like a novel. The pattern is always the same: organize the information, THEN think about it.
The mistakes I see every week
Scanning an unsorted table by eye. You trust your eyes over the tool, and your eyes skip a row.
INSTEAD: Before you read a statement closely, underline its flag word (highest, median, fewer than) and sort by that column.
Sorting the wrong column. The statement says "stores with fewer than 13 employees have high ratings," so you sort by Rating. Now the group you need is scattered.
INSTEAD: Sort by the column that DEFINES the group. The group here is "fewer than 13 employees," so sort by Employees, then check ratings inside that group.
Expecting the sort to do math it can't do. If a statement asks about revenue per employee, no column holds that number. Sorting by Revenue will mislead you.
INSTEAD: Recognize when you need a new number. Write the few values you need on paper, estimate, and only work exact numbers when the answer is close.
Ignoring the boundary words. "More than" and "at least" are not the same. "Above 4.3" and "4.3 or higher" are not the same. One row sitting right on the line decides the statement.
INSTEAD: Translate every cutoff into a symbol on your paper (<, ≤, >, ≥) before you look at the data.
Doing it all in your head. You think you're "smart enough" to hold eight numbers in memory at 9:40 at night. You aren't, and neither am I.
INSTEAD: Note the store letters and values that matter for each statement. A line like "D B F: 4.4 4.6 4.8, all > 4.3, Y" takes ten seconds and kills the silly mistake.
What you should ask yourself
What do you want MORE: to feel fast because you skipped a click, or to BE fast because the table did the hunting for you? Sorting is not a crutch. It is the tool the question writers put on the screen. Using it is not cheating. Ignoring it is just pride.
And don't get too down on yourself if you've been eyeballing tables for weeks. This is one of the easiest habits on the whole test to fix, because the test is predictable. Every Table Analysis has a sort menu. Every one has flag words. You can train the move until it is automatic.
Your challenge for today
Pull up three Table Analysis questions you've already done. Redo them with one rule: you may not read a statement closely until you have sorted by the column it depends on. Write the flag word, the column you sorted, and your answer on paper for each statement. Time yourself. Then compare that time to your first attempt. If the second run isn't faster AND cleaner, look at your notes and figure out exactly which statement slowed you down and why. "I have no idea" is not an allowed answer.
