Health score setup: 8 rules for weights and validity

Understanding the separation between validity periods and weight distribution is critical for accurate score auditing. Validity determines how long a score remains relevant before it requires manual or automatic refresh, while weighting dictates how much influence each individual measure has on the final overall score. These two logic sets operate independently, meaning a change in one does not automatically alter the other.

For validity, the rules are time-based and reactive to user actions. According to Gainsight, if you update the Score within the Validity Period, the Validity is extended by another week, starting on the date on which the Score was modified. This extension rule ensures that recent manual adjustments keep the score active for a standard duration, preventing stale data from influencing customer success decisions. You must verify that your team understands this specific extension trigger to avoid unnecessary manual updates.

For weighting, the logic is structural and dependent on the composition of the scorecard. Gainsight can auto calculate the overall score from the individual Score of all Measures in the Scorecards. If a measure is missing or marked as not applicable, the weight distribution must be handled explicitly to maintain the integrity of the overall score. This requires a separate audit of how your platform handles missing data compared to how it handles valid data.

Audit your current health score weights and verify that N/A values are handled correctly in your calculation logic.

• Update scores within the validity window to extend the period by one week, as described in Gainsight documentation Gainsight.
• Rely on automatic calculation of overall scores based on individual measure scores in Gainsight scorecards Gainsight.
• Confirm that your team holds the required Manage Customer Success Settings permissions before creating a health score in HubSpot HubSpot.
• Note that Vitally places no limit on the number of properties a single health score can use Vitally.
• Verify how N/A values are handled, such as Vitally’s method of proportionately distributing the 10% weight of an empty CSM pulse trait across other categories Vitally.

The following table maps the eight distinct configuration items to the specific rules documented by each publisher. Each row isolates a single rule to ensure that platform-specific logic is not conflated during your audit.

Use this table to verify that your current setup matches the documented behavior for each platform.

Gainsight documentation explains that modifying a score extends its validity period. Specifically, if you modify the score on the 6th Dec 2018, the validity is extended for one more week, starting from the 6th day, according to Gainsight. This extension resets the countdown rather than simply adding days to the original end date. The source provides a concrete example of this new period: the new Validity Period would be 6 Dec 2018 - 12 Dec 2018, according to Gainsight. This means the original validity window is replaced by a fresh seven-day window anchored to the modification date.

When auditing your score logic, note that this behavior applies specifically to the platform described in the source. Other tools may handle validity extensions differently, so do not assume this rule applies universally across all customer success platforms. In Gainsight, a score updated inside its current validity window is extended by one week starting on the modification date.

To verify this in your own setup, check whether your platform’s documentation specifies a similar extension rule. If your tool does not explicitly state how modifications affect validity, document your current behavior and test it with a controlled change to confirm the outcome. This ensures your team understands when a score becomes stale and when it remains valid for decision-making.

Remember that validity periods are distinct from weighting logic. A score can be valid (within its period) but still have incorrect weights applied to its components. Verify both aspects separately during your audit. Where Gainsight documentation applies, confirm the extension only for updates made during the active validity period. This prevents using outdated scores for churn risk assessments or renewal conversations.

When auditing your score logic, verify how your platform handles property limits and weight redistribution for missing data. Vitally states there is no limit on how many properties a single health score can use, so one score can draw on as many of those 50 as you need, according to Vitally. This rule applies specifically to the Health scores feature in the Vitally Help Center. In contrast, HubSpot provides a different structural approach by starting with pre-defined groups such as 1:1 Engagement, Supported Tickets, CSM Sentiment, and NPS, so the score reflects both support activity and relationship health, according to HubSpot. These pre-defined groups are part of the Create a health score in the customer success workspace process.

Understanding weight distribution is critical when traits are not filled out. Vitally explains that if the CSM pulse trait hasn't been filled out and is N/A, then we take the 10% weight of that category and proportionately distribute it across the other category weights to add up to 100%, according to Vitally. This mechanism ensures that the total weight remains at 100% even when specific data points are missing. A separate Vitally example is an Integrations health score calculated for 3 possible integrations, according to Vitally. In this specific scenario, Score #1 and #2 have weights of 40%, while score #3 has a weight of 20%, according to Vitally. These percentages illustrate how individual components contribute to the overall health score calculation.

