What Is ServiceNow Upgrade Readiness? A Plain-Language Guide
What Problem Does the Readiness Practice Solve?
ServiceNow publishes new family releases. These updates include new features, security patches, and configuration changes. Organisations usually have to evaluate each release, plan when to adopt it, and prepare for changes. The question is: are we ready to upgrade? What could go wrong? What will we need to change?
Without structured preparation, upgrades become risky. A team upgrades to a new release, discovers that a critical plugin is not compatible, and must roll back immediately. Or they upgrade and a custom report breaks. Or they upgrade and the application runs slowly because a performance setting changed. Proper planning lowers the chance of these problems. The readiness practice helps you plan and prepare.
What the Readiness Practice Covers
Upgrades and release readiness is a practice rather than a single module: ServiceNow provides the Upgrade Center, with an upgrade preview that predicts which customised records the upgrade will skip and a monitor for the upgrade itself, alongside Instance Scan and the Automated Test Framework, and the practice is how a team uses those tools to prepare for a release. It helps you identify what changed in the release (the new and changed features, problem fixes and known error articles that the upgrade preview links to). It helps you identify which customised records the upgrade would skip, using the upgrade preview. The practice also asks whether your team, processes and systems are ready for the upgrade.
Checklists (technical readiness, team readiness, data readiness) and any readiness scoring are the team’s own practice built around the output of the platform tooling, not features of a module. A workable plan follows the platform’s upgrade sequence: clone production to a test and a non-production instance, apply the upgrade to the non-production instance, process the skipped list there, test, then apply the upgrade to the test and production instances. The production implementation plan should cover the upgrade steps, with roles, responsibilities and communication plans attached.
Who Uses the Readiness Practice?
The primary users are platform owners and architects who plan upgrades for their organisations. They are responsible for deciding when to upgrade and ensuring the organisation is prepared. IT operations staff carry out the upgrade and check the new release afterwards.
Business stakeholders (HR, finance, IT leaders) provide input to the readiness assessment. They identify which processes are mission-critical (time off requests, payroll processing, customer contracts) and which can tolerate some downtime. They help assess the impact of new release features on their business processes.
How It Works at a High Level
When a new release becomes available, you preview it in Upgrade Center. In your own checklist, record the facts about your environment (which modules you use, which critical plugins, how many users, what your SLA is). The upgrade preview analyses your configuration and lists the records the upgrade would skip, which becomes the technical starting point for your readiness checklist. The checklist includes technical tasks (review breaking changes, test plugins), process tasks (document current workflows that might be affected), and team tasks (train staff on new features).
You work through the checklist over weeks, testing changes and fixing issues discovered. As you address items, the number of completed items goes up. When the checklist reaches the completion level the team agreed in advance, and the high-risk items carry evidence, the team declares itself ready to upgrade. You schedule a cutover window, and IT operations executes the upgrade. After the upgrade, you validate that the system works and all processes are functioning normally.
How the Readiness Practice Differs from Other Tools
The readiness practice is not a change management tool (Change Management guides the approval and scheduling of individual changes). It is not a testing tool (the Automated Test Framework runs tests) and it is not the upgrade itself, which ServiceNow applies to the instance at the scheduled time through the Upgrade Center. Instead, it is the readiness practice described above, used to plan and prepare for major platform upgrades.
When to Use the Readiness Practice
Use the readiness practice when your organisation is planning a major release upgrade (moving from one release to the next). Use it for the first time your organisation experiences an upgrade so that you establish a repeatable process. Use it if your environment is complex (many modules, many custom extensions, many integrations) because complexity increases upgrade risk. Use it if your SLA is strict (limited downtime tolerance), so the problems get found before the cutover window rather than during it.
You do not strictly need the readiness practice for minor updates or patches (these usually do not require the full readiness process), though it does not hurt to use it. Some organisations use it for every release; others use it for major releases only. Decide based on your risk tolerance and change velocity.
When the Readiness Practice Is Not a Good Fit
If your ServiceNow environment is brand new and you have not yet customised it heavily, upgrade risk is relatively low and a formal readiness process might be overkill. If you have a strict release schedule and cannot delay upgrades, be aware that the readiness practice adds planning time; you will need to start the process weeks or months before a target upgrade date. If you have limited IT staff and cannot dedicate time to readiness activities, the value of the practice may not justify the effort.
How the Readiness Practice Relates to Neighbouring Applications
Once readiness is confirmed, you schedule the upgrade in the Upgrade Monitor module, which also tracks its progress. After the upgrade, you use Incident Management to track any issues that occur, and you may use Problem Management to conduct a post-upgrade review.
Key Success Factors
Start the readiness process early; do not wait until a week before the scheduled upgrade. Allocate dedicated resources (a readiness lead, a technical lead) who drive the process. Engage business stakeholders early so they understand what is changing and why. Test in a non-production environment first so you discover issues before they affect production. Have a rollback plan in case the upgrade needs to be reverted. After the upgrade, schedule a retrospective to capture learnings and improve the next upgrade cycle.
Read the readiness result as evidence of what was checked
A readiness checklist can show a high level of completion and still leave the most dangerous risk untouched. The reason is that the items on the list describe activities, and an activity can be marked complete without anyone confirming its result. Before acting on a readiness outcome, ask what each completed item actually proves. A “reviewed release notes” tick proves that someone read them. It does not prove that the reviewer compared the notes with the custom code in use. The reading habit that prevents surprises is to convert every completed item into a statement of evidence.
| Signal in the readiness report | Evidence it supplies | Gap it leaves open |
|---|---|---|
| Release notes reviewed | Someone opened the notes | That the changes were matched to your custom code and integrations |
| Plugin compatibility item closed | The item was marked as checked by its owner | That the plugin behaves correctly after the upgrade, or that its vendor agrees |
| Technical readiness section complete | The checklist items in that section are ticked | That the test results support the tick, or that the test coverage was adequate |
| Team training item closed | A session was scheduled or held | That users understand the changed workflow |
| Overall readiness outcome above the target set | The weighted checklist reached the agreed level | That the high-weight risks were given their weight in the first place |
When a high score hides a weak area
An overall score is an average, and averages hide concentrated risk. An instance can score well because most of its checklist is routine, while a single custom integration carries the whole business exposure. The way to see this is to look at the sections individually and ask whether any one of them would stop the upgrade if it were the only section that counted. If the answer is yes for any section, the score should not be the decision basis.
Check the weighting too. Items weighted equally can make a trivial cosmetic check count as much as a data migration check. Agree the weights with the technical lead before the checklist is used, not after the result is known, because the temptation to adjust weights to reach a target is strong.
A short procedure for challenging a readiness result
- Open each section and identify the one or two items that would cause the most damage if they were wrong.
- For each of those items, ask for the evidence behind the tick: a test result, a ticket, an export or a signed review.
- Where no evidence exists, record the item as unverified rather than complete.
- Confirm the weighting with the technical lead and note any item that carries a weight that looks wrong for the risk.
- Decide the go or no-go on the verified picture, and list the unverified items as known exposure with an owner.
Signs that the readiness process is being run for the report
- Items are closed in a batch shortly before the review meeting, with no dates on the evidence.
- The same people own every section, so no independent reviewer has looked at the outcome.
- Open items are reclassified as out of scope when the deadline approaches.
- Nobody can name a readiness item that was reopened after it was first closed.
Questions about reading readiness results
Should a readiness target ever be waived?
A target can be waived, but the waiver should name the risk being accepted and the person accepting it. A waiver recorded that way is a decision. A waiver that appears only as a changed number is a finding waiting to happen.
Who should check the outcome besides the owner of the readiness plan?
A reviewer who did not build the checklist. Peer review of the evidence, not of the score, is the check that catches the batch-closing habit described above.
What do we record when an item was closed and later proved wrong?
Reopen it, record why it was wrong, and note whether the same kind of item is closed elsewhere on the list. A single wrong tick is often a sign that a whole category was marked on assumption.
Is a readiness score useful at all?
It is useful as a summary and as a trend across cycles. It should not be the only reason for a go decision, and it works best when the sections behind it are read as well.
The practice of treating each check as evidence runs through several related pages. The metrics page for upgrades and release readiness pairs well with the checklist, and the note on release acceptance criteria explains how to set the evidence bar before the readiness work begins.
Frequently asked questions
How far in advance should we start the Upgrades and Release Readiness process?
Start the readiness process well before your planned upgrade date. This gives you time to assess readiness, address issues discovered, test in a non-production environment, and prepare teams. Complex environments with many customizations may need more time. Simple environments may need less. Do not start too early (requirements may change); do not start too late (you will not have time to address issues).
What if the readiness assessment reveals that we are not ready to upgrade?
That is the point of the assessment: to identify issues before they cause production problems. Prioritise the most critical issues, fix them, and re-assess. If some issues cannot be fixed in time, you may need to postpone the upgrade or accept the risk and proceed with a more limited upgrade. Escalate to leadership for a decision. Never upgrade when critical readiness issues are unresolved.
What happens if we upgrade and discover an issue?
That is why you have a rollback plan. If an issue is minor and can be worked around, you might proceed. If an issue is critical (the system is not working correctly, data is affected), you should roll back to the previous release. After a rollback, investigate the issue and plan a future upgrade attempt after the issue is resolved.
Related guides
Related Oblytech services
Where this topic turns into delivery work, these are the Oblytech services that cover it.
Planning, running or fixing a ServiceNow programme? Tell us where you are and we will suggest a sensible next step.
Contact us