If you want to draft a document in standard English, what can you do?

If you are a transactional lawyer, and you now believe you have room to improve the language of the forms you use, here are my recommendations:

1. Get Adams’s Manual of Style for Contract Drafting.
Although it might be a while before you have the time to read Adams’s book straight through, you can immediately begin using it as a reference. You’ll learn a lot that way, plus it will help settle language disputes.

You’ll also found the following reference valuable:

• Bryan A. Garner, A Dictionary of Modern Legal Usage (2d ed., Oxford U. Press 1995).

It will help you master the subtleties of legal language.

2. Turn off autopilot.
Your standard forms can sometimes foster haste and laziness. Never rely too heavily on the form or assume all you need to do is change the names and change the dates. Get to know every provision in your document. Proofread carefully. Triple-check.

3. Stay current.
You and others at your office have used this form document as a starting place for years, so what could be wrong? Plenty. Laws change, and so do contracting practices. Know what you need and what you don’t need in the document. No matter the source of the form, there’s no substitute for learning, on your own, what the law requires for the transaction you’re documenting.

If not in plain English, then what?

So if plain English is not right or cost effective for every document—especially large transactions with competent lawyers—what is the proper style for modern transactional drafting? According to Kenneth Adams, the leading expert on the subject, it’s called “standard English,” and he details that standard in his book, the only comprehensive style guide for transactional drafting:

• Kenneth A. Adams, Manual of Style for Contract Drafting (2d ed., ABA 2008).

Adams is careful not to use the phrase “plain English.” His Manual is not directed at those who write consumer-credit disclosures, website disclaimers, and the “limitation of liability” on the back of a baseball ticket. He is speaking to lawyers who prepare complex contracts for business clients.

What is “standard English”?

Adams says standard English is “English as used by educated native speakers.” Adams, A Manual of Style for Contract Drafting at xxvi. He’s in full agreement with me that the content of complex contracts need not be conveyed in plain English: “Using standard English has nothing to do with dumbing-down contract prose to make it accessible to the nonlawyer.” Id. For Adams, and for me, plain English applies to “the simplified language of consumer contracts.” Id. at xxvii.

But Adams also insists that the language of modern contracts is dysfunctional. It abounds with “deficient usages . . . flagrant archaisms, meaningless boilerplate, redundant synonyms . . . inefficient layout, and so forth.” Id. at xxv. He aims to motivate you to improve your drafting—make it standard English—and then he tells you how.

If you need to draft in plain English, what can you do?

There will be times you’ll need to draft in plain English. A corporate client needs a revised employee manual. Your supervisor asks you to draft a disclaimer for the firm’s website. A nonprofit organization you represent needs a basic contract. Or you need to write the “forepart” of an SEC registration statement, which, since 1998, must be in plain English.

So here are three recommendations for getting up to speed on plain English:

1. Read up on it.
Get familiar with the literature in the field. Yes, I’m going to plug my own book here:

• Wayne Schiess, Plain Legal Writing: Do It.

But here are two other excellent sources for expert guidance on plain-English writing:

• Joseph Kimble, Lifting the Fog of Legalese: Essays on Plain Language (Carolina Academic Press 2006).
• Rudolf Flesch, How to Write Plain English: A Book for Lawyers and Consumers (Harper & Row 1979).

These books will take you beyond simple mantras like “dumb it down” and “write it so your mother could understand it.” They’ll give you concrete, reliable guidance on revising traditional legal language into plain English.

2. Assess yourself.
You can use your word processor to assess the plainness of your text. It will measure the average sentence length—aim for 20 or below. It will tell you the Flesch Reading Ease Score, which ranges from 0 to 100; the higher the score, the easier the text is to read. And it will tell you the Flesch-Kincaid grade level: the numbers of years of schooling a reader would need to understand the text; a passage with a higher score is harder to read.

To do this in Word 2007, find the “Office” button—on the top left with the multicolored logo—then:

• select Word Options > Proofing
• find the section called “When correcting spelling and grammar in Word”
• check the box for “Check grammar with spelling”
• check the box for “Show readability statistics”

While you’re there, consider clicking “Settings” and unchecking all (or most of) the grammar and punctuation items. This will prevent you from having to go through a grammar-check every time you run a spell-check. The grammar check is not a useful tool. Now, each time you spell-check, you’ll get a statistical analysis of your text.

The analysis will show your average sentence length and the numerical Flesch scores. Remember, these scores come from a computer algorithm that measures words and sentences and has no human insights; it can’t tell sense from nonsense.

But if you’ve written a document intended for nonlawyers that has a Flesch-Kincaid Grade Level of 19 (that’s college plus three years), you should probably work on simplifying the text. Likewise, since a Flesch Reading Ease score of 60 is “plain,” if your Flesch Reading Ease Score is in the 20s or 30s (even the 40s might be tough for nonlawyers), it may be time for some pruning and revising.

3. Test your text.
Ask a trusted friend or relative who is not a lawyer to read the text. Then ask follow-up questions. Or ask where the reader got lost or felt “legalese” creeping in. Then revise accordingly.

The cost of revising forms into plain English.

In fact, revising all your form documents into plain English may be unrealistically expensive and time-consuming. Who’s going to pay for it?

Revising complex legal documents into plain English is taxing, tedious, and slow. The resulting plain-English only looks like it was easy to write. In reality, the process has several steps and usually requires collaboration. For example, here’s a process I recommend in my book, Preparing Legal Documents Nonlawyers Can Read and Understand:

• Read the entire document from beginning to end—taking notes—to get a sense of the content and complexity of the text.
• Create a list of the substantive content of the document. This will help you master the content, and you can use it as a checklist when you revise.
• Sort and order the content list, considering reader needs, the important topics, the order in which the transaction will be carried out, and other considerations. Begin thinking about headings, subheadings, and numbering.
• Rewrite the text in plain English.
• Revise and edit the text.
• Test the text on intended users and ask others to read and comment on the text. Your other readers should include at least one lawyer who is an expert on the subject matter and at least one nonlawyer unfamiliar with the subject matter.

Now imagine that process for a series of complex transactional documents. Again we must ask—who is going to pay for it?

What documents should be drafted in plain English?

Not every transactional document needs to be drafted in plain English—there, I said it. Large transactions between knowledgeable parties who have lawyers do not need to be drafted in plain English. Yes, many plain-English principles would work well in those documents, and we do need to improve the general state of drafted language in our transactions, but true plain English might not be right or cost effective for every transactional document.

Here’s a short list of the kinds of documents that should be drafted in plain English:

• Apartment leases
• Basic contracts
• Consumer regulations
• Credit-card agreements
• Employee manuals and handbooks
• Homeowners’ association bylaws
• Consumer insurance policies
• Jury instructions
• Opinion or advice letters
• Public notices
• Releases
• Software licenses and user agreements
• Website disclaimers
• Wills

For example, you wouldn’t write a brief to a federal judge in the same style you’d use for a report of the case to the nonlawyer client, would you? Likewise, you don’t need to use the same style for a $150 million credit agreement and a $150 contract.