NowTech

From verification to resolving defects. And beyond, toward a system you can keep using.

We investigate the impact of ServiceNow upgrades and, if problems are found, handle everything from root-cause analysis to fixes and re-verification. We also review how things are built today so your system is easier to prepare for future changes.

We can help whether you built it in-house or another IT vendor implemented and developed it.

Two people consulting while pointing at a monitor

Toward an upgrade-resilient system.

Along with fixing the problems found this time, we review your current system so it's easier to check and fix at the next upgrade. While keeping the customizations your business needs, we sort out their relationship to standard features and the impact of changes, shaping it into something easier to keep using.

A glass panel showing check marks and color-coded verification status
Needs fixingNeeds checkingUnchangedAn image of organizing the impact of changes by color.
  1. 01Review what standard features can handle

    We confirm the role your current customizations play and consider where standard features can be used.

  2. 02Map where changes have an impact

    We check screens, logic, and connections to other systems, making it clearer what to check when changes happen.

  3. 03Leave notes on what to check next

    We record why fixes were made and what was checked, so they can be used for the next verification and in-house improvements.

Rebuilding everything is not the premise. After understanding your current work and system, we decide together what review is needed for your environment.

"Upgrade-resilient" here doesn't mean no defects ever occur. It means a state where the impact of changes is easy to understand and verification, fixes, and maintenance are easy to carry out.

Prepare for regular upgrades.

With every upgrade, you need to check whether the screens and logic you've developed or changed still work as expected.

Product releasesTwice a year

How often ServiceNow normally publishes new releases

Your upgradesAbout once a year

A guideline for how often your environment needs upgrading to stay on a supported release

Supported releases are the latest and the one before it, based on ServiceNow's upgrade policy. Release timing, frequency, and policies may change, and treatment may differ by contract.Upgrade policy (ServiceNow, English)

You can consult us at any stage.

During preparation, mid-verification, or after defects are found post-upgrade. Tell us where you are now.

  1. Preparation

    "We don't know how much to check before an upgrade."

    "A previous person in charge or another IT vendor developed it, so we don't understand the current system."

  2. Mid-verification

    "Verification found a problem, but we don't know the cause or how to fix it."

  3. After the upgrade

    "After the upgrade, screens and logic that used to work stopped working."

  4. Looking ahead

    "Every upgrade takes time for the same kinds of checks and fixes."

    Toward an upgrade-resilient system

From verification reports to resolving problems.

Beyond verifying and reporting results, you can hand off root-cause analysis, fixes, and re-verification of any problems found.

  1. 01Organize the scope to check

    We investigate current settings, customizations, and business impact, and decide what to verify.

  2. 02Verify behavior

    We check whether the target screens and logic still work as expected after the upgrade.

  3. 03Investigate and fix

    We investigate where problems were found and make the needed fixes while confirming the approach with you.

  4. 04Confirm behavior after fixes

    We re-verify the fixed areas and related behavior and explain the results.

Upgrade checklist (example)

  1. Input validation on the request screenNot checkedCheckingCheckedIssue foundFixingRe-verified
  2. Notifications to approversNot checkedCheckingCheckedIssue foundFixingRe-verifiedNotifications not delivered. Investigate the cause and fix
  3. Data integration with the HR systemNot checkedCheckingCheckedIssue foundFixingRe-verified
  4. Monthly report outputNot checkedCheckingCheckedIssue foundFixingRe-verified

ReportWe verified 4 items. For 1, we investigated the cause, fixed it, and re-verified it together with related behavior.

The checklist is an image of the approach. Actual items are set for your environment.

Even if NowTech didn't build it.

We start by investigating your current settings and logic.Keeping your current support structure, you can also hand off only the verification and fixes for upgrades.

Your companyBusiness checks and decisions

We decide business impact and priorities together.

Current vendorContinue current maintenance and operations

Day-to-day operations and inquiries can stay as they are.

NowTechVerification, fixes, and system review

Handles verification, root-cause analysis, fixes, re-verification, and reviews for what's next.

An example of how roles might be divided. The roles of you, your current vendor, and NowTech are organized to fit your situation.

Consult us about upgrades.

Whether you're preparing or mid-verification, we'll start from where you are.

Tell us about your next upgrade schedule and any concerns from verification.

Consult us about upgrades