---
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 October 8, 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 provides ServiceNow customers with a comprehensive metric to assess the overall health and risk of their instance.
It consolidates multiple risk categories into a single score from 0 to 100, enabling clear visibility into areas requiring attention and guiding remediation efforts.
Show full answer Show less  

## Key Features

* **Four-step calculation process:** The score is derived through a structured method involving fixed reference comparisons, independent category scoring, weighted aggregation, and consistent scope across scan types.
* **Category-based scoring:** The model scores five distinct categories---Security, Performance, Manageability, Upgradeability, and User Experience---each independently rated from 0 to 100 to highlight specific risk areas.
* **Weighted roll-up:** Final overall Platform Health score combines category scores weighted by their relative risk importance, ensuring critical issues like Security have a greater impact than less urgent concerns like User Experience.
* **Stable reference points:** Each check compares its findings against a fixed baseline rather than variable scan maxima, preventing distortion of category weights from changes in unrelated checks.
* **Consistent scoring scope:** Both full and delta scans evaluate findings across the entire instance uniformly, ensuring score comparability over time.

## Calculation Details

The scoring model applies these mathematical steps:

* **Magnitude:** Measures how widely a check's findings occur, capped to prevent any single check from dominating the category score.
* **Weighted penalty:** Calculates the contribution of each check to its category's risk based on severity and impact.
* **Category health score:** Aggregates weighted penalties into a 0--100 score per category, independent of other categories.
* **Overall Platform Health score:** Combines weighted category scores into the final 0--100 metric reflecting overall instance risk.

## Category Weights and Risk Importance

| Category | Weight | Description |
|-|-|-|
| Security | \~40% | Highest risk, covering breach, compliance, and access vulnerabilities. |
| Performance | \~22% | Impacts all users; degradation compounds if unresolved. |
| Manageability | \~19% | Largest volume of issues affecting administration and support. |
| Upgradeability | \~9% | Can block or delay ServiceNow upgrades despite smaller volume. |
| User Experience | \~9% | Affects adoption and satisfaction but with lower urgency. |

This weighting ensures that remediation efforts focus on the most impactful risk areas without skewing unrelated categories.

## Practical Impact for Customers

ServiceNow customers can use the Platform Health score to:

* Quickly understand their instance's risk posture across critical areas.
* Prioritize remediation based on category-specific scores and their weighted importance.
* Track health consistently over time, regardless of scan type (full or delta).
* Make informed decisions to improve security, performance, manageability, upgradeability, and user experience.  
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/0uD14YiK3EqjCn1q5bOtqw "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 after F reaches 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}

## 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 does not change the score on its own.

## 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}