Legal English register: sounding like a lawyer in your second language

You can have perfect grammar and still not sound like a lawyer. Register is the missing layer: the set of choices about formality, caution and sentence shape that mark writing as legal writing. It is the hardest layer to learn from textbooks, because native speakers absorb it by imitation and rarely explain it. This page explains it.

The core idea: written legal English is a different dialect from spoken English, and the two do not mix. A phrase that is normal in a tutorial discussion ("the judge basically said the contract was dodgy") is a register error in a memorandum, even though every word in it is correct English. The reverse is also true: writing "it is submitted that" in a conversation would sound absurd. Your job is not to be formal everywhere. It is to know which room you are in.

1. Hedging: how lawyers are careful on purpose

New legal writers, and especially writers working in a second language, tend to either overclaim ("the defendant is clearly liable") or underclaim into vagueness ("maybe the defendant might possibly be liable"). Legal English has a middle register of professional caution, and it runs on a small set of fixed phrases:

• It is arguable that the exclusion clause does not cover deliberate breach.
• The court is likely to find that a duty of care existed.
• On balance, the stronger view is that the notice was invalid.
• It is submitted that the respondent's construction should be preferred.
• The clause appears to operate as a penalty.

Notice what these do. They commit to a position while honestly marking its strength. "Clearly" and "obviously" are the words to cut: if the point were clear, you would not be writing an advice about it, and markers read those words as a substitute for reasoning. Conversely, stacking hedges ("it could perhaps be argued that it may be possible") signals fear rather than caution. One hedge per claim, chosen to match how strong the claim really is.

Modal verbs carry precise weights in this register: must (obligation or certainty), will (confident prediction), should (recommendation or expectation), may (permission or real possibility), could (weaker possibility). Choosing between "the court will find" and "the court may find" is a legal judgment, not a style choice. Make it deliberately.

2. Formality: the floor, not the ceiling

Some choices are simply mandatory in written legal English:

• No contractions. "The defendant didn't respond" becomes "the defendant did not respond". This is the fastest register fix available, and markers notice it immediately.
• No conversational vocabulary. "The deal fell through" becomes "the agreement was not completed". "Got" almost always has a more precise replacement: obtained, received, became.
• Precise connectives. Spoken English links ideas with "so", "also" and "but". Written legal English prefers "accordingly", "therefore", "further", "however", "nevertheless", placed at the start of the sentence or after the subject. These are not decoration; they tell the reader the logical shape of your argument before they read it.
• Full forms of reference. In conversation, "the judge" covers everything. On the page, refer to a judge by surname and title abbreviation on first mention ("Gordon J", "Kiefel CJ", said aloud as "Justice Gordon" and "Chief Justice Kiefel"), and by "his Honour" or "her Honour" in the sentences that follow. Refer to the court deciding the case as "the court"; many firms and mooting guides capitalise "the Court" when it is the court you are addressing. Never "the judge said".

Formality has a ceiling too. Antique legalisms ("hereinbefore", "the said contract", "aforementioned") do not make writing more legal; modern Australian legal writing has largely abandoned them, and plain "the contract" or "that clause" is preferred. Aim for formal and plain at the same time. They are not opposites.

3. Nominalisation: the double-edged tool

Nominalisation turns a verb into a noun: decide becomes decision, breach (verb) becomes breach (noun), fail becomes failure. Legal English genuinely uses more nominalisation than everyday English, and some of it is load-bearing: "the breach", "the failure to warn" and "the exercise of the discretion" are how law names its objects so it can analyse them.

The register skill is knowing when it helps and when it suffocates. Compare:

• Dense: "The implementation of the termination of the agreement was effected by the respondent."
• Clear: "The respondent terminated the agreement."

The second is just as formal and far stronger. A working rule: nominalise to name a concept you are about to discuss ("the termination was invalid because..."), and keep a real verb when you are reporting who did what ("the respondent terminated the agreement on 1 March"). If your first language builds formality through noun-heavy structures, watch this pattern especially; the habit transfers, and English tolerates less of it than it first appears to.

