Skip to content

Task Status and Progress

Overview

Task status and progress fields help teams understand where work stands.

In practice, these fields serve different purposes. Status shows the task’s current state in its lifecycle, while progress can add context about how far the work has advanced. Together, they help people understand the current condition of a task and how work is moving.

Keeping these fields current can also improve shared visibility. Status changes may affect reporting, schedule visibility, workflow progression, and what managers see in dashboards. In some setups, related views and dependent process steps can also change when a task’s status changes.

Because connected behavior depends on which features are enabled, status and progress are best treated as both a communication tool and, in some workspaces, a workflow signal.

When you would use this

Use task status and progress when the current state of work needs to be visible to other people.

  • When you need to show the current state of a task clearly
  • When your team wants reporting to reflect task movement
  • When managers rely on dashboards or schedule views for visibility
  • When a task update may influence workflow progression
  • When multiple people need a shared understanding of where work stands

How it works

Status shows the task’s current state

The Status field indicates where a task stands in its lifecycle. This gives people a quick view of whether work is still underway, complete, or in another state defined by your team.

Progress adds context

The Progress field helps show how far the work has advanced. It can be useful when a status label alone does not provide enough detail.

The available information confirms that progress is part of this feature, but it does not define how progress is displayed or managed in every workspace.

Updates can affect other views

A task status change can affect other parts of the product, including:

  • reporting
  • schedule visibility
  • workflow progression
  • manager dashboards

In some workspaces, related views and dependent process steps can also change when status changes, where those features are enabled.

Not every workspace uses the same connected features. Some teams may use status mainly for visibility, while others may connect it more directly to workflow or process steps.

Typical workflow

  1. Open the task you want to review.
    Start with the task record so you can see its current status and progress.

  2. Check the current fields.
    Confirm the existing status and progress before making changes.

  3. Update the status as work changes.
    Change the status when the task moves forward or reaches a new state.

  4. Review progress if your team uses it.
    If progress is tracked separately, update or confirm it as needed.

  5. Look at related areas if relevant.
    If your workspace uses connected reporting, schedules, workflows, or dashboards, those areas may reflect the status change.

Fields, controls, or options you may see

Field or control What it means Notes
Status Shows the current state of the task May affect reporting, schedule visibility, workflow progression, and dashboards
Progress Shows how far the task has advanced Exact format may vary by workspace

You may also see the task reflected in related areas such as:

  • Reports
  • Schedule views
  • Workflow or process views
  • Manager dashboards

Status changes can influence more than the task itself. When supported in your workspace, they may update related views or affect dependent process steps.

Because this behavior varies based on enabled features, do not assume every task status change will trigger the same result in every environment.

Things to watch for

  • Downstream effects may be conditional.
    Related views and dependent process steps change only where those features are enabled.

  • Status and progress may be separate.
    The available information does not show that changing one always changes the other.

  • Workspace setup may vary.
    The exact way status and progress appear or behave can differ between teams.

  • Dashboards depend on current task data.
    If task fields are not kept up to date, related reporting and manager views may be less useful.

  • Assign a Task
  • Create a Task
  • Reporting
  • Schedule visibility
  • Workflow progression
  • Manager dashboards