Pattern Mastery Guide
In a case based WAT, the admission committee is evaluating your decision-making architecture. Unlike an argumentative essay, which tests your stance on an issue, a Case WAT tests your ability to act as a manager within a specific set of constraints—analyzing complex information, considering multiple stakeholders, and making clear recommendations under time pressure.
Schools like XLRI (for HR and BM), IIM Bangalore, and MDI Gurgaon favor this format specifically because it reveals whether you can balance cold logic with human empathy. The case format simulates what managers do daily: receive incomplete information, structure analysis independently, and make defensible decisions.
-
1
The 5 Repeatable Case ArchetypesBusiness dilemma, ethical choice, resource allocation, stakeholder conflict, crisis response
-
2
The S-A-O-R-I FrameworkSituation → Analysis → Options → Recommendation → Implementation—the universal case structure
-
3
30-Minute Time Blueprint5-2-18-3-2 split: Read → Plan → Write → Review → Polish
-
4
Visual Structure TechniquesHeaders, parallel structure, signposting, trade-off statements—show your thinking
-
5
Handling Incomplete InformationState assumptions, use conditional reasoning, build checkpoints—decide despite uncertainty
-
6
5 Ready-to-Use TemplatesComplete response structures for business, ethical, resource, stakeholder, and crisis cases
This is a Level 1 Core Pattern post covering all case-based WAT essays. For opinion-based topics, see Opinion Essay WAT. For problem-based topics, see Cause-Effect-Solution Essay WAT. The derivative post WAT vs Essay Writing covers key differences between academic essays and case-based responses.
Case-based WAT tests your ability to think like a manager who must act on incomplete information. You must quickly understand complex situations, structure analysis systematically despite time pressure, make clear decisions balancing multiple objectives, and communicate reasoning effectively in writing. The best responses make evaluators think: “This person can analyze, decide, and communicate—exactly what we need.”
What Evaluators Actually Assess
| Dimension | Weight | What They Assess |
|---|---|---|
| Problem Identification | 20% | Can you identify the REAL problem vs symptoms? Understand the decision needed? |
| Analytical Structure | 25% | Is your analysis organized and logical? Do you use appropriate frameworks? |
| Stakeholder Awareness | 15% | Do you identify affected parties? Understand competing interests? |
| Decision Quality | 25% | Is your recommendation clear, grounded, and implementable? |
| Communication Clarity | 15% | Can the evaluator follow your logic easily? Is language concise? |
Case WAT vs Case Interview: Critical Differences
| Dimension | Case Interview | Case WAT | Implication |
|---|---|---|---|
| Interaction | Verbal, iterative dialogue | Written, one-shot response | Must structure own analysis comprehensively |
| Clarification | Can ask questions | No interaction | Must state assumptions explicitly |
| Iteration | Can revise approach | One-shot response | First structure must be sound |
| Depth vs Breadth | Go deep on specific areas | Cover all key angles | Breadth > Depth in WAT |
| Correction | Can clarify misunderstandings | No chance to explain | Must be crystal clear in writing |
Every case based WAT falls into one of five archetypes. Recognizing the type immediately helps you select the right framework and focus your analysis on what evaluators are testing.
Case Based WAT: The 5 Case Types
What It Looks Like: A company faces a strategic decision with no obviously correct answer. Multiple options exist with different risks, returns, and implications.
Common Scenarios:
- Market entry decision (new geography, product, segment)
- Growth strategy choice (organic vs acquisition)
- Technology investment (build vs buy)
- Competitive response (match, differentiate, or ignore)
- Resource allocation (which initiative to fund)
What’s Being Tested:
- Can you evaluate trade-offs (growth vs efficiency vs risk)?
- Do you consider financial constraints realistically?
- Can you think about sequencing (maybe not either/or but which first)?
What It Looks Like: Protagonist faces situation where different courses of action align with different values or stakeholder interests.
Common Scenarios:
- Reporting misconduct by senior leader
- Financial performance vs employee welfare
- Knowledge of problematic product/practice
- Short-term results pressure vs long-term ethics
- Personal values vs organizational demands
What’s Being Tested:
- Can you identify the ethical dimensions?
- Do you acknowledge real-world pressures (jobs, revenue)?
- Can you think beyond binary “comply or don’t comply”?
- Do you show values without being preachy or naive?
What It Looks Like: Multiple worthy initiatives competing for limited resources (budget, people, time, management attention).
Common Scenarios:
- Budget allocation across departments/projects
- Hiring decisions with headcount constraints
- Time allocation with competing demands
- Capital allocation in investment portfolio
- Crisis response with limited resources
What’s Being Tested:
- Can you prioritize using clear criteria?
- Do you think about portfolio balance (quick wins + strategic bets)?
- Can you handle uncertainty (projections aren’t guaranteed)?
What It Looks Like: Different stakeholders have legitimate but conflicting interests. Must find solution that balances competing needs.
Common Scenarios:
- Labor-management conflict
- Customer demands vs operational constraints
- Investor expectations vs long-term strategy
- Department conflicts over shared resources
- Headquarters vs subsidiary disagreements
What’s Being Tested:
- Can you map stakeholder interests fairly?
- Do you see legitimate concerns on multiple sides?
- Can you find creative solutions or make explicit trade-offs?
- Do you think about implementation and buy-in?
What It Looks Like: Urgent situation requiring immediate decision under pressure and uncertainty.
Common Scenarios:
- Product defect or safety issue
- Data breach or security incident
- Negative publicity or PR crisis
- Sudden competitive threat
- Key employee/customer defection
What’s Being Tested:
- Can you prioritize under pressure?
- Do you balance compliance with stakeholder management?
- Can you think about both immediate actions and long-term implications?
All successful case based WAT responses follow the S-A-O-R-I framework: Situation → Analysis → Options → Recommendation → Implementation. This structure ensures you cover all dimensions evaluators assess.
The Universal Case Response Structure
| Section | Purpose | Word Allocation |
|---|---|---|
| S – Situation Analysis | Summarize core conflict, identify root cause | 15-20% (~50 words) |
| A – Analysis/Stakeholder Mapping | List parties and their interests; establish decision criteria | 15-20% (~50 words) |
| O – Options Evaluation | Present 2-3 paths with Pros/Cons | 35-40% (~120-150 words) |
| R – Recommendation | Your chosen path with strong “Why” | 15-20% (~60-80 words) |
| I – Implementation | Brief steps to execute and mitigate risks | 10-15% (~40-50 words) |
Section-by-Section Guide
Advantages: [Benefit 1], [Benefit 2]
Concerns: [Risk 1], [Risk 2]
Assessment: [Strong/Moderate/Weak choice because…]”
Time management is critical in case based WAT. You must read, analyze, and write a structured response in 30 minutes—with no opportunity for revision. Here’s the optimal split.
The 5-2-18-3-2 Split
| Phase | Time | Activity |
|---|---|---|
| Reading | 0:00 – 5:00 | Read twice, underline decision/constraints/stakeholders |
| Planning | 5:00 – 7:00 | Outline structure, decide recommendation |
| Writing | 7:00 – 25:00 | Execute the outline (S-A-O-R-I sections) |
| Review | 25:00 – 28:00 | Check logic, grammar, recommendation clarity |
| Polish | 28:00 – 30:00 | Final scan, ensure question answered |
What to Do in Each Phase
-
📖
During Reading (5 min)First pass (2 min): Skim entire case, understand basic situation. Second pass (3 min): Read carefully, highlight numbers, stakeholders, options, constraints. Mental framework: What’s the core problem? Who are stakeholders? What are options? What criteria matter?
-
📝
During Planning (2 min)Quick outline: Situation: [Company], [core decision], [constraint]. Criteria: [Factor 1], [Factor 2], [Factor 3]. Option A: [Assessment]. Option B: [Assessment]. Implementation: [Key considerations]. Recommend: [Choice + rationale].
-
✍️
During Writing (18 min)Situation: 3 min (40-50 words). Analysis: 3 min (40-50 words). Options: 8 min (120-150 words). Recommendation: 4 min (60-80 words). Implementation: 2 min (30-40 words). If stuck on phrasing, move on—fix in review.
-
✅
During Review (5 min)Content check: Is recommendation clear and justified? Did I address the actual question? Are key facts incorporated? Do NOT: Rewrite large sections, second-guess recommendation, add new arguments.
Know your recommendation before you start writing. If you’re still deciding while writing, you’ll run out of time. The 2-minute planning phase must end with a clear decision. Write to explain and justify that decision—don’t discover your conclusion while writing.
Since the examiner cannot hear you explain your reasoning, you must use visual cues in your writing to demonstrate structured thinking. Clear formatting makes your logic visible.
4 Techniques for Visual Structure
Expands to South India…
Option B: Small Farmer Products (₹100 crore)
Develops new product line…
Option C: Manufacturing Modernization (₹80 crore)
Upgrades production…
– Option A: ₹150 crore (exceeds comfortable limit)
– Option B: ₹100 crore (fits available capital)
– Option C: ₹80 crore (leaves buffer)
Revenue Potential:
– Option A: ₹200-300 crore (highest)
– Option B: ₹80-100 crore (moderate)
– Option C: Margin improvement only (defensive)
Analysis organization: “Three factors drive this decision…” / “To evaluate this, I’ll consider…”
Evidence-based reasoning: “Given that [fact from case]…” / “The data shows…”
Counterargument: “While Option A has merit, the concern is…” / “The strongest argument against my recommendation is…”
Conclusion: “Therefore, the optimal approach is…” / “Weighing these factors, the recommendation is…”
“The recommendation sacrifices [X benefit] to achieve [Y priority], a trade-off justified by [reason].”
Cases often mimic real business ambiguity—you won’t have all the data you want. This is intentional. Case based WAT tests whether you can decide despite uncertainty.
4 Strategies for Incomplete Information
- State Assumptions Explicitly: “Assuming the capital expenditure falls within the industry standard of X%, I recommend…”
- Use Conditional Reasoning: “If X is true, then Y is the best path; otherwise, Z.”
- Build in Checkpoints: “Before final execution, a pilot study should validate the assumption of 10% conversion rate.”
- Acknowledge Gaps: “Critical data gap: competitor response unknown. Recommend monitoring…”
- “We need more data, so I cannot decide.”
- “Without knowing X, it’s impossible to recommend.”
- “More research is needed before any action.”
- Leaving the recommendation section empty or vague.
Managers decide with incomplete information—that’s the job. Saying “I can’t decide without more data” fails the test. Instead, state your assumptions, make a recommendation, and specify what would change your decision. “I recommend Option B, assuming market growth exceeds 5%. If growth is below 3%, Option C becomes preferable.”
Each template provides a complete response structure for a specific case type. Adapt these to your case—the skeleton remains the same.
Template Library for Case Based WAT
[Company] faces [strategic decision] with [number] options. Revenue is [₹X crore], constraints include [capital/time/competition]. The core decision: [specific choice required].
[CRITERIA – 40 words]
Decision should prioritize: (1) [Growth/ROI], (2) [Risk management], (3) [Capability fit]. Additionally, [competitive pressure/time constraint] requires [urgency/caution].
[OPTIONS – 150 words]
Option A: [Name] (₹X investment)
Pros: [2-3 benefits with numbers]
Cons: [2-3 risks]
Assessment: [Strong/Moderate/Weak]
[Repeat for Options B, C]
[RECOMMENDATION – 80 words]
Recommendation: Option [X] because it [rationale tied to criteria]. Rejected alternatives: Option [Y] is [reason]; Option [Z] is [reason].
[IMPLEMENTATION – 40 words]
Phase 1: [Action]. Phase 2: [Action]. Success metrics: [KPIs]. Key risk: [Risk] mitigated by [Approach].
[Protagonist role] faces [ethical tension] where [Stakeholder A] wants [X] and [ethical principle] requires [Y]. Context: [pressure/consequences].
[ETHICAL DIMENSIONS – 50 words]
Core tension: [Value 1] vs [Value 2]. [Party A] prioritizes [short-term]. [Party B] concerned about [long-term/integrity]. Not binary—requires nuanced approach.
[OPTIONS – 120 words]
Option A: Comply with pressure
Pros: [Short-term benefits] | Cons: [Long-term risks] | Assessment: [Usually weak]
Option B: Refuse + Propose Alternative
Pros: [Maintains integrity] | Cons: [Relationship friction] | Assessment: [Usually strongest]
Option C: Escalate via Formal Channels
Pros: [Protected, transparent] | Cons: [Career risk] | Assessment: [Backup if B fails]
[RECOMMENDATION – 60 words]
Recommendation: Option B – Refuse the pressure while proposing compliant alternative. This protects integrity while maintaining relationship. If pressure persists, escalate via Option C.
[SAFEGUARDS – 40 words]
Document conversation. Propose alternative in writing. If rejected, escalate to [appropriate authority]. Personal protection: [audit trail, HR awareness].
[Role] must allocate [limited resource] across [number] competing priorities. Constraint: [specific limitation]. Each option has merit; trade-offs necessary.
[DECISION CRITERIA – 60 words]
Evaluate on: (1) Impact: Revenue/strategic value; (2) Feasibility: Resource requirement and risk; (3) Timing: Urgency and deferability.
Balance: Quick wins (immediate impact) + Strategic bets (long-term) + Risk diversification.
[PRIORITIZATION – 150 words]
Priority 1: [Option X] – [% of resources]
Impact: [Expected outcome with numbers] | Rationale: [Why top allocation] | Risk: [What could go wrong]
Priority 2: [Option Y] – [% of resources]
Impact: [Expected outcome] | Rationale: [Why second] | Trade-off: [What sacrificed]
Deferred: [Options not funded]
Rationale: [Why deprioritizing] | Revisit: [Conditions to reconsider]
[JUSTIFICATION – 60 words]
This portfolio prioritizes [criterion] while maintaining [balance]. Risk management: [%] reserve for [contingencies]. Expected outcome: [estimated impact].
[Company/Situation] involves [number] stakeholders with conflicting interests regarding [decision]. [Stakeholder A] wants [X], [Stakeholder B] wants [Y]. Decision needed by [timeline].
[STAKEHOLDER MAPPING – 80 words]
Stakeholder A: Position [X], Rationale [why], Leverage [power]
Stakeholder B: Position [Y], Rationale [why], Leverage [power]
Common ground: All agree on [shared goal], differ on [means/timeline].
[CONFLICT ANALYSIS – 60 words]
Core tension: [Value 1] vs [Value 2]. Not simple disagreement but legitimate conflict. Doing nothing or splitting difference would result in [poor outcome]. Active resolution necessary.
[RESOLUTION – 100 words]
Recommended approach: [Specific decision]
How this addresses each stakeholder:
– Stakeholder A: [What they gain]
– Stakeholder B: [What they gain]
Trade-offs made explicit:
– [A] doesn’t get [X] but gains [Y]
– [B] accepts [compromise] in exchange for [protection]
[COMMUNICATION – 50 words]
To Stakeholder A: Emphasize [how concern addressed]
To Stakeholder B: Frame as [how serves their priority]
Implementation: [Next steps with ownership]
[Crisis type] discovered at [time]. Impact: [affected parties/scale]. Stakeholders: [customers/regulators/investors]. Regulatory requirement: [deadline]. Reputational risk: [level].
[IMMEDIATE ACTIONS – 80 words]
Hour 1-2:
1. Contain: [Stop bleeding action]
2. Assemble: [Crisis team/roles]
3. Assess: [Scope determination]
Hour 2-6:
4. Comply: [Regulatory notification]
5. Communicate: [Stakeholder updates]
6. Investigate: [Root cause start]
[COMMUNICATION PLAN – 60 words]
To Customers: [What/when/channel]
To Regulators: [Compliance action]
To Media: [Holding statement]
To Employees: [Internal guidance]
To Investors: [Proactive update]
[ROOT CAUSE & PREVENTION – 50 words]
Investigation: [Approach to identify cause]
Immediate fix: [Tactical action]
Systemic fix: [Process/control improvement]
Monitoring: [Ongoing oversight]
[SUCCESS METRICS – 30 words]
Track: Time-to-recovery, recurrence rate, customer complaints, regulatory outcome.
The Complete Case WAT Checklist
- Situation paragraph establishes core problem clearly
- Decision criteria stated upfront (2-3 criteria)
- Options evaluated with consistent structure (Pros/Cons/Assessment)
- Specific facts from case incorporated (not generic)
- Numbers used where relevant
- Trade-offs acknowledged explicitly
- Recommendation is clear and specific (ONE option, not “it depends”)
- Rationale connects to earlier analysis and criteria
- Implementation considerations addressed (risks, metrics, timeline)
- Headers/formatting aids readability
Frequently Asked Questions: Case Based WAT
Quick Revision: Key Concepts
Test Your Understanding
Mastering Case Based WAT for MBA Entrance
The case based WAT is a distinctive format favored by top B-schools like XLRI, IIM Bangalore, and MDI Gurgaon. Unlike opinion essays that test your stance on issues, or abstract essays that test philosophical thinking, case-based WAT tests your decision-making architecture—your ability to analyze complex situations and make clear recommendations under time pressure.
What Makes Case WAT Different
In a case based WAT, you receive a 200-500 word business scenario and must produce a 300-500 word response in 25-30 minutes. This format simulates what managers do daily: receive incomplete information, structure analysis independently, consider multiple stakeholders, and make defensible decisions. Schools use this format specifically because it reveals whether you can balance analytical rigor with practical judgment.
Unlike case interviews where you can ask clarifying questions and iterate your approach, case WAT is a one-shot written response. You must create your own structure, state assumptions explicitly, and communicate your reasoning so clearly that evaluators can follow your logic without asking questions. This makes the S-A-O-R-I framework essential—it ensures you cover all dimensions evaluators assess.
The S-A-O-R-I Framework
Every successful case based WAT follows the S-A-O-R-I structure: Situation (identify core problem, not symptoms), Analysis (establish decision criteria, map stakeholders), Options (evaluate 2-3 alternatives with consistent structure), Recommendation (pick ONE option with clear rationale), Implementation (show you think about execution). This framework allocates roughly 15% to Situation, 15% to Analysis, 35-40% to Options, 15-20% to Recommendation, and 10-15% to Implementation.
The Options section is the analytical core—where you demonstrate structured thinking and trade-off analysis. Each option needs consistent structure: name, advantages, concerns, and assessment. This parallel structure makes your thinking visible and allows evaluators to compare your analysis of different alternatives.
Decision-Making Despite Uncertainty
A distinctive feature of case based WAT is handling incomplete information. Cases intentionally omit data to test whether you can decide despite uncertainty. Saying “I need more data to decide” fails the test. Instead, state assumptions explicitly, use conditional reasoning, and build in checkpoints—but always make a clear recommendation. “I recommend Option B, assuming market growth exceeds 5%. If growth is below 3%, Option C becomes preferable” shows sophisticated thinking while still deciding.
Visual Structure Matters
Since evaluators can’t ask clarifying questions, your case based WAT response must be self-explanatory. Use clear headers and labels for options, parallel structure for comparisons, signposting phrases for logic flow, and explicit trade-off statements. These visual cues demonstrate structured thinking and make your reasoning easy to follow. Remember: unclear writing means unclear thinking in the evaluator’s mind.
Practice 8-10 case WATs using the same S-A-O-R-I structure until your outline becomes automatic. Speed comes from reusing the skeleton, not thinking of a new format each time. The confidence to make decisions despite incomplete information develops with practice. Master this format, and you’ll demonstrate exactly what evaluators want to see: someone who can analyze, decide, and communicate—ready for the MBA classroom and the managerial roles beyond.
