How to review LSAT practice tests by question type

Why track LSAT question types?

The current multiple-choice LSAT contains Logical Reasoning and Reading Comprehension sections. Those broad section scores are useful, but they can hide very different problems. Two students with the same Logical Reasoning accuracy may need completely different work if one misses Necessary Assumption questions while the other struggles with Flaw questions.

Question-type tracking converts a vague goal such as “get better at LR” into a testable plan: identify the recurring category, review the reasoning task that category demands, drill it, and check whether accuracy improves on later full tests. LSAC’s official overview describes the current LSAT question formats and sections.

A seven-step practice-test review method

1. Finish under realistic conditions. Keep the timed result separate from any later untimed review.
2. Record every scored question. Include correct answers too; weakness estimates based only on misses are misleading.
3. Separate LR and RC. Do not combine the two sections into one question-type ranking.
4. Group questions by type. Use consistent labels across tests so the same skill is not split into multiple categories.
5. Calculate accuracy with sample size. A 0% result from one attempt is less informative than 55% across twenty attempts.
6. Compare lifetime and recent performance. Your last several tests should reveal whether an old weakness is still current.
7. Choose one or two priorities. Review the underlying method, drill deliberately, then use the next full test as new evidence.

Reviewing Logical Reasoning question types

Logical Reasoning categories describe the job the question asks you to perform. Useful labels commonly include Flaw, Strengthen, Weaken, Necessary Assumption, Sufficient Assumption, Must Be True, Most Strongly Supported, Method of Reasoning, Parallel Reasoning, Principle, and Explain or Resolve.

For each missed or uncertain LR question, write down three things: the task you thought you were performing, the exact reasoning step that failed, and the rule you will apply next time. Then compare that diagnosis with your category-level numbers. A repeated error pattern matters more than a single difficult question.

Track Reading Comprehension separately

Reading Comprehension measures a different set of tasks, so its question types should have their own ranking. Useful categories include Main Point, Primary Purpose, Passage Organization, Detail, Inference, Author’s Attitude, Function, Application, and Comparative Passage questions.

RC review should connect question results back to passage understanding. If Detail accuracy is strong but Passage Organization is weak, rereading individual lines may not fix the real issue. You may need a clearer structural map of each paragraph and the role it plays in the passage.

Use recent and lifetime performance together

Lifetime data gives you stability. Recent data gives you relevance. A category that was weak three months ago may no longer deserve the top spot, while a new timing or comprehension issue can emerge in your latest tests.

A practical approach is to keep all completed tests for long-term context and compare them with approximately the six most recent tests. Sort by the date you took each test, not the date you uploaded it. Give priority to categories that are weak in both views, or that have declined sharply in the recent view.

Common tracking mistakes

• Ranking tiny samples as if they are conclusive. Always display attempts beside accuracy.
• Looking only at wrong answers. You need the denominator to know whether a category is actually weak.
• Combining LR and RC labels. Separate sections make the recommendation understandable.
• Ignoring dates. Upload order should never decide which tests count as recent.
• Trying to fix everything at once. A short priority list produces a clearer study experiment.
• Treating analytics as a score guarantee. Tracking improves the quality of your study decisions; it does not promise a particular result.