---
sourceDocument: Brazil Impact
sourceDocumentLink: https://www.servicenow.com/docs/r/impact

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Health score calculation

# Platform Health score calculation model {#ariaid-title1}

Release version: Brazil  
Updated November 16, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Platform Health score calculation model

The Platform Health score is a comprehensive metric designed to quantify the overall risk of your ServiceNow instance by evaluating various risk categories independently and then combining them into a single score from 0 to 100.
This score helps you understand your instance's health across critical areas such as Security, Performance, Manageability, Upgradeability, and User Experience, enabling targeted remediation efforts based on risk severity and impact.
Show full answer Show less  

## Key Features

* **Four-step calculation process:**
  * **Fixed reference:** Each check compares findings to a stable reference point to ensure consistent weighting regardless of changes in other checks.
  * **Category scoring:** Each risk category (Security, Performance, Manageability, Upgradeability, User Experience) receives an independent 0--100 health score, highlighting which areas need attention.
  * **Weighted roll-up:** Category scores are combined into an overall Platform Health score using fixed weights that reflect the relative risk of each category, ensuring that critical issues like Security have greater influence than less urgent ones.
  * **Consistent scope:** Both full and delta scans evaluate findings on the same instance-wide basis, making scores comparable regardless of scan type.
* **Mathematical model:** The scoring uses logarithmic scaling and weighted penalties to calculate the magnitude of findings per check, compute category health, and then aggregate to the overall score. This approach prevents any single finding from disproportionately affecting the score.
* **Category weighting:** The score attributes approximately 40% weight to Security, 22% to Performance, 19% to Manageability, and 9% each to Upgradeability and User Experience, reflecting their typical risk impact on your instance.
* **Display and rounding:** The Platform Health score is shown as a whole number on dashboards to provide a clear and actionable summary, while the stored score retains full precision.

## Why it matters

This scoring model gives ServiceNow customers a reliable, risk-based assessment of platform health that:

* Identifies the most critical areas requiring attention based on their impact on security, performance, and overall manageability.
* Prevents skewing of health metrics by ensuring checks are independently evaluated and weighted appropriately.
* Supports better decision-making by providing clear insights into where to focus remediation efforts to reduce instance risk.
* Enables consistent tracking of platform health over time and across different scan types.

## What to expect

