You turn the page and there it is. Three dense paragraphs, a broken contract, a vague verbal promise, and three people all blaming each other.

The names blur. The timeline jumps about. Your pulse picks up.

Here is what is worth knowing: that panic says nothing about how well you know the law. It usually means you are reading the facts as a story when you should be reading them as evidence.

Problem questions do not test how much you can remember. They test whether you can find the legal dispute hiding in the noise and deal with it in an orderly way. That is exactly what IRAC is for.

What IRAC Is (and What It Is Not)

IRAC stands for Issue, Rule, Application, Conclusion. Some UK law schools call it ILAC, others use a close cousin. The label does not matter. The order of thinking does.

Treat it as a template to fill in and your answer will read like a form. Treat it as a way of thinking and it reads like advice from someone who knows the area.

In plain terms:

• Issue: what are the parties really fighting over?
• Rule: what is the legal test?
• Application: how do these facts measure up against it?
• Conclusion: where does that leave the person you are advising?

1. Issue: Find the Legal Spark

Raised voices in a café are drama. Whether an assault took place is law. Your job is to translate one into the other.

The trap is the lazy issue: “Can John sue Sarah?” It tells the marker nothing.

The fix is to tie the legal test to the one fact that causes the problem. For example: “Whether a pop-up food vendor owes a duty of care to a customer injured by an unlabelled allergen in a pre-packaged snack.”

That single sentence names the claim, the parties’ roles and the factual hook. Markers notice.

2. Rule: Lean Law, Not Lecture Notes

State the test, add any key exception, cite the authority. Then stop.

Copying out half a statute, or narrating every fact of a nineteenth-century case, burns time and earns nothing. A good rule of thumb: if you will not use it in the next paragraph, it should not be on the page.

This is also why so many people go looking for professional law assignment writing help the night before a deadline. They are rarely short of knowledge. They are short of a method, and a method is something you can build in an afternoon.

3. Application: Where the Marks Live

If IRAC were an engine, this would be the horsepower. It is where law and facts finally collide.

Do not retell the story. The examiner wrote it and knows it. They want to see what you make of it.

Take each element of the rule and test it against the facts, one at a time. If the rule asks whether harm was “reasonably foreseeable”, explain why an ordinary person in that position would, or would not, have seen it coming.

Grey areas are your friend. Real disputes are rarely one-sided, so show both sides: “The defendant may argue X, but the facts point more strongly towards Y because…” That one move signals legal thinking.

The Technique Most Guides Leave Out: The Fact-to-Element Map

Before you write a word, draw two columns. On the left, list each element of the legal test. On the right, jot down the facts that touch it, including the ones that cut against your view.

Anything in the scenario with no home on the map is probably a distraction or a hidden issue. Anything on the left with no facts beside it is a gap, and you should flag it openly.

This takes about five minutes and does three jobs. It stops you retelling the story, it makes sure no element gets skipped, and it hands you the counter-arguments ready made. Most lost marks in problem answers come from skipped elements, not wrong law.

Two habits sit well alongside it:

• The “because” test. Every sentence of application should contain a “because”. If it does not, you are probably describing, not analysing.
• One mini-IRAC per claim. With several parties, run a separate pass for each claimant against each defendant, in the order the facts raise them. It keeps a crowded scenario from collapsing into a muddle.

4. Conclusion: Land It Quietly

Your ending should feel like the natural result of everything before it.

Answer the question you asked in the Issue. Say who has the stronger case and what outcome is most likely. No new facts, no fresh legal theories in the final sentence.

Hedge honestly. “Likely” and “on balance” are fine. A coin toss and false certainty both lose marks.

A Worked Example

Scenario: Marcus buys a cold-pressed juice from an independent deli. The bottle is factory-sealed. A few sips in, he suffers a severe throat reaction caused by a harsh cleaning chemical left inside during manufacturing. Can he claim against the bottler?

Issue: Whether the bottling company owed and breached a duty of care to Marcus, as ultimate consumer, for injury caused by chemical residue in a factory-sealed bottle.

Rule: Under Donoghue v Stevenson [1932], a manufacturer owes a duty of care to the ultimate consumer where the product reaches them in the form it left the factory, with no reasonable chance of intermediate inspection. Breach is measured against what a reasonable producer would do.

Application: The bottle was sealed at the factory, so neither the deli nor Marcus could realistically inspect it. Leaving industrial cleaner inside a drinks bottle falls plainly below accepted hygiene standards. The injury flowed directly from the contaminated juice, so the harm was foreseeable and causally linked.

Conclusion: Marcus has a strong negligence claim and is likely to recover damages for his injury and medical costs.

A UK bonus point: the Consumer Protection Act 1987 deserves a line here too. Liability for defective products under that Act does not depend on proving fault, which can make it the stronger route. Spotting the statutory alternative is the sort of detail that lifts an answer.

Making It Sound Natural

First attempts feel stiff. That is normal, and it simply means the structure is working.

As you get comfortable, drop the labels and let transitions carry the logic:

• “Applying this test to the present facts…”
• “The defendant may point to [case], but that authority is distinguishable because…”
• “Because both elements are satisfied, liability will likely attach unless…”

IRAC is not a trick. It is a habit, and habits are built by repetition. Take one old problem question this week, build the fact-to-element map, and write it out in full.

Do it three times and the wall of text stops looking like a wall. It starts looking like a list of questions you already know how to answer.