The NEW Impact Platform Health Score - what changes, what to expect, and where to start!

[Naomi La]

See what matters most with the new Platform Health Score

Serious findings count more. Minor ones count less.

Effective

October 8, 2026 (October Monthly Release)

Applies to

Customers using the Platform Health experience in Impact Store App v12. Health Assessment reports continue to use the existing Health Assessment scoring model.

Availability

Impact Store App v12. Find it in Application Manager on your instance. Backwards compatible with Brazil Patch 1, Australia Patch 7, and Zurich Patch 13.

1000+

Definitions, up from 300+ in the previous scoring model

0–100

Score scale

Your initial score may increase or decrease.

The scoring method and definition coverage have changed. This reflects a new methodology, not a decline in platform health.

Overview

What's happening

We're upgrading the Platform Health Score to reflect risk more accurately. The new risk-weighted scoring model weights findings by severity, category, and impact, so your highest-value remediation work moves the score in proportion to the risk you address.

The Platform Health Score measures platform health using definitions evaluated by the Scan Engine. It turns 1000+ definitions into one score from 0 to 100, so you can see where your risk sits and what to address first.

Why your score matters

The previous scoring model weighted findings equally, so critical risks could be less visible. The new risk-weighted scoring model tells you how healthy your platform is overall. Drill into the findings to determine where to focus.

What's changing

Why the score is changing

The previous scoring model had three important limitations. It treated all findings equally, could change when new definitions were introduced, and could produce differences between Full and Delta Scan results because the scans covered different scopes. The new Platform Health Score addresses these limitations through risk weighting and scope-aware calculation.

Previous scoring model	New risk-weighted scoring model
300+ definitions	1000+ definitions, expanded coverage
Findings weighted equally	Risk-weighted: severity, category, and impact set the weight
Score movement did not reflect finding severity	Score movement is proportional to the risk you address
Full and Delta results could differ because their scopes differ	Scope-aware calculation puts Full and Delta results on one scale

Our approach

Why we're doing this

Aligned with best practice

Risk-weighted scoring is industry standard across large cloud and SaaS platforms.

Credibility

A score tied to risk helps you connect your work to business outcomes such as faster deployments, lower platform risk, and better adoption.

Clarity

Remediation priorities become clearer. Start with the high-risk items and see your score reflect that progress. Lower-impact issues can wait.

Completeness

You see a fuller picture of your platform health, based on expanded definition coverage.

What to expect

Your score may change initially

What to expect

Your initial score under the new risk-weighted scoring model may increase or decrease because the scoring method and definition coverage have changed. This does not necessarily indicate a sudden change in your instance. It establishes a new baseline based on the expanded, risk-weighted model.

Score changes reflect a new scoring methodology rather than a decline in platform health.

How to read your score under the new risk-weighted scoring model

•  Treat your initial score under the new risk-weighted scoring model as your baseline

•  Prioritize fixes by impact, because high-risk fixes tend to move your score the most

•  Report progress to leadership with a more risk-aware view of platform health

A detailed guide to interpreting your score is attached at the bottom of this article.

How it works

How the score is calculated

1	Weigh each definition W = DW × S × (Impact ÷ 10) × A
2	Measure how widely it fired M = 1.0 + log10(1+R) ÷ log10(1+Rmax)
3	Add up the risk that fired B_fired = sum of (W × M) for fired definitions
4	Set the ceiling B_max = sum of (W × 2.0) for all definitions
5	Score it 100 × (1 − B_fired ÷ B_max), rounded down

Example data

What each fix is worth

Example data

Platform Health Score after each remediation path (0–100)

Baseline		21
Fix 190 UX findings		23
Fix 4 Security findings		41
Fix 6 Security findings		62
Fix Security + slow query		73

Illustrative example: a 10-definition library that starts at a score of 21. Six Security fixes add 41 points. 190 UX fixes add 2. Your results will differ.

Next steps

What you need to do

1

Understand the change

Read the detailed guide and FAQ attached at the bottom of this article, then find Impact Store App v12 in Application Manager.

2

Run a Full Scan

Run a Full Scan to establish your baseline. Record your score and band.

3

Prioritize by risk

Start with the highest-risk findings, beginning with Act-level Security findings.

4

Report progress

Your score provides a more risk-aware view of platform health.

Reading your score

Read your score, then act

	Good · 40–100	Needs attention · 20–39	At risk · 0–19
What it tells you	Within acceptable bounds	Measurable risk is present on your platform	Significant Security or high-weight risk
What to do	Keep your scan cadence. Address open findings in your normal sprints.	Sort findings by weighted contribution. Address the highest first.	Escalate internally and engage your ServiceNow team.
Start with	Act- and Recommend-level findings	Act-level Security, then high-impact Performance and Upgradeability	Act-level Security findings rated Impact 8–10

Scores run from 0 to 100. The new risk-weighted scoring model uses three bands: Good, Needs attention, and At risk. The previous scoring model used four: At Risk (0–70), Fair (70–80), Good (80–90), and Excellent (90–100). Because the two models use different scoring methods, compare scores within the same model rather than across models.

Frequently Asked Questions

Who gets the Platform Health Score?

Customers using the Platform Health experience in Impact Store App v12. Health Assessment reports continue to use the existing Health Assessment scoring model.

How does the Platform Health Score differ from a Health Assessment score?

The Platform Health Score in the Impact app provides an ongoing view that can be refreshed through subsequent scans as findings are addressed. A Health Assessment score represents the results captured for a specific assessment report and continues to use the Health Assessment scoring model. Because the experiences use different scoring models, their scores should not be compared directly.

Did my platform get less healthy?

The underlying health of your platform did not change because of the scoring update. The score under the new risk-weighted scoring model evaluates platform risk using broader definition coverage and risk weighting, which may produce a different result.

How much will my score change?

It depends on your configuration and findings, and your score may increase or decrease. Run a Full Scan to establish your baseline under the new risk-weighted scoring model.

When does the new scoring take effect, and will it change my past scores?

The new risk-weighted scoring model applies when you run a new Full or Delta Scan in your Impact Store App. It doesn’t recalculate scores from earlier scans, so your historical scores stay as they were. Run a Full Scan to establish your baseline under the new model.

How is the score under the new risk-weighted scoring model calculated?

Each definition has a weight based on severity, category, and impact. Your score reflects the ratio of weighted definitions fired to the weighted definitions that could have fired. A detailed guide with the full formula is attached at the bottom of this article.

What does the score tell me to do first?

Start with the highest-risk findings, beginning with Act-level Security findings, and work your way down. You'll see your score move noticeably when you fix high-impact items.

Does this affect my other metrics (compliance, uptime, etc.)?

This update applies to the Platform Health Score. Your other metrics and reports are not part of this change.

The bottom line

Your score now provides a more risk-aware view of platform health. It shows where risk sits and which fixes matter most, so you can turn findings into a clear action plan.

Go deeper

Product documentation

Learn more about the Platform Health Score

Additional Resources: An Overview guide, Detailed customer guide and Comprehensive FAQ are attached at the bottom of this article.