* An actionable, easy-to-understand score that guides prioritization of fixes according to risk severity and category importance.
* Transparent category-level scores that help pinpoint root causes and target improvements effectively.
* Stable scoring methodology that minimizes fluctuations due to new definitions or changes in other categories.  
Your Platform Health score is the foundation for understanding instance risk. The score reflects platform risk through a four-step, category-weighted calculation that combines findings into a single 0--100 health
metric.
Each scoring category is evaluated independently, then combined into a single overall score using fixed category weights. A critical Security finding should not be weighted exactly the same as a cosmetic User Experience finding, and
remediating a Performance issue should not alter your Upgradeability score.
{#instance-health-score-calculation__table_calculation_steps__entry__3}

| Step | What happens | Why it matters |
|-|-|-|
| 1. Fixed reference | Each check compares its own findings to a stable reference point established when the definition was authored, not to the largest finding count in that scan. | Fixing one check doesn't distort the weight of another. |
| 2. Category scoring | Security, Performance, Manageability, Upgradeability, and User Experience are each scored independently, 0--100. | You can see exactly which category needs attention and why. |
| 3. Weighted roll-up | Category scores combine into one overall Platform Health score, weighted by how much each category matters to your risk. | Security counts more than a cosmetic issue. |
| 4. Same scope for Full and Delta | Full and delta scans count findings on the same instance-wide basis. See [Full and delta scans](https://www.servicenow.com/docs/fL7RsKaUfT0stBpQER214g "The full and delta instance scan feature with Impact Platform Health Scan Engine enables ServiceNow administrators and developers to initiate, monitor, and manage instance health.") for more information on scans. | Your score means the same thing, regardless of scan type. |
[Table 1. Health score calculation steps]

{#instance-health-score-calculation__table_calculation_steps}

## Formulas {#instance-health-score-calculation__section_formula}

Here are the four steps translated into the actual calculations.
{#instance-health-score-calculation__table_formulas__entry__3}

| Step | Formula | What it computes |
|-|-|-|
| 1. Magnitude | `Magnitude = min(2, 1 + ln(1+F) ÷ ln(1+R))` Note: Magnitude = 0 when F = 0, and is capped at 2 when F reaches or exceeds R. This is the natural logarithm. | How widely a check fired, capped at 2× so one check can't dominate its category. |
| 2. Weighted penalty | `Penalty = W × Magnitude` | The check's own contribution to its category's burden. |
| 3. Category health | `CategoryHealth = clamp(100 × (1 − ΣPenalty ÷ ΣCeiling), 0, 100)` | A 0--100 health score for that category alone, unaffected by any other category. |
| 4. Overall score | `Score = Σ (CategoryWeight × CategoryHealth)` | Category scores combined into one Platform Health score, weighted by importance. |
[Table 2. Platform Health formulas]

{#instance-health-score-calculation__table_formulas}

Where:

* F: The number of records a check found.
* R: The check's stable reference point. R is not set per definition. It is a fixed tier: 10 for checks that return one finding for an entire table, 20,000 for all others.
* W: The check's own weight, based on its severity and impact.
* <var class="keyword varname">Category Weight</var>: The category's share of overall risk, shown in the following category weights table.
* ΣPenalty: The sum of all weighted penalties in that category.
* ΣCeiling: 2 × W for every active check in the category, whether or not it fired.

{#instance-health-score-calculation__ul_formula_vars}  
Note:  
The Platform Health score displays as a whole number on the Executive, Platform Owner, and Team Lead dashboards. For example, a calculated score of 92.94 displays as 93%. Rounding applies to the display only and does not change the stored score.

## How categories are weighted {#instance-health-score-calculation__section_category_weights}

Category weighting reflects how much risk each area typically represents across the check library. These weights are applied only at the final roll-up step, so a change in one category's findings won't distort the calculated health of
another category. See [Scan Engine definitions](https://www.servicenow.com/docs/HYGJFcSGcpcvjlOxv13Z2g "The Scan Engine uses a large set of definitions to correct coding and workflow findings in real-time and perform scans across your entire instance to detect existing findings.") for their definitions.
{#instance-health-score-calculation__table_category_weights__entry__3}

| Category | Weighting | Description |
|-|-|-|
| Security | \~40% | The highest-consequence category, encompassing breach risk, compliance violations, and access-control vulnerabilities. |
| Performance | \~22% | Affects every user on the instance and compounds if left unaddressed. |
| Manageability | \~19% | The largest category by volume, impacting administration and supportability. |
| Upgradeability | \~9% | Smaller in volume but can block or delay ServiceNow release upgrades. |
| User Experience | \~9% | Important to adoption and satisfaction, but carries the lowest urgency overall. |
[Table 3. Category weights and risk assessment]

{#instance-health-score-calculation__table_category_weights}  
Note:  
Publishing new definitions is designed to have minimal impact to the score on its own, as your denominator includes active definitions. .

## Related concepts {#instance-health-score-calculation__section_related_concepts}

For more information, see the following:

* [Scan Engine definitions](https://www.servicenow.com/docs/HYGJFcSGcpcvjlOxv13Z2g "The Scan Engine uses a large set of definitions to correct coding and workflow findings in real-time and perform scans across your entire instance to detect existing findings.") --- Category definitions and their weights
* [Scan Engine Executive dashboard](https://www.servicenow.com/docs/DrlyU406sw05i~uhE1b09Q "The Executive dashboard includes trend charts and the following overview modules.")
* [Scan Engine Platform Owner dashboard](https://www.servicenow.com/docs/eCWwptsLeyqcWPcAdvGS5A "The Platform Owner dashboard includes trend charts and the following overview modules.")
* [Scan Engine Team Lead dashboard](https://www.servicenow.com/docs/dit~837itDATrjGdSxRJ2A "The Team Lead dashboard includes trend charts and the following overview modules.")
{#instance-health-score-calculation__ul_related}

