What the IRAC method is
IRAC is a framework for legal reasoning that turns a messy set of facts into a clear, structured argument. The letters stand for Issue, Rule, Application and Conclusion. It mirrors the way courts actually reason — identify the question, find the governing law, apply it to the facts, decide — which is why law schools teach it from the first week.
Its great strength is discipline. Weak legal answers describe the law in the abstract and never quite connect it to the problem; IRAC forces you to apply the rule to these facts, which is where legal skill is demonstrated and where the marks are. Once internalised, IRAC stops being a template you fill in and becomes the natural shape of a legal argument.
When to use IRAC (and when to adapt it)
IRAC is at its most useful in problem questions — the ‘advise the parties’ scenarios that dominate law assessment — where you work through each legal issue the facts raise. It also underpins essay answers, though essays usually need more evaluation and critique woven through. Many problem questions raise several issues; you run a separate IRAC cycle for each, then draw the threads together at the end.
You will use IRAC across contract, tort, criminal, public, land and equity, and in legal-skills and moot work. The substantive law changes; the analytical structure does not.
The four steps in detail
Issue. Identify the precise legal question the facts raise, framed in legal terms. Not ‘was it fair?’ but ‘did the defendant owe the claimant a duty of care?’ Pinpointing the right issue is half the battle; a misidentified issue sends the whole analysis off course.
Rule. State the law that governs the issue — the relevant statute, the leading cases and the test they establish. State it accurately and concisely, with authority (cited in OSCOLA). For a duty of care you would set out the Caparo v Dickman three-stage test; you are stating the law, not yet applying it.
Application. This is the heart of the answer. Apply the rule to the specific facts, arguing both sides where the law is genuinely uncertain. Use the facts explicitly: ‘Here, because X did Y, the proximity limb is likely satisfied, as in Donoghue v Stevenson…’ Strong application is analytical and two-sided, not a restatement of the rule.
Conclusion. Reach a clear, reasoned conclusion on the issue — advise the party on the likely outcome. It need not be certain (‘a court would probably find…’), but it must follow from your application. Then move to the next issue.
IRAC variations: CIRAC, ILAC and MIRAT
You will see several close cousins of IRAC, and your law school may prefer one. CIRAC adds a Conclusion at the start (Conclusion, Issue, Rule, Application, Conclusion), front-loading your answer. ILAC swaps in ‘Law’ for ‘Rule’ (Issue, Law, Application, Conclusion) and is common in Australia. MIRAT (Material facts, Issue, Rule, Application, Tentative conclusion) is used in some jurisdictions. They are the same idea with different emphasis; pick the one your course teaches and apply it consistently. The non-negotiable core, whichever label you use, is that application carries the analysis.
A worked example: negligence problem question
Facts: a café mops its floor but leaves no warning sign; a customer, Sara, slips, falls and breaks her wrist. Advise Sara. Working one issue through IRAC:
- Issue: Does the café owe Sara a duty of care, and has it breached that duty, causing her injury (the elements of negligence)?
- Rule: Negligence requires a duty of care, breach, causation and non-remote damage. A duty is established under the Caparo v Dickman test (foreseeability, proximity, fairness); occupiers owe a duty to visitors under the Occupiers’ Liability Act 1957; breach is judged against the reasonable person (Blyth v Birmingham Waterworks).
- Application: A café clearly owes a duty to its customers as visitors. The issue is breach: a reasonable occupier mopping a floor would foresee a slip risk and would put out a warning sign; failing to do so likely falls below the standard of the reasonable occupier. Causation is satisfied because, but for the wet unmarked floor, Sara would not have fallen, and a broken wrist is a foreseeable, non-remote consequence.
- Conclusion: Sara is likely to succeed in negligence against the café, subject to any contributory negligence (for example if she was running).
Notice how the application uses the facts (no sign, mopped floor, the fall) and authority together, and argues to a conclusion rather than merely describing the law.
Structuring a multi-issue answer
Real problem questions raise several issues — duty, breach, causation, defences — and sometimes several parties. Run a focused IRAC cycle for each issue, in a logical order (you cannot discuss breach before establishing a duty). Signpost clearly with sub-headings or topic sentences so the marker can follow your structure. Spend your words in proportion to the difficulty: skate over the obvious (the duty is clearly owed) and dwell on the genuinely contested issue (was there breach?). End with a short overall conclusion advising the party across all the issues.
The most common IRAC mistakes
- All rule, no application. Describing the law at length but never applying it to the facts is the single biggest mark-loser.
- Misidentifying the issue. The wrong issue derails the whole answer; read the facts carefully and frame the question in legal terms.
- One-sided application. Where the law is uncertain, argue both ways before concluding.
- No authority. Every rule needs a case or statute, cited in OSCOLA.
- Equal time on every issue. Weight your analysis towards the contested issues, not the obvious ones.
- A conclusion that ignores the application. Your conclusion must follow from your reasoning, not contradict it.
How to write first-class application
Because application carries the marks, it is worth seeing what separates an adequate application from an excellent one. An adequate application states that a rule is satisfied; an excellent one argues it, using the specific facts as evidence and engaging with the points that cut the other way. Three moves lift application. First, tie every assertion to a fact: ‘because the floor was wet and unmarked’, not simply ‘the occupier was careless’. Second, argue both sides where the law is genuinely uncertain — a court could find X, but the better view is Y because… — then commit to a position. Third, use authority by analogy: show how the facts resemble or differ from the facts of a decided case, rather than just naming the case.
Avoid the trap of ‘fact regurgitation’ (retelling the scenario) or ‘rule regurgitation’ (restating the law) dressed up as application. The marker is looking for the reasoning that connects the two. A useful self-test: if you deleted the rule section, would your application still make clear which law you are applying? If not, you are describing rather than applying.
Using IRAC in essays versus problem questions
IRAC is most at home in problem questions, but it also disciplines essay answers — with a shift of emphasis. A problem question asks you to apply the law and advise a party, so application dominates. An essay question (‘Critically evaluate the law on…’) asks you to evaluate the law, so the ‘application’ step becomes analysis and critique: is the rule coherent, fair, consistent with policy, in need of reform? You still identify issues and state the law accurately, but you weave in academic commentary, compare competing views, and build an argument towards a thesis rather than advising a client.
A practical approach for essays is to use IRAC within each section of a thematic structure: for each theme, identify the sub-issue, set out the relevant law, analyse and critique it, and reach an interim conclusion, before synthesising everything in your overall conclusion. This keeps an evaluative essay rigorous and grounded in authority, rather than drifting into unsupported opinion — the most common weakness in law essays.
Using and citing authority correctly
Legal argument is only as strong as the authority behind it, so the rule and application stages must be anchored in cases and statutes, cited in OSCOLA. State the ratio of a case — the binding principle — not just its name, and pinpoint the judge and paragraph where it matters: per Lord Atkin in Donoghue v Stevenson [1932] AC 562 (HL) 580. Distinguish binding authority (a higher court in the same hierarchy) from merely persuasive authority (lower courts, other jurisdictions, dissents, academic writing), and treat them accordingly in your argument.
Be precise about the current state of the law: note where a case has been overruled, distinguished or affected by statute, and cite the governing provision by section. Vague references (‘case law says…’) and outdated authority are quick mark-losers. For the full citation rules — cases, legislation, secondary sources, tables of authorities — see our OSCOLA referencing guide, which sets out the formats with worked examples.
Planning your answer before you write
Strong IRAC answers are planned, not improvised. Before writing, read the facts twice and list every legal issue they raise — parties, causes of action, defences. Sketch the issues in a logical order, because some depend on others (there is no breach to discuss until a duty is established, and no remedy until liability is). Note next to each issue the key authority you will use and whether the point is straightforward or genuinely contested, so you can budget your words accordingly.
This two-minute plan prevents the two classic failures: missing an issue entirely, and spending half the answer on an obvious point while rushing the hard one. In an exam, a quick issue-spotting plan in the margin is the single most reliable way to lift a grade, because the marks in a problem question are distributed across the issues — and you only score on the issues you actually identify and address.
Stuck on a law problem question or essay? Our law-qualified writers structure problem answers and essays using IRAC, with proper OSCOLA citation and current authority.
The IRAC cycle, issue by issue
For a problem question with several issues, you run the IRAC cycle once per issue and then draw the threads together. Visualising it as a repeating loop stops you from blending issues into one undifferentiated discussion.
Using IRAC under exam conditions
In timed exams, IRAC is as much a time-management tool as an analytical one. Spend the first few minutes issue-spotting — reading the facts twice and listing every legal issue — before you write, because the marks are distributed across the issues and you only score on those you identify. Then budget your time in proportion: a quick IRAC on the obvious issues, and the bulk of your time on the genuinely contested ones.
Under pressure, students often over-write the Rule (which they have revised) and under-write the Application (which requires thinking on the spot). Resist this: a concise statement of the law and a rich application to the facts scores far better than the reverse. A brief plan in the margin — issues listed, key authorities noted — is the single most reliable way to lift an exam grade.
Phrases that strengthen your application
Because application carries the marks, the language you use to connect law and facts matters. Certain phrasings signal genuine legal reasoning to a marker. Use connective phrases that tie the rule to the facts: ‘Applying this to the facts…’, ‘Here, because X…’, ‘This is analogous to [case], where…’, ‘By contrast with [case]…’, and ‘On balance, a court would likely find…’.
Equally, signal a two-sided argument with ‘It could be argued that… however, the better view is…’. These phrases force you to apply rather than restate, and they make your reasoning explicit. Avoid bald assertions (‘the defendant is liable’) without the reasoning that gets you there — the marker rewards the journey, not just the destination.
Key takeaways
IRAC turns messy facts into a clear legal argument: identify the Issue, state the Rule with authority, Apply it to the facts from both sides, and reach a reasoned Conclusion — repeating for each issue and weighting your time towards the contested ones. The marks live in the application, so tie every point to a fact and to authority, argue both ways where the law is uncertain, and avoid long descriptive passages of rule or fact. Used well, IRAC is not a rigid template but the natural shape of sound legal reasoning, in essays, problem questions and exams alike.
Related guides
Frequently asked questions
What does IRAC stand for?
Issue, Rule, Application and Conclusion. You identify the legal issue, state the governing rule with authority, apply it to the facts, and reach a reasoned conclusion. Repeat for each issue the problem raises.
What is the difference between IRAC and ILAC?
They are essentially the same method. ILAC uses ‘Law’ in place of ‘Rule’ (Issue, Law, Application, Conclusion) and is common in Australia. CIRAC adds a conclusion at the start. Use whichever your law school teaches, consistently.
Which part of IRAC carries the most marks?
Application. Identifying the issue and stating the rule are necessary, but the marks concentrate in applying the rule to the specific facts and arguing the outcome — ideally from both sides where the law is uncertain.
Can I use IRAC for essay questions as well as problem questions?
Yes, though essays need more critical evaluation woven through. IRAC gives the backbone; for essays you add analysis of why the law is as it is and whether it is satisfactory. For problem questions, IRAC is the natural structure.
How do I handle a problem question with several issues?
Run a separate IRAC cycle for each issue, in a logical order (duty before breach, for example), signpost each clearly, weight your words towards the contested issues, and finish with an overall conclusion advising the party.
Can someone help me structure a law problem question?
Yes — our law-qualified writers structure problem answers and essays using IRAC with proper OSCOLA citation and current authority. See our law assignment help page or place an order.
Need a problem question or law essay structured and written by a law-qualified writer? Place an order or explore our law assignment help — rated 4.4/5 across 871 verified Trustpilot and Sitejabber reviews.