When configuring your own system, check if your platform allows unlimited properties or if it relies on fixed groups. If your tool uses a similar N/A handling mechanism, verify that the redistribution logic matches your intended impact on the final score. For platforms like HubSpot, ensure that the pre-defined groups align with your specific support and relationship metrics. For platforms like Vitally, confirm that your property selection does not exceed practical limits, even if the system technically allows unlimited properties.

Planhat describes its traffic light utility as a feature where the values and "traffic light" coloring of Health Scores and Success Units enables you to quickly identify opportunities and risks, and Planhat makes it easy for you to act in response, either automatically or manually, according to Planhat. The platform positions Health Scores as a great way for you to see, at a glance, whether each customer Company could be an opportunity for expansion or advocacy, or at risk of downgrade or churn, according to Planhat.

For automation triggers, Planhat notes that it's very easy to automatically take action in response to specific changes in Health Score - for example, you can choose from a variety of templated Automations to do things such as create an Opportunity or a Task, or send a notification, according to Planhat. Those Planhat Automations can create an Opportunity or a Task, or send a notification, in response to specific health-score changes.

Custify offers a different approach by focusing on behavioral signals. Their customer success tool can monitor customer behavior and usage patterns to identify signs of disengagement or dissatisfaction, according to Custify. CustifyAI is an AI tool for customer success, churn risk, playbooks, and summaries, according to Custify.

When configuring these triggers, you must decide whether your team responds to visual alerts or automated actions. Planhat’s system supports both manual and automatic responses to the same score changes, giving you flexibility in how your team engages with at-risk accounts, according to Planhat. Custify's customer success tool can monitor customer behavior and usage patterns to identify signs of disengagement or dissatisfaction, according to Custify.

To set up these alerts effectively, start by defining what constitutes a risk in your specific context. Planhat lets users choose Automations in response to specific health-score changes, according to Planhat. Custify can monitor customer behavior and usage patterns to identify signs of disengagement or dissatisfaction, according to Custify.

Consider how your team will consume these alerts. Planhat's traffic light coloring helps you quickly identify opportunities and risks and act automatically or manually, according to Planhat. Custify’s AI tool generates summaries and playbooks that can guide specific next steps, according to Custify. Your choice between these approaches should align with your team’s workflow and the level of automation you are comfortable implementing.

Use this worksheet to audit your current health score logic against the eight configuration items. After you set up the HubSpot customer success workspace, create a health score and select the segment of contacts or companies before you set scoring criteria and points, according to HubSpot. Record your current segment selection in the first row. Document each reference item: validity extension, auto calculation, predefined groups, permissions, property limits, weight distribution, traffic-light colors, and automation triggers. If your platform lacks a listed configuration item, record that absence. This exercise helps you identify gaps in your configuration before you adjust weights or validity periods.

Review your platform's documentation for each configuration item in the reference table. Focus on how N/A values are handled in your calculation logic, as this often requires specific weight redistribution rules. Verify that your automation triggers align with your traffic light alerts. Compare your current setup with the reference table earlier in this post. This comparison will highlight where your implementation differs from the documented rules. Use these insights to plan any necessary changes to your health score configuration.

• Onboarding tools: compare 4 customer project plans

How does modifying a score affect its validity period?

Gainsight extends the validity period by one week when a score is updated within its current validity window. The new validity period starts on the date the score was modified, according to Gainsight. This rule applies specifically to updates made during the active validity period.

Can a single health score use more than 50 properties?

Vitally states there is no limit on how many properties a single health score can use. One score can draw on as many of the available 50 properties as needed, according to Vitally. This allows for comprehensive scoring logic within a single metric.

What happens if a health category is marked as N/A?

Vitally proportionately distributes the weight of an N/A category across the other category weights to add up to 100%. For example, if a CSM pulse trait is N/A, its 10% weight is redistributed, according to Vitally. This ensures the total weight remains balanced despite missing data.

Which permissions are required to create a health score in HubSpot?

HubSpot requires Manage Customer Success Settings permissions to create a health score. Users must have this specific permission level to perform the action, according to HubSpot. Verify your access level before attempting configuration.

How do traffic light colors help identify churn risks?

Planhat uses "traffic light" coloring on Health Scores and Success Units to enable quick identification of opportunities and risks. This visual aid makes it easy to act in response, either automatically or manually, according to Planhat. The coloring system supports rapid decision-making for customer success teams.

This post is general operational information, not legal advice about notice periods or renewal clauses. It does not promise that any method keeps a customer. A review model checked the facts once, and that check can miss errors, so open the sources before you act.