This post uses hypothetical scenarios for illustrative purposes only. It does not describe any actual client, transaction, or representation, and is not legal advice.
Here is what a legal template looks like from the outside: a Word document with blanks where the names go. The founder downloads it, fills in the company name, swaps the date, and sends it to a counterparty. It looks right. It reads like a real agreement. And in the narrow sense of containing enforceable language, it probably is a real agreement.
Here is the problem: a template that contains the right words in the right order is doing roughly ten percent of what a well-built practitioner form actually does. The other ninety percent is the infrastructure around the words. The control sheet that forces the drafter to identify the governing documents, the conflict checks, the securities-law pathway, and the approval chain before changing a single bracket. The completion checklist that prevents someone from skipping the exhibits or forgetting the joinder. The three-pass review protocol that catches the cross-reference that now points to the wrong section because someone deleted a paragraph in the middle. The attorney-review warning that says, in plain language, this document is a starting point and not a legal opinion.
Strip all of that away and what remains is a contract that looks finished but has no quality infrastructure behind it. That is what most free template libraries deliver. It is also what most AI-generated contracts deliver, for the same reason: the output looks polished, but the process that produced it had no checkpoints.
The difference between a template and a practitioner master
A practitioner master is what a transactional lawyer actually works from. It is not a blank form. It is a controlled document with its own version number, its own completion discipline, and its own review protocol baked into the file itself. The distinction matters because the quality of a legal document is not determined by the quality of the final prose. It is determined by the quality of the process that produced the final prose.
Consider what a well-built practitioner master for a stock purchase agreement contains beyond the agreement text itself. First, a matter completion sheet at the top of the file that requires the drafter to identify the parties, the governing documents, the approval path, the securities-law basis, the closing mechanics, and the deal team contacts before drafting begins. Every one of those fields is a forcing function. A drafter who has to write down the federal exemption basis before touching Section 3 will catch the accredited-investor issue before it becomes a closing problem. A drafter who skips that step will not.
Second, an AI completion prompt embedded in the document that tells any language model exactly how to approach the form: treat every row as an evidentiary control, not a generic task; assign a named human owner and objective evidence to each open item; reconcile defined terms across all schedules; simulate the failure cases. This is not a generic instruction to “fill in the blanks.” It is a role-specific directive that constrains the model’s output to the document’s actual requirements. The Montague Law Entrepreneur Forms Library includes these prompts in every form precisely because the prompt is part of the document’s quality infrastructure, not an afterthought.
Third, a completion checklist at the end that enumerates every step the drafter must verify before the document goes out: version control, source documents used, defined-term reconciliation, factual versus legal sign-off separation, and archival. A document that ships without running the checklist has not been completed. It has merely been drafted.
Fourth, a three-pass quality review protocol. Pass one checks completeness: every workstream, every owner, every deadline, every document, every approval. Pass two checks consistency: names, dates, defined terms, cross-references, consideration amounts, and share counts must match across every section and every exhibit. Pass three is operational proof: walk the closing script with the actual people and systems that will execute it. A document that passes all three is ready to go out. A document that has only been proofread for typos has passed zero of three.
Why the infrastructure matters more than the prose
The prose in a well-drafted agreement is important, but it is also the part that gets the most attention and needs it the least. Lawyers have been writing purchase-price adjustment clauses and indemnification baskets for decades. The language is mature. The formulations are well understood. The risk is not that the language will be bad. The risk is that the language will be perfectly good and applied to the wrong facts.
A stock purchase agreement with a flawless indemnification section and the wrong share count in the recitals is a dangerous document. A board consent with beautiful “RESOLVED” paragraphs that references the wrong certificate of incorporation is a dangerous document. A closing checklist that lists every document but assigns no owner and no deadline to any of them is a dangerous document. In each case, the words are fine. The process failed.
This is the gap that template libraries cannot close by adding more templates. The problem is not the supply of contract language. The problem is the absence of control infrastructure. A founder who downloads a stock purchase agreement template, fills in the names, and sends it to a buyer has a document that contains all of the right sections and none of the right controls. The sections will look correct to someone who does not know what to look for. The missing controls will be invisible until something goes wrong at closing or, worse, after closing.
What AI gets wrong about legal documents
The rise of AI-assisted drafting has made this problem more visible, not less. A language model asked to draft a stock purchase agreement will produce one. It will be well-organized, clearly written, and formatted professionally. It will also, with near certainty, include provisions nobody asked for: a defined-terms section that defines terms used only once, a mutual indemnity in a transaction that calls for one-way protection, a notice provision copied from a form that does not match the parties’ actual addresses, and three sentences of hedging in the representations that dilute the very protections the buyer needs.
The model does this because each addition is individually defensible and collectively invisible. No single extra clause looks wrong. The document as a whole looks thorough. The problem is that thoroughness optimized for appearance rather than function produces a document that is harder to negotiate, harder to close, and harder to enforce, because every unnecessary provision is a potential dispute point that did not need to exist.
The fix is not to ask the model to “keep it lean.” That instruction gets absorbed into the model’s general prior and changes nothing. The fix is to embed the constraints in the document itself, the way a practitioner master does: name the specific provisions that belong, name the ones that do not, require the drafter to justify every addition against the completion checklist, and run the three-pass review before anything goes out. The guardrails that actually work are structural, not stylistic.
What founders should look for in a template
A template worth using has five characteristics that distinguish it from a blank form.
First, it has a matter completion sheet or equivalent control header that forces the drafter to identify the transaction-specific facts before changing any bracketed text. If the template lets someone start editing the purchase price section without first confirming the cap table, the governing documents, and the approval authority, the template is missing its most important feature.
Second, it has version control. The document should state its version number, its preparation date, and whether it is an original practitioner master or a working draft. The fundraising and investor forms in the Entrepreneur Forms Library carry version tags for exactly this reason: a drafter needs to know whether the form reflects the current state of the law and the current state of the firm’s practice.
Third, it has a completion checklist that is specific to the document type. A stock purchase agreement checklist is different from a board consent checklist is different from a closing checklist. Generic “review before sending” instructions are not a checklist. A checklist names specific items, requires specific evidence, and assigns specific responsibility.
Fourth, it has an attorney-review warning that states plainly that the document is a starting point and not a finished product. This matters for two reasons. It protects the founder from the false confidence that comes with a professional-looking document. And it protects the lawyer who built the form from the implication that the form was intended to be used without legal review.
Fifth, it separates factual completion from legal sign-off. A drafter can fill in the company name, the share count, and the purchase price. A drafter cannot confirm the securities-law exemption, the board-approval sufficiency, or the tax treatment. The template should make that boundary visible, not bury it. A well-built secondary stock purchase agreement form separates these workstreams explicitly, with counsel sign-off fields that cannot be completed by the drafter.
The bottom line
A legal template is a container. What matters is what the container requires of the person using it. A blank form requires nothing: fill in the names, save the file, send it out. A practitioner master requires everything: identify the facts, confirm the law, run the checklist, review in three passes, get counsel sign-off, and only then send it out. The difference between those two processes is the difference between a document that looks right and a document that is right.
The good news is that the infrastructure is not hard to build or hard to use. It is a matter completion sheet, a checklist, a review protocol, and a clear warning about the boundary between drafting and legal advice. Any firm that builds its forms this way gives its clients something far more valuable than contract language. It gives them a process that catches the mistakes the language alone cannot prevent.
If you are building or reviewing transaction documents and want access to practitioner-quality forms with built-in completion 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.
