A Semester Playbook for Consulting Clubs and Career Centers

A common pattern in consulting club case practice goes like this. There is a kickoff meeting in September, a weekly session where members pair off, and a shared folder of cases that every cohort inherits. By October the pairs have often settled into the same two people running the same ten cases, nobody has told anyone how they are really doing, and the members who most need reps are the ones who have quietly stopped coming.

That is not a motivation problem. It is a design problem, and a small number of structural choices fix most of it. This playbook is for club officers and career-center staff running a fall semester of case practice for a mixed group: some students who have never seen a case, some who are weeks from first-round interviews. It assumes volunteers, student time, and no budget. Early August is a good moment to read it, because the setup work below is cheapest before classes start.

Start with a baseline, not a kickoff speech

The first meeting should not be a presentation about how to do cases. It should be a case. In the first two weeks, have every member run one 30-minute case with a trained case giver, or record themselves attempting one so that a calibrated case giver scores the recording on the club's rubric (more on that below).

The baseline does two jobs. It gives you a before-number for every member, so later progress is something you can see rather than something you assume. And it lets you sort members into three working levels:

• Foundations: has not completed a full case, or needs the shape of a case explained.
• Working: has done several cases; structure and math are present but inconsistent, especially under time pressure.
• Polishing: structure and math are reliable; the gaps are synthesis, delivery, and consistency.

Pair by level, rotate on a schedule

Most reps should be level-matched. Two Foundations members can follow the same case at the same speed, make the same kinds of mistakes, and learn from each other. Putting a first-time candidate opposite someone who has done sixty cases tends to produce a one-sided session: the stronger member gives hints without noticing, and the newer member leaves with a sense of how far away they are rather than what to do next.

Cross-level pairing still has a place. Roughly one session in three, have a Polishing member give the case to a Foundations or Working member. Giving a case is one of the fastest ways to learn what a good answer sounds like: you hold the data, you know the answer key, and you see exactly what the candidate skipped.

Rotate partners on a fixed schedule instead of letting people self-select. Two weeks is a reasonable interval. Over a twelve-week stretch that gives each member six different partners, six different ways of structuring a problem, and no chance to settle into a pair that has memorized each other's habits.

Large clubs can use pods of four: two pairs who run cases in parallel, then swap and observe. Watching a case from outside is a different skill from running one, and it trains the eye for what the rubric describes.

One rubric for the whole club

Uneven feedback is the most common reason club practice plateaus. One case giver says "great structure," the next says "too generic," and the member concludes that feedback is noise. A shared rubric fixes that, but only if everyone uses it the same way. Keep it to five dimensions, each scored 1 to 5:

• Structure: a clear, prioritized approach that fits the problem.
• Analysis and math: correct, sensibly set up, and checked.
• Communication: top-down, concise, easy to follow.
• Synthesis and recommendation: ends with an answer, reasons, and a risk.
• Composure and delivery: steady pace, clear voice, responds to cues, calm under pushback. Score behavior, not accent or style.

Write a one-line anchor for a 1, a 3, and a 5 on every dimension. For structure: a 1 is a list of buckets with no priority; a 3 is a sensible structure that gets prioritized when the interviewer asks; a 5 is a hypothesis-led structure that adapts as data arrives. The anchors matter more than the labels, because they stop two case givers from meaning different things by a 4. Our piece on the interviewer's perspective is a good primer for the people writing them.

Then calibrate. Before the semester starts, block 60 to 90 minutes with your case givers. Play a recorded 15-minute segment of a case (or act out a scripted one), and have everyone score it independently before anyone discusses it. The disagreements are the point. Rewrite the anchors until two people reading the same line would give the same score.

Finally, keep feedback short and written. Two lines after every session: one thing to repeat, one thing to change. A single behavior to change beats a list of eight.

Keep the case material alive

Case libraries decay. A case that has circulated through two cohorts is a memory test: members recognize the shape in the first sentence and skip the thinking. Interviewers at firms typically write or adapt their own cases, so a memorized answer has little value outside the club. Four habits keep the material useful:

• Have each case giver change the numbers and the setting before using a case, and keep a one-page answer key with the changed figures.
• Write cases from the news or from local businesses. A local gym chain deciding whether to open a second location is a perfectly good market-entry prompt.
• Rotate case types on a schedule (profitability, market entry, pricing, cost reduction) so members do not default to the type they like.
• Mark down recited frameworks. Every structure needs at least one branch that only fits this prompt.

Members who read before a session get more from it. Point them to the write-ups on profitability, pricing and cost-reduction cases, so session time goes to practice rather than explanation.

Alumni mock days

Alumni are the scarcest resource a club has, and they are most useful when members are ready to hear them. Schedule an alumni mock day after members have completed several cases, typically around the middle of the semester, not in the first month.

Run it on a tight schedule: a 30-minute case, 10 minutes of fit questions, 10 minutes of feedback, and a short buffer. Each member leaves with the club rubric filled in by someone outside the club. Send alumni the rubric, the case, and the answer key a week ahead, and ask them to be candid. Students tend to hold back with alumni, and alumni tend to soften feedback with students. Tell members plainly that an alumni session is practice, not a verdict.

Avoid collisions with exams and with real interview windows; a mock day that lands in midterm week gets cancelled by the people who needed it. Keep a list of which alumni gave sessions and send each a short thank-you that names one thing their feedback changed.

A fall-semester cadence

The table below is organized around a twelve-week fall semester, which suits an MBA-style cycle where interviews run into winter. If members are juniors targeting MBB internships, the undergraduate calendar typically puts applications in early September and first rounds from late September into October. Run the baseline in August or the first week of classes and compress weeks 3 to 8 into weeks 2 to 6; the loop is unchanged. On a quarter-system campus, keep the order and shift the dates. Our MBA and undergrad recruiting calendars show the usual shapes, but check your own school's schedule before you fix a date.

On the compressed undergraduate version, the second checkpoint and the alumni mock day move to about week 6, and the simulation block starts right after.

Measuring progress without inventing metrics

A spreadsheet is enough. One row per member per case: date, case giver, case type, five scores, and a one-line note. From that you can answer the questions that matter:

• How did each dimension move between baseline, the second checkpoint, and the last score?
• How many full cases has each member completed, and with how many different partners?
• Who has not had a case with someone outside the club, and who has gone more than three weeks without a session?

Skip attendance as a headline number. It rewards showing up and hides the quiet member who has not run a case in a month. Clubs and universities whose members practice on CaseGrade can see cohort readiness in an admin dashboard. It covers sessions on the platform, so keep the rubric sheet for human-run cases.

If volunteers are scarce, cut in this order: anything that is not practice (speaker events, socials) first, then extra workshops, then the alumni day. Keep the baseline, the rubric, and the rotation. Those three are the loop. For the reps members do on their own between sessions, point them to the five-step reset for the moments a case goes sideways.