Form and document automation
Form and document automation is a legal software archetype in which a structured questionnaire is the input and a finished document is the output: the product collects answers from a client, and the same answers populate the documents the matter needs, without anyone retyping them.
It is the one archetype in this set whose value is realised after the intake conversation rather than during it. The other archetypes are judged on whether a prospective client is captured, held and followed up. This one is judged on whether what the client typed becomes a usable document, which makes its buyer question a data question rather than a pipeline question.
Three of this research base's thirty-two product entities carry this label. One carries verified evidence from official vendor surfaces, Gavel. The other two are research stubs with no capability verification compiled, so this project describes nothing about what they do. This is the thinnest verified archetype in the set, and the page is written accordingly.
What the one verified vendor documents
These are Gavel's own statements about its own product, captured . None has been independently tested.
Gavel says workflow questionnaires can conditionally show questions relevant to a client, that clients can pause and return to an intake while their progress remains saved, and that its dashboard exposes intake progress to the attorney and client. On the output side, it says its workflows can generate document sets using intake-form data, and that attorneys and clients can view, update and reuse intake responses in its data manager. It names Docusign, Zapier and Clio Manage among the systems its workflows connect to, captured .
Read the last one carefully, because it is the sentence a buyer will lean on. Naming a system a workflow connects to establishes that a connection is offered. It does not describe what crosses that connection, in which direction, or as fields rather than as text.
This archetype meters usage, not seats
The commercial shape here is different from the rest of the set, and it is the most decision-relevant thing this research base holds about the archetype.
Gavel's published plans include monthly session allowances that rise with the plan, and the Lite plan includes one builder or admin seat, ten workflows and a Clio integration. Gavel states that Lite and Standard subscribers must upgrade to Pro or Scale to add builders or organizational users, and that Pro and Scale subscribers are billed a monthly overage for seats above their tier allowance. It also states that annual plans billed upfront receive two months free. All three were captured on .
So a firm's cost here moves with two things at once, how many people build and administer workflows and how many sessions the firm consumes. For a firm with high inbound volume, the allowance constrains intake independently of the headline price. And the unit that constrains it is not defined in anything this project has captured: what counts as one session, and how many sessions a given monthly volume of inquiry consumes, are both open questions here. That is the first thing to put to the vendor, before the monthly rate.
The label is a function, not a fence
Document generation is not confined to products carrying this archetype label. Law Ruler, which this project files under a different archetype, says its document automation can place client information into editable legal templates, and says signature requests can be sent through email or text message, both captured .
That is worth knowing before shopping. A firm whose only unmet need is turning intake answers into a document may already have the capability inside a product it runs, and the archetype question is not which vendor owns the label but which system in the firm will hold the answers.
What this evidence does not establish
This page rests on one verified product. The two other products carrying this archetype label are research stubs with no capability verification compiled, so nothing here describes the category, and no product carrying this label has been measured against another on any axis. Every capability statement is the vendor's own account on a dated capture, and availability of a feature is not a demonstration that it works for a given firm. No practitioner in the captured evidence describes using a product of this archetype, so there is no buyer-side account here at all, which is a weaker evidence position than the other archetypes in this glossary. Nothing establishes what a session is, what a firm's monthly volume would consume, or which practice-management mappings are native rather than custom implementation work. And nothing in this research base records where the collected data goes once the document has been generated, which is the question this archetype most needs answered.
Related
Gavel appears with its capture dates and material limitation in the legal intake software directory. The standards behind every statement on this page, including what counts as a source and what may never be published, are at methodology.
Nothing on this page is legal advice.