Legal document automation software turns a firm's standard documents into templates with fields, so a lawyer fills in the client and matter details once and the software produces the finished document. Simple systems replace fields with values; advanced document assembly adds conditional clauses and questionnaires that change the document based on answers.
Firms use it for engagement letters, notices, standard agreements, and in estate planning for wills and trust documents that follow a firm-approved form.
LawAOS does field-based automation. The firm creates document templates with {{variable}} fields, fills them in a form, and the result opens in the editor inside the matter. Templates keep version history and can be restored. LawAOS does not have conditional logic, questionnaires, pre-built document templates or a court-forms library.
- Field templates (what LawAOS does)
- One template per document, with {{variable}} fields such as client name, matter number and dates, filled in a form. Suited to letters, notices and agreements whose wording does not change between clients.
- Conditional document assembly (what LawAOS does not do)
- A questionnaire decides which clauses appear. Estate planning practices producing complex trust packages often rely on this; a firm that needs it should use a dedicated assembly tool.
- Court-forms libraries (not included)
- Some products ship official court forms for particular courts. LawAOS does not.
Document templates sit alongside matter templates and workstream templates. A matter template can include documents as well as stages, workstreams, starter tasks and folders, so launching the matter template creates the first drafts with the matter.
A filled document opens in the LawAOS editor, which paginates like Word and exports to .docx and .pdf. If it has a signature block, it can go straight to e-signature from the matter.
- Start with the five documents the firm drafts most often.
- Replace client and matter details with {{variable}} fields, using the same field names across templates.
- Keep one owner per template and use version history instead of saving copies.
- Use the clause library for alternative wording rather than trying to encode choices in the template.
- Review each filled document before sending; field automation does not check legal content.
Create a document template
Write or import the document in the editor and mark its variable parts as {{variable}} fields.
See the moduleFill the form
Launching the template shows a form of its fields. Enter the values, and LawAOS creates the document.
See the moduleEdit in the matter
The filled document opens in the editor inside the matter, with comments, compare and version history.
See the moduleSend for signature
Documents with a signature block can be sent for e-signature, and the executed copy is filed back to the matter.
See the moduleKeep the library current
Each template has version history, restore and launch history, so the firm can see which version produced which document.
See the module
Stated plainly, so you can decide before you sign up rather than after.
- LawAOS ships no pre-built document, matter, workstream or form templates; every template is created by the firm.
- Templates have no conditional logic and no questionnaires.
- There is no court-forms library.
- Filled documents are not checked for legal accuracy; a lawyer reviews each one.
Anything the list leaves open, our team answers directly.