How to Structure Your Case Interview Opening Statement
Master the first 2 minutes of a case interview: clarifying questions, structuring the problem, and opening in a way that signals top-tier quality.
On this page
A strong case interview opening statement shows the interviewer that you understand the client's decision before you start analyzing. McKinsey's interviewing page emphasizes structuring ambiguous challenges; in practice, that means asking only the clarifying questions that affect your approach, restating the objective in one sentence, and presenting a structure that fits the client instead of a memorized template.
This guide gives you the sequence and exact words for the first three minutes, plus a practice loop using Road to Offer structure drills.
Opening statement essentials
- The opening sequence has four parts: listen and note, ask 1 to 2 clarifying questions, restate the objective, present a structured framework.
- The candidate-led format at BCG and Bain weights the opening higher than McKinsey because your structure is the entire 35-minute roadmap.
- Use the BOTM checklist (Business model, Objective, Timeline, Metric of success) to choose clarifying questions that genuinely change your structure.
- Take the full 2 to 3 minutes of silent structure time. A clean structure at 3 minutes beats a half-formed one at 90 seconds.
- End every framework presentation with a stated starting bucket and a hypothesis grounded in a specific detail from the prompt.

The opening statement covers the first three moves: prompt capture, clarification, and structure.
What is a case interview opening statement?
The first 3 to 5 minutes of a case after the prompt. Four sequenced moves that signal how you think before any analysis. Skipping any one creates compounding risk. Management Consulted's case structure guide calls it the first scored moment of the interview.
The four steps in order
Candidates who skip steps 2 or 3 regularly misalign with the case's actual objective and spend 15 minutes solving the wrong problem.
How should you take notes during the prompt?
Two jobs at once: absorb content and capture details on paper. Write down the client, situation, explicit objective, quantitative anchors (revenue, growth, time horizons), and unusual details. Specifics are usually clues. If the interviewer mentions Q3 of last year or "market leader," that affects framing.
What to say when the prompt ends
"Thank you. Let me make sure I captured the key details. I have a couple of clarifying questions before I structure my approach."
This single sentence acknowledges the prompt, signals notes, and previews the next move.
What clarifying questions should you ask?
Ask 1 to 2 questions that genuinely affect your structure. More than 3 sounds like stalling. Asking what the prompt already answered signals you were not listening.
A good question, if answered differently, would change your analytical approach. Use the BOTM checklist:
- Business model: "How does the client generate revenue? Subscription or transaction?"
- Objective: "When you say 'improve profitability,' is the target a specific margin level, or root-cause understanding?"
- Timeline: "Is this a 12-month fix or a longer-term strategic question?"
- Metric of success: "Is this go/no-go, or are they already committed and looking for the best approach?"
Examples for common case types
- Profitability case: "Has the decline developed over 12 months or several years? That changes cyclical vs structural focus."
- Market entry case: "Is the client considering organic growth, acquisition, or both? That changes the scope."
- Growth strategy case: "Are they open to adjacent products, or growing within current lines? That changes share-capture vs portfolio framing."
How do you restate the objective?
One sentence, before structure time. The step takes 15 seconds and protects you from the most expensive error in a case: solving the wrong problem.
Script: "So to confirm: [Client] is facing [situation], and the core question is [explicit objective]. I'm going to take a couple of minutes to structure. Does that sound right?"
The closing question gives the interviewer a clean chance to correct you. Most confirm. Occasionally they add a nuance. Either way, you are protected.
Practice your opening under realistic pressure
Run through the first three minutes of a case with AI feedback on your clarifying questions, structure specificity, and hypothesis logic.
What should you do during silent structure time?
You have 2 to 3 minutes after asking "Could I take a couple of minutes to structure my thinking?" Use it deliberately.
- Identify the case type. Profitability, market entry, market sizing, growth, M&A, pricing, or operations. A starting point, not a finished structure.
- Identify the specific question. Not "this is a profitability case" but "why has EBITDA margin declined 6 points in three years despite revenue growth."
- Design 2 to 4 buckets that cover the key drivers. MECE, hypothesis-informed, and using the language of the actual business.
- Pick a starting bucket and a reason. Grounded in your hypothesis about where the answer most likely lives.
Why generic frameworks fail
A profitability tree for SaaS should look different from one for retail. If your labels read "Revenues / Costs / Market" on every profitability case, that is memorization, not thinking. Use framework names as a starting library, then rewrite the buckets around the business model, objective, and constraint in the prompt.
How do you present the structure?
Four steps, 60 to 90 seconds total:
- Signal: "I've organized my thinking into [number] areas."
- Walk through each bucket: specific label, 2 to 3 sub-elements, one sentence on why it matters here.
- State your starting point: "I'd like to start with [bucket], because given [detail from the prompt], the most likely driver is [hypothesis]."
- Invite the interviewer in: "Does that make sense as a starting point?"
This demonstrates structured thinking, business specificity, and a clear hypothesis.
How does BCG and Bain's candidate-led format change the opening?
Your structure is the roadmap for the full 35-minute conversation. No interviewer question redirects you. A weak opening at BCG or Bain is hard to recover from.
MBB vs Tier 2 opening expectations
The McKinsey Case Interview Guide covers the interviewer-led format in depth. The BCG Case Interview Guide covers the candidate-led version.
What are the most common opening mistakes?
- Skipping clarifying questions. Transfers all problem-definition risk to you.
- Asking too many. More than 3 sounds like stalling.
- Reciting a textbook framework. Identical labels signal memorization.
- No stated starting point. Always end with "I'd like to start with X because..."
- Presenting before ready. A clean structure at 3 minutes beats a half-formed one at 90 seconds.
How do you practice the opening alone?
Write a prompt, set a 3-minute timer, draft a structure, then deliver the sequence out loud. Record it and check: structure-shaping clarifying question, objective restatement, client-specific labels, stated starting point with hypothesis, and "Does that make sense?" close.
Our structure drills include opening exercises with AI feedback on specificity, MECE quality, and hypothesis clarity. The opening is weighted heavily in the scoring rubric. For complete prep, pair the drills with live behavioral practice.
Sources and Further Reading (checked June 17, 2026)
- McKinsey case interview preparation, structuring as a primary evaluation criterion: mckinsey.com/careers/interviewing
- BCG case interview preparation, evaluation of problem-solving approach: careers.bcg.com/global/en/case-interview-preparation
- Bain case interview preparation, format and assessment criteria: bain.com/careers/hiring-process/case-interview
- Management Consulted, case interview structure guide and BOTM clarifying question framework: managementconsulted.com/case-interview-structure
- Management Consulted, insider scoring guide on McKinsey question-by-question scoring: managementconsulted.com/insiders-look-case-scoring-system
Run the opening sequence on a real drill
Get AI feedback on clarifying questions, structure specificity, MECE quality, and hypothesis logic. Built for the first 3 minutes of MBB cases.
Frequently asked questions
Resources and related guides
- Learn the case methodPractice
- Browse all free resourcesResource hub
- Hypothesis-Driven Case Interview: How to Lead with a HypothesisFrameworks · Mar 1, 2026
- Case Structure vs Case FrameworkFrameworks · May 1, 2026
- Impact-Effort Matrix: How to Prioritize Like a ConsultantFrameworks · Jun 12, 2026
- When To Use Consulting Frameworks (And When To Skip Them)Frameworks · Jun 2, 2026