Tiptoeing Around “Nonlawyer”

I’ve previously written about the word nonlawyer, in this 2020 blog post. Prompted by something I posted on LinkedIn yesterday (here), I thought I’d try again, to reflect a further thought. So this post is my definitive take, until my next nonlawyer post!

I think what Julie Savarino says in this LinkedIn post (see also Julie’s follow-up post here) captures the prevailing argument against nonlawyer:

Let’s all stop using “NON-LAWYER”! John Croft, President & Co-Founder of Elevate Services told me he is often called or referred to as a “non-lawyer” to his face, which can be implicitly insulting & offensive. He said, “I am also a non-doctor, non-architect & a non-veterinarian but no one ever calls me that.” Just because he did not go to #law school or pass the bar does not make him (or anyone else) “less than” a #lawyer. A better term to use is “business professional” or “allied business professional”.

I stand by what I said in my 2020 post:

Regarding nonlawyer—please, no hyphen!—I see why people object. Generally, it’s not great to define people by what they aren’t. So instead of calling someone a nonlawyer, you could refer to them by what they are. A contract manager. A paralegal. A businessperson. Whatever. And when referring to a group of such people, something like support staff might be appropriate, depending on the context.

But that’s not always going to work. Specifically, today’s [other blog] post aims to rebut the notion that only lawyers should be responsible for contract drafting. That notion inherently divides the world into lawyers and others. It follows that in rebutting that argument, I have to refer to the “others” group. It would be impossible for me to refer to each of the functions that together constitute the “others” group.

In that post, I also say “I could say ‘people who aren’t lawyers,’ but that expresses the same meaning as nonlawyer, just with more words.” That’s what I’d like to revisit in this post.

The difference between nonlawyer and people who aren’t lawyers is that in the former, the not-a-lawyer status swallows the person, whereas in the latter, the person comes before the not-a-lawyer status.

People care about this sort of messaging. This is from a study on Dutch preferences regarding whether to say autistic person or person with autism (here):

There are different words to describe people with an autism diagnosis. For instance, we can put the person before autism (e.g. ‘person with autism’), or we can put autism before the person (e.g. ‘autistic person’). Previous research showed that autistic adults in English-speaking countries generally liked it better when autism is placed before the person.

I think it’s safe to say that because it’s unlikely that someone would base their sense of self on not being a lawyer, it would be odd for anyone to prefer nonlawyer over people who aren’t lawyers. Furthermore, nonlawyer is more clumsy than autistic person.

So I recommend you use nonlawyer only as an adjective in those contexts where nonlawyer affords meaningful economy or is already enshrined in regulations. For example, in the phrase nonlawyer ownership. Instead of the noun nonlawyer, say people who aren’t lawyers or those who aren’t lawyers, or some variant.

So that’s my current understanding regarding nonlawyer. Thank you for indulging me in thinking it out publicly. My thanks to Elizabeth de Stadler for gently easing me down the right path.

While I’m on the subject, the shortcomings of nonlawyer can perhaps be found in other words and phrases that express what people aren’t. Consider the phrase that prompted yesterday’s LinkedIn post—non-native English speaker. Like nonlawyer, it prioritizes the lack over the person. Because it’s unlikely that anyone would base their sense of self on not having English as their first language, say instead those whose first language is other than English, or some variant. But beyond that, it seems unhelpful to turn learning a second language into a negative. I suspect there’s extensive polemic on this issue; go here for just one example. And while we’re at it, native could be understood as having unhelpful connotations. So there’s no shortage of reasons not to use non-native English speaker.

(For the six of you who care about such things, I included a hyphen in non-native English speaker because of the potential for a reader miscue if you omit it—the reader might momentarily think it’s a different word, nonn-ative. But that’s not a hill I wish to die on!)

About the author

Ken Adams is the leading authority on how to say clearly whatever you want to say in a contract. He’s author of A Manual of Style for Contract Drafting, and he offers online and in-person training around the world. He’s also head of Adams Contracts, a division of LegalSifter that is developing highly customizable contract templates.