Plain-English steps
Service owners write and read the tests for their own services.
Certify every ServiceNow upgrade, skipped records included
Only current and previous family releases are supported, so most instances upgrade about once a year. Service owners prove each upgrade and skipped customization in plain English.
- Every skipped record retested
- Evidence in the change record
- Service owners write the tests
Open the 'Service Portal' app
Click the 'Request a laptop' item
Click the 'Order Now' button
Remember the 'Request number' as {{req.id}}
Check that 'Stage' shows 'Waiting for Approval'
Service owners own certification
Results in your change record
The ServiceNow integration links runs to change requests and attaches the evidence.
Evidence and sign-off
An evidence pack in Quality View and a named sign-off for the upgrade.
Certify each ServiceNow release
The ServiceNow release rhythm
You schedule the upgrade. The support window decides how long you can wait.
| Release | Timing | Can you defer? |
|---|---|---|
| Family release | Two a year | Within limits; only current and previous are supported |
| Patches | Through the year | You schedule them |
| Skipped records | After every upgrade | No; they must be reconciled |
Typical cadence. Dates vary by instance and region; check your vendor's release calendar.
Compare all vendor calendarsWhere ServiceNow upgrades hurt
The upgrade leaves your changes alone, and that is the risk.
- Customized objects are skipped, and each needs a decision and a retest
- Approvals and fulfillment tasks route differently or stall
- Client scripts and UI policies stop firing when forms change
- Portal widgets and identity or asset integrations drift
Services people use daily
Certify the services employees and customers use every day.
- Incident to resolution: assignment, SLA timers and closure
- Request fulfillment: catalog items, approvals and delivery tasks
- Change approval: risk assessment, approvers and scheduling
- Employee onboarding: HR cases, tasks and equipment orders
Certify platform changes too
Platform teams change catalog items and rules every sprint. The suite that certifies the upgrade certifies each change.
- Assignment rules and SLA definitions
- Catalog variables and approval rules
- Access controls
Hire-to-productive, end to end
ServiceNow sits in the middle of onboarding. Certify both of its hand-offs.
A hire completes in Workday.
ServiceNow opens the onboarding case, orders equipment and creates accounts.
Salesforce grants the new employee the right access.
Questions
Why test if we choose when to upgrade?
You still upgrade about once a year to stay supported, and skipped customizations need proof that they still work.
Does this replace the platform's own test tools?
It complements them. Qventis One certifies end-to-end business processes, including steps in other applications.
Bring your skipped list
Leave with proof
Bring one service and your upgraded sub-production instance. We run it with you and show the evidence.