See who is on each task and when it is due.

Tasks are the to-dos that keep a matter moving: drafting the complaint, filing the motion, chasing a client who has gone quiet. Each carries a priority and a stage, and you add the people responsible.

Build the board and the checklist once

Name the columns for a practice area or one matter. Break a large job into sub-tasks with their own dates. Save the set as a task list that dates itself from the matter.

Stages you control

Reusable lanes per practice area, or per individual matter.

Task list and task template describe the same thing. The list is the named container, and the tasks inside are templates until they land on a real matter.

Task lists and templates

Sub-tasks under a parent

Break a big job into steps that each carry their own dates.

Lists that date themselves

Apply a list and the open date becomes real deadlines.

Keep the hours and the thread on the task

Every task row carries a record-time control, so the billable hour lands on the work that produced it. Comments sit on the task, and the matter gathers its tasks on one tab.

Record time from the task

Log the billable hour against the work that produced it.

Discussion on the task

Comment where the work is instead of in an email thread.

Every task on the matter

The case's outstanding work gathered on its own tab.

Start with tasks, stages, and lists.

Browse the docs

FAQs

Stages, sub-tasks, reusable lists, comments, and recording time.

What can a task belong to?

Usually a matter, where it carries a priority, a stage, and any assignees you add. A task can also belong to a lead when a lead's workflow creates one. Lead tasks differ in three ways: no stage field, scheduling limited to a fixed date or none, and no clone or sub-tasks until the lead becomes a matter.

Can I change the columns on the task board?

Yes, at two levels. You can build reusable stage layouts for a practice area so every matter of that kind opens with the same lanes, and you can manage the columns on a single matter's board when one case needs something different. Task types are separate, and label the kind of work rather than its progress.

What are sub-tasks for?

Breaking a larger job into trackable steps. A sub-task is a full task in its own right with its own priority, stage, dates, and assignees, nested under a parent. In the task list a parent with sub-tasks shows a small arrow you can expand, so the detail is there without cluttering the view.

What does a task list actually save?

Retyping the same checklist for every case of a kind. A task list is a reusable bundle of pre-written tasks including their priorities, assignees, and sub-tasks, plus a scheduling rule. Applying it to a matter clones the whole set across, and the rule turns that matter's open date into real start and due dates.

Can I add a whole checklist to a matter that already exists?

Yes. Open the matter's Tasks tab and assign a task list, and every task in it is copied onto the matter with its sub-tasks, assignees, and scheduling included. Assigning a list adds tasks, so running the same one twice gives you a second copy of each.

Can I bill time against a task?

Yes. Each task row carries a record-time control, so the billable hour is logged against the work that produced it rather than reconstructed later. The entry lands in Activities like any other and flows through to the invoice from there.

How does the team discuss a task?

In comments on the task itself, which keeps the decision next to the work instead of in somebody's inbox. It is the same thread you get on a matter, a contact, a lead, a document, and an invoice: mention a colleague with @ to notify them, reply to what was said, react to it. Reading comments needs only view access, while posting one needs create access, so a member can follow a discussion they are not contributing to.

Stop asking what is outstanding.