Workflow automation in a small Australian law firm: what to automate first and what to leave to a person

Automate the steps that are identical on every matter and produce a checkable output: opening the file, generating standard documents, diarising key dates and sending status updates. Keep advice, trust withdrawals and the final read of an outgoing document with a person. MatterFirst, a legal practice management platform for Australian law firms, runs these as trigger, condition and action rules.

Most small firms buy automation and then use almost none of it. The usual reason is not the software. It is that nobody decided which steps are safe to hand over, so the firm either automates nothing or automates a whole matter type at once and turns it off after the first embarrassing letter. This guide gives you a test to apply step by step, a worked conveyancing example, and how five platforms describe automation on their own material.

What "automation" means inside a practice management system

Strip away the marketing and a workflow rule has three parts.

• Trigger. The event that starts the rule. A matter is created, a matter moves to a new stage, a date arrives, a document is uploaded, a lead is marked as accepted.
• Condition. The filter that decides whether this particular matter qualifies. Jurisdiction is Victoria. Matter type is purchase, not sale. Fee arrangement is fixed fee.
• Action. What happens. Assign a task list, generate a document, create a key date, send an email, move the matter, notify a supervisor.

Two rules that look similar can behave very differently depending on whether the platform supports conditions. A rule that fires on every new matter of a type is a checklist. A rule that fires only when the matter is a NSW purchase over a certain value, and routes it differently, is closer to a real process.

The second thing worth understanding is what the action itself is made of. "Generate a document" can mean a merge of matter data into a template, which is deterministic and produces the same output for the same inputs, or it can mean a model writing prose, which does not. For anything that goes to a client, a court or the other side, you want to know which of those you have. A useful separation is set out in our guide on what should be a merge field and what genuinely needs a model.

The test: should this step be automated?

Apply four questions to every step in a matter type. If the answer to all four is yes, automate it. If any answer is no, leave it with a person, or automate only the preparation and keep the release manual.

1. Is the step identical every time? Sending the client an acknowledgement on file opening is identical. Deciding whether to act at all is not.
2. Is the output checkable in seconds? A generated letter can be read before it goes. A calculated limitation date can be checked against the statute. A judgement call about a special condition cannot be verified at a glance.
3. Does a person still carry the professional obligation? Costs disclosure, conflicts and trust withdrawals stay with a person no matter how good the tooling is, because the obligation is personal and the regulator will ask who authorised it.
4. What happens if it fires wrongly? An internal task assigned in error costs a minute. An email to the wrong party costs a relationship, and possibly a complaint. Automate outbound communication last and with the tightest conditions.

Automate these first

In roughly this order, because each one pays back the setup time quickly and fails safely:

• Matter opening. When a lead is accepted, create the matter, attach the contacts in the right roles, apply the matter type and open the file with the standard task list already on it.
• Key dates and limitation dates. These should be calculated by rule from the facts of the matter, with the governing provision recorded next to the date. Diarising is the single highest-consequence clerical step in a law firm, and it is pure calculation.
• Standard document generation. Client care letters, authorities, standard requisitions, cost agreements built from a clause library. Deterministic merges, generated on a trigger, read by a person before release.
• Internal task routing. Assign the file opening checklist to the paralegal, the review to the supervising solicitor, the settlement booking to the conveyancer.
• Status updates to the client. Simple, factual updates tied to a stage change. "Your contract has been received and is being reviewed" is safe. Anything that resembles advice is not.
• Billing prompts. A reminder to raise the invoice at settlement, a prompt to record a disbursement when one is incurred, a task to reconcile the matter before closing.

Keep these with a person

• The decision to act, and the costs disclosure and conflict clearance that go with it.
• Any withdrawal from trust. The system can prepare and record the transaction and hold the review workflow open. A human authorises it.
• Anything that interprets a document rather than reading it. Extraction can tell you the settlement date in a contract. A solicitor decides what a special condition means.
• The last read of anything leaving the firm. Generation saves the drafting time. It does not transfer the responsibility.
• Portal invitations and access. Who can see a file is a deliberate decision, not a side effect of a rule firing.

A worked example: a conveyancing purchase

This is the shape of an automation map for a single matter type. Build yours in this format before you touch any settings screen, because the argument about what belongs in each column is the actual work.

Note what is not in the table. No rule sends advice, moves money or files a document with a registry. The rules remove the copying, not the judgement.

How the platforms describe automation

Verified against each vendor's own public material in September 2026. Where a vendor's page does not state something, this table says so rather than guessing.

One caveat. Marketing pages describe capability at a level that will not tell you whether the specific rule you need is possible, so take your three hardest rules into every demonstration and ask the vendor to build one live. The Clio detail above comes from its help centre, which is generally where the precise answer lives for any vendor.

How MatterFirst handles this

MatterFirst is a legal practice management platform for Australian law firms, built by North Cape Technology, a Melbourne software company.