4. Reporting verbs: held, found, submitted

Legal English spreads the work of the everyday verb "say" across a set of precise verbs, and the choice between them is read as legal analysis, not style. Getting them right is one of the fastest ways to sound like a lawyer; getting them wrong can misdescribe the authority you are citing.

For courts:

• held: the court's binding answer to the legal question before it. "The court held that the clause was void." Reserve this for the decision itself.
• found: a finding of fact. "The court found that the letter was posted on 1 March." Facts are found; law is held.
• observed or noted: a comment made along the way that was not the decision. Useful when you rely on a remark rather than the holding, and honest about its weight.
• considered: the court examined an issue or an earlier authority, without yet saying what it concluded.

For parties and writers:

• submitted: the standard verb for a formal argument put to a court, and the verb inside the fixed phrase "it is submitted that" for your own position.
• contended or argued: a party's position, stated neutrally.
• conceded: a party accepted a point that did not help its own side. The verb carries that meaning by itself; you do not need to add "reluctantly".
• denied, asserted, maintained: each marks a different posture toward a claim.

The verbs to avoid: "the court said" and "the judge talked about" are conversational and hide the thing a legal reader most wants to know, which is whether the statement was the decision or a passing comment. "The plaintiff thinks" and "I feel" are register errors with a one-step fix: "the plaintiff contends", "it is submitted that".

If your first language covers most of this territory with one general verb of saying, this set has to be learned as vocabulary, the same way you learned the fixed phrases in section 1. It is a short list, and markers reward it out of proportion to its size, because writing "held" for something that was actually an aside does not just sound wrong. It overstates the authority.

5. Spoken versus written: a quick translation table

A worked example

Here is a paragraph in competent spoken register, the kind you might say aloud in a tutorial:

> The supplier basically ignored the delivery date, so we think the buyer's got a pretty good case. The contract doesn't say anything about late delivery, but courts don't usually let people get away with that.

And the same paragraph in written register:

> The supplier failed to deliver by the date fixed in the contract. It is submitted that the buyer has a strong claim. Although the contract is silent on late delivery, a court is unlikely to excuse the delay.

The moves, one by one:

• "basically ignored" becomes "failed to deliver by the date fixed in the contract": the conversational verb is replaced by a precise one, and the vague complaint becomes a specific, checkable statement.
• "we think" becomes "it is submitted that": the fixed phrase from section 1, marking a position rather than a feeling.
• "a pretty good case" becomes "a strong claim": same meaning, formal vocabulary, no intensifier padding.
• "doesn't say anything" becomes "is silent on": the contraction goes, and the standard legal collocation arrives.
• "courts don't usually let people get away with that" becomes "a court is unlikely to excuse the delay": a deliberate hedge ("unlikely to") replaces the conversational generalisation, and the vague "that" becomes the specific "the delay".

Notice what did not change: the argument. Register translation restates your claim in the written dialect; it does not make the claim true. Whether a court really would take that view is the legal question, and answering it is still your job.

A self-check before you submit

1. Search your draft for apostrophes: every contraction goes.
2. Search for "clearly", "obviously" and "basically": delete or replace with reasoning.
3. Find your three longest sentences and check whether a buried verb ("make a decision", "effect a termination") can become a real one (decide, terminate).
4. Check every "the court said" and every "I think": replace with the precise reporting verb (held, found, observed, submitted, contends).
5. Read your conclusion aloud. If it would sound normal spoken across a table, it is probably under-formal; if you stumble over it, it is probably over-nominalised.

Register is learnable. It is a finite set of habits, not a talent, and every draft you check this way builds it a little more permanently.

If you want feedback on register in your own writing, Legal Writing Lab is a free feedback tool for international law students writing Australian legal English. It flags formality and clarity issues in your draft, explains each one, and never writes your work for you. Your words stay yours.