What a written case interview actually is
A written case interview presents you with a packet of information, often charts, exhibits, market data, and background text, that you review individually within a set time limit, then present your analysis and recommendation, sometimes to a panel, sometimes in written form. This format is used by several major consulting firms, often for later rounds, and it tests a different mix of skills than a live, conversational case: heavy reading comprehension and independent structuring under a hard time limit, without an interviewer to bounce ideas off along the way.
Reading dense material quickly and accurately
Skim the packet once for a general sense of what's included, then go back through more carefully, focusing on the exhibits and data since these usually carry the specific numbers you'll need. Note the source and date of each exhibit, since written cases often deliberately include a chart that looks relevant but has a mismatched timeframe or unit, and catching that is part of what's being tested.
- Identify the actual question you're being asked to answer before getting deep into the exhibits, so your reading has a clear purpose.
- Flag numbers and facts that seem contradictory between exhibits, these are often intentional and worth resolving before you build your final answer.
- Don't try to absorb every detail equally, prioritize the information most relevant to the core question.
- Watch for units and currency changes between exhibits, a mismatch here is a classic trap that can throw off an otherwise solid analysis.
Structuring your notes under time pressure
Build your notes around the structure you'll eventually present, not as a chronological record of what you read. As you go through the packet, sort findings directly into the buckets of your framework (for example, market factors, company factors, financial factors) rather than taking generic notes you'll have to reorganize later. This saves significant time when you get to the presentation stage, since your notes are already close to presentation-ready rather than a jumble you have to sort through under additional time pressure.
Presenting after your prep time ends
When prep time is up, lead with your recommendation first, then walk through the two or three strongest pieces of supporting evidence from the exhibits, referencing specific numbers rather than vague summaries. Written case presentations are judged partly on how well you synthesize a large amount of information into a clear, concise argument, so resist the urge to walk through everything you read, focus on what actually supports your conclusion and leave the rest out even if it took you time to read through it.
How this differs from a live, conversational case
In a live case, you build your structure and ask for data incrementally, adjusting as the interviewer responds. In a written case, all the information exists upfront, and there's no back and forth to refine your framework mid-way, you have to structure correctly from what's in front of you within the time limit. This makes strong MECE habits and fast reading comprehension more important relative to live conversational skill, though the underlying analytical approach is the same.
How to practice specifically for this format
Practice with a real timer and a full exhibit packet if you can find one through a casebook, simulating the actual conditions as closely as possible rather than just reading through a case casually. Time yourself on the reading and structuring phase separately from the presentation phase, so you know where your bottleneck actually is, some candidates read quickly but struggle to organize what they've read, while others read too slowly to leave enough time for a clean synthesis at all.
Handling questions from a panel after your presentation
Many written case formats end with a panel asking follow-up questions after your presentation, probing either your recommendation directly or a specific exhibit you may have glossed over. Treat these the same way you would a live case follow-up, stay calm, refer back to the specific exhibit or number in question, and be willing to say you'd want to look at something more closely if you genuinely don't remember a detail, rather than guessing or fabricating a figure you're not sure about. Panels generally respect an honest 'I'd want to double check that specific number' far more than a confident but incorrect answer.
Managing the clock during your prep time
Written case prep time typically needs to cover three distinct phases, reading, structuring or calculating, and preparing your actual presentation, and it's easy to spend so long on the first phase that the other two get rushed. Set rough internal checkpoints, for example planning to finish reading by the halfway mark, so you notice quickly if you're falling behind schedule rather than realizing with five minutes left that you haven't started organizing your actual answer yet. Practicing this pacing specifically, not just the analytical content, is part of what makes written case performance improve with repetition.
Common traps built into written case exhibits
Written case packets are often deliberately constructed to include a few specific traps: a chart with an unusual or non-standard axis scale, two exhibits that appear to show the same metric but are actually measuring slightly different things, or a footnote containing a critical qualifier that changes how a headline number should be read. Get in the habit of checking axis labels, units, and footnotes on every exhibit before using its numbers in your analysis, since these details are often exactly where the exercise is testing your attention rather than your raw analytical ability.
Developing a personal shorthand for faster note-taking
Given the volume of material and the tight time limit, writing full sentences while reading through a written case packet is usually too slow. Develop a personal shorthand in advance, arrows for increase or decrease, abbreviations for recurring terms like revenue or margin, simple symbols for flagging a number you'll want to double check later. Practicing this shorthand ahead of time, rather than inventing it on the fly during the actual exercise, saves meaningful time during the real thing and keeps your notes usable when you return to them under pressure.