• Skip to main content
Checklist Legal logo
  • Innovation
  • Services
    • Build your client base
    • Sell your Services + Products
    • Protect your business + your team + your clients
    • Speaker
    • Pro Bono Program
  • Resources
    • Blawg
    • Book
    • Listen
  • Events
  • Mission & Values
    • Our Mission & Values
    • Our Impact
Get in Touch

Plain Language and Government Contracts

Dealing with a tricky government contract you want to simplify? Government lawyers pushing back on your updates to their agreement?

Whilst the preferred term is Plain Language (because it’s more inclusive)…the Office of Parliamentary Counsel’s Plain English Manual is filled with gems on explaining terms to clients, phrases to avoid with examples on clear writing, and interpretation tips.

“The Office of Parliamentary Counsel is active in encouraging the use of plain language in legislation and in developing and using plain language techniques. In addition to OPC’s participation in major plain language projects such as the Tax Law Improvement Project and the Corporate Law Economic Reform Program, we have incorporated plain language drafting into all of our work. This Manual outlines some of the techniques we use”

One of my favourites is the support for ditching Shall in favour of Must (if you want to impose an obligation)

What do you think? Could this help negotiate with Government (and other) lawyers? Do your contract guides meet these suggestions? Let me know what you think!

Cheers,

Verity

Some extracts from the Manual below or see the full document here:  Plain English Manual

“Contravene or fail to comply”

  1. In the traditional style, “contravene” is treated as not covering omissions.  This was probably never right (see R v Commonwealth Court of Conciliation and Arbitration 89 C.L.R. 636 at 649), but the position has been put beyond doubt by paragraph 22(1)(j) of the Acts Interpretation Act.

Example don’t say “contravene or fail to comply with” say “contravene”.

“Shall”, “must” and “is to”

  1. The traditional style uses “shall” for the imperative. However, the word is ambiguous, as it can also be used to make a statement about the future. Moreover, in common usage it’s not understood as imposing an obligation.

Say “must” or “must not” when imposing an obligation, not “shall” or “shall not”.

If you feel the need to use a gentler form, say “is to” or “is not to”, but these are less direct and use more words.

We shouldn’t feel any compunction in using “must” and “must not” when imposing obligations on the Governor‑General or Ministers, because “shall” and “shall not” were acceptable in the past.

Categories

  • B Corp Life (2)
  • Business Legals (20)
  • Client Stories (4)
  • Events (12)
  • Femme Founders (29)
  • Fun (7)
  • In-House Life (5)
  • Legal Design + Innovation (50)
  • News (9)
  • Online Business Legals (2)
  • Podcast (12)
  • Ponderings (16)
  • Professional Development (35)
  • Publication (9)
  • Simplifying Legals (6)
Banner linking to contract resources
Checklist Legal logo
  • Home
  • The Blawg
  • Events
  • The Book
  • Femme Founders Resources
    • Femme Founders
    • One Roof Member Expert
  • Legal Legends Resources
    • The Podcast
    • The Book
    • Articles
  • Mission & Values
    • Our Mission & Values
    • Our Impact

We acknowledge the Wurundjeri and Boon Wurrung people as the Traditional Owners and Custodians of Country on which we work. 

Checklist Legal supports the Uluru Statement from the Heart to achieve justice, recognition and respect for First Nations people and a referendum to enshrine a First Nations Voice in the Constitution.

Checklist Legal © 2022

Owned by Verity White Rebels Family Trust (100%), Verity White is the Sole Director.

  • Privacy
  • Legals
  • Sitemap

Terms of use