# Work in Project Workspace

Canonical HTML: [https://collty.com/help/projects/work-in-project-workspace](https://collty.com/help/projects/work-in-project-workspace)
Audience: Project participants
Reading time: 15 min
Updated: 2026-07-15T00:00:00.000Z

Run daily delivery: plan tasks, assign specialists, connect dependencies, update progress and keep project communication in context.

## One place for active delivery

Project Workspace is the working surface for an active project. The left side shows progress and the project calendar; the main area shows the tasks for the selected planning period; the top actions open Project chat, Team chat and Project Analytics without losing the current task context.

The workspace follows the project's operating model. Sprint controls appear for sprint-based delivery, hours appear only when time tracking is enabled, and financial actions remain hidden when the project does not use billing or invoices.

## Find the work that matters now

1. **Choose a planning period:** Select a week or configured delivery period in Calendar. The task list updates to that period without changing the project's total duration.
2. **Switch between Date and Status:** Date keeps work in delivery order. Status groups work by its current state and unlocks the status filter.
3. **Filter by tags:** Use one or several project tags. Match all narrows the result to tasks containing every selected tag.
4. **Use All only when necessary:** All shows tasks across planning periods. Return to the active period for focused daily work.
5. **Read the completion counter:** The Done/Total indicator summarizes the currently visible scope, not unrelated tasks outside the filter.

## Create and maintain a delivery task

1. **Add a task:** Choose Add task, give it a concrete outcome and place it in the correct delivery period.
2. **Add useful detail:** Write the description as completion evidence. Checklist lines are useful when one outcome has several verifiable parts.
3. **Assign the project team:** Choose one or more specialists from the active project team. When time tracking is enabled, distribute the planned hours between them.
4. **Add dates, status and tags:** Dates place the task on Calendar; status drives delivery reporting; tags make cross-sprint filtering possible.
5. **Link the source plan:** If the task came from Project Architect, keep its Architect link so the delivery task remains connected to the original plan item.
6. **Save, then update the state:** Keep the task current as work moves from Pending to In progress, Done and, when the client owns acceptance, Accepted.

## Use task status consistently

| Status | Use it when | What it communicates |
| --- | --- | --- |
| Pending | The task is planned but work has not started | The commitment exists in the selected delivery period |
| In progress | At least one assignee is actively working | Workload and current delivery activity |
| Done | The team has completed the expected outcome | The work is ready for review or acceptance |
| Accepted | The authorized client reviewer confirms the result | The delivery outcome has passed its acceptance boundary |

> **Good to know:** Do not use Done only to make the progress number look better. The task description, checklist and linked evidence should make completion understandable to another project participant.

## Connect work with Work Graph

Work Graph explains how tasks affect one another. Open a task, choose a relationship type, then search the project task list. The relationship is visible from both ends so a blocker is not hidden inside one person's task.

| Relationship | Meaning | Use it for |
| --- | --- | --- |
| Blocked by | This task waits for another task | A real predecessor that prevents work from moving |
| Blocks | This task must finish before the selected task can move | Making downstream delivery risk visible |
| Handoff | The result moves from this task to another | Design-to-development, research-to-strategy or team-to-team transfers |
| Related | The task provides useful context without stopping work | Parallel work, shared evidence and contextual links |

> **Good to know:** On mobile, Choose task opens as a full-screen searchable sheet with its own scrolling list. Tasks remain compact rows and do not stretch to fill the viewport.

## Keep progress and collaboration separate

- Task status says what happened to the deliverable; Team Pulse says how collaboration around the task feels.
- Use Project chat for decisions and communication tied to this project.
- Use Team chat for the wider team conversation when that channel is available to your role.
- Task comments keep a discussion attached to the relevant work item instead of burying it in a general thread.
- Private messages and scheduled meetings are available from the communication layer when a conversation should move to a smaller group.

## A practical daily routine

1. **Open the current delivery period:** Scan Progress, Calendar and the visible task count before changing anything.
2. **Review blocked and active work:** Filter by Status and inspect Work Graph links before assigning more work.
3. **Update only changed tasks:** Keep assignees, status, dates and checklist evidence current.
4. **Record collaboration signals:** Use Team Pulse when there is meaningful evidence, not as a decorative daily vote.
5. **Open Analytics for patterns:** Use task details for one item and Project Analytics for workload, schedule and cross-sprint patterns.

## Related guides

- [Create A Project And Choose Its Operating Model](https://collty.com/help/projects/create-a-project-and-choose-its-operating-model)
- [Read Project Analytics And Team Pulse](https://collty.com/help/projects/read-project-analytics-and-team-pulse)
- [Plan With Project Architect](https://collty.com/help/projects/plan-with-project-architect)