What your case study assignment actually asks for
Before we get to structure, read your brief the way a grader reads it. A typical brief says something like: 2,000 words, analyse the strategic position of the company in the case using two frameworks from the course, recommend a course of action, Harvard referencing, due week 10. Every word there is a marking instruction. The word count is a ceiling, the named frameworks are expected to appear, and the recommendation is not optional decoration — it is usually worth a full rubric row.
So the honest answer to how to write a case study starts before any writing: translate the brief into a checklist, and build the paper backwards from it. If the rubric mentions critical analysis, your analysis section needs causes and trade-offs, not just findings. If it mentions justified recommendations, each suggestion needs a because-clause that points at evidence you presented earlier. (If you are not yet sure what a business case study is, or how it differs from a case analysis, the case study Q&A guide covers definitions first.)
The 8-section case study structure (what goes where)
Most business and management case study papers follow the same skeleton. Your course may rename sections or merge two of them, but the logic underneath stays the same: compress the argument, set up the case, prove the problem, analyse with theory, then decide.
Executive summary
150–200 words that compress the whole paper: the situation, the main problems found, the option chosen and why. Written last, read first. Graders often form their expectations of the mark here.
Introduction
Name the case, the task your paper performs, and your central claim (a one-sentence thesis). Close with a roadmap: Section 2 examines…, Section 3 analyses… Keep it under 10% of the word count.
Background / case description
Facts from the case that your argument will actually use — market position, finances, people, timeline. Not a retelling. If a fact never gets referenced by your analysis, cut it.
Problem statement
The core issue, stated in one or two sentences, plus the smaller issues under it. Separate symptoms (falling sales, staff turnover) from causes (pricing model, management gaps) — mixing these up is the single most common way to lose analysis marks.
Methodology (when required)
Many course assignments skip this; research-heavy ones require it. One paragraph is usually enough: which frameworks you applied (SWOT, PESTLE, Five Forces, a decision model) and what data from the case you used.
Analysis / discussion
The engine room and the biggest section, often half the word count. Run each framework, but interpret as you go: what does the matrix show, which force is strongest, which external factor actually threatens the strategy. Cite theory where it explains the situation.
Recommendations
Specific actions, each tied to a finding from your analysis and checked for feasibility (money, time, people). Two well-argued recommendations beat six vague ones. Name the first step and the main risk for each.
Conclusion and references
Restate the problem and your chosen solution in two or three sentences — no new information. Then the reference list in your required style, plus appendices for long tables if your brief allows them.
Want to see this skeleton filled in? The annotated case study example shows each section with margin commentary.
Executive summary template (150 words, copy and fill)
Write this last, keep it under 200 words, and never let it contain a sentence you could not point to in the paper. Fill the bracketed slots and delete anything that does not apply:
This report analyses [the situation] facing [company / subject] in [industry or context]. Using [framework 1] and [framework 2], the analysis identifies [problem 1] and [problem 2] as the main issues. The evidence in the case points to [root cause] as the underlying driver, while [constraint] limits what the company can do in the short term. Three options were considered: [option A], [option B] and [option C]. Evaluated against [decision criteria], [chosen option] is recommended because [main reason]. Implementation should begin with [first step], followed by [second step] within [timeframe]. The key risk is [risk], which can be reduced by [mitigation].
Notice what the template never does: it never retells the case story, and it never says this report will discuss… without saying what the discussion found. Both habits read as filler to a marker who has sixty papers to grade.
How to decode your marking rubric
Rubrics sound abstract on purpose. The table below translates the phrases that appear on most business-school rubrics into concrete work, and shows where in the paper you prove each one.
| Rubric phrase | What the grader means | Where you show it |
|---|---|---|
| Demonstrates understanding of the case | You selected the facts that matter — no retelling, no wasted summary | Background section; evidence used later |
| Applies relevant theory and frameworks | Named models explain the situation, not decorate it | Analysis section |
| Critical analysis / depth of argument | Causes, not symptoms; trade-offs acknowledged; counter-arguments met | Problem statement + analysis |
| Recommendations are justified | Each action traces back to a finding and is feasible | Recommendations section |
| Structure and coherence | Signposted sections; one idea per paragraph; a roadmap you follow | Whole document |
| Evidence and referencing | Case exhibits plus academic sources, cited in the required style | In-text citations + reference list |
| Within the word count | You planned a budget per section and stuck to it | Planning, then trimming |
Two habits follow directly from this table. First, highlight every verb in your rubric — analyse, evaluate, recommend, compare — and make sure each one has a home in your paper. Second, when the rubric weights the analysis section at 40%, give it roughly 40% of the words. Graders notice when the weight and the page length disagree.
A 7-day case study plan you can actually keep
This schedule assumes about two focused hours a day and a 2,000-word target. Compress it if your deadline is closer — the order of the steps is what protects you, because drafting analysis before frameworks are done is what causes 2 a.m. rewrites. Tick each step as you finish it; the bar tracks your progress.
- Day 1 — Read the brief and rubric twice. List the deliverables: word count, frameworks, referencing style, deadline.
- Day 1 — Skim the whole case once without taking notes, just to know how it ends.
- Day 2 — Read again with a pencil. Mark every fact, number and quote your argument might use.
- Day 3 — Run your frameworks on the case (SWOT, PESTLE, Five Forces) and write one finding sentence per quadrant or force.
- Day 4 — Draft the analysis and problem statement. This is the half of the paper that earns the most marks — start here, not with the introduction.
- Day 5 — Draft recommendations tied to your findings, then the introduction and background around them.
- Day 6 — Write the executive summary from the finished draft. Check the word count and trim description first.
- Day 7 — References, appendices, one slow read-aloud proofread, submit with an hour to spare.
On day 3, the SWOT analysis builder turns scattered case facts into a structured matrix you can paste into your draft, and the word counter keeps each section inside its budget as you write.
The same paragraph, weak and strong
Analysis marks are won at paragraph level. Both versions below describe the same case finding — a café chain losing lunchtime customers. Switch between the tabs and compare what each one does.
The company has had problems with its lunchtime sales recently. Sales have been going down for a while and fewer customers are coming to the stores at midday. The company needs to look into this issue and find ways to improve the situation so that customers come back. Marketing could also be improved.
Why it scores poorly: it repeats the case, names no cause, uses no framework, and the "recommendation" is a wish. Every sentence could appear in any paper about any company — which is exactly the problem.
Lunchtime sales fell in both quarters covered by the case, and exit surveys blame queue times above eight minutes (case exhibit 3). Viewed through the lens of the 4Ps, the product has not changed — the place strategy has: two of the five busiest stores lost their second counter to the new mobile-order pilot. The queue, not the menu, is the bottleneck. Any fix that only adds promotion will therefore spend money on a problem pricing and process create.
Why it scores well: a specific claim, evidence from a named exhibit, a framework used to explain the cause, and an implication that narrows the recommendations. That claim → evidence → theory → implication rhythm, repeated across paragraphs, is what critical analysis means on a rubric. (The five-move method behind this rhythm is unpacked in the case study analysis guide.)
Common ways students lose marks
- Retelling the case. Half a page of company history reads as padding. Keep only the facts your analysis cites.
- Symptoms posing as problems. Falling sales is a symptom. The problem is why. Your problem statement should survive the question "and what is causing that?"
- Frameworks as decoration. A SWOT matrix pasted in with no interpretation adds nothing. After each framework, write what it proves.
- Recommendations that float free. Every recommendation must trace to a numbered finding. If you cannot draw the arrow, the grader cannot either.
- Ignoring the brief's named frameworks. If the professor asked for PESTLE, a paper built only on SWOT loses marks it did not have to.
- Blowing the word count. Over by 20% and under by 20% both read as poor planning. Budget per section early.
- Referencing panic at the end. Collect citations as you write, not after. The APA citation generator and its Harvard and MLA siblings take the formatting pain out if you feed them as you go.
A copyable case study outline
Here is the whole structure as a plain outline with suggested word shares for a 2,000-word paper. Copy it into your notes file and fill it in section by section. If the deliverable is a talk rather than a document, the analysis does not change — only the packaging does; the case study presentation page shows how this same outline converts to slides (one section, one claim, evidence down in the notes).
CASE STUDY OUTLINE (2,000 words — adjust shares to your brief) 1. Executive summary (~150 words) — problem, evidence, chosen option, reason 2. Introduction (~180 words) — case, task, thesis, roadmap 3. Background (~300 words) — only facts the analysis will use 4. Problem statement (~150 words) — core issue + sub-issues, causes over symptoms 5. Methodology (~80 words) — frameworks applied, data used 6. Analysis (~800 words) — framework 1, framework 2, each with interpretation 7. Recommendations (~240 words) — 2-3 actions, each with reason, first step, risk 8. Conclusion (~100 words) — restate problem and solution, no new content References — case + academic sources in required style Appendices — long tables and exhibits, if the brief allows
Test yourself: the 5-question structure quiz
Answer all five — if the wrong option stings a little, that is the one to reread.
1. What belongs in the executive summary?
2. Where does the company's history go?
3. Which recommendation is strongest?
4. Falling sales are stated in the case. What is the most likely marking mistake?
5. When do you write the executive summary?
Deadline closer than the plan allows?
If the timeline above does not fit your week, a quoted, deadline-bound writer can take the draft off your hands — you set the topic, level and deadline, and see the price before you commit.
Frequently asked questions
How long should a case study be?
There is no universal length. Undergraduate case studies commonly land between 1,500 and 3,000 words and MBA assignments between 3,000 and 5,000, but your brief overrides every rule of thumb. What matters is the internal share: analysis gets the biggest slice, description the smallest. Check it as you write with the word counter.
Do I write the executive summary first or last?
Last. The summary compresses a finished argument, and you cannot compress an argument you have not made yet. Draft the body, then distil it into 150 words using the template above.
How many frameworks should I use in one case study?
Use the frameworks your brief or rubric names, and no more. Two or three applied with evidence beat five applied as decoration. If the brief is silent, pick the one that matches the question: SWOT for position, PESTLE for external forces, Five Forces for industry competition.
Can I use first person in a case study?
Business case studies are usually written in the third person, but some courses allow I or we when you defend a decision. The brief and your department style guide decide this, so check both before you start. If nobody says anything, third person is the safe default.
How do I cut words when I am over the limit?
Cut description before you cut analysis: retold facts, long histories, and framing sentences go first. Then split long sentences — a 40-word sentence almost always hides two 20-word ones. The readability checker flags exactly which sentences to attack.
What is the difference between a case study and a case analysis?
A case study paper combines description and analysis in a fixed structure. A case analysis puts nearly all its weight on the argument: problems, causes, theory, recommendations. If your brief asks for analysis only, start with the problem rather than the company history — the definitions guide breaks down all the variants.
Was this guide useful?