The Task Management report helps you understand how task work is progressing across your onboarding and Professional Services projects.

For managers and delivery leaders, it helps answer one practical question:

Where is work getting stuck, and what needs our attention?

Use the report to monitor outstanding work, identify blocked or overdue tasks, prepare for upcoming commitments, find ownership gaps, and investigate task patterns that may put delivery timelines at risk.

Use Task Management to understand:

This report is especially useful when you need a task-level view across multiple projects instead of opening each project individually.

Task Management uses the standard GUIDEreports filters, including:

You can combine filters to focus the report on the work relevant to your review.

For example:

Now the report answers a much narrower question:

Which customer-owned tasks are currently Stuck for this customer?

For complete filter behavior and date-range options, see Use GUIDEreports: Filters, drilldowns, sorting, and navigation.

Start with the summary metrics to understand the size and current state of the workload.

Question it answers: How much task work exists?

Total Tasks counts all tasks regardless of task or project status.

Use it as a broad task-volume metric.

Because it includes completed, inactive, and other task populations, do not interpret Total Tasks as the amount of work still remaining.

Question it answers: How much task work is still outstanding across active delivery projects?

For the Task Management Standard report, Active Tasks:

Use this metric to understand the amount of work still outstanding within the report's active-project scope.

Question it answers: How much task work has been completed or is no longer required?

Completed Tasks includes tasks whose status is:

and uses the Task Management active-project scope.

Important: A task marked Not Applicable may represent work that was not required rather than work that was performed. Completed Tasks therefore means completed or no longer required, not only work completed through Done.

Question it answers: Where is work currently blocked?

Stuck Tasks counts tasks currently in the Stuck status within the report's active-project scope.

Use it as a high-priority investigation signal.

A Stuck status tells you that work has been identified as blocked.

It does not tell you why.

Use the drilldown and underlying task context before deciding what action is needed.

Weekly metrics help separate work that is coming due from work that recently reached completion.

Question it answers: What does the customer need to complete this week?

This metric focuses on tasks with Customer responsibility whose due dates fall within the current workweek.

Use it before customer calls or weekly project reviews to identify near-term customer commitments.

Question it answers: What does our own team need to complete this week?

This metric applies the current-workweek logic to tasks with Internal responsibility.

Use it to prepare for delivery-team standups, portfolio reviews, or short-term workload planning.

Question it answers: How much internally owned work reached Done this week?

This metric focuses on Internal tasks that moved into the Done category during the current workweek.

Use it to review recent internal delivery progress.

Question it answers: How much customer- or partner-owned work reached Done this week?

For this metric, External includes:

It focuses on externally owned tasks that moved into Done during the current workweek.

Overdue reporting helps answer two different questions:

How much overdue work exists?

and:

Where is it concentrated?

Overdue work has an end date before the current time and has not reached a completed or Not Applicable state.

Use overdue metrics as a signal that planned timing has already been missed.

Then investigate the task before deciding why.

Question it answers: How much internally owned work is past its planned end date?

Use it to identify internal delivery commitments that may need follow-up, replanning, or blocker resolution.

Question it answers: How much externally owned work is overdue?

Use this as an external-action signal when reviewing customer or other externally owned responsibilities represented by the widget.

Question it answers: How much overdue customer work already has an identified owner?

This metric focuses overdue Customer responsibility tasks that already have an assignee.

It helps distinguish:

“This task is overdue and has an owner.”

from:

“This task may also have an ownership gap.”

Those situations usually require different follow-up.

A portfolio-wide overdue total tells you how much work is late.

Overdue Tasks by Project helps you understand where that work is concentrated.

Use it to identify projects carrying the largest overdue-task populations and review how those tasks are distributed across statuses.

This widget excludes projects that are:

This view narrows the investigation to overdue customer-owned work.

Use it when you want to identify projects where customer action items may be contributing to delivery risk.

The chart gives you the project-level signal.

The drilldown gives you the individual tasks.

Unassigned work deserves different attention from work that already has an owner.

Question it answers: How much incomplete work currently has no qualifying assignee?

A task is considered assigned when it has at least one assignee who is still a member of the project.

Use Is Assigned = False in the drilldown when you need to locate the individual tasks.

Question it answers: Who is responsible for the work that currently lacks an assignee?

This view groups unassigned tasks by responsibility.

Use it to distinguish ownership gaps across:

Question it answers: Which projects have the largest concentration of ownership gaps?

This widget excludes:

projects.

Use it to prioritize the projects where assignment cleanup may have the greatest impact.

