Law firm automation templates are ready-made rules that watch for an event, such as a matter opening, an invoice going overdue or an intake arriving, and respond with an action, such as creating a task, notifying the team or emailing the client. A template saves the firm from designing each rule from scratch.
LawAOS ships 22 automation recipes across matters, workstreams, documents, contacts, invoicing, billing, docket, calendar, intake, signatures, conflicts and AML/KYC, trust accounts, proposals and messages. Each recipe is one rule: a trigger the database raises, an optional condition, and one action.
Firms can also save any working rule of their own as a template, and it appears in the same gallery. These are automation templates only: LawAOS does not ship pre-built document, matter or workstream templates.
- Trigger
- A real event, such as matter opened or updated, task, document, contact, invoice, time logged, expense, docket entry, deadline added, calendar event, intake submitted, lead, signature, conflict check, AML/KYC, trust transaction, proposal or message received.
- Condition
- An optional test on a field, for example a matter status changing to Closed, so the rule fires only when it should.
- Action
- One of four: create a task, notify, send a branded email, or update a field. Text can include {{token}} fields such as the matter name or client name.
- Webhooks
- Rules can also send signed outbound webhooks for firms that connect their own systems.
- Start with the rules that cover a missed step you have seen, such as the engagement letter or the final bill.
- Switch on one rule per module first and watch the tasks and notifications it creates for a week.
- Add a condition before widening a rule, so it does not notify on every edit.
- Save a rule the firm relies on as a template, so a department can reuse it.
- Chain steps by adding a second rule on the same trigger; a single rule carries one action.
| Recipe | What it does | Module |
|---|---|---|
| Open a matter, draft the engagement letter | The moment a Legal Matter is created, put the engagement letter on the board so onboarding never slips. | Matters |
| Email the client when a matter closes | Sends the client a branded wrap-up on your firm's letterhead, with a link back to their matter. | Matters |
| Raise the final bill when a matter closes | Closing a matter creates the final-billing task, so work in progress is never written off by accident. | Matters |
| Flag a critical matter to the team | A matter set to Critical priority raises an in-app notification rather than waiting to be noticed. | Matters |
| Announce a new task | Posts a notification whenever a task is created, so nothing sits unseen on a board. | Workstreams |
| Escalate a task that stalls | A task moved to In Review notifies the team, so review queues do not go quiet. | Workstreams |
| Review every new document | An upload creates a review task against the matter it was filed on. | Documents |
| Follow up a new contact within a day | Creates the follow-up task the moment a contact is added, with their details already on it. | Contacts |
| Chase an overdue invoice | Emails the client a branded reminder the moment an invoice goes overdue, quoting the balance. | Invoicing |
| Confirm a payment internally | Marks the team when an invoice is paid, so nobody chases a settled bill. | Invoicing |
| Review a recorded expense | A disbursement creates an approval task before it reaches a client bill. | Billing Log |
| Calendar a docket filing | A new docket entry creates the task to compute and diarise the response deadline. | Docket |
| Announce a new deadline | Notifies the team whenever a deadline is added to a matter. | Docket |
| Prepare for a scheduled hearing | Scheduling an event creates the preparation task on the same matter. | Calendar |
| Conflict-check every enquiry | An intake submission creates the conflict-check task before anyone opens a matter. | Intake |
| Work a new lead | A lead entering the pipeline creates the first-contact task. | Intake |
| Track a signature request | Any movement on a signature request notifies the team that owns it. | Signatures |
| Report a conflict-check result | Notifies the team the moment a conflict check clears or flags. | Conflicts and AML/KYC |
| Review an AML / KYC change | An AML/KYC state change creates the review task, with the trail on the record. | Conflicts and AML/KYC |
| Watch every trust movement | Any trust transaction notifies the team: client money oversight, not an afterthought. | Trust accounts |
| Follow a proposal's outcome | A proposal changing state notifies whoever is carrying the opportunity. | Proposals |
| Never miss a client message | An inbound message raises a notification against the matter it belongs to. | Messages |
Generated from the built-in automation catalog in the product, so this list matches what the Automations module shows.
Open the gallery
The Automations module lists the built-in recipes grouped by module, with the firm's own saved templates alongside.
See the moduleApply a recipe
Applying a recipe creates a rule with its trigger, condition and action filled in, ready to adjust.
See the moduleAdjust the wording and tokens
Edit the task title, notification or email text and its {{token}} fields to match the firm's language.
See the moduleLet it run on real events
The rule fires on the event it names, such as a new matter, an overdue invoice or a filed docket entry, and creates tasks in the matter's workstreams.
See the moduleSave your own as a template
Save as template on any working rule adds it to the gallery for the rest of the firm.
See the module
Stated plainly, so you can decide before you sign up rather than after.
- LawAOS does not ship pre-built document, matter, workstream or form templates; the recipes on this page are automation rules only.
- Each rule has one action, and the four actions are create a task, notify, send a branded email and update a field.
- Automations have no delays and no branching.
- There is no Zapier or Slack integration; signed outbound webhooks are the connection point.
- Rules that send email need the firm's SMTP or the platform relay configured.
Anything the list leaves open, our team answers directly.