The diagnostic

Sit a full Bluebook practice test before you read another word of this course.

#Why first, and why real conditions

A diagnostic taken comfortably — at your desk, pausing, checking one answer — produces a number that tells you nothing, because it measures a situation you'll never be in. The point isn't the score. It's the shape: which domains leak points, whether you run out of time, whether accuracy falls off a cliff in the last ten questions.

So: one sitting, both sections, the 10-minute break, phone in another room, no pausing. If you can, do it at the time of day your real test is scheduled.

#What to record afterwards

Bluebook gives you a score and a breakdown. Go past it. For every question you got wrong, write one line:

Q14 RW · Boundaries · picked C · didn't check what came after the comma
Q31 M  · Advanced  · picked A · solved for x, question asked for 2x

Three fields: domain, what you picked, why. The third is the only one that's hard and the only one that's worth anything.

Then sort the "why" column. Almost everyone finds their misses collapse into four or five recurring reasons — not thirty separate gaps. Those four or five reasons are your course.

#Reading the shape

• Accuracy falls in the last third of a module → a timing problem, not a content problem. Go to The per-question budget.
• One domain is far below the others → a content problem. Start with that folder.
• Misses are spread evenly and you finished with time to spare → a method problem. You're reading the answers before you've decided what the question wants; the domain lessons fix this.
• Module 2 felt easy → you were routed to the easier form. That's information, and it's the most important thing the diagnostic can tell you.

#How often to repeat

Every two to three weeks, not more. A practice test is a measurement, and measuring more often than you can change anything just eats the finite supply of real practice tests. There are only so many; spend them deliberately.