Overview
GUIDEreports drilldowns help you move from a summary metric or chart to the individual records behind it.
Depending on the report, a drilldown may contain task, project, CSAT, time-entry, or workspace-user data.
Use this reference when you see a column in a drilldown and want to understand what it represents.
How drilldowns work
Not every GUIDEreports widget has a drilldown.
Hover over a widget and watch your cursor:
If the cursor changes to a pointer hand, you can select the widget to open its drilldown.
Once you're in a drilldown, every column header can be sorted A → Z or Z → A.
For more about navigating reports and investigating results, see Use GUIDEreports: Filters, drilldowns, sorting, and navigation.
Which drilldown should I expect?
Different GUIDEreports use different record types.
Record type | Commonly used in |
Task | Task Management, Customer Engagement, and task-focused areas of PM Command Center |
Project | Projects Overview, Historical Trends, and project-focused areas of PM Command Center |
CSAT | CSAT |
Time entry | Advanced Time Reporting |
Workspace user | Users Overview |
Some reports, such as PM Command Center, can use more than one drilldown type depending on the widget you open.
Task drilldown fields
Task drilldowns help you investigate the individual work contributing to task metrics, charts, and customer-engagement signals.
Field | What it shows |
Task Name | The name of the task. |
Project Name | The project the task belongs to. |
Responsibility | Who is responsible for the task: Internal, Customer, or Partner. |
Priority | The task's assigned priority. |
Visibility | The task's customer visibility setting. |
Sign Off Required | Whether sign off is required for the task. |
Csat Enabled | Whether CSAT is enabled for the task. |
Start Date | The task's scheduled start date. |
End Date | The task's scheduled end or due date. |
Created At | When the task was created. |
Updated At | When the task was most recently updated. |
Is Assigned | True when the task has at least one assignee who is still a member of the project. |
Assignee Names | The names of users assigned to the task. When multiple people are assigned, their names appear alphabetically and are separated by commas. |
Is Complete | True when the task's current status belongs to the Done category. |
Is Overdue | True when the task's end date has passed and the task is not currently in the Done category. |
Completed At | When the task reached completion. |
Days Open | The number of days since the task was created. This value can include decimals, updates over time, and is empty once the task is done. |
Is Subtask | True when the task is a subtask of another task. |
Status Created At | When the task entered its current status. |
Status Updated At | When the task's current status was most recently updated. |
Status Explanation | Additional text entered to explain the task's current status, when available. |
Status Label | The task's current status label as configured in the workspace. |
Brand Name | The brand associated with the task's project. |
Brand Is Retired | Whether the associated brand has been retired. |
Important: Status Explanation is not available to customer or partner users.
Useful task fields for common investigations
If you're trying to find... | Look at... |
Tasks with no owner | Is Assigned, Assignee Names |
Overdue work | End Date, Is Overdue |
Blocked work | Status Label, Status Explanation |
Customer-owned work | Responsibility |
Tasks that have remained open a long time | Days Open |
Recently completed work | Completed At |
Subtasks versus main tasks | Is Subtask |
Recently changed work | Updated At, Status Updated At |
Why Days Open can change
Days Open is time-based.
For an open task, it continues to calculate through the current time. That means you may see a different value when you return to the report later.
Once the task is done, the field is empty.
Project drilldown fields
Project drilldowns provide the underlying project records behind portfolio, historical, forecasting, and project-health metrics.
Field | What it shows |
Project Name | The project's name. |
Customer Name | The customer associated with the project. |
Internal Summary | The project's internal summary. |
External Summary | The project's external summary. |
Start Date | The project's scheduled start date. |
Due Date | The project's planned due date. |
Done Date | The date the project was completed. |
Forecasted End Date | The project's currently forecasted completion date. |
Kicked Off At | When the project was kicked off. |
Created At | When the project was created. |
Updated At | When the project was most recently updated. |
Cash Value | The Cash Value stored on the project. |
Billing Rate | The billing rate stored for the project. |
Is Forecasted Late | Whether the project is currently identified as forecasted late. |
Is Forecasted Ahead | Whether the project is currently identified as forecasted ahead of schedule. |
Is Complete | Whether the project is complete. |
Is Overdue | Whether the project is currently considered overdue. |
Duration Days | The project's reported duration in days. |
Planned Duration Days | The project's planned duration in days. |
Forecasted Duration Days | The project's forecasted duration in days. |
Forecasted Variance Days | The reported difference between planned and forecasted project timing, expressed in days. |
Pm Member Ids | The underlying member IDs associated with the project's project manager assignment. |
Phase Names | The names of phases associated with the project. |
Milestone Names | The names of milestones associated with the project. |
Brand Name | The brand associated with the project. |
Brand Is Retired | Whether the associated brand has been retired. |
Status Updated At | When the project's current status was most recently updated. |
Status Explanation | Additional context recorded for the project's current status, when available. |
Status Label | The project's current status label. |
Rag Status | The project's reported RAG-status value. |
Rag | The project's associated RAG value in reporting. |
Note: Project duration and forecasting fields are designed to help compare planned and expected delivery. Where exact calculation logic matters, use the applicable report or GUIDEreports widget library rather than trying to recreate the calculation from the drilldown values alone.
Useful project fields for common investigations
If you're trying to understand... | Look at... |
Which customer owns the project | Customer Name |
Planned versus expected completion | Due Date, Forecasted End Date |
Future delivery risk | Is Forecasted Late, Forecasted Variance Days |
Projects expected to finish early | Is Forecasted Ahead |
Actual completed timing | Done Date, Duration Days |
Project structure | Phase Names, Milestone Names |
Financial context | Cash Value, Billing Rate |
Project health | Status Label, Rag Status, Rag |
Recent project changes | Updated At, Status Updated At |
Cash Value
Cash Value represents the value stored on the project.
Depending on your workspace configuration, this field may be populated manually or through automation.
How your organization interprets Cash Value depends on how the field is used in your workspace. It should not automatically be interpreted as recognized revenue.
CSAT drilldown fields
The CSAT drilldown helps you move from satisfaction scores and trends to the individual surveys and responses behind them.
Field | What it shows |
Project Name | The project associated with the CSAT survey. |
Customer Name | The customer associated with the survey. |
Csat Level | The level where the CSAT survey was sent, such as project or milestone. |
Public Csat Surveys Status | The survey's current reporting status. |
Sent At | When the survey was sent. |
Responded At | When the recipient responded. |
Rating Label | The descriptive label associated with the response rating. |
Rating Score | The numerical rating provided in the response. |
Comment | The written comment submitted with the response, when provided. |
Is Satisfied | Whether the response is categorized as satisfied by the CSAT reporting data. |
Project Status Category | The reporting status category of the associated project. |
Project Status Label | The project's status label. |
Milestone Name | The milestone associated with the response, when the survey is milestone-level. |
Milestone Status Category | The reporting status category of the associated milestone. |
Milestone Status Label | The milestone's status label. |
Recipient First Name | The survey recipient's first name. |
Recipient Last Name | The survey recipient's last name. |
Recipient Full Name | The survey recipient's full name. |
Recipient Email | The email address associated with the survey recipient. |
Useful CSAT fields for common investigations
If you're trying to understand... | Look at... |
What score the customer gave | Rating Score, Rating Label |
Why a customer gave that score | Comment |
Whether the response was project- or milestone-level | Csat Level |
When feedback was requested and received | Sent At, Responded At |
Which project or milestone the feedback relates to | Project Name, Milestone Name |
Who received the survey | Recipient Full Name, Recipient Email |
Delivery status at the associated level | Project Status Label, Milestone Status Label |
Tip: A CSAT score tells you what the customer selected. The Comment field can provide the context you need to understand the response.
Time-entry drilldown fields
Advanced Time Reporting uses a specialized time-entry drilldown.
These fields help you understand what work time was logged against, when it was logged, whether it was billable, and who logged it.
Field | What it shows |
Task Name | The task associated with the time entry, when applicable. |
Project Name | The project associated with the time entry. |
Customer Name | The customer associated with the project. |
Entry Level | The level where time was entered, such as directly against a project or against a task. |
Date Worked | The date the work occurred. |
Billable | Whether the time entry was recorded as billable. |
Time Worked | The amount of time recorded. |
Project Status Category | The reporting status category of the associated project. |
Project Status Label | The project's status label. |
Task Status Category | The reporting status category of the associated task, when applicable. |
Task Status Label | The task's status label, when applicable. |
Task Is Subtask | Whether the associated task is a subtask. |
Category Name | The time-entry category associated with the entry. |
Member First Name | The first name of the member associated with the time entry. |
Member Last Name | The member's last name. |
Member Full Name | The member's full name. |
Useful time-entry fields for common investigations
If you're trying to understand... | Look at... |
Who recorded the time | Member Full Name |
When the work occurred | Date Worked |
How much time was recorded | Time Worked |
Whether the time is billable | Billable |
What project received the effort | Project Name |
What task received the effort | Task Name |
Whether time was entered at the project or task level | Entry Level |
What type of work consumed the time | Category Name |
Project time versus task time
Project time is entered directly against a project.
Task time is entered against an individual task.
The Entry Level field helps distinguish between the two when reviewing time-entry records.
Workspace-user drilldown fields
The Users Overview report uses workspace-member records rather than project or task records.
Field | What it shows |
First Name | The user's first name. |
Last Name | The user's last name. |
Full Name | The user's full name. |
Workspace Role | The user's role in the workspace. |
Timezone | The timezone associated with the user. |
Is Primary | Whether the user is marked as a primary member in the reporting data. |
Allotted Capacity Hours | The capacity hours allocated to the user. |
Created At | When the workspace-member record was created. |
Updated At | When the record was most recently updated. |
The user's email address. | |
Public Workspace Members Status | The user's current workspace-member status in reporting. |
Invitation Accepted At | When the user accepted their workspace invitation. |
Locked At | When the account was locked, when applicable. |
Failed Login Attempts | The number of failed login attempts recorded for the user. |
Deactivated At | When the user was deactivated, when applicable. |
Useful user fields for common investigations
If you're trying to understand... | Look at... |
Who the user is | Full Name, Email |
Their workspace access level | Workspace Role |
Their reporting status | Public Workspace Members Status |
Whether they accepted their invitation | Invitation Accepted At |
Their configured capacity | Allotted Capacity Hours |
Whether the account has been deactivated | Deactivated At |
Account-access issues | Locked At, Failed Login Attempts |
Their configured timezone | Timezone |
How to use a drilldown during an investigation
The following is an illustrative Professional Services scenario.
A delivery leader sees an increase in overdue work during a weekly review.
Instead of opening projects one by one, they use the report to narrow the investigation.
1. Find the signal
The summary widget shows that overdue work has increased.
2. Open the drilldown
If the widget supports a drilldown, the cursor changes to a pointer hand when hovering over it.
The leader opens the underlying records.
3. Sort the fields that matter
They might sort by:
Project Name to group work by implementation
End Date to review task deadlines
Assignee Names to understand ownership
Days Open to prioritize long-running work
4. Review context
They use Status Label, Status Explanation, responsibility, and project information to understand what the records have in common.
5. Take action in the underlying work
The drilldown helps identify what needs attention.
The team can then review the actual project, task, time entry, user, or customer response before deciding what action is appropriate.
Best practices
These are suggested reporting practices rather than product requirements.
Use the drilldown after you find a signal
Start with a metric or chart, then use the drilldown to identify the individual records behind it.
This keeps your investigation focused.
Sort around the question you're asking
Don't sort a table just because you can.
If the question is about ownership, start with the assignee or project fields.
If the question is about timing, start with due dates, forecast dates, or Days Open.
Expect blank fields when the value does not apply
Not every field applies to every record.
For example:
A time entry logged directly to a project may not have a Task Name.
A project may not have a Done Date if it is not complete.
A CSAT response may not have a Milestone Name if the survey was sent at the project level.
A task may not have Assignee Names if nobody is assigned.
A blank value does not automatically indicate a reporting problem.
Use calculated fields as investigation signals
Fields such as Forecasted Variance Days, Days Open, and RAG-related fields can help you identify records worth reviewing.
Use the field to find the signal, then review the underlying project or task before deciding why the result occurred.
Be careful with technical fields
Some fields, such as Pm Member Ids, expose underlying reporting identifiers rather than customer-friendly names.
They can be useful for reporting and troubleshooting but may not be the best field for a business-facing review.
Frequently asked questions
Why do different reports have different drilldown columns?
The drilldown reflects the type of record behind the report.
For example:
Task Management focuses on tasks.
Projects Overview focuses on projects.
CSAT focuses on survey responses.
Advanced Time Reporting focuses on time entries.
Users Overview focuses on workspace members.
That means there is no single universal GUIDEreports drilldown schema.
Why does PM Command Center sometimes show different columns?
PM Command Center contains both task-focused and project-focused reporting.
A task-based widget can open a task drilldown, while a project-based widget can open a project drilldown.
Can I sort every drilldown column?
Yes.
Every drilldown column header can be sorted A → Z or Z → A.
Does every widget have a drilldown?
No.
Hover over the widget.
If your cursor changes to a pointer hand, the widget has a drilldown available.
Why is a field blank?
Usually because there is no value for that record or the field does not apply.
For example, an incomplete project does not have a completion date, and project-level time may not have an associated task.
Why is Days Open different from the last time I looked?
Days Open continues to calculate through the current time while the task remains open.
Because of that, the value can change each time the report is viewed.
Why can't a customer or partner user access Status Explanation?
Status Explanation is not available to customer or partner users.
It is an internal reporting field used to provide additional context around status when an explanation has been entered.
Why are multiple names shown in Assignee Names?
A task can have more than one assignee.
When multiple users are assigned, the names appear alphabetically and are separated by commas.
What is the difference between Status Label and Status Category?
A Status Label is the status name shown in your workspace.
A Status Category, where present in specialized drilldowns such as CSAT or time reporting, is the broader reporting category associated with that status.
This allows GUIDEreports to analyze statuses consistently even when workspace labels differ.
Why do some project timing fields look similar?
They represent different views of project timing.
For example:
Due Date represents planned completion.
Forecasted End Date represents currently expected completion.
Planned Duration Days represents planned duration.
Forecasted Duration Days represents forecasted duration.
Forecasted Variance Days helps show the difference between the planned and forecasted timing.
Use these fields together when investigating project schedule risk.
Continue learning about GUIDEreports
GUIDEreports overview — Choose the right report for your question.
Use GUIDEreports: Filters, drilldowns, sorting, and navigation — Learn how to move from report signals to underlying records.
GUIDEreports widget library — Understand what each reporting widget measures and how it is scoped.
GUIDEreports access, report types, and permissions — Understand who can access and manage GUIDEreports.
Standard report articles — Learn how to interpret the metrics and workflows in each Standard report.