Week 8 of 8
Production upgrade and sign-off
ServiceNow can roll back a patch or hotfix, by default within 10 days. It does not offer that for a move between families, and it advises against restoring production from backup. So the decision to upgrade production rests on the evidence you collected on dev and test.
ServiceNow’s own checklist ends with functional and performance tests on a production clone, a production performance benchmark before the upgrade, and user acceptance testing after it.
This week: build the go/no-go pack and plan the first 48 hours
- Collect the evidence: skipped records resolved and tested, ATF suite results exported, role matrix passed, integrations passed, UAT signed.
- Run an Instance Scan before and after the test upgrade and explain any new findings.
- Benchmark key production transactions before the upgrade so you can compare after it.
- Agree the go/no-go criteria and who can waive a red item, in writing, before the meeting.
- Plan the post-upgrade smoke test and UAT in production, and a short hypercare log for the first week.
Number of the week
51
steps in ServiceNow’s own upgrade planning checklist, from identifying testers to UAT after the production upgrade.
Source: ServiceNow docs, Upgrade planning checklist (Brazil)Use this week
- Go/No-Go Readiness Checklist →
Criteria with thresholds, blocking flags and an automatic recommendation.
- Hypercare Defect Triage Log →
Separate real defects from training and data issues after the upgrade, and feed them back into regression.
- Guide: testing a ServiceNow family upgrade →
The full playbook in one place, with sources.
That is the playbook. From next week you will get the weekly roundup of new statistics, guides and templates from The Sign-Off Table.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.