Automate the routine work around a matter

Workflows do the follow-up when something happens - a document arrives, a matter opens, a task is done - and pause for a person's approval where it matters.

Much of the work around a matter is the same every time. A summons arrives and someone diarises the deadlines. A matter opens and someone runs the intake checklist. A lease is uploaded and someone reads it and tells the team. A workflow does that follow-up the moment it is needed, so nothing waits on someone remembering - and where judgement matters, it stops and asks a person first.

A lease is uploaded to a matter and the firm's Document review workflow starts on its own: Squire drafts a review and asks for approval, the lawyer reads the draft and ticks Approve this review, and only then is the review saved to the matter as a note. Then a second workflow, Contract expiry watch, set to run when a contract is 30 days from expiry: on that contract's matter, the team is notified and a Decide on renewal task appears, assigned to the matter lead.

How a workflow works

Every workflow reads as one sentence, and the builder narrates it back to you in plain English before you save it.

When

Something happens: a matter is opened, a document is uploaded or its summary is ready, a task is created or completed, a contract is created, executed, changes status or nears expiry, a table changes - or someone clicks the workflow's button on a matter.

Only when

Optional filters narrow it down, so a workflow runs only for the matters, documents or tasks it is meant for.

Then

The steps run in order: ask Squire to analyse or draft, create to-dos or notes, notify people, pause for someone's input, update records, or fill in a table. Each step can use what the steps before it produced.

A person decides where it matters

A workflow can stop part-way and ask someone to approve or add to the work before it carries on. Squire drafts; the person it asks reads the draft, approves it or adds comments, and only then does the workflow save the note or tell the team. The request arrives as a notification and waits under Pending Actions until it is answered.

  • Save & test runs a new workflow on sample data and shows each step's result - nothing real is created - before it goes live.
  • Owners and admins see every run, step by step, under History, and can switch any workflow off.
  • A step that asks Squire to draft or analyse produces a draft for a person to check. Where the result matters, follow it with an approval step.

Start from a template

Each template is a complete workflow you can use as it is or change to suit your practice.

New matter intake

An intake checklist and a briefing for the team as soon as a matter opens.

Summarize new documents

Every uploaded document gets a summary and a note of its key dates and obligations.

One-click matter status report

A button on the matter that writes a full status report as a note.

Human-in-the-loop document review

Squire drafts a review of each new document; a person approves it before it is saved.

Contract expiry watch

The team is told, and a to-do created, when a contract nears expiry or its notice deadline.

Follow up on completed tasks

When a task is done, Squire suggests the next step to the person who finished it.

Need something the templates don't cover? Build it from scratch, or choose Have us build it for you and someone from Squire will set it up with you.

Where to find it

Open the Workflow section in the sidebar: View All to set up and manage workflows, Pending Actions for anything waiting on you, and History to review what they have done. A workflow started by a button appears on the matter, under Tasks → Automations.

Workflows decide when. Skills decide how.

A workflow runs work without anyone asking. A skill teaches Squire how your firm does a kind of work - an NDA review, a compliance check - so it follows your method whenever it is asked, and you can run it as a command for the same result every time. Teach Squire your way of working