## Your Final Weeks of Study, Logical Reasoning Edition

Yesterday, we covered how to brush up on the Reading Comprehension section in the final weeks before the June LSAT. Today, we’ll talk about how to handle the Logical Reasoning section in the coming weeks.

The first thing you’ll notice is that the basic strategy is the same: First, identify weaknesses; then work on your speed and endurance.

## The LSAT 5-Month Study Plan

A few weeks ago, we started a series of posts providing LSAT study plans of varying lengths, using the September 2016 exam as a target. Continuing that series, this post is going to outline a five-month study plan to help you maximize your preparation for the test. As an aside, if you’re not ready to start prepping yet, you don’t need to panic yet. As long as you give yourself at least three months, you should be in an optimal position to succeed.

## The LSAT 6-Month Study Plan

Now that it’s April, the June LSAT is fast approaching. The next test after that in September seems pretty far off. Some students may want to start preparing early, though. Trying to cram all of the material on the LSAT into a few weeks of studying can be very overwhelming. Some prefer to space the process out. For those folks, here is a template to help guide your studying over a six month period.

The June LSAT is far enough away that you can get away with celebrating St. Patrick’s Day and even taking a day off studying if you choose. Tomorrow’s hangover will be but a distant memory come test day. If green beer is your thing (it shouldn’t be), go for it, or spike that kale smoothie if your tastes align more with the health nut set.

## An Introduction to the LSAT

If you’re perusing this blog, there’s a good chance you’re considering law school. Or maybe your heart has been set on law school since you took your first step. Or maybe you’re just doing some research for a friend or relative who may go to law school.

## 5 Quick Tips to Supercharge Your Logical Reasoning Performance

During my time writing for this blog, I’ve repeatedly vented about my hatred for logic games. Fortunately for everyone, I won’t be talking about logic games this week; instead, I get to talk about a section that is near and dear to my heart — logical reasoning — and the dead horse that is my vendetta against logic games will get at least a weeklong reprieve. Without further adieu, here are my five quick tips for upping your logical reasoning score.

## Negate your way to LSAT dominance.

Let’s say I was trying to prove that every time you drink Fireball, you puke. If you wanted to prove the opposite, you’d have to find a way to show that there has not been a single instance in which you both consumed Fireball and vomited. Pretty tough, right? But let’s say that instead, you just wanted to show that it’s not true that you puke EVERY time you have Fireball. You’d just have to show me a single incident in which you had Fireball and didn’t vomit.

## Your February 2016 LSAT Recap

The February LSAT is in the books. Compared to the other LSATs in the year, the February LSAT has an aura of mystery about it. Since the test is undisclosed, no one outside LSAC ever gets to see it, except on test day. This leads to the rumor that the February LSAT is weird or different.

It isn’t.

## Skip smart on LR.

With the February exam so painfully close – ack! – you should now be doing a whole lot of time-pressure practice. But just hurrying isn’t going to get you where you need to be. You have to hurry in a smart fashion.

When I was studying for the LSAT back before the wheel was invented (yes, the crusty psychometricians at LSAC are older than time itself, and so am I), I found myself hitting a ceiling. That ceiling was 168.

## Flawesome!

Flaw Questions are the most common single question type on the LSAT. They also happen to be my favorite question type. I love pointing out people’s flaws, but people don’t always appreciate it. Like this one time, a guy at my house was about to say “glad,” but then changed it to “nice,” and it came out “glice.” I tried to point out the error, but somehow I was the bad guy?