ServiceNow Impact v12: reading the new Platform Health score

ServiceNow Impact is ServiceNow’s paid customer success offering. Through the Impact app, a Store app you install on your instance, you plan product adoption, measure value, and check instance health with Platform Health.

Version 12 of the app came out on October 8, 2026. The Q4 release announcement on the ServiceNow Community lists five changes: Setup Hub, a new score, expanded scan definitions, new value models for HR and customer service, and the maturity assessment. For admins who report the Platform Health score to their managers or customers as a measure of instance health, the score change matters most. The number will go up or down the next time you run a scan, even if nothing on the instance has changed.

The new features are only in the Impact app#

The Q4 announcement says these features are exclusive to the Impact app. On the ServiceNow Store, the Impact app’s price is listed as “Paid”.

According to the official documentation, Impact subscriptions come in three packages: Guided, Total, and Integrated Success. Guided, the entry tier, comes with a dedicated customer success manager. Total adds a team that includes a customer success executive and a platform architect. Pricing is not published. UpperEdge, which advises customers on ServiceNow contract negotiations, wrote in December 2025 that list price is 10% of annual subscription fees for Guided and 30% for Total. That is a third party’s view, not an official ServiceNow figure.

Platform Health grew out of an app from Bravium Labs (Best Practice Engine), which ServiceNow acquired in 2025. According to the post-acquisition explainer, scanning is included in every paid Impact plan. On Guided, you can enable at most 10 custom definitions (scan definitions you write yourself), and the Proposed Fix library is not available. To get the same features as Total, you buy the Platform Health add-on.

What changes in the Platform Health score#

Platform Health scans your instance against definitions based on ServiceNow best practices. The issues it finds (Findings) roll up into a score from 0 to 100. A ServiceNow employee’s explainer on the score names three problems with the old method. Every Finding counted the same, so critical issues did not stand out. The score moved just because new definitions were added. And a Full Scan, which checks everything, and a Delta Scan, which checks only changes, covered different scopes, so their results drifted apart.

The new method weights each definition by severity, category, and impact. Fixing a critical security issue moves the score more than fixing a minor UX issue. The explainer walks through an example with only 10 definitions. Starting from 21, fixing 6 security Findings raises the score by 41 points, while fixing 190 UX Findings raises it by only 2. The post notes that this is an illustration and that real results depend on the environment.

ServiceNow Docs says each category is scored from 0 to 100 and then combined using the weights below. The table heading says “Proposed weight”, and every value is approximate.

Category	Weight
Security	about 40%
Performance	about 22%
Manageability	about 19%
Upgradeability	about 9%
User experience	about 9%

Fixing Findings in one category does not move the score of any other category.

The rating bands change#

The score bands changed too. Here are the old and new bands.

Method	Bands
Old	At Risk (0–70), Fair (70–80), Good (80–90), Excellent (90–100)
New	At risk (0–19), Needs attention (20–39), Good (40–100)

Under the old method, anything below 70 was At Risk. Under the new one, 40 and above is Good. A score of 60 is At Risk under the old method and Good under the new one. The explainer also asks you to compare scores only within the same method, since the two are calculated differently. If your internal reports chart the score month by month as a line, add a note at the month of the switch and do not connect the new numbers to the old ones.

When it applies, and to whom#

The new method applies when you run a new Full Scan or Delta Scan in Impact app v12. Scores from past scans are not recalculated and stay as they are. It applies to users of the Platform Health screens in the Impact app. Health Assessment reports keep the existing scoring method, and the explainer says not to compare those two scores either.

Your first score may go up or down. The explainer says this is not a sudden change in instance health but a new baseline under a new standard. It recommends four steps:

1. Read the guide and FAQ attached to the explainer, and check for Impact app v12 in Application Manager
2. Run a Full Scan and record the score and band as your baseline
3. Start with security Findings at the Act level (action required), which has the highest severity
4. Report progress using the new score

Where the sources disagree#

The material on this change is spread across two community posts, the Docs, and the Store release notes, and they disagree on several points.

