The LSAT plateau is one of the most demoralizing experiences in test prep. You feel like you're working hard, you're clearly putting in the time, and yet your diagnostic scores won't budge. You're stuck at 157. Or 163. Or 168. The number varies, but the feeling is universal: something isn't working, and you don't know what it is.
After working with dozens of students — and having scored a 180 myself — I've found that plateaus almost always come from the same three sources. The good news is that once you identify which one applies to you, the path forward becomes clear.
1. You're practicing the wrong thing
The most common plateau cause: you're drilling speed and volume when you should be drilling understanding. You do 20 Logical Reasoning questions, check your answers, move on. You're learning which answer was right, but not why the wrong answers were wrong.
This matters because the LSAT is a test of structural reasoning. The same logical patterns appear across thousands of questions in slightly different clothes. If you can't articulate exactly what made each wrong answer wrong — not just "it seemed off" but the precise structural reason — you'll keep making the same errors in slightly different disguises.
The fix: slow down dramatically. Take one question at a time. Before looking at the answer, write out what you think the correct answer should look like. Then, for every wrong answer, write one sentence explaining why it fails. This feels painfully slow. It also works.
2. You don't have a real error log
Most students review their mistakes in a general way. They look at the correct answer, think "oh, I see," and move on. This is almost useless for improvement.
What you need is a detailed error log that categorizes not just what you got wrong, but why. Not "I got this Necessary Assumption question wrong" — that's the question type, not the error. The actual error might be: "I confuse necessary conditions with sufficient conditions under time pressure" or "I pick trap answers that are true but don't address the argument's gap."
Once you have 30 or 40 logged errors, patterns emerge. You'll find that 60% of your mistakes come from two or three specific cognitive habits — not from a broad weakness across question types. Now you have a target. You can drill specifically for those patterns instead of doing undifferentiated practice that hits everything equally.
3. You've hit the ceiling of your current approach
Some plateaus aren't about effort or practice volume — they're about method. You learned an approach early on (maybe from a prep course, a book, or YouTube), it got you from 145 to 160, and now it's not taking you further. That doesn't mean the approach was wrong; it means you've extracted what it can give you.
Breaking through usually requires changing how you process the test at a structural level — not just doing more questions, but thinking about the test differently. This is especially true in Logic Games and Reading Comprehension, where students often lock into patterns that work adequately but not exceptionally.
Common signs your method has hit a ceiling:
- You score consistently but can't explain your reasoning on questions you get right
- Under time pressure, your score drops more than 3–4 points
- You find yourself guessing on a question type even though you've "studied" it extensively
What to do next
Diagnose before you prescribe. Most students jump to "I need to do more Logic Games" or "I need to work on Reading Comp" without understanding what's actually limiting them. Spend a week doing nothing but careful review of your last 60–80 practice questions. Build the error log. Find the patterns. Then build a targeted 4–6 week plan around those specific gaps.
If you've already tried this and you're still stuck, it's often a sign that you need outside eyes. A good tutor doesn't just explain questions — they watch how you think through them in real time, identify what you're doing before you get to the wrong answer, and help you rebuild the process at the root.
The plateau isn't a sign that you've hit your ceiling. It's a sign that your current method has hit its ceiling. Those are very different things.