Case Interview Checklist and Rubric Prep

Most candidates do not need another broad explanation of case scoring. They need a way to turn one mock into better practice the next day. This page gives you a simple before, during, and after checklist so you can use every rep to improve. It complements the broader case interview scoring rubric without repeating it, and it works well with the case interview prep guide, frameworks guide, math practice, synthesis guide, and behavioral interview consulting pages.

TL;DR: what do you need to know?

• Use 1 checklist per mock case so feedback becomes specific instead of random.
• Score structure, math, communication, and synthesis separately after every case.
• Pick 1 skill to watch before the case and 1 drill to assign after it.
• A good rubric separates interviewer-style scoring from friendly peer advice.
• Road to Offer drills help turn checklist feedback into focused practice reps.

What Problem This Checklist Solves?

The common failure in case prep is false progress. You do a mock, get a few comments, nod along, and move on. That feels productive, but it does not produce clean learning. A checklist forces specificity. Instead of "need to be more structured," you get "my opening branch had overlap" or "I did not justify why I chose a profitability tree."

That matters because case performance is built from habits, not awareness. If you cannot name the exact mistake, you will repeat it in the next mock. A checklist gives you a shared language for what went wrong and what to practice next.

The right mindset is simple: each mock should produce one or two concrete actions. Not ten. Not a rewrite of your entire prep plan. Just the next rep.

How Should You Prepare Before the Mock?

Set one goal for the case

Pick one primary focus before you start. Examples:

• "Keep my opening structure MECE."
• "Lead every calculation with the setup."
• "Give a one-sentence synthesis at the end of each branch."
• "Pause before answering data questions."

If you try to improve everything in the same case, you will improve nothing cleanly. One focus makes the review usable.

Pick the rubric lens you want to test

Do not wait until the end to decide how you are measuring the rep. Use a simple lens based on the owner rubric: structure, math, communication, judgment, and synthesis. That is enough. You do not need a giant form.

If you want the broader partner-style view, skim case interview scoring rubric first, then use this page to make that rubric actionable in practice.

Define the case conditions

Write down the case type, the format, and the time limit. A mock case feels different depending on whether you are doing a live interview, a solo drill, or a timed AI session. Your review only makes sense if you know the conditions.

For example, a weak opening in a 5-minute timed drill matters differently than a weak opening in a full 30-minute case. Context changes the diagnosis.

What Should You Watch During the Case?

Track the opening separately

Your opening is where you show whether you can own the problem. Check whether you:

• Restated the objective clearly
• Asked clarifying questions that mattered
• Built a case-specific structure
• Explained why your branches fit the problem

If the opening is muddy, the rest of the case starts on a weak footing. That is why the frameworks guide matters, but this checklist is about whether you actually used a framework well in real time.

Watch your math process, not just the answer

Do not only mark whether the number was right. Mark whether you:

• Named the formula or setup
• Kept units straight
• Rounded intentionally
• Sanity-checked the result

This distinction matters because a correct answer with a bad process is fragile. It will fail under pressure in a harder case. A clean process survives harder numbers.

Notice how you communicate transitions

Candidates often know the content but lose points when they move between ideas. During the case, notice whether you signpost:

• "I have two hypotheses."
• "There are three drivers here."
• "I want to test the volume side first."
• "My recommendation so far is..."

If you want a deeper view of communication and synthesis mechanics, cross-reference the synthesis guide and keep this checklist focused on execution.

Record any moments of drift

Drift is when you wander from the original objective. It can happen in a few ways:

• You explore a branch without saying why
• You chase a number that does not change the decision
• You answer the interviewer's prompt but not the case question

Mark those moments immediately. They are often more useful than the final score because they reveal decision errors, not just presentation errors.

How Do You Review the Case Afterward?

Score the rep in one pass

Use a simple 1 to 4 scale or a pass, partial, fail system. Keep it stable across sessions. The point is consistency. If you change the scale every time, you lose the pattern.

Write scores for:

• Opening structure
• Analytical accuracy
• Communication
• Hypothesis management
• Recommendation quality

Write the one-line diagnosis

After the score, write one sentence that starts with the real issue, not the symptom. For example:

• "My structure was generic, so the rest of the case had no focus."
• "My math was fine, but I never explained the business meaning."
• "My synthesis came too late and lacked a clear decision."

That sentence is the bridge between feedback and practice.

Turn diagnosis into a drill

Every miss should map to one drill. Examples:

• Weak opening structure -> do try drills focused on opening frameworks.
• Weak math setup -> run timed reps from case interview math practice.
• Weak closing -> practice a 30-second recommendation from the synthesis guide.

If you want a wider practice loop, use the dashboard to track your reps and the assessment to see where the gaps show up most often.

Which Mistakes Should You Flag Every Time?

Generic framework use

If your branch names could fit any case, that is a red flag. You want case-specific language, not a memorized template.

Unexplained math

If you jump straight to a number, you hide your thinking. Interviewers need the setup to trust the answer.

Weak synthesis

If the case ends with "I think they should probably consider..." your practice rep was incomplete.

No explicit tradeoff

Good recommendations usually include a tradeoff or a risk. If you never mention one, you may be skipping the real business tension.

No follow-up note

If you finish the case and do not write down the lesson, the feedback evaporates.

How Should You Use This in a Weekly Prep Plan?

Use the checklist in a tight loop:

1. Pick one focus before the mock.
2. Run the case.
3. Score the rep right after.
4. Write one diagnosis sentence.
5. Choose one drill for the next session.

That is enough. You do not need a huge tracker to start. You need repetition plus a narrow review habit.

The fastest improvement usually comes from the weakest repeated pattern, not from trying to optimize every part of the case at once. That is why this page pairs well with the broader rubric article and with the case interview prep guide. The checklist tells you what to notice. The drills tell you how to fix it.

Frequently Asked Questions

How many checklist items should I track in one mock?

Track enough to be useful, not so many that you stop using the checklist. Five categories is usually enough: opening, math, communication, hypothesis management, and synthesis.

Should I use the same checklist for live mocks and solo drills?

Yes, but keep the interpretation separate. A solo drill can focus on one skill, while a live mock should show whether you can integrate the skills under pressure.

What if my feedback is vague?

Convert it into a concrete observation. "Be more confident" becomes "I buried my conclusion." "Be more structured" becomes "My second branch overlapped the first."

Do I need to score myself after every case?

Yes. If you skip the review, the case becomes entertainment instead of training. A fast score plus one diagnosis sentence is enough.

How do I know what to drill next?

Pick the item that appears most often or that blocks the rest of your case performance. If the opening is weak, fix that first because it affects everything downstream.

Sources and Further Reading (checked 2026-05-01)

• BCG case interview preparation: careers.bcg.com/case-interview-preparation
• McKinsey interviewing: mckinsey.com/careers/interviewing
• Bain case interview preparation: bain.com/careers/hiring-process/case-interview
• Princeton Case Interview Preparation: careerdevelopment.princeton.edu/guides/interviews/case-interview-preparation
• Case interview scoring rubric