Report Designs in Process HQ

This page applies to business users. It describes each report design available when you build a report in Process HQ, and helps you choose the right design for the outcome you want.

What is a report design?

A report design is the visualization Process HQ uses to display your report data, such as a grid, a chart, a KPI, or a scorecard. You select a report design in the DESIGN section of the report builder.

The report designs available to you depend on the report's data source:

• Dataset reports: Reports built from a dataset. Dataset reports visualize and explore your organization's data.
• Process reports: Reports built from a process. Process reports measure how well your processes are performing.

Some report designs work with any report, while others are specific to dataset reports or process reports.

Choose a report design

Choosing a report design involves two decisions: the report's data source and the visualization you want. The data source is fixed when you create the report, and it determines which designs are available. Within those available designs, choose the visualization that best communicates the outcome you want your audience to see.

The following table summarizes which designs are available for each data source. A Report Source of Any means the design is available for both dataset reports and process reports.

Design	Report Source
Duration KPI	Process
Count KPI	Process
Aggregation KPI	Process
Automation KPI	Process
Scorecard	Process
Process Diagram	Process
KPI	Dataset
Heatmap	Dataset
Scatter	Dataset
Grid	Any
Pie	Any
Donut	Any
Bar, Stacked Bar, or 100% Bar	Any
Column, Stacked Column, or 100% Column	Any
Area, Stacked Area, or 100% Area	Any
Line	Any

Process report designs

Process report designs display data from a process so you can measure and communicate how well that process is performing.

Process reports can use the process-specific designs in this section, as well as any design listed in Report designs available for any report.

For details on how each process KPI type is defined, see KPI types.

Duration KPI

The Duration KPI report design displays how long cases, activities, or sequences take to complete, or how often they meet a service level agreement (SLA).

Use the Duration KPI design when you want to track time-based performance or SLA conformance against a target, such as average case cycle time or the percentage of cases that meet an SLA.

For example, the following Duration KPI report tracks the average time it takes to complete a case. The headline value shows the average case duration across all time, and the trend chart breaks that duration down by month so you can see whether cases are getting faster or slower over time.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Count KPI

The Count KPI report design displays the number of activities, sequences, or attributes in a process.

Use the Count KPI design when you want to track volume or frequency, such as the number of cases that include a rework loop. You can set a target, baseline, and reference lines to measure performance against a goal.

For example, the following Count KPI report tracks how many occurrences of an application being received and then being verified occurred each month. The headline value shows the total number of occurrences across all time, and the trend chart breaks that count down by month so you can see how the frequency changes over time.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Aggregation KPI

The Aggregation KPI report design displays an aggregated value based on a numeric attribute, such as an average, sum, minimum, maximum, or median.

Use the Aggregation KPI design when you want to track a numeric business value from your process data, such as total order value. You can set a target and baseline to measure performance against a goal. The Aggregation KPI design is only available when your process contains a numeric attribute.

For example, the following Aggregation KPI report tracks the average number of story points per Jira ticket. The headline value shows the average across all time, and the trend chart breaks that average down by month so you can see how it changes over time

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Automation KPI

The Automation KPI report design displays the overall automation percentage for a process, calculated across all activities. By default, the KPI defines a higher trend direction as better, since a rising automation percentage means less manual effort. The Automation KPI design is only available when the process has an Automation attribute mapped.

Use the Automation KPI design to track process automation when you need more customization than the system-provided Automation Rate KPI in a process view.

The Automation KPI design enables you to:

• Filter by case attributes to compare automation across regions or teams.
• Set a target for how much a process should be automated.
• Add automation tracking to dashboards and scorecards.

For example, the following Automation KPI report tracks the automation rate for a Jira tickets process. The headline value shows an 80% automation rate across all activities, and the trend chart breaks that rate down by month so you can see how it changes over time.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Scorecard

The Scorecard report design combines multiple KPI reports into a single score, so you can measure your overall progress toward a business goal. You can include process KPI reports and dataset KPI reports. A scorecard displays a grid of the individual KPI scores, each linking to its underlying report, alongside the overall score.

A scorecard calculates its score in two stages:

• Individual scores: Each KPI with a target receives an individual score based on how its current value compares to that target. By default, all KPIs have equal weight, but you can assign custom weights to reflect each KPI's relative importance to your business goal.
• Overall score: The scorecard combines those individual scores using a weighted geometric mean, producing a single overall score.

For example, the following scorecard, combines three duration KPI reports that each track average ticket duration into a single overall score of 53 out of 100. The grid lists each KPI report with its current value, target, status, weight, and the score it contributes. In this example, the Bugs KPI has not met its target while the Test and Story KPIs have, so the overall score reflects that mix.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Use a scorecard when you want to give leadership a single, at-a-glance measure of overall business health, or track progress toward a business goal that combines metrics from multiple sources.

To use the scorecard design, start by creating a report from a process. Once you select the scorecard design, you can add a KPI report from any process or dataset. Only KPI reports with targets contribute to the overall scorecard score. You must have access to all the reports referenced in a scorecard to see the score.

Keep the following in mind when you build a scorecard:

• Maximum number of reports: A scorecard can combine up to 20 KPI reports.
• Data sources: A scorecard can include process KPI reports from up to three different processes. There is no limit on the number of dataset KPI reports.
• Custom weights: When you set custom weights, the sum of all weights must equal 100. If you delete a KPI report from a scorecard that uses custom weights, you must update the remaining weights to total 100 before you can save the scorecard.

Process diagram

The process diagram report design displays a process diagram that shows the flow of activities and sequences in a process. A process diagram report communicates how work moves through a process rather than a single metric.

For example, the following process diagram report shows an account onboarding process, from Application received through Account funded. Each node is an activity and each arrow is a sequence between activities. The size of a node reflects how often the activity occurs, the color reflects duration (blue for shorter, red for longer), and the labels show the case count and average time. The tabs above the diagram, from Basic to Full, control how much detail the diagram shows.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Use a process diagram report design when you want to show the shape of a process, including its activities, sequences, and where cases deviate from the expected path.

Dataset report designs

Dataset report designs display data from a dataset so you can visualize and explore your organization's data.

Dataset reports can use the dataset-specific designs in this section, as well as any design listed in Report designs available for any report.

KPI

The KPI report design displays a single value from a dataset as a headline number. A key performance indicator (KPI) design gives your audience one metric to focus on, such as total revenue or open order count.

Use the KPI design when you want to measure progress toward a business goal.

For example, the following KPI report shows the number of closed orders, 15, against the target goal of 20 by the end of the month. The progress bar shows that the current value is 75% of the target.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Heatmap

The Heatmap report design displays dataset values as a color-coded matrix, where color intensity represents magnitude. A heatmap makes it easy to spot concentrations and outliers across two dimensions.

Use a heatmap when you want to compare a measure across two categories at once, such as sales by region and month.

For example, the following heatmap shows the average order total by industry and state. Industry is on the y-axis and state is on the x-axis, and each cell's color reflects the average order value, with green for higher averages and red for lower ones. This makes it easy to spot which industry-and-state combinations have the highest and lowest average order values.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Scatter

The Scatter report design plots dataset values as points on two axes. A scatter report reveals the relationship or correlation between two numeric fields.

Use a scatter report when you want to show how two measures relate, such as order value against delivery time.

For example, the following scatter report plots each customer's total order cost against their total outstanding balance, colored by region. The upward pattern shows that customers with higher order totals tend to carry higher outstanding balances.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Report designs available for any report

The report designs in this section are available whether you build your report from a dataset or a process. These designs cover the most common ways to visualize tabular and categorical data.

Report design	Best used for
Grid	Showing detailed records in rows and columns, with optional sorting and aggregation.
Pie	Showing how parts contribute to a whole across a small number of categories.
Donut	Showing how parts contribute to a whole, with room for a summary value in the center.
Bar, Stacked Bar, or 100% Bar	Comparing values across categories, including how subcategories stack within each bar.
Column, Stacked Column, or 100% Column	Showing how values change over time using vertical bars, including stacked subcategories
Area, Stacked Area, or 100% Area	Showing how values change over a continuous range, such as time, with filled regions.
Line	Showing trends in values over a continuous range, such as time.

Feedback