# Drafting engagement letters from a form: how AI drafting works inside a firm's own templates

*2026-09-06* — How a drafting system turns a short form or intake data into a first draft in the firm's own templates, who it suits, what it costs and what the first week involves.

Every firm has a person who is very good at engagement letters. They know which clause goes with which matter type, which paragraph to drop for a returning client, and where the fee schedule changes. Every firm also has a queue of letters waiting for that person.

The draft is not the hard part. The hard part is that the draft is the same work every time, and it sits between a client saying yes and the matter starting to bill.

## What drafting from a form means

A drafting system takes structured input and produces a first draft in the firm's own templates and clause library. The input can be a short form that a paralegal fills in, or the data an intake agent already collected. The output is a document that looks like the firm wrote it, because the firm did: the templates, the clauses and the house style are all the firm's. The system assembles and fills. It does not invent language.

Engagement letters are the usual starting point, because they are frequent and structured. The same approach covers proposals, contracts, memos, escrituras and tax opinions. Anything where the shape is fixed and the facts change.

Three properties matter more than the drafting itself.

The draft is marked where a person must check. Fee amounts, scope language, jurisdiction-specific clauses and anything the input did not fully cover are flagged in the document. A reviewer opens the draft and goes straight to the marks.

Every document shows which data and which template version produced it. If a letter went out with the wrong limitation clause, the firm can see whether the template was wrong, the input was wrong, or the reviewer missed the flag. That trail is what makes the system defensible when a regulator or an insurer asks.

The failure mode is a flagged blank, not a confident mistake. When the system does not have what it needs, it leaves a visible gap and says so. It does not fill the gap with something plausible. A blank is caught in review. A plausible wrong clause is caught by the client's lawyer six months later.

The system drafts. A person signs. Nothing leaves the firm without a named human approving it, and client files are never used to train anything. The firm's documents stay the firm's.

## Does a firm your size need it

Count how many documents of the same type the firm produces in a month. If the number is small and one person produces them all, a good template in Word is enough. Drafting systems earn their place through repetition.

The clearer signal is delay. If matters wait for an engagement letter, or proposals go out late because the person who writes them is in court, the bottleneck is the drafting queue, not the volume. A firm of any size can have that bottleneck.

The third signal is inconsistency. Two associates producing the same letter with different clauses, or an old fee schedule surviving in one template but not another. That is a sign the clause library lives in people's heads and their personal folders. Putting it into a system is as much about tidying the library as about the drafting.

For notarial and property practices, the case is stronger still. The documents are long, the fields are many, and errors are expensive to fix after signing. Through flows we have built, 7,455 documents have been signed electronically. In one archive project, more than 103,000 notarial files were indexed and cross-linked, and 1,538 deeds were read and parsed into structured records. That is the same machinery, pointed at the back catalogue instead of the next letter.

## What it costs

Drafting is built as a fixed-price phase within a plan. The price depends on how many document types are in scope, how clean the existing templates are and where the input data comes from. A single engagement letter template with a form in front of it is a small build. A clause library spanning several practice areas, fed by intake data and connected to an e-signature flow, is a larger one.

Because the size varies, drafting work starts with the audit. The audit prices the build as a phase, and its fee is credited against that phase if the firm goes ahead. The firm sees every number before committing.

Ongoing costs are model usage, which is low for document work, and the reviewer's time. The reviewer's time is the point: it goes down from writing to checking, and the checking is directed to the marked sections.

There is one cost that is easy to underestimate. The firm's templates and clause library need to be in a state the system can use. If they are scattered, the first phase includes consolidating them. That is unglamorous work, and it is the work that makes everything after it reliable.

## What the first week looks like

The first week is spent on the templates, not the software.

The firm hands over its current engagement letter templates and whatever passes for a clause library. Together with the person who usually drafts, we go through them and answer the same questions for each: which fields change per matter, which clauses are conditional and on what, and which sections must always be checked by a human before signing. That last list becomes the flag rules.

The input form is designed from the fields. If intake data already exists, it is mapped instead. A paralegal should be able to fill the form in a couple of minutes, and every field should be one the firm actually needs.

By the end of the week, the system produces drafts for a set of past matters. The person who normally drafts compares each one against the letter that actually went out. Differences are either template fixes or flag-rule fixes, and both get made before anyone uses the system for a live matter.

Go-live waits for that person to say the drafts are right. As with every build, the people who do the work test it, and nothing ships until they trust it.

The full scope is on the service page: [/services/drafting-knowledge](/services/drafting-knowledge). To watch a form become a marked-up draft, the demos are here: [/demos](/demos).