Task Management also helps you look beyond today's task status and identify historical patterns in task templates.

These views are different from current-state metrics.

This table looks at historical occurrences of tasks being marked Stuck.

A task can contribute to this pattern even if it is no longer Stuck today.

Use it to identify templates that may deserve review for:

The table identifies the pattern.

It does not establish the cause.

Use this table to identify task templates whose task instances have repeatedly completed later than expected.

This can be a useful reason to review whether:

This view identifies task templates whose tasks frequently finish earlier than planned.

Repeated early completion can be useful when reviewing whether a template's planned duration still reflects actual delivery behavior.

Task Management uses the task-oriented GUIDEreports drilldown.

Depending on the widget, fields can include:

Every drilldown column header can be sorted A → Z or Z → A.

For complete field definitions, see the GUIDEreports drilldown field reference.

The Task Management workflow is:

Summary → concentration → individual task → action

For example, if Stuck Tasks is high:

The report identifies the records that need investigation.

The task and project provide the operational context.

Several task fields are especially helpful during investigation.

Days Open measures the time since the task was created.

For open tasks:

Once the task is Done, the field is empty.

Status Explanation can provide free-text context associated with the task's current status.

It is not available to customer or partner users.

The following is an illustrative Professional Services scenario.

A delivery leader is preparing for a weekly portfolio review and wants the meeting focused on work that actually needs intervention.

They review:

This provides a quick picture of outstanding work, blockers, and ownership gaps.

They check:

Now they know which short-term commitments could become problems if they do not move.

They compare:

They use:

One implementation accounts for a large share of overdue work.

The leader reviews:

Now the conversation can move from:

“We have a lot of overdue work.”

to:

“Most of the overdue work is concentrated in these two projects, and these are the specific internal and customer tasks we need to address.”

If the same types of tasks repeatedly create friction across projects, the team reviews the Top 5 historical tables.

That helps separate today's individual issue from a recurring template-level problem.

These are suggested reporting practices rather than product requirements.

Instead of reviewing every widget, begin with a question such as:

Which active projects have blocked or overdue work that needs intervention this week?

Then use only the metrics that help answer it.

Total Tasks is broad.

Use Active Tasks when your question is specifically about incomplete work within the Standard report's active-project scope.

Completed Tasks includes both:

Keep that distinction in mind when discussing task completion.

A task due this week is an opportunity to follow up before it becomes overdue.

Use these metrics for delivery planning, customer calls, and weekly reviews.

Use Is Assigned, Assignee Names, and Responsibility before deciding what follow-up is needed.

An unassigned task and an assigned-but-Stuck task usually require different next steps.

Summary and overdue widgets help investigate current work.

The Top 5 tables help identify recurring template behavior.

Do not treat them as the same kind of signal.

For the Standard Task Management metrics documented here, active-project calculations exclude projects that are:

The dashboard tells you where a pattern exists.

The underlying task tells you the context you need before acting.

For the Task Management Standard report, Active Tasks are not Done or Not Applicable and belong to projects that are not:

No.

The Standard Task Management active-project scope excludes On Hold projects.

The Completed Tasks metric includes both Done and Not Applicable.

Not Applicable can represent work that is no longer required, so the metric should not be interpreted as only work that was performed.

A Stuck Task has a current task status of Stuck within the Task Management active-project scope.

The status tells you that work is blocked but not why.

Review the underlying task for context.

External includes Customer- and Partner-responsibility tasks.

The Standard report counts those tasks when they move into Done during the current workweek.

An overdue task has passed its end date and has not reached a completed or Not Applicable state.

Overdue Customer Tasks provides a broader external overdue-work signal.

Assigned Customer Tasks Overdue specifically focuses on overdue tasks with Customer responsibility that already have an assignee.

Open the task drilldown and use Is Assigned = False.

A task is considered assigned when at least one qualifying assignee remains a member of the project.

The field is empty when the task has no qualifying assignee.

When multiple users are assigned, their names can be shown together for the task.

For open tasks, Days Open continues calculating through the current time.

That means the value can change each time you view the report.

The Top 5 table uses historical Stuck occurrences.

A past Stuck event can remain part of the template pattern even after the task moves to another status.

Status Explanation is not available to customer or partner users.

Yes.

Use the Customer filter and combine it with Task Status, Task Responsibility, dates, custom fields, tags, or other available filters as needed.

See Use GUIDEreports: Filters, drilldowns, sorting, and navigation.

First, narrow the Standard report with filters.

Then review the GUIDEreports widget library for other available task widgets.

If you need a different combination, you can build a custom GUIDEreport.