Deleted Words Matter: What Courts Do With Drafting History
A lawyer deletes a sentence from a draft. Four rounds later, the parties are in a dispute over what the remaining language means. An opposing expert is arguing that the contract obligates one party to indemnify the other for a category of claim. The defense says the language was never meant to cover that category. Which argument wins?
In commercial litigation — especially under Delaware law, which governs a large share of U.S. commercial contracts — the answer can turn on what earlier drafts of the provision said and no longer say. Delaware Chancery has explicitly described the drafting history of a disputed provision as "especially revealing" when interpreting contract language. Other courts, in Delaware and elsewhere, have used the fact that a particular clause was struck from an earlier draft as evidence that the parties did not intend the removed language to bind them.
This post is about why deleted words matter in contract interpretation, what courts actually do with drafting history, and what that means for how you manage redlines across negotiation rounds. It is not legal advice. It is a practitioner-level explanation of the doctrine and its implications for your workflow.
The rule: ambiguity opens the door to drafting history
American contract interpretation starts from the text. If the language of a contract is unambiguous, most courts will enforce it as written without looking at anything outside the four corners of the document. The debate starts when the text is ambiguous — that is, when the disputed language is reasonably susceptible to more than one interpretation.
Once a court finds ambiguity, extrinsic evidence becomes admissible to help determine what the parties meant. The usual categories include prior course of dealing, course of performance, industry usage of trade, and — relevant here — the negotiation history of the contract itself. Drafts, redlines, term sheets, and the sequence of proposals and counter-proposals that produced the final text are all potentially fair game.
Different states treat this threshold differently. New York courts, applying the strong four-corners rule, are relatively stingy about admitting extrinsic evidence. California courts, following Pacific Gas & Electric Co. v. G.W. Thomas Drayage & Rigging Co., are more willing to consider extrinsic evidence to determine whether the language is ambiguous in the first place. Delaware is somewhere in the middle, but Delaware Chancery is notably willing to engage seriously with drafting history once ambiguity is established.
Why Delaware matters
Delaware matters out of proportion to its size because a large share of U.S. commercial contracts — M&A agreements, LLC operating agreements, joint ventures, shareholder agreements — are governed by Delaware law. When those contracts go into dispute, they usually end up in Delaware Chancery, which has produced a body of contract interpretation opinions that other jurisdictions read and cite.
Two themes recur in those opinions. First, that drafting history is one of the more persuasive categories of extrinsic evidence because it captures what the parties actually said to each other during negotiation, as opposed to what they claim in hindsight. Second, that deletions — words that appeared in an earlier draft and were removed before signing — are often as informative as insertions. A deletion is not silence. It is an active choice by a drafting party to remove language that was on the table.
What courts do with deletions
The typical move looks like this. A court interprets an ambiguous provision. The plaintiff argues the provision covers X. The defendant argues it does not. The court looks at the drafting history and finds that an earlier draft contained explicit language about X, which was struck during negotiation. The court treats the deletion as evidence that the parties deliberately chose to exclude X from the scope of the provision.
The logic runs both ways. Sometimes a deletion is used against the party that insisted on it (they knew the issue was on the table and negotiated it out; they cannot now claim the remaining language implicitly covers what they explicitly removed). Sometimes a deletion supports the party that insisted on it (the deletion shows the contract was not intended to reach that far). Which direction it cuts depends on what the dispute is about and who was pushing which language.
What matters for our purposes is that courts treat the drafting record as signal, not noise. The words that were removed are not throwaway context. They are data about what the parties agreed, and what they agreed not to agree, and both of those things can matter in a dispute.
Contracting around drafting history
Sophisticated parties sometimes try to contract around this. A standard integration clause (merger clause) already prevents the use of prior agreements to vary a final written contract. Some contracts go further and include language purporting to bar the use of drafting history, preparatory materials, or preliminary drafts in the interpretation of the final text.
These clauses have mixed reception. Some courts respect them as legitimate allocations of interpretive risk between sophisticated parties. Others treat them skeptically, especially when the contract is genuinely ambiguous and the clause would leave the court without guidance on meaning. The practical lesson is the same either way: do not treat such clauses as a reason to be careless about drafting history. Assume the file will be read.
Workflow implications: don't lose the deltas
If drafting history carries interpretive weight, then the integrity of your drafting history is a legal question, not just a productivity one. The most common way drafting history gets corrupted is not dramatic — it is the ordinary fact that someone had to re-type negotiated positions by hand into a new version of the document.
The usual scenarios:
- Template switch. The counterparty sends their paper instead of marking up yours. You need to re-apply every edit you had in your redline to the new base. An edit gets missed. A deletion gets quietly reinstated. The negotiated position disappears from the record.
- Internal template update. Legal ops rolls a new version of the master NDA mid-deal. You transfer your deal-specific edits into the new template by hand. You apply them to the wrong section. The intent of the original deletion — that a certain category of information is excluded from the confidentiality obligation — is lost.
- Round-over-round drift. Between rounds, the draft is re-based, or a clean copy is produced, and the full set of tracked changes is not carried forward. The deletions from round one are accepted silently. The negotiation record of those decisions is no longer in the file.
None of this is malicious. It is what happens when a human being has to do a precise, repetitive, position-sensitive task under time pressure. The result is that the drafting file ends up misrepresenting what the parties actually negotiated. In a dispute years later, the file is what the court reads.
What to do about it
Two things. First, treat the drafting file as a first-class legal artifact, not a working document. Keep the tracked-changes versions from each round. Name them unambiguously. Make sure your matter management system is capturing the round-by-round state, not just the final execution copy.
Second, stop re-applying negotiated edits by hand when the base changes. This is the workflow that carry-forward redline is designed for: when you have a round-one redline and a new base (refreshed draft, counterparty paper, updated internal template), clausul matches each of your negotiated edits to the corresponding provision in the new base and re-applies them as native Word tracked changes. Unmatched edits are flagged — not silently dropped — so you can handle them deliberately.
The point is not to remove human judgement from the process. The point is to make sure that when a deliberate negotiation decision is made in round one, it survives to round five without being quietly unmade by a typo or a missed paragraph.
Frequently asked questions
Do courts actually read the drafting history of a contract?
Yes, in many jurisdictions. When a contract is ambiguous, courts frequently look at extrinsic evidence to interpret disputed provisions, and drafting history is one of the more persuasive categories of that evidence. Delaware Chancery in particular has called drafting history "especially revealing," and has relied on what earlier drafts struck out to interpret the language that remained. Jurisdictions that follow a stricter four-corners rule (New York, for example) limit extrinsic evidence more narrowly, but even there drafting history can come in once the court finds ambiguity.
Is this Delaware-specific?
The strongest doctrine is in Delaware because so many commercial contracts are governed by Delaware law, and because Delaware Chancery writes detailed contract interpretation opinions. But the underlying principle — that deliberate deletions from earlier drafts shed light on intended meaning — shows up in courts across the country when contracts are ambiguous enough for extrinsic evidence to become admissible.
What about contracts with a merger clause or a "no drafting history" clause?
Merger clauses (integration clauses) limit the use of prior agreements and negotiations to vary the terms of a final written contract. Some sophisticated parties go further and try to contract around the use of drafting history entirely. These clauses are enforceable in some jurisdictions but not all, and courts still rely on drafting history when a contract is genuinely ambiguous and the clause does not clearly foreclose it. The practical lesson is the same: assume your drafting file could be read.
What does this have to do with redline workflows?
If drafting history has interpretive weight, then losing or mangling the history of your edits is a real cost. Re-typing negotiated positions by hand across rounds — because the counterparty sent a refreshed base or your template changed mid-deal — is where that history gets corrupted. An edit that was deliberate in round one disappears without a trace in round three because nobody remembered to re-apply it. A carry-forward workflow preserves those decisions.
Is a redline admissible as evidence?
Whether a redline is admissible depends on the rules of evidence in the relevant court and the purpose for which it is offered. Drafting history is typically offered to interpret ambiguous contract language rather than to prove a separate agreement. Federal Rule of Evidence 408 also limits the use of compromise negotiations to prove liability, which is worth keeping in mind when settlement-context redlines are involved. The short answer: drafting history is commonly used in contract interpretation disputes, and you should not assume your file is invisible.