> For the complete documentation index, see [llms.txt](https://docs.new-vue.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.new-vue.com/glossary/calculations/guest-experience-calculations.md).

# Guest Experience Calculations

## Ratings

<details>

<summary>Average Rating</summary>

This is the simple average of all guest review ratings currently shown. Each review is counted based on its own review date.

</details>

<details>

<summary>Average Rating LY</summary>

Average Rating using a 364-day shift, which means looking 52 weeks back instead of a full calendar year. This way, the comparison falls on the same weekday as the current period, not the same calendar date. Over a leap year, the dates will drift further apart. This shows the same window as last year by weekday, not by exact date.

</details>

<details>

<summary>Average Rating To Date</summary>

This is the average rating from all reviews dated on or before the latest date shown, with no other date filters applied. It ignores the start of any selected date range and any Season filter, always using the full review history up to that cutoff date. This creates a running cumulative average, not a limited period average like the Year-to-Date measures elsewhere in this pack.

</details>

<details>

<summary>Average Rating YoY</summary>

This shows the percent change between the Average Rating for the current period and the Average Rating LY, using a 364-day shift (52 weeks back). The comparison is by weekday, not by exact calendar date, so dates may drift over a leap year.

</details>

<details>

<summary>Average Rating YTD - Cards</summary>

This is a Year-to-Date calculation for Average Rating that takes seasons into account. If a Season filter is active, it uses that season's first and last dates. If no season is selected, it uses January 1st of the current year through today. If today is the 1st of a month, it uses yesterday as the cutoff to avoid low or missing totals before today's data is complete.

</details>

<details>

<summary>Average Rating - YTD LY (Cards)</summary>

This is the Average Rating YTD - Cards, but shifted back 364 days (52 weeks). This means it matches the same weekday as the reference period, not the same calendar date, and dates will drift further apart over a leap year.

</details>

## Employees

<details>

<summary>5 Star Employee Mentions</summary>

For the selected employee, this counts 5-star reviews where the employee is mentioned by name. The system uses a fuzzy text search that removes punctuation and normalizes apostrophes, looking for the employee's first or full name surrounded by spaces. Very short or common first names (like "will," "may," "can," and any under 4 letters) are excluded from first-name matching to avoid mistakes, so those employees are only matched if their full name appears in the review.

</details>

<details>

<summary>Avg Employee Rating</summary>

For the selected employee, this shows the average rating from all reviews that mention the employee by name, using the same fuzzy name-matching method as above. This includes all matching reviews, not just 5-star ones.

</details>

## Surveys

<details>

<summary>Survey Responses</summary>

This shows a unique count of survey response IDs (Answers\[responseId]) for whatever is currently displayed.

</details>

<details>

<summary>NPS Score</summary>

This Net Promoter Score is calculated using only the survey's NPS question. The system checks the highest answer value in the data to see if the scale is 0 to 10 or something else, like 0 to 5. If the highest value is above 5, promoters are answers of 9 or higher, and detractors are 6 or lower, following the standard 0 to 10 NPS rules. If the scale is smaller, promoters are 6 or higher and detractors are 3 or lower. The NPS is then calculated as (% promoters minus % detractors) times 100, using the standard formula after setting these thresholds.

</details>

<details>

<summary>NPS To Date</summary>

This is the NPS Score, but only for responses dated on or before the latest date shown. All other date filters are removed. It gives a running cumulative NPS up to that cutoff date, rather than a set period like the YTD (Cards) version below.

</details>

<details>

<summary>NPS YTD - Cards</summary>

This is a season-aware Year-to-Date calculation for the NPS Score. It checks if a Season filter is being used by comparing the filtered date range to the full range. If a season is selected, the NPS Score uses that season's first and last dates. If no season is selected, the window is from January 1st of the current year through today. However, if today is the first of the month, yesterday is used as the cutoff to avoid a low or blank total before all of today's data is available.

</details>

<details>

<summary>NPS YTD LY - Cards</summary>

This is the NPS YTD - Cards metric, but shifted back by 364 days, or 52 weeks. This means it matches the same day of the week as the reference period, but not the same calendar date, and it can drift further off during a leap year.

</details>

<details>

<summary>Number of Surveys YTD - Cards</summary>

This is a season-aware Year-to-Date calculation for Survey Responses. It checks if a Season filter is being used by comparing the filtered date range to the full range. If a season is selected, Survey Responses are counted from that season's first to last date. If no season is selected, the window is from January 1st of the current year through today. If today is the first of the month, yesterday is used as the cutoff to avoid a low or blank total before all of today's data is available.

</details>

<details>

<summary>Number of Surveys YTD LY - Cards</summary>

This is the Number of Surveys YTD - Cards metric, but shifted back by 364 days, or 52 weeks. This means it matches the same day of the week as the reference period, but not the same calendar date, and it can drift further off during a leap year.

</details>

## Review Topics

<details>

<summary>Review Count by Review Topic</summary>

For the topic words currently selected from the Review Topics table, this counts the number of reviews whose text includes at least one of those words. Each review is counted only once, even if it mentions more than one selected word.

</details>

<details>

<summary>Average Rating by Review Topic</summary>

This shows the average rating for reviews that mention at least one of the currently selected topic's words. It uses the same matching logic as the count above.

</details>

<details>

<summary>Average Rating To Date by Topic</summary>

This is the Average Rating by Review Topic, but only for reviews dated on or before the latest date shown. All other date filters are removed. It gives a running cumulative average for the topic up to that cutoff date, rather than a set period.

</details>

<details>

<summary>% 5 Star Mentioning Topic</summary>

Out of all 5-star reviews, no matter which topics are currently filtered, this shows the percentage whose text mentions at least one of the currently selected topic's words. The denominator always includes all 5-star reviews, not just those matching another topic filter.

</details>

<details>

<summary>% 1 Star Mentioning Topic</summary>

Out of all 1-star reviews, no matter which topics are currently filtered, this shows the percentage whose text mentions at least one of the currently selected topic's words. The denominator always includes all 1-star reviews, not just those matching another topic filter.

</details>

## Reviewers

<details>

<summary>Number of Reviewers</summary>

This shows the number of unique reviewer names for the data you are viewing. If two different guests have the same name or username, they are counted as one reviewer.

</details>

<details>

<summary>Number of Reviewers LY</summary>

Number of Reviewers using a 364-day shift, which means looking 52 weeks back instead of a full calendar year. This way, the comparison falls on the same day of the week as the current period, though not the same calendar date. Over a leap year, the dates will drift further apart.

</details>

<details>

<summary>Number of Reviewers YoY</summary>

Shows the percent change in Number of Reviewers for the current period compared to last year, using a 364-day shift (52 weeks back instead of a full calendar year). This means the comparison is on the same day of the week, not the same calendar date, and the dates drift further apart over a leap year. If there is no prior-year figure, the result is left blank instead of showing an error.

</details>

## Reviews

<details>

<summary>Number of Reviews</summary>

This is the total number of review records for the data you are viewing.Number of Reviews LY\
Number of Reviews using a 364-day shift, which means looking 52 weeks back instead of a full calendar year. This way, the comparison falls on the same day of the week as the current period, though not the same calendar date. Over a leap year, the dates will drift further apart.

</details>

<details>

<summary>Number of Reviews YoY</summary>

Shows the percent change in Number of Reviews for the current period compared to last year, using a 364-day shift (52 weeks back instead of a full calendar year). This means the comparison is on the same day of the week, not the same calendar date, and the dates drift further apart over a leap year. If there is no prior-year figure, the result is left blank instead of showing an error.

</details>

<details>

<summary>Number of Reviews YTD - Cards</summary>

This is a season-aware Year-to-Date calculation for Number of Reviews. It checks if a Season filter is being used by comparing the filtered date range to the full range. If a season is selected, the calculation uses that season's first and last dates. If no season is selected, it uses January 1st of the current year through today. However, if today is the first of the month, it uses yesterday as the cutoff to avoid a low or blank total before all data for the day is available.

</details>

<details>

<summary>Number of Reviews - YTD LY (Cards)</summary>

Number of Reviews YTD - Cards, shifted back 364 days (52 weeks instead of a full calendar year). This means the comparison falls on the same day of the week as the reference period, but not the same calendar date. Over a leap year, the dates will drift further apart.

</details>
