The DILR Information Map: Separate Facts, Restrictions and Consequences Before You Solve
Most CAT DILR sets bundle Facts, Restrictions, and unstated Consequences together, and aspirants often mistake a derived Consequence for a given Fact. This guide introduces the FRC Map for sorting the prompt before solving, with worked examples and a practice plan.

The DILR Information Map: Separate Facts, Restrictions and Consequences Before You Solve
Picture a DILR prompt: "there are 5 boxes," "no two adjacent boxes share a color," and "Box 3 must be blue." The first sentence is a Fact. The second is a Restriction. The third, once you work through the other clues, might turn out to be a Consequence you derived, not something the prompt actually stated. Most aspirants read all three the same way and start placing values immediately. That is where a CAT DILR information map earns its keep: a simple habit of sorting every prompt sentence into Facts, Restrictions, or Consequences before you touch a single value, so an assumption never masquerades as a given.
- Most DILR prompts mix three kinds of information, Facts, Restrictions, and Consequences, and reading them the same way causes wasted re-reads mid-solve.
- The CAT DILR information map, or FRC Map, sorts every prompt sentence into one of these three lanes before you place a single value.
- Mistaking a Consequence for a Fact is the single most common categorization error, and it causes cascading placement errors once the assumption breaks.
- Sorting a prompt this way typically adds under 90 seconds to your read but removes minutes of confused re-checking later in the set.
- Only Facts and Restrictions should be used to start solving; Consequences get derived and labeled as you go, never assumed upfront.
This guide is for CAT aspirants who read a DILR prompt once, start placing values immediately, then stall and reread the same paragraph to figure out what they missed. If that's happened more than once this month, the fix is usually in how you sorted the prompt, not in your logic.
What Is the CAT DILR Information Map?
A CAT DILR information map is a pre-solving habit: sort every sentence in a set's prompt into Facts, Restrictions, or Consequences before placing a single value. Most 4-question DILR sets bundle direct statements with limiting conditions and unstated implications in the same paragraph, and untangling them first prevents wasted re-reads mid-solve.
We call this the FRC Map: Facts, Restrictions, Consequences. Each lane has a one-word test. Facts are Given, stated outright with no interpretation needed. Restrictions are Bound, they narrow which arrangements are even possible. Consequences are Forced, they only exist once you combine a Fact with a Restriction and follow the logic through.
The FRC Map: Given. Bound. Forced.
- Facts (Given). Direct statements from the prompt, for example "there are 5 boxes." No inference required, just read and record.
- Restrictions (Bound). Conditions that limit which arrangements are possible, for example "no two adjacent boxes share a color." They shrink the solution space without stating a specific answer.
- Consequences (Forced). Outcomes forced once you combine Facts and Restrictions, for example "Box 3 must be blue." Never stated outright, always derived, and always labeled as derived once you find them.
Aspirants who skip this sorting step tend to solve well until an early guess turns out wrong, then lose several minutes as they rebuild the grid from scratch. Our companion piece on why most DILR sets feel impossible covers the reading habits that usually cause that first wrong guess.
How Do You Separate Facts From Restrictions?
Separating Facts from Restrictions comes down to one test: does the sentence hand you a specific value, or does it narrow which values are allowed? A DILR prompt stating "5 people sit in a row" is a Fact. A prompt adding "the tallest person does not sit at either end" is a Restriction on that Fact.
Spotting a Fact
Facts read like simple statements: counts, categories, and names. "There are 4 teams," "each team plays 3 matches," or "the colors used are red, blue, and green" are all Facts. Write these down first, exactly as given, since Facts rarely need interpretation.
Spotting a Restriction
Restrictions read like conditions: words such as "only if," "unless," "cannot," "at most," and "immediately after" are common signals. A Restriction never hands you a placement outright. It just narrows which placements remain possible once you test combinations.
Take a set assigning 5 delivery slots to 5 vendors. "There are 5 vendors and 5 slots" is a Fact. "Vendor C's slot is not adjacent to Vendor A's" is a Restriction. Neither tells you which slot Vendor C actually gets, that has to be worked out, which is exactly what makes it a Consequence once you find it.
| Signal | Usually a Fact | Usually a Restriction |
|---|---|---|
| Phrasing | States a count, name, or category directly | Uses conditional words like "unless," "only if," "cannot" |
| What it gives | A specific value or list of values | A rule that narrows possible combinations |
| Where it sits | Usually the opening lines of the prompt | Usually the middle clauses, often joined with "and" |
Why Does Mistaking a Consequence for a Fact Wreck Your Solve?
A Consequence is anything forced once you combine a Fact with a Restriction, and it is never stated outright in the prompt. Treating a Consequence as a Fact means trusting a derived value as if it were given, and if that derivation was wrong, every placement built on it fails too.
Consequences only appear after you actively combine two or more prompt statements. "Box 3 must be blue" becomes true only once you cross-check the color Restriction against a Fact about how many colors exist. Until you have done that cross-check, it is not information you possess, it is a placement you have not made yet.
Deriving a Consequence Correctly
Work only from confirmed Facts and Restrictions first. Once two of them combine to force a single outcome, write it down in a visibly different way, a circled entry, a different pen color, or a small "D" marker, so it never gets mistaken for something the prompt handed you directly.
- Confirm it using at least one Fact and one Restriction together, not a hunch.
- Mark it visibly, a circled entry, a different color, or a small "D" beside the value.
- Re-check it first if any later clue seems to contradict your grid.
Why the Mix-Up Cascades
So why does this one mix-up cause so much damage? A wrongly labeled Consequence behaves like a false Fact for every question that follows. If question 2 assumes Box 3 is blue and that placement was actually a shaky derivation, questions 3 and 4 inherit the same error, and an aspirant often does not realize the source until they recheck the entire grid.
Back to the box-and-color example: once you confirm 5 boxes, 3 colors, and the no-adjacent-repeat Restriction, you might find only one color fits Box 3. That is a Consequence, not a Fact. If a later clue seems to contradict it, the Consequence is what you re-examine first, not the original Facts.
Build Your Full CAT Preparation Plan
The FRC Map fixes one habit inside DILR. A complete CAT preparation plan applies the same rigor across QA and VARC too.
Explore CAT Preparation ResourcesCommon Mistakes That Undo the Information Map
Even aspirants who understand all three lanes slip back into old habits once the DILR clock is visible. The table below lines up the panic move against the pro move for mistakes that show up most often in the middle of a timed set.
| Panic Move | Pro Move |
|---|---|
| Starting to place values before finishing the sort | Reading the entire prompt once, sorting all three lanes first |
| Treating an inferred value as if it were stated | Marking every derived Consequence visibly different from a Fact |
| Rereading the whole prompt when a placement contradicts itself | Re-checking only the Consequences built on the broken assumption |
| Skipping Restrictions because they don't hand you a value directly | Recording Restrictions with the same care as Facts, since they shrink the search space |
| Assuming the same sorting speed works for every set type | Adjusting sort time slightly for denser, clue-heavy prompts |
Most of these mistakes share a root cause: solving speed getting prioritized over sorting accuracy in the first two minutes of a set. Slowing down for that initial sort almost always pays for itself before the second question, since every later placement depends on the first few Consequences being right.
For a system to log Facts and Restrictions the same way on every set, see our guide on how to build your DILR notebook. A consistent notebook format makes the sort faster each time you repeat it.
How Should You Practice the FRC Map Before Exam Day?
Practicing the FRC Map means drilling the sort as its own skill before combining it with full solving. A short daily routine across old DILR sets builds the habit until sorting Facts, Restrictions, and Consequences happens automatically, without slowing down your actual solve time.
| Day | Drill | What to Track |
|---|---|---|
| Day 1-2 | Sort 3 old DILR prompts into F/R/C columns, untimed, no solving | Can you sort a full prompt in under 2 minutes? |
| Day 3-4 | Sort, then solve, marking each Consequence with a "D" as you derive it | How many Consequences you mislabel as Facts |
| Day 5-6 | Redo 2 sets you got wrong earlier, checking if the miss traces to a mislabeled Consequence | Percentage of past errors that were sorting errors |
| Day 7 | 1 full DILR section, 40 minutes, sort-first on every set | Attempts and accuracy versus your last untimed baseline |
Build this sorting drill into your CAT 2026 study planner as a standing 15-minute daily block, separate from full mock attempts. Aspirants who track sorting accuracy on its own, not just overall DILR score, tend to catch mislabeled Consequences weeks before they would otherwise show up as a wrong answer on a mock.
DILR sets that feel impossible are often just sets read the wrong way. Once Facts, Restrictions, and Consequences get sorted before solving starts, the same prompt reads as three short, manageable lists instead of one dense paragraph. Widen the lens with our full library of CAT preparation guides covering QA and VARC as well.
The FRC Map, Recapped
- Facts (Given): read and record, no interpretation needed
- Restrictions (Bound): narrow the possibilities, recorded with equal care
- Consequences (Forced): derived, never assumed, always marked as derived
Not Sure Where Your DILR Accuracy Really Stands?
A short strategy call maps your current DILR accuracy, your target percentile, and the fastest habit to fix first.
Get Your Free CAT 2026 Strategy CallFrequently Asked Questions
How do I know if a sentence in a DILR prompt is a Fact or a Restriction?
A Fact states something directly, for example there are 5 boxes. A Restriction limits how Facts can combine, for example no two adjacent boxes share a color. Ask whether the sentence gives information or narrows possibilities: Facts give, Restrictions narrow.
What is the most common mistake when separating facts from consequences in DILR sets?
Aspirants most often treat a Consequence as if it were a Fact, assuming something was stated when it was actually derived a few steps earlier. Once that assumption turns out wrong, every placement built on top of it collapses, and that forces a slow restart mid-solve.
Does building an information map before solving cost time in the 40-minute DILR section?
No, it saves time. Sorting a prompt into Facts, Restrictions, and Consequences usually takes 60 to 90 seconds and prevents the costlier habit of re-reading the entire prompt mid-solve after an early assumption turns out to be wrong later in the set.
Can the CAT DILR information map be used on every set type, including ones that aren't grid or seating based?
Yes. Every DILR set, whether it is a grid, a seating arrangement, a network, or a data table, states some information outright, restricts other parts through conditions, and leaves the rest to be derived. The three-lane sort applies regardless of set format.
Solve real CAT DILR sets timed
Hand-picked LR puzzles and DI caselets with timer + solution breakdown.