The first is the number of scan definitions. The Q4 announcement says the migration of scan definitions is complete and the count has grown from 544 to 1,004. The score explainer says it grew from just over 300 under the old method to just over 1,000. They may be counting different things, but I could not confirm that from the sources.

The second is the formula. In the score explainer, the formula takes the sum of the weights of detected definitions, divides it by a ceiling calculated from the weights of all definitions, and subtracts that ratio from 100. Breadth of detection is measured against the highest count observed. In the Docs, each definition is compared against a fixed baseline set when the definition was created, each category is scored, and the categories are then combined by weight. The Store release notes, like the Docs, describe evaluating the five categories separately against fixed baselines. The FAQ attached to the score explainer gives the formula “100 × (1 − detected risk ÷ maximum risk)”, the same shape as the explainer’s. The Docs, on the other hand, say that comparing against the highest count was the previous method. The sources do not settle whether the two community documents or the Docs match the current implementation.

The third is supported releases. The score explainer lists compatibility with Brazil Patch 1, Australia Patch 7, and Zurich Patch 13. The Store page for v12 lists Brazil, Australia Patch 5, and Zurich Patch 12. The reliable way to check whether you can install it is to select your instance version on the Store.

When you explain the score internally, state in the report which source’s calculation method you are relying on. If questions come up later, you can point to your basis.

Setup Hub puts configuration in one place#

The previous setup flow (Guided Setup) was a text-heavy, step-by-step screen. In v12 it is replaced by Impact Setup Hub. According to the Q4 announcement, you can go from installing the app to finishing configuration in one place, with ServiceNow Otto’s AI guiding the steps. Setup progress is kept across upgrades.

Setup Hub requires the impact app admin and admin roles. On the ServiceNow landing page, choose “Manage Your Products” and then “Impact”. If the app is not installed, it starts with installation. Configuration is split into six areas: AI agents, users and access, Platform Health, instance registration, data sync and migration, and collecting data for value measurement. Platform Health alone has seven steps. Some areas have a fixed order, and you cannot move on until you finish the previous one. You can stop partway and pick up later.

New value models for HR and customer service#

According to the Q4 announcement, the value models and dashboards for HR and customer service now follow the same format as the ITSM update in August. The products covered are HR Service Delivery and Customer Service Management. They show outcomes that can be converted to money alongside those that cannot, and let you review and adjust the formulas and assumptions. Your current models stay in place until you switch.

The Docs release notes say a setting was also added to switch metrics that were calculated from estimates over to actual data from Performance Analytics. Value Reports, which show return on investment in monetary terms, require at least two years of data per product. In the Impact app, you can only view reports published on the Impact Delivery Instance; you cannot create or manage them. For a product you adopted recently, the dashboard may show numbers while reports are not yet available.

The maturity assessment now takes multiple respondents#

Impact offers Accelerators, a menu of scoped engagements. One of them, the Maturity Assessment, used to be answered by one person. In v12, the assessment owner can invite other members and assign them questions by domain. According to the Docs, responses are collected over 14 days. Every question is single choice, and respondents pick the option that matches current practice, not plans or documentation. All questions and domains carry equal weight.

The owner sees the combined results from everyone, but participants cannot see each other’s answers. When you set a target level for each domain, the questions with the largest gaps are highlighted, and an action plan with owners and notes is created. According to the Store release notes, the action plan can be exported as an Excel file with a summary sheet and one sheet per domain.

Impact subscriptions limit how many Accelerators you can run at the same time. On Guided, the limit is one at a time across all types. The sources did not say how the 14-day collection period for multiple respondents counts against this limit.

Other changes#

The Docs release notes also say that on-demand scans of Platform Health definitions now finish in under a minute per instance on average. In September, v11 added the Scan Engine API, which lets you run scans on demand through an API, so you can feed Findings into the approval stage of a CI/CD pipeline.

What I could not find out#

Neither the Store page nor the Docs say whether the Impact app’s interface is available in Japanese (the Docs themselves have a Japanese version). The packages available under contract in Japan appear to be listed on ServiceNow’s Japan-specific contract terms page, but I could not retrieve that page to confirm. I also cannot tell from public sources which of the two formula descriptions matches the current implementation.