Contract drafting is the art of translating a business deal into enforceable legal language. Unlike litigation writing, which interprets existing agreements, drafting requires you to anticipate future disputes and create language that resolves them before they arise. A well-drafted contract is clear, comprehensive, and leaves no room for reasonable disagreement about what the parties intended.
The fundamental principle of contract drafting is precision. Every word matters, and ambiguity is the enemy. Courts interpret contracts based on their plain language, and if your language can reasonably be read two different ways, a court may choose the interpretation that hurts your client. The goal is to draft provisions that can only be read one way — the way you intended. This requires not just legal knowledge but also careful attention to defined terms, consistent usage, and logical structure.
Good contract drafting also requires understanding the business deal behind the legal language. You cannot draft an effective contract without understanding what the parties actually want to accomplish, what risks they are willing to accept, and what scenarios keep them up at night. The best contract drafters are not just wordsmith lawyers — they are practical problem-solvers who translate commercial reality into legal protection.
Document Structure
Recitals
Provide background context for the agreement and state the parties' general intent.
Recitals (the 'WHEREAS' clauses) set the stage but are generally not operative provisions. Use them to explain why the parties are entering the agreement, which can help a court interpret ambiguous operative provisions. Keep them concise and factual.
Definitions
Define key terms precisely to ensure consistent usage throughout the agreement.
Define any term that has a specific meaning in the contract that differs from its ordinary meaning, or any term used frequently. Place definitions in a dedicated section or define them inline on first use. Use defined terms consistently — never use a defined term in one place and the undefined version elsewhere.
Operative Provisions
Set forth the parties' substantive rights and obligations.
This is the heart of the contract. Use active voice and clear subject-verb-object structure. State obligations using 'shall' (mandatory duty), rights using 'may' (permission), and conditions using 'if/when/upon.' Be specific about amounts, deadlines, and performance standards. Avoid vague terms like 'reasonable efforts' unless you define what that means.
Representations & Warranties
Document factual statements each party makes about themselves and the subject matter.
Representations look backward (stating present or past facts), while warranties look forward (promising certain conditions will continue). Be precise about what is being represented, by whom, and as of what date. Include appropriate qualifiers like 'to the best of its knowledge' where needed, but be aware these limit the scope of the representation.
Conditions
Specify events that must occur before obligations become effective.
Distinguish between conditions precedent (must happen before obligations arise), conditions concurrent (must happen simultaneously), and conditions subsequent (trigger termination of obligations). Be clear about who bears the risk if a condition is not satisfied and what happens in that scenario.
Termination
Define how and when the agreement can be ended and what happens afterward.
Specify the grounds for termination (breach, convenience, insolvency, force majeure), the required notice period, the cure period for breaches, and what obligations survive termination (confidentiality, indemnification, payment for services already rendered). Survival clauses are frequently litigated — be explicit about what survives and for how long.
Boilerplate
Address standard legal issues that apply to the agreement as a whole.
Do not treat boilerplate as an afterthought — these clauses matter. Key provisions include: governing law, dispute resolution (litigation vs. arbitration), entire agreement/merger clause, amendment requirements, waiver provisions, severability, assignment restrictions, and notice requirements. Tailor each provision to the specific deal rather than copying generic language.
Do's and Don'ts
Do
- Define every key term precisely and use defined terms consistently throughout the agreement
- Use 'shall' for obligations, 'may' for permissions, and 'will' for future actions or conditions
- Include specific deadlines, amounts, and performance metrics rather than vague standards
- Anticipate disputes by drafting provisions that address foreseeable problems
- Read the entire contract from the other party's perspective to identify exploitable ambiguities
Don't
- Do not use 'and/or' — it creates ambiguity about whether both or either condition must be satisfied
- Do not use the same word with different meanings in different sections
- Do not include provisions you do not understand — every clause should have a clear purpose
- Do not rely on verbal agreements or understandings that are not reflected in the written contract
- Do not forget to address what happens when things go wrong — breach, termination, and dispute resolution provisions matter most when the relationship breaks down
- Do not use 'best efforts' without defining what that means in context — courts interpret it differently across jurisdictions
Before & After Examples
Before
Seller will deliver the goods in a reasonable time.
After
Seller shall deliver the Goods to Buyer's facility at 123 Main Street, Chicago, IL 60601, no later than thirty (30) calendar days after the Effective Date. If Seller fails to deliver the Goods by the Delivery Date, Buyer may, at its option: (a) extend the Delivery Date by providing written notice to Seller, or (b) terminate this Agreement and receive a full refund of any prepaid amounts within ten (10) business days of termination.
The improved version specifies the delivery location, the exact deadline, and the consequences of late delivery. The vague version invites litigation over what 'reasonable time' means — a question that could cost more to resolve than the goods themselves are worth.
Before
This agreement can be terminated by either party at any time for any reason.
After
Either party may terminate this Agreement for convenience upon sixty (60) days' prior written notice to the other party. Upon termination for convenience: (a) Client shall pay Provider for all Services performed through the termination effective date; (b) Provider shall deliver all work product completed as of the termination effective date; and (c) Sections 7 (Confidentiality), 9 (Indemnification), and 12 (Limitation of Liability) shall survive termination for a period of three (3) years.
The improved version specifies the notice period, the obligations that arise upon termination (payment, work product delivery), and which provisions survive. The vague version creates chaos — can a party terminate mid-performance with no notice, no payment obligation, and no surviving confidentiality protection?
Common Mistakes to Avoid
Using 'and/or' which creates genuine ambiguity about whether both or either condition applies
Failing to define key terms, leading to disputes about what 'deliverables,' 'completion,' or 'material breach' means
Using inconsistent terminology — referring to the same concept with different words in different sections
Neglecting to address what happens upon termination, especially regarding payment, work product, and surviving obligations
Copying boilerplate from other agreements without tailoring it to the specific transaction
Drafting from only one party's perspective without considering how the other side might interpret ambiguous language
Failing to include a mechanism for resolving disputes, leaving the parties to litigate every disagreement from scratch