You know the topic. You can name a few cases. Yet the moment a business law problem question lands in front of you, your answer turns into a pile of definitions.

Half a page in, you realise you have described the law without answering anything.

That gap is rarely about knowledge. It is about what you do with it once you have it.

A problem question is not asking what you know. It is asking what the law means for these people, in this mess, right now.

Here is a practical way through it.

1. Start With What the Question Is Really Asking

Picture a business that pays for machinery. It arrives six weeks late. Production stalls, a customer cancels, and the owner starts talking about legal action.

Most people spot “breach of contract” and stop there. That is the easy part.

The real questions sit underneath. What exactly did the contract promise? Did the date matter in law? And what can the business realistically recover?

Facts in a problem question are never decoration. Every date, email and change of order is there because it might shift the outcome.

The supplier’s good reputation probably is not relevant. The signed delivery clause almost certainly is.

2. Why Good Knowledge Still Produces Weak Answers

Here is what usually happens. You recognise the area, so you write down everything you remember about it. The page fills quickly, which feels like progress.

It is not. The legal analysis has not even started.

Two habits cause most of the damage.

The first is mixing up a rule with its effect. Proving a breach does not automatically let the buyer walk away, or claim every pound lost.

The second is ignoring the other side. Perhaps the supplier says the buyer changed the specification a week before delivery. That alters the picture, and a one-sided answer misses it.

Strong answers do not hide uncertainty. They point to it and explain why it matters. Was the date expressly agreed? Did the buyer accept the late goods? Were the losses foreseeable?

3. IRAC Works Best When You Use It Like a Lawyer

IRAC stands for Issue, Rule, Application and Conclusion. It keeps your reasoning in order.

• Issue: what legal question needs answering?
• Rule: which principle governs it?
• Application: how do these facts meet, strain or break that rule?
• Conclusion: what outcome is best supported?

Application is where your reasoning becomes visible. Saying a supplier must deliver on time shows knowledge. Explaining why delivery after an expressly agreed date may be a breach shows understanding.

Whether you are working alone, with a study group or through a Business Law Assignment Service, the standard to aim for is the same: connect the rule to the facts instead of listing law.

Do not let IRAC make your writing robotic. If a question raises three issues, work through it three times and keep each one self-contained. Headings are optional. The thinking is not.

4. The Habit Most Guides Skip: Work Backwards From the Remedy

Most advice says start with the issue. I get cleaner answers by starting somewhere else: what does this party actually want?

A buyer might want to cancel, claim damages or simply receive the goods. Each goal sends you down a different legal route.

In the late machinery case, the buyer’s real aim may be to recover profit lost on the cancelled order. That is a question about damages, and it needs a proper test.

Under the approach associated with Hadley v Baxendale, contractual losses may be recoverable if they arise naturally from the breach, or were reasonably within both parties’ contemplation when the contract was made because of known special circumstances. The analysis should also consider causation and whether reasonable steps were taken to limit the loss.

So ask: did the supplier know the machinery was needed for that customer’s order? Did the buyer try to source a replacement quickly?

Before writing, build a quick three-column fact map:

• Fact: what happened, with the date or wording.
• Legal hook: which rule it touches.
• So what: how it changes the outcome.

If a fact does not connect to a legal issue, give it little space. Background should explain the dispute, not distract from it.

5. Turning Your Notes Into a Clear Answer

Read the scenario twice. First, get the story. Second, mark dates, promises, payments, written messages and changes to the deal.

Then build each paragraph in the same order:

• State the specific issue.
• Give the rule or authority.
• Tie it to the facts.
• Weigh the opposing argument.
• Land a provisional conclusion.

Never leave a rule in one paragraph and its relevance three paragraphs later. If the contract names a delivery date, explain why that wording matters before you discuss the delay.

Check jurisdiction as well. English law and Scots law are not interchangeable, and mixing them looks careless.

Cases need a job. Name the principle, then show how closely the facts match. A case name on its own adds nothing.

6. Mistakes That Quietly Cost Marks

Some weaknesses hide behind detail.

• Too much background. If the scenario clearly shows a contract exists, do not spend a paragraph on how contracts form.
• Treating every fact as equal. The owner’s anger explains the dispute. The contract terms decide it.
• Forced certainty. If the facts support two readings, say so. Honest weighing beats bold guessing.
• Ignoring the instruction word. “Advise” wants practical judgement. “Critically evaluate” wants limits and competing views.
• Claiming loss without proving it. Think causation and remoteness, not just the figure.
• Repeating the scenario. Quote a fact only to analyse it.

7. Bringing It Together: A Final Check Before You Submit

Read your answer as if you were the other party’s adviser. Where would you attack it?

Then ask three things:

• Could a reader who has not seen the scenario follow every fact I rely on?
• Does every case I mention change my conclusion?
• Have I said what would happen if one key fact were different?

That last question separates a decent answer from a confident one. A single sentence such as “if the date was only an estimate, the position weakens” shows you understand how fragile legal outcomes can be.

A strong answer is not judged by how many cases or terms it holds. It is judged by the reasoning that connects them.

Find the real dispute. Choose the rules that address it. Test the facts. Consider what the other side would say. Then reach a conclusion that matches the strength of your evidence.

A problem question is rarely asking you to prove one party entirely right. It is asking you to explain the legal position as accurately as the facts allow.

Each rule has a purpose. Each fact has a place. Each conclusion follows from what came before.