Somebody at your firm still opens last month's engagement letter in Word, does a find-and-replace on the client's name, hopes they caught every instance, saves it as a PDF, and emails it with a note asking the client to print, sign, and scan. Then someone else checks the inbox for a week to see if it came back.
Engagement letter automation replaces that with a template, a trigger, and a signature service. It is the first thing we recommend building in law office automation because the document is standard, the data it needs already exists in your intake tool, and the delay between "yes" and "signed" is where clients change their minds.
Why the engagement letter is the best first automation
Three reasons. The content is stable: your fee terms, scope language, and conflict disclosures change rarely, and when they change, they change for everyone. The inputs are few: client name and address, matter description, fee arrangement, responsible attorney, and a date. And the outcome is measurable: the time from consultation to signed letter, which you can see in any intake tool's pipeline report.
It also sits at the exact point in client intake where manual work does the most damage. A prospect who has said yes is ready to sign that day. Every day the letter sits in a draft folder is a day for a competitor to send theirs.
Building the template
Start from the letter you use today and mark every spot that changes. Those become merge fields: {{client_full_name}}, {{client_address}}, {{matter_description}}, {{responsible_attorney}}, {{fee_type}}, {{hourly_rate}} or {{contingency_percentage}}, {{retainer_amount}}, {{date}}. The exact syntax depends on the tool, but the discipline is the same: if it varies by client, it is a field, and the field name matches a field in your intake system.
Then mark every block that is sometimes present and sometimes not. A contingency fee paragraph. A flat fee paragraph. A litigation hold notice for disputes. A limited scope statement. Those become conditional sections, and the condition is a field value ("if fee_type is contingency, include this paragraph"). Clio Grow, Lawmatics, and most document generation tools support conditionals; if yours does not, keep one template per fee type and let the trigger pick the right one.
Keep the template in one place with one owner. A firm with four versions of the engagement letter floating around has four sets of fee terms.
The trigger-to-signature sequence
The trigger is a stage change in the intake tool: the lead moves to "Engaged" or "Ready to sign," or the attorney checks a box after the consultation. Do not trigger on form submission; the letter should only go out after a conflict check and an attorney decision.
On trigger, the tool generates the letter from the template, pulling every merge field from the lead record. It then hands the PDF to a signature service with the client's email and, optionally, the attorney as a second signer. The signed document, once it comes back, is saved to the client record and the automation moves the lead to "Client" and creates the matter in the case management system.
Build in a reminder branch. If the letter is unsigned after a set number of days, send a follow-up (a personal one, from the attorney's name), and create a task for a phone call after a second interval. Signature services have reminder settings of their own, but a firm-controlled message usually reads better.
E-signature choices
Clio Grow includes e-signature for its own documents, which keeps the whole sequence in one tool if you are a Clio firm; the same is true of Lawmatics and of Filevine's Vinesign. DocuSign is the common choice when the firm already uses it for other documents, or when opposing parties and third parties need to sign things through the same account. Zapier and Make both connect DocuSign to the major intake tools when the built-in option does not fit.
Whichever service you use, confirm three things. That the signed PDF comes back with an audit trail (signer email, timestamp, IP). That the completed document is written back to the client record automatically rather than sitting in the signature service's own portal. And that the signature event can trigger the next step, because "signed" is the moment the matter should open.
What to do when the letter comes back
Signature should fire the matter creation, not a person. In Clio, a converted Grow lead creates a Manage matter; we cover the downstream steps in Clio workflow automation. In Filevine, the signed letter can advance a Lead Docket lead into a project. In a Zapier-based setup, the DocuSign "envelope completed" trigger creates the matter and the standard folder set.
Then the onboarding sequence starts: a welcome message, a document request list specific to the practice area, and, if a retainer is due, an invoice or payment link with the retainer amount pulled from the same field that populated the letter. That last step is the difference between a signed client and a paying one.
The engagement letter is one template. The same approach applies to every other document the firm produces from client data, which is the subject of our page on legal document automation.
Questions we get
Our engagement letters vary a lot by attorney. Can we still automate them?
Yes, but the first step is a conversation about why they vary. Usually it comes down to two or three genuine differences (fee structure, scope, practice area) that become conditional sections, and a lot of stylistic drift that the firm should standardize anyway. One template with conditions is manageable; twelve personal templates is not.
What about engagement letters that need attachments, like a fee schedule or a privacy notice?
Most generation tools can append a static PDF to the generated letter or send several documents in one signature envelope. Keep the static attachments in the same template library as the letter so a change to the fee schedule updates everywhere at once.
Is an e-signed engagement letter enforceable?
Electronic signatures are broadly accepted for this kind of agreement in the United States, and the audit trail from a signature service is usually stronger evidence than a scanned wet signature. Confirm any specific requirements in your jurisdiction and practice area with your own ethics resources, particularly for contingency agreements, which some states require in a particular form.
If you want help getting your engagement letter from Word into a working template, tell us what you are working with.