Back to blogStudy Tips & Exam Prep

The IRAC Method Explained (With a Real Worked Example)

CaseBriefer Team · 22 August 2026 · 4 min read

Study Tips & Exam Prep

IRAC gets taught in the first week of law school and then never explained properly again. You're handed the acronym, told it's how you answer exam questions, and left to figure out the rest yourself. So let's actually walk through it.

IRAC stands for Issue, Rule, Application, Conclusion. It's a structure for legal reasoning, not a formula you fill in mechanically. The structure exists because it mirrors how courts actually reason: identify the question, state the law that governs it, apply that law to the facts in front of you, then reach a conclusion. If you skip a step, your answer stops making sense, even if every individual sentence is correct.

Some Australian unis teach ILAC instead, Issue, Law, Application, Conclusion. Same structure, different letter for the middle bit. Use whichever your course teaches, the substance doesn't change.

Issue

State the specific legal question raised by the facts. Not the area of law, the actual question.

Weak: "This question is about negligence."

Better: "The issue is whether the manufacturer owed Sarah a duty of care, given there was no direct contract between them."

A problem question usually raises more than one issue. Spot them all before you start writing. Missing an issue entirely costs you more marks than answering one issue imperfectly.

Rule

State the legal rule that governs the issue, with authority. This means naming the case or the statute the rule comes from. "There is a duty of care" isn't a rule, it's a conclusion with the reasoning stripped out. The rule needs to say when a duty of care arises and why, sourced from the relevant case law.

For our example: "A manufacturer owes a duty of care to the ultimate consumer of a product where injury from the product's defect is reasonably foreseeable, and no reasonable opportunity for intermediate inspection exists: Donoghue v Stevenson [1932] UKHL 100."

Notice the rule is stated in general terms, not yet applied to Sarah. That's the next step.

Application

This is where most students lose marks, either by skipping it or by quietly turning it back into a restatement of the facts. Application means taking the rule from the step above and testing it, element by element, against the specific facts you were given.

"Sarah purchased a bottle of ginger beer manufactured by the defendant. The bottle was opaque, sealed, and gave no opportunity for inspection before consumption, satisfying the 'no intermediate inspection' element from Donoghue. It was reasonably foreseeable that a decomposed snail in the bottle would cause injury to whoever eventually drank it. On these facts, the manufacturer owed Sarah a duty of care."

That's application: rule, meet facts, in both directions. If you find yourself just repeating the facts from the question without connecting them back to the rule's specific elements, you're not applying, you're describing.

Conclusion

Answer the issue directly. One or two sentences. No new arguments here, no hedging that undoes the analysis you just did.

"The manufacturer owed Sarah a duty of care, and is likely liable in negligence for her injury."

If the law is genuinely unsettled or the facts cut both ways, say so and pick the stronger side. Examiners want a conclusion, not a shrug.

Common mistakes worth avoiding

Stating the rule without authority. A rule with no case or statute behind it is just an assertion. Examiners are checking whether you know where the law comes from, not just what it says.

Application that's just facts repeated back. If you could delete the case name from your application paragraph and it would still read the same, you haven't actually applied the rule.

One IRAC for a multi-issue problem. Complex problem questions usually have several distinct issues, sometimes nested inside each other. Run IRAC separately for each one. Cramming three issues into a single IRAC paragraph is how conclusions get muddled.

Conclusions that contradict the application. If your application shows a strong case for one side, your conclusion should say so plainly. Don't soften a clear answer into "it's arguable either way" just to hedge your bets.

Practising it under time pressure

The structure only becomes fast once it's automatic. Practise on old problem questions with a timer running, and resist the urge to write a beautiful first paragraph before you've even finished spotting the issues. Skim the whole question first, list every issue you can find, then IRAC each one in turn. It feels slower at first. By exam day, it's the only way to make sure you don't run out of time halfway through and lose marks on issues you never got to.

Stop writing your own notes.

Generate a free case note

5 free case notes · 5 free reading summaries