> ## Documentation Index
> Fetch the complete documentation index at: https://docs.holace.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Tasks Overview

> Tasks attached to journeys vs floating, assignees, due dates, and status flow.

Tasks are HoLaCe's built-in to-do system. Every task has a title, an assignee, an optional due date, an optional journey link, and a status. They're how individual work items get tracked when a Stage transition isn't the right unit ("call the adjuster," "request records from Dr. Smith," "follow up on filing fee invoice").

\[Screenshot: Tasks page with a list of open tasks, due dates, and assignee avatars]

## Where tasks live

Two views:

1. **Sidebar → Tasks** — every task assigned to you across every journey, filtered by default to "open and due soon." This is your daily plate.
2. **Journey → Tasks tab** — every task attached to a specific journey. Useful when you're in deep on one case.

Both views read from the same task records — there's no parallel system.

## Attached vs. floating tasks

| Type         | What it means                                                                                                    |
| ------------ | ---------------------------------------------------------------------------------------------------------------- |
| **Attached** | The task has a `journeyId` set. It's tied to a specific case and shows up on that journey's Tasks tab.           |
| **Floating** | The task has no journey. Use for personal reminders, firm-wide admin work, or anything that isn't case-specific. |

When you create a task from inside a journey, it's automatically attached. When you create one from the Sidebar Tasks page, you can choose to attach or leave it floating.

## Creating a task

1. Click **+ New Task**.
2. Title (required). Be action-oriented — "Call adjuster re: medical records" beats "Adjuster."
3. Assignee (defaults to yourself; change to anyone on the firm).
4. Due date (optional — but you'll want one for accountability).
5. Description (optional — paste relevant context, links).
6. Journey link (optional — start typing a client name to attach to a journey).
7. Priority — Low, Medium, High, Urgent.
8. **Roadblock** flag — see [Roadblocks](/admin-cross-cutting/tasks/roadblocks).
9. Save.

## Status flow

| Status        | Meaning                           |
| ------------- | --------------------------------- |
| `pending`     | Created, not yet started          |
| `in_progress` | Actively being worked             |
| `blocked`     | Waiting on someone or something   |
| `completed`   | Done — drops off the default view |

Move statuses by clicking the status chip on the task row, or by checking off the task to mark it complete.

## Filtering and sorting

The default Tasks page filter is **assigned to me, not yet completed, sorted by due date ascending**. Use the filter bar to change scope:

* **Assignee** — anyone on the firm
* **Status** — open / in progress / blocked / completed / all
* **Journey** — scope to a specific case
* **Priority** — only Urgent, only High, etc.
* **Due window** — overdue, today, this week, this month, no due date

Filters compose. You can pin filter combos to your sidebar as saved views.

## Reassignment

Click the assignee avatar on any task row and pick a new person. They get a **`ASSIGNMENT_NEW`** notification (and an email if their notification preferences allow it). The previous assignee gets `ASSIGNMENT_DECLINED` for transparency.

## Bulk actions

Multi-select tasks (shift-click) to mark complete, change priority, reassign, or delete in bulk. Useful when triaging the start-of-day list.

## Tasks vs. Stage Steps

Don't confuse tasks with Stage Steps. Steps are the structured checklist that drive Stage progression on a journey ([Avenue System](/getting-started/glossary)). Tasks are flexible to-dos that don't gate progression. If something is a *required* part of moving to the next stage, make it a Step. If it's an action item with a deadline, make it a Task.

<Note>
  Roadblocks (a task flagged as blocking real progress): [Roadblocks](/admin-cross-cutting/tasks/roadblocks).
</Note>