The Historical Trends report helps you understand how your onboarding and Professional Services performance is changing over time.

While reports such as Projects Overview focus heavily on the state of projects today, Historical Trends is designed for a different question:

Are our delivery patterns improving, declining, or staying consistent over time?

Use this report to look beyond a single current-state number and identify longer-term patterns that may be difficult to see in individual projects.

Historical Trends can help you investigate questions such as:

The report is especially useful for monthly, quarterly, and leadership reviews where direction over time matters more than one snapshot.

Historical Trends uses the standard GUIDEreports filters.

These include:

Filters let you compare trends for the population you actually care about.

For example, you could narrow the report to:

That lets you move from:

“Are our projects getting faster?”

to a more specific question such as:

“Are Enterprise implementations getting faster?”

For complete filter behavior, see Use GUIDEreports: Filters, drilldowns, sorting, and navigation.

This distinction is the most important part of using the report correctly.

For example:

Completed Projects tells you how many projects are currently represented as complete within the applicable reporting scope.

A completion trend tells you how completed-project volume has changed across successive periods.

Neither is inherently better.

They answer different questions.

Project-creation and project-start trends help you understand how the amount of incoming work changes over time.

Question it answers: Is our incoming project volume changing?

Use the monthly trend to identify periods where project creation rises, falls, or remains relatively consistent.

This can help provide context for other delivery trends.

For example, if project duration begins increasing during the same period that incoming volume increases sharply, that may be worth investigating.

The chart does not prove that higher volume caused longer delivery.

It simply helps you identify patterns that may deserve a closer look.

Question it answers: What happened to the projects that started during different periods?

This view combines:

Use it to understand whether projects started during different months are now represented differently across project statuses.

For example, a cluster of older projects that remain active may deserve further investigation.

Completion trends help you understand how work is moving out of the delivery portfolio.

Question it answers: How is our completed-project volume changing month to month?

Use this trend alongside project creation or start trends.

Looking at the two together can help you understand whether project inflow and completion volume appear to be moving in similar or different directions.

For example:

Each pattern creates a different question for the delivery team to investigate.

Use the detailed completion view when the trend tells you something changed and you need to understand which projects contributed to that result.

Project records can provide context such as:

This is the bridge between the historical pattern and the underlying projects.

Duration trends help you understand whether completed projects are generally taking more or less time.

Question it answers: Are completed implementations getting faster or slower?

Use the monthly view to identify changes in delivery duration over time.

Project duration uses the working days configured at the workspace level.

That matters when interpreting the numbers.

Do not compare the displayed duration directly with manually counted calendar days unless your working-day configuration matches the calendar.

If average duration increases, avoid jumping directly to a conclusion.

The change could coincide with differences in:

Use filters and the project drilldown to investigate which projects are contributing to the pattern.

One of the most useful ways to use Historical Trends is to compare related trends instead of reading each chart independently.

These comparisons identify patterns.

They do not establish cause.

Use them to decide where deeper analysis would be valuable.

Historical customer-participation views can help you understand whether the makeup of the customer team involved in implementations is changing.

Use the monthly view to investigate questions such as:

Are newer projects involving more customer stakeholders than projects earlier in the year?

A rising number is not automatically positive, and a falling number is not automatically negative.

Different implementation models may require different levels of customer participation.

Treat this as a description of the delivery motion rather than a universal engagement score.

Historical messaging views can help you understand how customer-facing communication changes over time.

Use the monthly trend when you care about direction, rather than only the total number of messages.

For example, a significant change in messaging activity may be worth comparing with changes in:

Again, the report identifies a pattern — not the reason for it.

Historical CSAT trends help you understand whether customer sentiment is changing over a longer period.

A single CSAT score gives you one point of reference.

A trend helps answer:

Is satisfaction generally moving up, down, or remaining stable?

For example, if project duration improves while satisfaction declines, the team may want to investigate whether faster delivery is still producing the expected customer experience.

