A Manual Of Style For Contract Drafting

Why Nobody Writes Contracts From Scratch Anymore

Most commercial agreements aren't written from scratch. That's the first thing I learned early on, and it's still true. We borrow templates, edit clauses, swap names, and move on. The problem is that when three people edit the same document, the style fragments. One drafter uses "shall" everywhere. Another treats it as plain advice. A third switches to "will" depending on how they feel about enforceability. The resulting contract looks like a patchwork quilt made by people who don't know each other. This is where a writing manual matters. Not as a legal rulebook, but as a style guide for the actual words on the page. I've spent years dealing with contracts that fell apart not because of bad legal terms but because of inconsistent drafting conventions. The other side's lawyer spent twenty minutes pointing out that "must," "shall," and "shall be obligated to" appeared in the same agreement, questioning which obligations were actually binding. We couldn't defend it cleanly. That kind of mistake isn't expensive in hours. It's expensive in credibility.

A Manual Of Style For Contract Drafting

The core idea is simple. Define your drafting conventions once and make them non-negotiable. Every person who produces contract language in your organization follows the same rules for capitalization, defined terms, verb tense, and structural hierarchy. When you ship a document, the reader should never have to guess what "Service Provider" refers to or whether "must" means something different from "shall." Consistency reduces ambiguity. Ambiguity creates dispute. I keep my manual focused on practical drafting decisions. Not theory. These are the rules I actually enforce: Defined terms get capitalized the first time they appear in parentheses, then capitalized every time after that. "Agreement" means the executed contract. "agreement" in lowercase is just ordinary speech. This sounds obvious until you're reading a fifty-page SaaS contract and realize the vendor capitalized "Term" in one section and left it lowercase in another. The drafters hadn't decided whether "Term" meant the duration of the contract or just any temporal reference. It created real interpretive risk.

Modal verbs follow a strict hierarchy. "Shall" creates a binding obligation. "Will" states a fact or future outcome. "May" grants permission. "Must" appears only in recitals and definitions where external statutory language already uses it. I've seen contracts where "must" and "shall" were used interchangeably, and the opposing counsel argued that "must" indicated a mandatory statutory requirement while "shall" was merely aspirational. That argument held up under scrutiny because the contract itself provided the opening. Section numbering uses a clean decimal system. 1.1, 1.1.1, 1.1.2. No skipping levels. No jumping from 3 to 3.1.3 without 3.1.1 and 3.1.2. When clauses get deleted during negotiation, the numbering should absorb the gap or the document should use lettered sub-sections consistently. I once inherited a contract where the drafters had deleted entire subsections and left orphaned numbering like 4.2.5 sitting in space. The other side's reviewer flagged it as a sign of sloppy drafting and used that signal to question the completeness of their entire indemnification section. It was a weak argument on its merits, but it created doubt where there shouldn't have been any. Capitalization of common nouns follows a defined-term rule. Only words that appear in the definitions section get capitalized throughout the body. "Confidential Information" is capitalized because it's defined. "confidential information" is correct when discussing the concept generically. Every other noun stays lowercase unless it's a proper name or starts a sentence. This eliminates the endless debate about whether "Product" or "product" carries legal weight in a particular clause.

What This Manual Does Not Cover

The style guide isn't a substitute for substantive legal review. It won't tell you whether your limitation of liability clause is enforceable in Delaware. It won't advise you on whether to use mutual or confidentiality obligations. It doesn't replace a subject-matter expert. What it does is remove one category of error from the process. The category where sloppy drafting creates unintended ambiguity. I learned this distinction the hard way. Early in my career, a client asked me to review a master services agreement before execution. The legal terms were fine. The commercial terms were reasonable. But the drafter had switched between British and American spelling throughout the document. "Obligations" and "obligations" appeared depending on which section they came from. "Authorized" and "authorised" swapped places without explanation. The client's general counsel refused to sign, saying the inconsistency suggested the contract hadn't been properly reviewed. He was right. It hadn't been. The legal substance was sound, but the presentation undermined confidence in the process. The workaround I adopted after that incident was to run a find-and-replace sweep for regional spelling variants before any document went to signature. "ize" versus "ise." "or" versus "our." "ment" versus "men." You'd be surprised how many contracts slip through with mixed conventions. It takes about four minutes in a standard word processor. I do it religiously.

Implementation Without Bureaucracy

A manual only works if people actually use it. The biggest failure mode I've seen is over-engineering. A thirty-page style guide nobody reads is worse than a one-page checklist everyone follows. My current manual is two pages. It covers defined terms, modal verbs, numbering, capitalization, punctuation in lists, and exhibit structure. That's it. Anything beyond that belongs in a training document, not a reference manual. I require every drafter to attach a compliance checklist to new contracts. Not a review process. A simple table where they confirm each convention has been applied. One checkmark per rule. Takes thirty seconds. The checklist gets archived with the executed agreement. When a dispute arises years later and someone asks why a particular term was capitalized a certain way, the checklist shows whether it was intentional or accidental. Automated tools help but they have limits. Grammar checkers catch typos. They don't catch contextual inconsistencies. A spell-checker won't tell you that "Client" is defined in section 1.2 but referenced as "client" in section 8.4. Redlining software shows what changed. It doesn't show what should have changed but didn't. I've set up custom dictionary entries in my word processor for organization-specific defined terms. This catches some errors before they reach the final draft. Most errors still come through manual review.

