Tasks

Tasks cover all the work items across your various projects. They show how budgets are being used by your team to complete project deliverables.

Each task is the unit of work your team plans, executes, and reports against. Budgets sit on deliverables, tasks and bugs sit underneath as the work, and timelogs pull actual spend up against both. That's how the numbers on Project Overview (Resourced, Worked, Cost to business) are calculated, one task at a time.

What a task captures

• Title, Priority, Status — the shape of the work and where it sits in progress
• Assignees (who's doing it, one or more team members, each with their own hours estimate) and Reporter (who it's accountable to)
• Budget — shown only for deliverables. Tasks and bugs don't carry their own budget; they roll under their parent deliverable
• Estimated hours and Start / End dates for the planned time window. When a task has multiple assignees, hours split per person, which is what the Planning view surfaces column-by-column
• Billable — flag whether logged time counts toward client-billed work or internal overhead
• Labels for cross-project categorisation (see Settings → Project setup → Labels)

Start creating tasks by selecting Add New to create your first task. If your quote is already approved, select Import from Quote to populate your tasks automatically.

Sub-tasks

Every task belongs to one of three types — Deliverable, Task, or Bug — set when you create the task. Only Deliverables can have sub-tasks nested underneath them, allowing you to break larger deliverables into smaller, assignable tasks or link related bugs to track progress more effectively.

Importing from a quote

If your project has an approved quote, use Import from quote to turn your quoted scope into tasks in one action, so the deliverables your client signed off become the deliverables your team executes against. Pick how the quote's structure should map — the modal walks you through the three options.

The button only appears once a project has at least one approved quote. Imports always create new tasks, so if you've already imported and want to redo it, delete the tasks first — the modal warns you before it duplicates.

Working on a single task

Click any task in the list to open its side panel. This is where the day-to-day work happens: updating fields, writing what's been done, tagging colleagues, and checking how the numbers are tracking against the plan.

The panel has four layers:

• Fields at the top, all editable inline (the ones listed above). Changes save as you make them, so anyone else with the task open sees your update in real time.
• Description as a working record of what the task involves, what's been done, and what's still outstanding. Treat it as the ticket's running notes so whoever picks it up next can get up to speed without asking around.
• Activity tabs as the audit trail: All (every event in one stream), Comments (threaded notes between the team; use @name to tag someone into their notifications), Activity (field-level change history), Timelogs (every hour logged against this task by every team member, the raw material behind the Reports section below).
• Reports to see how the numbers are tracking. For deliverables, this compares Budget against Resourced and Worked spend. For tasks and bugs, it shows Resourced and Worked against the parent deliverable's budget. Empty until timelogs start landing, then it builds up automatically, priced against each person's rate card. If it shows "Missing information to generate report", the task either has no assignees, no logged time, or (for deliverables) no budget set.

Managing your tasks

• Toggle between List view (a flat list of all tasks) and Nested view (deliverables with their sub-tasks grouped underneath) using the icons next to the Add New button. Nested view helps you quickly compare signed-off budget, resourced costs, and actual worked costs from timesheet data.
• Always keep your task statuses up to date, as they indicate progress towards completing your deliverables. Keeping them accurate provides a clear view of progress and reduces the need for colleagues or clients to check in on incomplete tasks. Regularly updating statuses helps the team stay aligned, improves project visibility, and ensures expectations are managed throughout the project lifecycle.
• Filter by assignee by clicking a team-member avatar at the top of the list (or Unassigned to see work no one's picked up). Handy for a quick "what's on Sam's plate this week?" scan.
• Filter by status, priority, type, or label from the dropdown next to the avatars, when you want to narrow to something like "what's high priority and still To do?". The Labels tab searches every label in the workspace by name, so it stays usable however many you have.
• Change task type from the box icon next to the title on any task. Useful when a task turns out to be a bug, and it's also how you assign a standalone task to a deliverable after the fact.

Kept current, your tasks are the ground truth for every number that flows up: Worked spend on the Project Overview, allocations on the Resourcing page, and the profitability picture on Project Spend. Everything else in Trellis reads from what's here.

Who can do what

Viewers see the Tasks page in read-only mode. They can browse tasks, filter and switch views, and even join the conversation via comments — but they can't create tasks, edit any fields, or see the Reports section that surfaces budget-vs-actual data. Every other role has full write access to tasks on projects they're a member of. Owners, Admins, and Editors can open any project without joining it, but every write on this page still needs project membership — Trellis offers to add you the moment you try one.