The trend does not prove those changes are related.

It tells you where additional investigation may be worthwhile.

For deeper survey-response analysis, use the CSAT Standard report.

Time trends can help you understand whether tracked delivery effort is changing.

Use time trends alongside project volume and duration when you need additional delivery context.

For example, increasing tracked time during a period of increasing project volume may be expected.

A time trend becomes more useful when it is interpreted alongside the work being delivered.

For deeper time-entry analysis, use Advanced Time Reporting.

Historical Trends uses the project-oriented drilldown structure also used by Projects Overview.

Depending on the widget, project records can include fields such as:

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

For complete definitions, see the GUIDEreports drilldown field reference.

The following is an illustrative Professional Services scenario.

A delivery leader is preparing for a quarterly review.

The leadership team wants to know:

Are we scaling delivery without making implementations slower or hurting the customer experience?

They start with:

Project volume has increased over several months.

Next, they review:

Now they can see whether completed-project volume is changing alongside project intake.

They check:

If project volume has increased while average duration remains stable, that tells a different story than increasing volume alongside sharply increasing duration.

They review:

This helps the team understand whether the customer-team structure involved in projects is changing.

They review the available 12-month CSAT trend.

Now the team can compare delivery trends with customer feedback.

If one month stands out, they use the project drilldown to review the projects contributing to that period.

The conversation moves from:

“Average duration went up.”

to:

“Average duration increased during these months, and these are the projects and customer segments contributing to that change.”

That's the purpose of Historical Trends: turning movement over time into a focused investigation.

These are suggested reporting practices rather than product requirements.

A single high or low month can be useful, but a repeated pattern is usually more informative.

Review several periods before concluding that a delivery motion has materially changed.

Project volume, completion, duration, customer participation, satisfaction, and effort can provide useful context for one another.

Use related trends together when investigating change.

Two metrics moving at the same time does not prove one caused the other.

Use the report to identify relationships worth investigating, then review the underlying projects.

If your workspace contains very different project types, an overall trend may combine populations that are not useful to compare directly.

Use custom fields, customers, tags, or other filters to narrow the population before drawing conclusions.

A chart tells you when something changed.

The drilldown helps you identify which projects contributed.

Move to record-level investigation before deciding what operational change is needed.

Project-duration reporting uses your workspace working-day configuration.

Remember that when comparing historical duration values with other manually calculated timelines.

Historical Trends is best for patterns.

If you need to know which projects require intervention right now, use a report such as Projects Overview or PM Command Center.

Projects Overview helps you understand the current project portfolio and identify present or forecasted project risk.

Historical Trends helps you understand how delivery measures change over time.

Use one for current state and the other for direction over time.

Yes.

It uses the standard GUIDEreports filters.

For full filtering behavior, see Use GUIDEreports: Filters, drilldowns, sorting, and navigation.

Looking at both can help you understand whether incoming project volume and completed-project volume appear to be moving together or differently.

The comparison identifies a pattern. It does not by itself establish whether capacity is sufficient or explain why the pattern occurred.

Not necessarily.

Duration can vary with differences in project scope, customer type, implementation motion, or other characteristics of the project population.

Use filters and the drilldown to investigate the projects behind the change.

No.

It describes customer participation structure, not the quality of engagement.

Different projects may require different numbers of customer stakeholders.

Yes.

Apply report filters to narrow the trend to the population you want to analyze.

This is especially useful when workspace-wide trends combine different implementation motions.

When a widget supports a drilldown, hover over it.

If your cursor changes to a pointer hand, select the widget to open the available underlying records.

For field definitions, see the GUIDEreports drilldown field reference.

See the GUIDEreports widget library.

The widget library is the central reference for built-in widget scope and calculation behavior.

First, check the GUIDEreports widget library for another available trend widget.

If the available Standard report does not answer your question, you can build a custom GUIDEreport using the widgets available in GUIDEreports..