When the Manual Breaks

There are situations where strict adherence to a style guide creates more problems than it solves. Joint ventures between organizations with different drafting traditions are the most common example. One party writes in blue-lined, heavily defined terms. The other writes in plain language with minimal definitions. No style manual bridges that gap automatically. The drafters have to negotiate which convention dominates, and that negotiation is substantive, not stylistic. Governing law matters too. Some jurisdictions expect certain phrasing conventions. English contracts traditionally use "herein," "thereof," and "aforementioned" more liberally than American contracts. Civil law jurisdictions have their own expectations. If you're drafting for a multi-jurisdictional audience, the style manual should include a section on jurisdiction-specific conventions. I maintain separate appendices for UK, US, and Singaporean drafting standards. They overlap significantly. The differences matter in high-stakes transactions. The biggest limitation is human compliance. A style manual cannot enforce itself. I've seen contracts produced by senior lawyers who ignored the manual entirely and expected junior staff to clean up inconsistencies afterward. This doesn't work. The cleanup time usually exceeds the drafting time. A better approach is to make the manual a precondition for internal approval. No signed contract leaves the building without a style compliance check. It adds five minutes to the process. It saves hours of revision later.

The Practical Checklist

Here's what I actually check before sending any contract out. Not the legal analysis. The style analysis. Every capitalized noun appears in the definitions section. Every defined term is capitalized consistently from first use through the entire document. Modal verbs follow the shall-shall-shall hierarchy. Section numbers are sequential with no gaps or orphans. Spelling is uniform. Punctuation within defined terms matches the definition exactly. Exhibits and schedules are referenced by their titles, not abbreviated descriptions. Dates use the same format throughout. Percentages and monetary amounts follow a consistent structure. "USD" versus "US dollars" versus "$" should not appear interchangeably. After the check, I run the document through a comparison tool against the previous version. Not to find substantive changes. To find style drift. Sometimes a clause gets rewritten during negotiation and the new version accidentally reverts to an older convention. "Shall" becomes "will." A defined term becomes lowercase. These changes happen silently. They don't show up in a normal redline because the substance hasn't changed. Only a style-aware review catches them.

I keep a running log of every style issue I've encountered in actual contracts. Not theoretical issues. Real ones. Things like "party A used 'include' when 'including' was required by the definitions section" or "the signature block used 'Executed as a deed' in one jurisdiction and 'Executed under seal' in another within the same multi-party agreement." The log has grown to about forty entries over five years. Each one represents a real problem that either appeared in a contract I drafted or one I reviewed. The log gets updated quarterly. Old entries stay. New ones get added. It's not glamorous. It works.

Where to Start If You Don't Have a Manual

Write the first version in an afternoon. Two pages maximum. Cover the five conventions that matter most to your organization. Test it on three recent contracts. Revise based on what broke. Repeat until the manual stops changing. A living manual that changes every quarter isn't a manual. It's a proposal. It needs to settle into something stable enough that people stop asking whether the rule changed again. Train the people who actually draft contracts. Not the entire legal department. The people who produce the language that gets signed. One hour session. Walk through the rules with real examples from your own contract library. Show the good drafts and the bad drafts. Let people see the difference between a contract that follows the manual and one that doesn't. The visual contrast is more convincing than any explanation. Measure compliance. Track how many contracts return from signature review with style issues. If the number drops over six months, the manual is working. If it doesn't drop, the problem isn't the manual. It's the enforcement. Consider making style compliance part of the signature authorization workflow. Require the approving manager to confirm that the style check was completed. Not to re-check the style. Just to confirm someone checked it. This creates accountability without adding significant overhead.

The goal isn't perfection. The goal is enough consistency that ambiguity doesn't creep in through the back door. Contracts fail for dramatic reasons sometimes. Most of the time they fail because of small, cumulative drafting inconsistencies that compound into interpretive uncertainty. A style manual attacks that category of risk directly. It's not exciting work. It's necessary work.

A Note on Digital Tools

Several platforms claim to automate contract style compliance. They exist. They're useful for basic checks. They miss context-dependent errors. A tool can tell you that "shall" appears forty-two times in a document. It can't tell you whether those forty-two instances are all obligations or whether some are statements of fact that should read "will." It can flag inconsistent capitalization. It can't decide whether a particular capitalization is intentional or accidental without understanding the defined-term structure. I use these tools as a first pass. They catch the obvious issues. The human review catches the subtle ones. The combination works. Using either in isolation leaves gaps. I've seen contracts pass automated style checks that still contained fundamental consistency errors because the automation didn't understand the document's internal logic. The tool flagged that "Fee" was capitalized consistently. It didn't flag that "Fee" was defined as "the fee described in Schedule A" in one section and "the fees payable under this Agreement" in another, creating a definitional mismatch that mattered in a dispute. The manual plus human review plus automated screening is the most reliable approach I've found. None of these elements alone is sufficient. Together they reduce style-related risk to a level where it rarely surfaces as a substantive problem. That's the target. Not elimination. Reduction to an acceptable threshold.

I'm still refining my own manual. It's been through six revisions over seven years. Each revision came from a real contract issue, not a theoretical concern. That's the only way a style manual improves. Through practical feedback from actual drafting work. Everything else is speculation.