Business law case study writers do it with IRAC

Study guidance, not legal advice. Legal rules differ between jurisdictions and change over time — always work from your own course materials, statutes and prescribed cases.

What business law case study writing actually demands

A marketing case asks "what should they do?" A law case asks "what legal question does this situation raise, what rule governs it, and how does the rule apply to these facts?" The difference sounds small and is not. Most students lose marks by narrating the parties' dispute and then announcing a verdict — that is journalism. What earns credit is a disciplined link: fact → issue → rule → reasoned application.

The other demand is precision with sources. Business law papers expect you to name the legal principle you rely on and where it comes from, in the citation style your course prescribes. What you rarely need is the full depth of a law degree: the business case study is testing whether you can spot legal risk in a commercial decision and reason about it cleanly.

Which is why every competent business law case study writer eventually lands on the same skeleton. It has a name, and you can copy it below.

IRAC: the four moves, explained

IRAC organises each legal issue into four moves. One issue = one IRAC pass. If the case raises three issues, you run the structure three times (many courses accept ILAC or CREAC variants — same bones).

• Issue — the legal question, phrased so it can be answered yes or no, or "whether…". One or two sentences. If your issue sentence cannot be disputed, it is not an issue.
• Rule — the legal principle that governs the issue, with its source: a statute, a leading case, or a doctrine taught in your course. State the rule's elements, because the application will test each one.
• Application — the engine room, and normally the longest section. Tie every element of the rule to a specific fact, and deal with the counter-argument while you are there. This is where marks concentrate.
• Conclusion — the likely outcome on those facts, stated briefly and without new arguments. Hedged where the facts genuinely allow two readings.

Copyable IRAC template

Copy each block into your draft and replace the bracketed prompts. The Application block is deliberately the longest — match that weighting in your paper.

ISSUE
Whether [party] [did the act in question] in circumstances that [trigger the legal doctrine],
i.e. whether [the precise legal question — phrased so it can be answered yes/no].
(Every further issue in the case gets its own numbered question here.)

RULE
Under [the doctrine / statute / case your course prescribes], [the legal test applies] where:
  (a) element one — [state it];
  (b) element two — [state it]; and
  (c) element three — [state it].
Source: [statute / case / course materials, in the citation style your brief requires].

APPLICATION
Element (a): The facts state that [specific fact], which [satisfies / does not satisfy] element one
because [reason tied to the fact — quote or cite the case wording].
Element (b): Here the parties part ways. [Party] will argue [reading]; however, [counter-fact]
points the other way because [reason].
Element (c): [Weigh it. If the element is arguable, say what turns it — timing, notice, conduct.]
On balance, the stronger reading is [x], though a court could reach [y] if it treated [fact] as decisive.

CONCLUSION
On these facts, [party] would most likely [outcome], because [one-sentence anchor to the decisive element].
[If genuinely two-sided: "The result is less certain if [alternative reading] prevails."]

BUSINESS LAW CASE STUDY - IRAC SKELETON
Issue:    Whether [party] [act] in circumstances that [trigger the doctrine].
Rule:     Under [doctrine/statute], liability arises where (a) [element], (b) [element], (c) [element].
Application: Element (a) - [fact] satisfies it because [reason].
             Element (b) - [party] argues [reading]; however [counter-fact] because [reason].
             Element (c) - [weighing; what turns it].
Conclusion: [Party] would most likely [outcome] because [decisive element].
Repeat per issue. Cite in the style your brief requires.

Worked mini-outline (illustrative scenario)

Scenario, invented for teaching: a café owner emails a supplier: "Will you sell me 200 kg of house-roast beans at the usual price? Reply by Friday." The supplier replies "200 kg is tight, but we can do 150 kg at that price." The café pays a deposit for 150 kg; the supplier later refuses to deliver, citing the missing 50 kg as an unaccepted term. The café claims a binding deal existed for 150 kg.

1. Issue 1 (IRAC): whether the supplier's reply accepting part of the offer formed a binding agreement for 150 kg. Rule: the general contract principles taught in the course — offer, counter-offer, acceptance, consideration — as covered in class and the prescribed text. Application: the reply changed the quantity, which under the course's counter-offer doctrine operates as a rejection plus a new offer; the café's deposit accepts that new offer for 150 kg. Conclusion: a binding deal for 150 kg is the stronger reading.
2. Issue 2 (IRAC): whether the supplier's refusal to deliver breaches that agreement, or whether the "tight" wording introduced a condition. Application: "tight, but we can do" reads as willingness, not condition — but the deposit timing matters, and the analysis should say which fact a tribunal would treat as decisive.
3. Business wrap-up: what this means commercially (put quantity terms in the reply; document acceptance), plus limits: invented facts, general principles only, jurisdiction-specific rules not covered.

The 5-step approach for a business law case study

1. Read for legal events, not drama. First pass: mark every promise, payment, delivery, refusal, omission and deadline. Those are your facts-in-waiting.
2. List every issue the facts raise. Draft them as "whether…" questions. Choose the two or three your word count can treat properly and say why you prioritised them.
3. Run IRAC per issue. One pass each: question, rule with elements, fact-tied application, brief conclusion. Never blend two issues into one paragraph.
4. Argue both sides inside Application. State the other party's best reading, then answer it with a fact. A one-sided application caps your grade even when your conclusion is right.
5. Close the loop commercially. End with what the decision means for the parties' next move, and state your limits: general principles, invented or public facts, no jurisdiction-specific advice.

The same facts, weak and strong

Pitfalls specific to law case studies

• Summarising instead of issue-spotting. The parties' backstory earns nothing. Convert it into "whether…" questions fast.
• Rule without source. A principle floating with no statute, case or course reference is an opinion. Cite where your course says the rule lives.
• Conclusion leakage. Deciding the case inside the Issue sentence ("Whether the supplier wrongfully breached") tells the marker you started at the end.
• Element amnesia. If your rule has three elements and your application tests two, you handed away the marks hiding in the third.
• Treating every issue equally. Word-count discipline: your strongest issue gets the deepest IRAC pass, and you say why the others are secondary.
• Statute-quoting without application. Copying a section's text and moving on is decoration. Each element must meet a fact.

Issue-spotting drill

Three quick questions on the IRAC discipline.

Free tools that help with law case studies

• Thesis statement generator — for the advisory wrap-up ("the café should put quantity terms in writing"), an arguable one-liner keeps the ending tight.
• Word counter — IRAC papers overflow; check the count against your brief's window before trimming, not after.
• Readability checker — legal prose drifts into 45-word sentences. Find yours and split them.
• Harvard referencing generator — many law-adjacent business courses use author–date referencing for texts; format once, correctly.

Frequently asked questions

Was this page useful? 👍 Yes 👎 Not really