GUIDEreports gives you real-time visibility into your projects, tasks, customers, team, time, and customer satisfaction data.

You can start with a standard report built around a common business question or create a custom report using available reporting widgets when your team needs a different view.

The easiest way to get value from GUIDEreports is to start with a question:

What are you trying to understand or decide?

From there, choose the report that gets you closest to the answer.

Each standard GUIDEreport is designed around a different type of question.

You do not need to use every report.

Start with the one that best matches the decision you are trying to make.

Most GUIDEreports use the same general investigation process:

Start broad → apply filters → identify a signal → drill into the records → take action

For example, you might:

See Use GUIDEreports: Filters, drilldowns, sorting, and navigation for a complete guide to working with report filters and underlying records.

GUIDEreports is available in both GUIDE 1.0 and GUIDE 2.0, but the data shown depends on the experience where you access reporting.

Important: GUIDEreports does not combine GUIDE 1.0 and GUIDE 2.0 data into one reporting view.

If your organization is working across both experiences, keep the reporting scope in mind before comparing totals or presenting results.

Your existing reporting data also remains available under Reports (Legacy).

Standard reports are created and maintained by GUIDEcx.

They provide ready-to-use views for common onboarding, Professional Services, project management, customer engagement, and operational questions.

Use a standard report when it already answers most or all of the question you are investigating.

Use Task Management when your question is about the work happening inside your projects.

For example:

This report is especially useful during weekly delivery reviews when you need to identify work that requires immediate attention.

Use Projects Overview when you need a portfolio-level view of project health and delivery.

For example:

Start here when the question is primarily about projects rather than individual tasks.

Use Customer Engagement when you want to understand how customers are participating in their onboarding work.

For example:

This report can help Customer Success and delivery teams identify engagement signals before they become larger project risks.

Use Historical Trends when the question is less about today's snapshot and more about how performance is changing over time.

For example:

Use this report for operational reviews where the direction of performance matters as much as the current value.

Use PM Command Center when you want a focused view of work that may require project-manager attention.

This can help PMs and delivery leaders prioritize where to investigate first instead of reviewing every project or task individually.

Use Advanced Time Reporting when your question involves logged time.

For example:

Advanced Time Reporting includes the standard GUIDEreports filters plus Date Worked and Time Entry Member.

Use CSAT when you want to understand customer satisfaction.

For example:

Use the drilldown when you need to move from an overall score to the individual response behind it.

Use Users Overview when you need information about the people in your GUIDEcx workspace.

For example:

Users Overview does not have report-level filters.

One of the most useful ways to approach GUIDEreports is to think in layers.

For example:

7 Late Projects

That tells you there is something to investigate.

A visualization can help you see whether a problem is spread across the portfolio or concentrated in particular customers, projects, statuses, or other groups.

When a widget supports a drilldown, you can inspect the individual records behind the result.

Not every widget has a drilldown. Hover over a widget and look at your cursor.

If the cursor changes to a pointer hand, the widget can be opened for more detail.

This lets you move from:

“We have 18 overdue tasks.”

to:

“Most of those overdue tasks are coming from these three projects.”

That second answer is usually much more useful.

Sometimes a standard report gets you close to the answer but does not provide the exact view your team needs.

In that case, you can create a custom GUIDEreport using the available widgets.

For example, your team may want a focused report for:

Custom reports let you choose the combination of widgets that best supports your reporting question.

A useful rule is:

Build the report around one clear question.

A focused report such as:

“Which enterprise implementations need attention this month?”

is usually easier to understand and act on than a dashboard trying to answer every possible question at once.

See Build a custom GUIDEreport for the complete report-building workflow.

The following is an illustrative onboarding scenario.

A Professional Services leader is preparing for the team's weekly portfolio review.

Their goal is not to review every project.

Their goal is to answer:

Which projects need our attention this week, and why?

They might begin with Projects Overview to find:

After identifying a project that needs attention, they can move to Task Management to investigate:

If customer-owned work appears to be contributing to the problem, they can use Customer Engagement to focus the investigation on customer activity.

Instead of walking through every dashboard metric, the team uses GUIDEreports to move from:

Portfolio signal → affected project → underlying work → next action

These are suggested reporting practices rather than product requirements.

Before opening GUIDEreports, decide what you're trying to understand.

This makes it easier to choose the right report and ignore information that is not relevant to your decision.

If your organization uses both GUIDE 1.0 and GUIDE 2.0, confirm which experience your report data is coming from before comparing results.

A workspace-wide result can combine very different customers, project types, statuses, or delivery motions.

Use filters when you need to compare a specific population.

A high number of late projects or overdue tasks is a signal, not an explanation.

Use charts and drilldowns to understand the underlying records before deciding what action to take.

You do not need one report to answer everything.

Projects Overview might identify the project that needs attention, while Task Management explains the task-level work contributing to the issue.

Do not recreate an existing standard report just because custom reporting is available.

Start with the standard reports. Build your own when your reporting question genuinely requires a different view.

Start with the question you need to answer.

If the question is about:

If none of the standard reports fits the question, consider building a custom GUIDEreport.

No.

A report may contain several metrics because different users bring different questions to the same reporting area.

Focus on the widgets that help answer your current question.

For example, if you are investigating customer delays, you may care much more about Overdue Customer Tasks than overall task volume.

Yes.

In fact, that can be one of the most effective ways to use GUIDEreports.

For example:

Projects Overview might tell you that a project is at risk.

Task Management can then help you understand whether blocked or overdue work is contributing to that risk.

Customer Engagement can help you determine whether customer-owned work is involved.

Think of the standard reports as different views of your operational data, not isolated dashboards.

Most standard reports use the shared GUIDEreports filter set.

There are two important exceptions:

For more information, see Use GUIDEreports: Filters, drilldowns, sorting, and navigation.

No.

Hover over a widget to check.

If your cursor changes to a pointer hand, that widget supports a drilldown.

If it does not, there is no drilldown available for that widget.

Yes.

All drilldown column headers are sortable A → Z and Z → A.

Sorting changes the order of the records you are reviewing. It does not change the underlying calculation.

Different widgets and reports can use different calculations and inclusion rules.

For example, one metric may include every project while another focuses only on projects that meet particular status or timing conditions.

Check the definition of the widget before assuming two metrics should match.

GUIDEreports uses the data associated with the GUIDE experience where you access the report.

GUIDEreports accessed from GUIDE 1.0 shows GUIDE 1.0 reporting data, while GUIDEreports accessed from GUIDE 2.0 shows GUIDE 2.0 reporting data.

Use Reports (Legacy) when you need access to reporting data across both experiences.

First, check whether the standard report can answer your question by applying filters.

If not, consider creating a custom GUIDEreport using the available widgets.

You can also use Reports (Legacy) when the information you need is not available in the current GUIDEreports experience.

Standard reports are created and maintained by GUIDEcx around common reporting use cases.

Custom reports let eligible users choose from available widgets and build a reporting view for their own question.

Use a standard report when it already solves the problem. Build a custom report when it doesn't.

Use the GUIDEreports widget library.

The widget library explains what each widget shows, the question it answers, how it is calculated, and when it is most useful.

Before assuming the data is incorrect, check:

These checks can often explain why a result differs from what you expected.

For a detailed troubleshooting workflow, see Use GUIDEreports: Filters, drilldowns, sorting, and navigation.

Use these resources as you explore GUIDEreports: