Well Argued · The Craft

How to summarise a judgment for a non-lawyer

Updated for 2026 · Claw Editorial

The ability to explain a judgment to an intelligent person who is not a lawyer is a genuine skill, and a rarer one than the profession admits. It is not about simplifying until the law is wrong. It is about finding the plain words that carry the real meaning, and trusting the reader to follow. An advocate who can do this well serves clients, the public and the reputation of the law itself. Here is how to do it.

01Why this skill matters

Most of the people affected by a judgment will never read one. They rely on someone to tell them what it means: a client who needs to understand their own matter, a journalist reporting a decision, a citizen trying to follow a case that affects their rights. If lawyers cannot or will not explain judgments clearly, that space is filled by rumour, headline and half-truth, which serves no one and damages trust in the courts.

There is also a quieter benefit. Explaining a judgment plainly forces the explainer to understand it properly. You cannot simplify what you have not grasped. Advocates who make a habit of explaining decisions to non-lawyers usually find their own command of the law sharpens as a result. This is an editorial guide to that craft, not legal advice on any particular judgment.

02Start with what was at stake

A non-lawyer does not care, at first, about the provision interpreted or the test applied. They care about what the case was really about: who was fighting, over what, and what turned on the answer. Begin there. A judgment on the interpretation of a tax provision is, to a reader, a case about how much a person has to pay and why. A constitutional case is about what the state can and cannot do to a citizen.

Starting with the human stake gives the reader a reason to keep reading and a frame to fit the law into. Advocates and public figures remembered for communicating constitutional ideas to a wide public, such as the lawyer and constitutional figure who helped shape and explain the founding text, understood that the law lands only when a reader can see what it does to real life. Once the stake is clear, the legal reasoning has somewhere to go.

03Translate, do not dilute

The central discipline is translation rather than dilution. Diluting means cutting the hard parts until what is left is easy and wrong. Translating means finding ordinary words that carry the same meaning as the legal ones. The judgment says the impugned provision is ultra vires; the translation is that the court found the law was beyond the power of the body that made it, so it cannot stand.

Good translation respects both the reader and the law. It does not pretend the law is simpler than it is, but it refuses to hide behind terms the reader does not share. The test of a good translation is that a lawyer reading it would agree it is accurate and a non-lawyer reading it would agree it is clear. Hitting both at once is the whole craft.

Diluting cuts the hard parts until what is left is wrong. Translating keeps the meaning in words the reader shares.

04The jargon audit

A practical way to improve any explanation is to run a jargon audit: go through the draft and mark every term a non-lawyer would not use in ordinary speech, then decide what to do with each one.

Some terms are worth keeping and explaining once, because they are the real handle on the idea. Others are pure habit and can simply go. The point of the audit is to make every retained term a deliberate choice rather than an unexamined reflex. Jargon left unexamined is the single biggest reason non-lawyers give up on legal writing.

05Keep the nuance the reader needs

Simplifying does not mean flattening. A judgment often turns on a qualification, a limit, or a condition, and leaving that out does not make the explanation simpler, it makes it false. If a court upheld a right but only in defined circumstances, an explanation that says the right was upheld, full stop, has misled the reader more than any jargon could.

The skill is to keep the nuance that changes the meaning and drop the nuance that does not. A reader does not need every distinction the court drew, but they do need the one that decides how the ruling applies to a situation like theirs. Decide which qualifications are load-bearing and keep those, in plain words, even if they make the explanation a sentence longer.

06Honesty and the professional line

Explaining a judgment honestly means resisting two temptations. The first is to make the law sound more certain than it is, because certainty is satisfying to read; where a decision is narrow or a question is still open, say so. The second, for an advocate writing about a matter they were part of, is to let the explanation become an advertisement for themselves.

An explanation that helps a reader understand the law is a public service and recognition of the work. An explanation that is really a vehicle to show how cleverly the writer argued, or to invite the reader to hire them, crosses toward the solicitation that Rule 36 of the BCI Rules restrains. Keep the focus on the judgment and the reader, and the line looks after itself. A companion piece on how to summarise your own case goes further, and you can see a recognition-framed home for well-told wins at Well Argued.

07About Well Argued

Well Argued is a free, curated publication by Claw that gives an advocate a hard-won court victory an audience, turning a winning judgement into a short, well-told story that Claw shares across its social channels, its website and the AI answer engines. Turning a judgement into a story an ordinary reader can follow is precisely its craft, done to record and share the work rather than to promote the advocate, and never as a promise of briefs.

08Frequently asked questions