Build Your DILR Notebook

Build Your DILR Notebook

The CAT aspirants who improve fastest at DILR are rarely the ones who solve the most sets. Two students can attempt the same number of mocks and end up in very different places, because one of them is extracting a reusable lesson from every set and the other is reviewing each set once and moving on. Sets solved and forgotten do not compound. Sets solved and logged, the set type, the exact mistake, the time spent, the shortcut discovered, build a resource you can return to before every mock. That resource is a DILR notebook, and this guide walks through a specific 4-page structure for building one that actually adds up over months of practice.

This is for CAT aspirants who have already solved hundreds of DILR sets across mocks and sectionals, but do not feel meaningfully faster or more accurate than they were 2 months ago. If every set gets reviewed once and then forgotten, practice volume stops translating into skill, no matter how many mocks get added to the pile.

The 4-Page DILR Notebook System

The 4-Page DILR Notebook is a simple structure for capturing what a timed DILR set actually teaches you, beyond whether you got it right. Each page tracks a different dimension of skill: what kind of set it was, what specifically went wrong, how long it really took, and what technique it revealed. Update all 4 pages after every timed set, not only the ones you get wrong.

Page 1: The Set-Type Library

Every DILR set belongs to a broader structural family, even when the surface story changes. A puzzle about people assigned to hotel rooms and a puzzle about machines assigned to production lines can share the same underlying skeleton: a linear arrangement with a handful of binding constraints. The Set-Type Library exists to make that overlap visible, so you stop treating every new set as a cold start.

For each set, record 3 things: the structural type (linear or circular arrangement, grid or matrix, network or flow diagram, scheduling puzzle, or data table with charts), a one-line note on the constraint or clue that gave you the fastest entry point, and the source, meaning the mock name and set number. Keep entries short. The library should be scannable in 2 minutes before a mock, not read like a textbook.

Illustrative entry: Type: scheduling puzzle, 5 events across 3 days. Opening move: started from the event with only 1 valid day, not the event mentioned first in the passage. Solved in under 9 minutes once I stopped reading sets in the printed order.

Pairing this page with a deliberate set-selection approach, like the SCAN Method covered in our guide on choosing the right DILR sets, sharpens which sets you attempt inside the fixed 40-minute section.

After 15 or 20 entries, patterns become obvious. Perhaps 3 different network diagram sets all opened faster once you identified the node with the highest degree first. That is not something you would notice from a single set. It only becomes visible once entries pile up in one place, which is what separates this page from an ordinary post-mock review.

Page 2: The Mistake Log

Marking a set wrong tells you almost nothing on its own. Wrong because you misread a constraint and wrong because you built the wrong skeleton from the start point to 2 completely different fixes. The Mistake Log exists to capture the failure mode itself, since that is the only version of a mistake you can actually train against.

Log the failure as one of 5 categories: misread constraint, such as missing a word like "at least" or "never"; wrong skeleton, where the table or diagram could not hold all the clues; ran out of time, where the approach was right but the set was never finished; arithmetic slip, where the logic was correct but a number was not; and missed case, where 1 valid arrangement was found when 2 existed.

Illustrative entry: CAT mock 4, Set 3, grid puzzle. Failure: missed case. Assumed the fourth slot was fixed once 3 were placed, but a second valid grid existed. Lost the full set. Fix: check whether remaining slots are actually forced before assuming they are.

If wrong skeleton shows up often in your log, it is worth revisiting how you approach the first 2 minutes of a set. Our guide on why DILR sets feel impossible walks through the FAST Start Method for exactly that moment.

Once 10 or more entries accumulate, one failure mode usually dominates. Some aspirants misread constraints repeatedly under time pressure. Others consistently miss cases in grid puzzles. That single named pattern is far easier to correct over the next few mocks than a vague sense of being more careful.

Page 3: The Time Log

Most DILR time advice is generic: do not spend more than 10 to 12 minutes on a set. The Time Log replaces that generic number with your own actual data, tracked against set type and difficulty, inside the fixed 40-minute DILR sectional window that cannot borrow time from VARC or QA.

After every set, log 4 fields: set type, your estimated difficulty (easy, medium, or hard), planned time, and actual time taken. Log this even for sets you abandoned, since an abandoned set often reveals more about misjudged difficulty than a set you finished.

Illustrative entry: Type: scheduling puzzle, difficulty: medium, planned: 8 minutes, actual: 11.5 minutes. Third scheduling puzzle this month running over by 3 to 4 minutes.

A single overrun means nothing on its own. A pattern across 8 or 10 scheduling puzzles overrunning by roughly the same margin means you have a calibration problem, not a bad-luck problem, and you can now plan for it directly instead of hoping it improves by itself.

Page 4: The Pattern Bank

The Pattern Bank is where technique actually lives. Every DILR set you solve teaches at least 1 small trick: a shortcut for narrowing possibilities, or a faster way to read a chart. Most of these get discovered once, used for that single set, and never written down anywhere.

Write each pattern in your own words, as a rule you would say to yourself mid-set, not as a textbook definition. Group entries loosely by set type so you can scan the relevant ones in the last few minutes before a mock starts.

Illustrative entries:

• When 3 people share exactly 1 attribute in an arrangement puzzle, check that attribute's constraints before anything else. It tends to eliminate half the possibilities in a single step.
• When a data table has a fixed row or column total, use that total to backfill missing cells instead of solving each cell from scratch.

After a few months, the Pattern Bank becomes a personal playbook that beats any generic tips list, because every line in it is something you have already proven works for you, under real timed conditions.

Common Mistakes When Keeping a DILR Notebook

A notebook kept badly is barely better than no notebook at all. The most common failure is rarely laziness. It is a handful of specific habits that quietly drain the notebook of its value. The table below lines up the panic-mode version of each habit against the version that actually compounds.

How to Build the Habit of Using It

The notebook only helps if updating it becomes as automatic as attempting the set itself. A weekly routine, built around when you actually take mocks and sectionals, keeps the habit from quietly lapsing after the first few busy weeks.

This routine works alongside a broader CAT preparation plan, not instead of one. Our full library of CAT preparation resources covers section-wise strategy and timing drills that pair well with a notebook like this one.

The Bottom Line

A DILR notebook is not extra homework bolted onto your mock schedule. It is what turns mock attempts, otherwise disconnected data points, into a single accumulating record of what you know how to do and where you still slip. The 4 pages each track a different axis of that record.

None of this replaces solving DILR sets. It changes what each set is worth. A set logged carefully across all 4 pages teaches more than several sets solved and forgotten, and that gap only widens the closer you get to test day.

The Optima Learn Editorial Team builds CAT preparation content from exam-pattern analysis and Optima Learn's adaptive practice data. This guide is part of our DILR preparation series, focused on turning repeated mock practice into a system you can trust on test day.