º£½ÇºÚÁÏ

This post uses hypothetical scenarios for illustrative purposes only. It does not describe any actual client, transaction, or representation, and is not legal advice.

A common Florida deal pattern looks like this: three weeks into negotiating a services agreement, both sides are working from a file named something like Agreement_FINAL_v3_clean_edits(2).docx. The buyer’s counsel sends over “the latest” with a redline attached. The redline shows a change to the indemnity cap that the clean copy does not contain. Nobody can say which version the business owner approved on the phone last Thursday, because the file she approved has since been saved over. Signing is Friday.

Nothing in that scene is exotic. It is what happens when a document moves through a negotiation without version control — the discipline software teams treat as table stakes and most deals still skip. Here is what the discipline actually consists of, why each piece exists, and what it looks like now that AI tools are producing more drafts, faster, than any associate ever could.

Version zero is the document you received, not the one you wrote

Every negotiation starts with a document someone else produced — the counterparty’s form, the client’s decade-old template, the prior deal’s purchase agreement. That document is version zero, and the first rule is that it is never edited. It is saved exactly as received, in its own folder, and every later version is measured against it.

The rule sounds trivial until the base arrives as a PDF. The instinct is to have someone retype it or run it through a converter and start marking up the result. The disciplined move is to convert it to an editable file and then verify the conversion word for word against the PDF before a single change is made. A redline is only as trustworthy as its base; if the base silently dropped a sentence in conversion, every comparison downstream inherits the error and reports it as your change or, worse, hides it entirely.

Nothing gets overwritten, because history is evidence

The second rule is that no version is ever saved over. Each revision that leaves the working session gets a number — v01, v02, v03 — and the prior one is archived, not deleted. Iterating inside a single working session does not require a new number for every save; the boundary is exposure. The moment a draft has been seen by the client, the other side, or a reviewing partner, it is frozen forever.

This matters because a negotiation is a sequence of positions, and disputes are fought over the sequence. A post-closing fight routinely turns on when a word entered the document and who put it there. Consider the eight-figure holdback that turned on the single word “final” — the kind of dispute where the ability to reconstruct exactly which draft introduced a term, and whose redline carried it, is worth more than any argument about what the parties must have meant. If your file history is one overwritten document, you have no history, and you are litigating from memory against someone who kept theirs.

Every version is a pair

A version is not a file. It is two files: the clean draft and a redline showing every change against the base the recipient already knows. Sending a clean copy with the changes described in an email is not version control; it asks the reader to reconstruct the diff by hand and to trust that the description is complete. Sending only a redline is not much better, because the recipient has to accept every change themselves to see what they would be signing.

Three things make the pair trustworthy. First, the redline has to consist of real tracked changes — insertions and deletions the document itself records — not text colored red and blue to look like one. A cosmetic redline cannot be accepted or rejected, cannot be verified, and cannot be relied on. Second, the redline runs against the base the other side last saw. A comparison against your own intermediate draft tells the counterparty nothing useful and, when the two documents disagree, invites the suspicion that something was slipped in between. Third, the header of the redline states exactly which two versions are being compared, so that a reader six months later does not have to guess.

Verification is a test, not a feeling

The clean and the redline are produced separately and can diverge. That divergence is the most dangerous error in document work, because the counterparty reads both and will find the discrepancy at the worst possible moment. So before any version leaves, two mechanical tests get run, and they are tests in the literal sense: they either pass or they do not.

The first test is reject-all. Rejecting every tracked change in the redline must reproduce the base version word for word. If it does not, the redline is misrepresenting what was changed. The second test is accept-all. Accepting every tracked change must produce exactly the clean draft. If it does not, the clean contains something the redline never disclosed, or the redline promises something the clean lacks. The clean, for this reason, is never retyped; it is generated by accepting the tracked file, so that the two cannot drift.

Around those two tests sits a shorter sweep: section numbering is an unbroken sequence, every internal cross-reference points at a section that still exists after the edits, brackets balance and each remaining bracket is a deliberate blank, and nothing intended as an internal note to draft survives in a document headed outside. Then someone reads the rendered redline page by page. Not skims — reads. Software catches structure; only a reader catches a garbled clause that passed every structural check.

The label on the outbound draft is a promise

Internal version numbers are working history and can run high; a heavily negotiated form may pass through a dozen internal turns before the client sees the second one. What the recipient sees should be a clean external counter — the first draft sent is their v1, dated and labeled, whatever it was internally. What actually went out is frozen in its own folder, so that there is never a question about which document a recipient has in hand, and the internal history stays intact behind it.

The label is a promise because Florida law does not wait for signature pages to treat words as binding. Under Florida’s Uniform Electronic Transaction Act, , an email exchange agreeing to a change can be an enforceable record with an enforceable signature. In a representative scenario, an operations manager emails the other side that “the revised exhibit works for us” and the reply says “agreed” — that exchange is a version event whether or not anyone updates a document, and a version log that does not capture it has a hole in it. The discipline is to record, in one line per version, what changed, on whose instruction, and by what medium, including the emails.

What changes when the AI is in the room

Generative AI tools now produce full contract turns in minutes, and the temptation is to treat speed as a reason to loosen the process. It is the opposite. A tool that can generate five drafts in an afternoon can also overwrite, retype, and cosmetically color five drafts in an afternoon, and it will describe each as “the updated version” with perfect confidence. The rules above are exactly the rules that keep a fast tool honest: a frozen base, real tracked changes, the reject-all and accept-all tests reported in plain terms with every delivery, and a human who reads the pages. The firms getting real leverage from these tools are the ones that made the tool follow the discipline, not the ones that let the tool replace it. That is the same conclusion reached in a different setting in what agentic M&A execution changes and what still requires a human, and it holds even more firmly for the document a client will actually sign.

None of this is glamorous, and none of it shows up in a term sheet. It shows up when a deal goes sideways and one side can say, with a file to prove it, exactly what every draft said and when — and the other side cannot. The likely outcome in that fight favors the side that kept the versions.

If you are negotiating an agreement and want the drafting process run with this kind of discipline, feel free to reach out to our firm manager, Magda, at Magda@montague.law, or fill out our contact form. Mention you read this post.