Custom GUIDEreports let you create a reporting view around the questions that matter most to your team.

Instead of starting with a blank dashboard and adding every interesting metric, start with one question:

What do I want this report to help me understand or decide?

Then choose the widgets that help answer it.

For example:

A focused report is usually easier to understand, maintain, and act on than a dashboard trying to answer everything at once.

Only certain GUIDEcx roles can create custom reports.

See GUIDEreports access, report types, and permissions for the complete permissions model.

If you're new to GUIDEreports, the GUIDEreports overview can also help you decide whether an existing Standard report already answers your question.

Before selecting any widgets, write down the question the report should answer.

For example:

Which customer onboarding projects need attention during our weekly delivery review?

That question gives you a filter for every decision that follows.

When you're considering a widget, ask:

Does this help answer the report's question?

If not, you probably don't need it.

Tip: You can create multiple reports, so you do not need one report to answer every question your team has.

From GUIDEreports, select New Report in the upper-right corner.

This opens the custom report-building experience.

Choose a name that tells people what the report is for.

Helpful names usually describe the audience, business question, or review process.

For example:

Avoid vague names such as:

A clear name makes the report easier to recognize later — especially if your workspace has several shared reports.

Use the report description to explain what the report is designed to answer.

For example:

Use this report during our weekly delivery review to identify active projects with late, forecasted-late, stuck, or overdue work.

A good description helps another person understand:

This becomes especially useful for Workspace reports that other team members may use without the original author present.

Review the available widgets and select the ones that support your reporting question.

Adding a widget is straightforward: select the widget you want to add to the report.

Each widget has its own predefined calculation.

You cannot change how an individual widget is calculated today, so choose widgets based on the question each one is designed to answer.

For example, a report about project delivery risk might include widgets that help answer questions such as:

A report focused on customer participation might instead use widgets around:

The goal is not to add the largest number of widgets.

The goal is to build a report where each widget contributes to the same reporting conversation.

See the GUIDEreports widget library for definitions, calculations, and suggested uses for each available widget.

When you're ready to save the report, decide who needs access to it.

Choose Personal when the report is for your own use.

Personal reports are useful when you are:

Only the report owner can view a Personal report.

Admins and Managers can create Personal reports.

Choose Workspace when the report should be available to your internal team.

Workspace reports are useful for shared processes such as:

Only Admins can create Workspace reports.

Workspace reports are visible to internal users who have GUIDEreports access.

For the complete visibility and ownership rules, see GUIDEreports access, report types, and permissions.

When the report is ready, select Save Changes in the upper-right corner.

The report is saved according to the visibility you selected.

If it is a Personal report, it remains available only to you.

If an Admin publishes it as a Workspace report, eligible internal users can view it.

The following is an illustrative Professional Services scenario.

An onboarding leader wants a report for the team's Monday delivery meeting.

The initial idea is:

“Let's build a dashboard with all our project metrics.”

That is technically possible, but it does not give the report a clear purpose.

Instead, the team defines the question:

Which active onboarding projects are most likely to need intervention this week?

Now the widget choices become easier.

The report might include widgets that identify:

During the meeting, the team can start with the summary signals and then investigate the underlying records when a widget supports a drilldown.

Because the report will be used by the broader delivery team every week, an Admin publishes it as a Workspace report.

The result is a dashboard designed around a decision rather than a collection of unrelated metrics.

Custom reports use the same GUIDEreports filtering and investigation concepts as Standard reports.

Filters help narrow the report to the population you want to evaluate.

For example, the same custom report might be used to review:

The widgets continue to use their own predefined calculations within the filtered report population.

See Use GUIDEreports: Filters, drilldowns, sorting, and navigation for a complete explanation of filters, drilldowns, and sorting.

Your first version does not need to contain every metric your team might eventually want.

Use the report, then pay attention to the questions people actually ask.

For example, after a few weekly reviews you might realize:

Those are good reasons to simplify or rethink the report.

A custom report should make a recurring decision easier — not create more information for your team to process.

These are suggested reporting practices rather than product requirements.

A strong report has a clear purpose.

Instead of “Customer Metrics,” try building around a question such as:

“Which customers need follow-up this week?”

That question makes your widget choices much easier.

Before rebuilding a dashboard from scratch, check whether a Standard report already answers your question.

GUIDEcx maintains Standard reports for common reporting needs such as project health, task management, customer engagement, time, CSAT, and user information.

Create something custom when your team genuinely needs a different combination of signals.

Start with the widgets most directly related to your question.

You can refine the report after using it in a real review.

This is particularly valuable for Workspace reports.

A useful description can tell the next person exactly what the report is meant to support without requiring them to ask the author.

Before adding another chart or metric, ask:

What would someone do differently because they saw this?

If there is no clear answer, the widget may not belong on that report.

If you're still trying to determine what belongs on a dashboard, start with Personal visibility.

Admins can change their own report between Personal and Workspace visibility when the reporting view is ready to be shared.

Workspace reports remain managed by their Admin owner.

If a dashboard will become part of an important recurring business process, decide who should own and maintain it.

Admins and Managers can create Personal reports.

Only Admins can create Workspace reports.

See GUIDEreports access, report types, and permissions for the full role breakdown.

Use Personal when the report is for your own workflow or when you're still experimenting.

Use Workspace when an Admin wants the report to become a shared reporting resource for eligible internal users.

Yes.

Managers can create and manage Personal reports.

Managers cannot successfully publish Workspace reports.

No.

The available widgets use predefined calculations.

Use the GUIDEreports widget library to understand what each widget measures before deciding whether it belongs on your report.

The current report-building experience uses the available predefined widgets.

The supplied reporting documentation does not establish support for creating your own widget formulas or changing the calculation behind an existing widget.

There is no single ideal number.

Use enough widgets to answer the report's question clearly.

If your team has to scan many unrelated metrics before figuring out what matters, consider splitting the dashboard into more focused reports.

Usually, start with the Standard report first.

Create a custom report when the existing Standard report does not support the specific question or combination of metrics your team needs.

Yes.

Use report-level filters to narrow the population you want to analyze.

The widgets then apply their predefined calculations within that reporting context.

See Use GUIDEreports: Filters, drilldowns, sorting, and navigation for more information.

No.

Not every widget has a drilldown.

Hover over a widget. If your cursor changes to a pointer hand, you can select it to open the available underlying records.

Yes.

Every drilldown column header is sortable A → Z or Z → A.

If you're an Admin, yes.

An Admin can create a report as Personal and later change it to Workspace visibility.

Managers can create Personal reports but cannot publish them as Workspace reports.

No.

Other Admins can view your Workspace report, but they cannot edit it or save a copy for themselves.

Keep ownership in mind when building reports that will support long-term team processes.

No.

Workspace report visibility is not configurable for individual users or subsets of the internal team.

If a report should remain private, keep it as a Personal report.

Name it after the question, audience, or process it supports.

For example:

These names are usually more useful than generic titles like Project Dashboard.

Explain why the report exists and when someone should use it.

For example:

Use this report during our weekly onboarding review to identify active enterprise projects with late, forecasted-late, stuck, or overdue work.

First check the Standard reports and the complete widget library to make sure an existing option does not already meet the need.

If the required metric is not represented by an available widget, the current custom report builder cannot create a different calculation from an existing widget.