Automations are expressed as trigger, condition and action rules, and generating a document is available as an action rather than as a separate manual step, so a rule can open a matter, assign the work and produce the standard documents in one pass. Lead workflows sit in front of that: a lead captured from any channel moves through a qualification pipeline and converts into a matter with the workflow already triggered.

Obligations and limitation dates are calculated by rule and cite the governing statute alongside the date, for example the Limitation Act 1969 (NSW) s 14(1), so the diary entry carries its own authority. Matters can be recorded in all eight Australian jurisdictions.

On the document side, document generation is deterministic by default. A firm defines its own document types in a builder from sections that are merge fields, matter data projections, clause library entries and signature blocks, with AI used only where a section genuinely calls for synthesis. Output is branded PDF and Word with the firm's letterhead, colours and typography, and uploaded Word precedents are merged with matter data and kept whole. Generated documents file on the matter and can be emailed, shared to the client portal or routed for e-signature.

Document AI extracts key terms from uploaded contracts, flags risks and connects the result to the matter workflow, and firms can define custom extraction rules for the fields that matter to their own documents. The AI assistant is matter aware and drafts communications under human oversight rather than sending them.

Pricing is per workspace rather than per user, from $199 per month with users included, and every paid plan includes the client portal, automations and a monthly AI balance in Australian dollars that is drawn down by metered AI work. Deterministic work, such as generating a document with no AI sections, draws down nothing. The detail is on the pricing and AI metering pages.

Integrations that connect today are Xero, Stripe, Microsoft 365 and Google Workspace, plus a documented REST API with webhooks. Other providers in the integrations catalogue, including PEXA, InfoTrack and the accounting packages beyond Xero, are listed as coming soon and should not be counted in a buying decision until they ship.

Who this suits, and who it does not

MatterFirst suits Australian firms of roughly two to twenty fee earners that run repeatable matter types, want onshore hosting, and need trust accounting built for Australian jurisdictions. The trust compliance review workflow covers NSW, VIC, QLD and WA: four jurisdictions, not all eight, which is the specific thing to check before you commit if you practise in SA, TAS, ACT or NT. Matters themselves can be recorded in all eight.

It is a weaker fit if your practice depends today on a connection to PEXA or InfoTrack, because those are listed as coming soon rather than available, or if your firm's documents are genuinely bespoke on every file, in which case automation of any kind will return less than the setup costs you. Firms leaving FilePro or LawMaster can start with a migration assessment.

Rolling it out without breaking anything

1. Pick one matter type. The highest volume one, usually conveyancing or a standard commercial matter. Not the complex litigation.
2. Map it on paper first, in the trigger, condition, action, who-checks format above.
3. Automate the internal steps first. Task assignment and file opening fail safely. Client emails do not.
4. Run it in parallel for two weeks. Let the rules fire and have a person do the step as well, then compare.
5. Keep an exception list. Every time someone overrides a rule, write down why. After a month, that list tells you which conditions are wrong.
6. Review monthly for the first quarter. Rules rot when matter types change and nobody notices until a date is missed.

A related question to settle at the same time is which steps a system should be calculating for you, covered in our piece on limitation dates and diarising.

FAQ

What should a small law firm automate first? Matter opening and key date calculation. Both are identical on every file, both produce output you can check in seconds, and both fail internally rather than in front of a client. Standard document generation comes next.

Does MatterFirst let a workflow generate a document automatically? Yes. Generating a document is available as an action inside an automation rule, so a matter reaching a given stage can produce its standard documents without anyone opening a template.

Is it safe to automate client emails? Factual status updates tied to a stage change are generally safe, for example confirming that a contract has been received. Anything that could read as advice, or that depends on facts the system cannot verify, should be drafted automatically and sent by a person.

Does MatterFirst handle Victorian trust accounting? Yes. The trust compliance review workflow covers NSW, VIC, QLD and WA. If you practise in another state, ask specifically about that jurisdiction before you commit.

Can automation calculate limitation dates? In MatterFirst, obligation rules calculate limitation and key dates and cite the governing statute next to the calculated date. Treat the citation as the reason to check the date once when the rule is set up, not as a substitute for checking it.

How much does MatterFirst cost? Pricing is per workspace, from $199 per month with users included, with additional users charged on top. Current plan pricing and included AI balances are on the pricing page.

What if I cannot verify a vendor's automation claim? Ask for a live build of your three hardest rules during the demonstration, and check the vendor's help centre rather than its marketing pages. If a capability is only described in a brochure, treat it as unproven. Our evaluation checklist sets out the questions to put to any vendor.

The short version

Automation earns its place when it removes copying, not when it removes judgement. Map one matter type, automate the internal steps first, keep trust movements and the last read with a person, and review the exception list monthly. Six rules that work beat a hundred that were switched off.