LSAT Logic Games Minimum Maximum Questions

Minimum and maximum questions test your ability to find the absolute boundaries of what is possible within a game’s rules. They are among the most common and often most challenging question types in the Logic Games section, directly rewarding the quality of your initial diagram and the depth of your deductions. Mastering these questions is crucial because they frequently appear in the later, higher-difficulty questions of a game, where points are won or lost.

Core Concept: Understanding What Is Being Asked

A minimum/maximum question asks for the least or greatest number of times a particular condition can occur. Common phrasings include: "What is the minimum number of spaces that must be between X and Y?" or "What is the maximum number of contestants who could be selected?" The critical first step is to interpret the question correctly. You are not looking for a typical number or a common arrangement; you are looking for the extreme edge of what the rules allow.

For example, if a game involves assigning seven workshops to days Monday through Friday, a question might ask, "What is the maximum number of workshops that could be scheduled for Tuesday?" You must push the scenario to its limit, cramming as many workshops into Tuesday as possible without violating a single rule. This often requires a different mode of thinking than sequencing or grouping questions, as you are actively stress-testing your diagram to find its breaking point.

Strategy 1: Leverage Prior Deductions and Master Diagrams

Your success with minimum/maximum questions is almost entirely dependent on the work you do before you reach them. A well-crafted master diagram that incorporates all initial deductions is your most powerful tool. These questions reward a complete understanding of how rules interact to constrain possibilities.

Before attacking the question, review what you already know is fixed. Are any entities locked into specific positions? Are there unavoidable gaps or blocks? For a "minimum" question, these fixed constraints often force a certain number of events to occur. For a "maximum" question, these same constraints prevent you from adding more. For instance, if a rule states, "K is inspected at some time before L, and L is inspected at some time before M," you have a fixed sequence block: K - L - M. This block inherently takes up three slots. If the question asks for the minimum number of inspections before M, the answer is at least 2 (K and L), because the rules make that unavoidable.

Strategy 2: Test Extreme Scenarios Systematically

When prior deductions don't directly yield an answer, you must engage in targeted experimentation. Testing extreme scenarios means constructing a hypothetical arrangement that pushes the variable in question to its limit. Work directly on your diagram or a quick sketch.

• For MAXIMUM questions: Try to place the target entity everywhere it could possibly go. Add it to groups, put it in sequences, and fill slots with it. As you do this, you will hit a rule that stops you. The point just before that rule is broken is your maximum.
• For MINIMUM questions: Try to exclude the target entity as much as possible. Keep it out of groups, delay it in sequences, and generally shunt it aside. You will eventually find a rule that forces it to be included. The point where it becomes unavoidable is your minimum.

Always test systematically. If you're looking for a maximum number of entities in a group, add them one by one, checking all rules after each addition. This prevents careless errors.

Strategy 3: Process of Elimination with Falsification

For these questions, systematically eliminating impossible placements is often faster than finding the correct number directly, especially when the answers are simple integers (e.g., 1, 2, 3, 4, 5). Use the answer choices to guide your testing.

Take the answer choice that seems most extreme (often the highest number for a maximum, or the lowest for a minimum) and try to make it work. If you can construct a valid scenario that fits that number, you have found your answer for a maximum question. For a minimum question, if you can construct a valid scenario with that low number, you must then check the next lowest number to see if it's also possible. Your goal is to find the smallest number that is still possible.

For example, if a minimum question has choices 1, 2, 3, and 4, start by testing if 1 is possible. If you can make a valid scenario with 1, the answer is 1. If 1 is impossible, test 2. If you can make a scenario with 2, then the answer is 2, because you have proven 1 is impossible and 2 is possible. This method turns abstract reasoning into concrete, manageable tasks.

Common Pitfalls

Pitfall 1: Confusing "Could Be" with "Must Be." These questions almost always ask "What is the maximum number that could be..." or "the minimum number that must be..." These are fundamentally different. "Could be" asks for a possibility—you only need to find one valid scenario that achieves that number. "Must be" asks for a certainty—you must prove that number is true in every possible valid scenario. Failing to distinguish these will lead you to pick a possible number when the question demands a necessary one, or vice versa.

Pitfall 2: Forgetting a Rule Under Pressure. When pushing for an extreme, it's easy to become so focused on the target variable that you overlook a basic rule from the setup. You might succeed in placing six items on Tuesday but violate a rule that says "Item A and Item B cannot be on the same day." Always perform a final rule check on your extreme scenario. A quick mnemonic like "BLEND" (Blocks, Limitations, Exclusions, Not-blocks, Direct orders) can help you scan all rule types.

Pitfall 3: Stopping Your Search Too Early. You test the number "3" for a maximum and find a valid scenario. You pick it and move on. However, the correct answer might be "4." You didn't test far enough. For maximums, you must test until you find a number that is impossible. The correct answer is the number just before the first impossible one. Conversely, for minimums, the answer is the number just after the last impossible one.

Pitfall 4: Neglecting the Interaction of Multiple Rules. A single rule in isolation might suggest a maximum of 4. But a second, unrelated rule might indirectly lower that maximum to 3. The real constraint often emerges from the interaction between rules. Always consider the system as a whole. If your extreme scenario feels too easy to build, double-check that you've considered how all rules work together.

Summary

• Minimum/Maximum questions ask for the absolute boundaries of what the game's rules allow, requiring you to think in extremes.
• Your initial deductions and master diagram are the foundation for answering these questions efficiently; thorough setup work pays direct dividends here.
• Employ targeted scenario testing: push for inclusion to find maximums and push for exclusion to find minimums.
• Use the answer choices to guide elimination, testing whether extreme numbers are possible or impossible to zero in on the correct boundary.
• Avoid critical misinterpretations by carefully noting whether the question stem asks for what could be (a possibility) or what must be (a necessity).