OBLYTECH Logo
OBLYTECH Logo

ServiceNow Change and Release Management: Freezes and Requests

For your ServiceNow change and release management process, document how change requests relate to releases, how you decide when work can ship, what happens when it misses its date, and who signs off the move into production. Confirm field names, roles and options on your own instance before you build a process around them.

How the change and release workflow runs from request to go-live

Consider the following workflow for pipeline and manual deployments, adapting the order and mechanics to your tools and approval process.

  • Raise the change request with a clear scope, a named owner and a test evidence plan.
  • Approve the change and attach it to its target release on the calendar.
  • Build and test the content, then record the results against the request.
  • Pass the release freeze, or request a documented exception.
  • Complete the approvals for risk, timing and technical readiness.
  • Move the release into production, confirm the result and close the linked changes.

Our guides on update sets and release management cover the build side of this flow in more detail.

Attaching each change request to its release record

As a process recommendation, track the intended release for each change request so the release manager can review the planned content before the freeze. Check that approved work has a scheduled target.

Consider recording the target release at approval and checking it again when development is complete. If the scope has grown since approval, review its release target again. The governance model behind update sets and releases is the place to decide who makes that call.

Checking each change for schedule clashes before approval

Conflict detection checks a change request’s planned window against blackout windows, maintenance windows and other change requests on the same configuration item or assignee. Running it before approval means a clash surfaces while the schedule can still move, not on go-live day.

The conflict calendar marks other active change requests, blackout schedules and changes scheduled outside a maintenance schedule. Use the Scheduling Assistant to resolve any schedule conflicts. For how blackout and maintenance windows are set up, see how change windows work.

Conflict detection can run automatically when the configuration item, planned start date or planned end date is entered or updated, and it can also be scheduled to run at set intervals. The settings sit under Conflict Properties in the change administration menu.

By default, not all conflict analysis properties are selected. Review which checks are enabled, including the checks against parent and child configuration items, so that clashes on related items are flagged.

What a freeze date stops and how exceptions get through

Define a freeze date in your process as the point after which a release stops taking new content without an approved exception. Decide who can approve late additions and how to assess their effect on testing. Consider business events such as a month-end close or a peak trading period, and put the dates in the release calendar where change approvers can see them.

Write a freeze as a window with a start and an end, not as a single date. That gives emergency changes a defined route through it. An exception should name the change, the risk, the test evidence and the approver, and it should be recorded on the release record so the next review can see it. If you want help setting these rules up, the ServiceNow change management consulting page describes how that work is scoped.

Moving deferred items to the next release without losing them

Deferred items are requests planned for a release and then taken out. Possible reasons include failed testing, a shift in business priority, or a freeze that arrived before the work was ready. The trouble starts when the item stays attached to the old release record. Check the old and new release plans so deferred work stays visible.

Move each deferred item to the next release on the calendar, record why it was deferred, and ask its owner to confirm the new target. Keep the reason on the record so any later deferral can be considered alongside the earlier decision. If items keep failing to move cleanly between releases, the troubleshooting guide for update sets and release management covers the usual causes.

Fitting platform upgrades into the release roadmap

A release roadmap lays out the windows for your own changes across the year. Platform upgrades follow their own timetable and touch the same instance, so they need rows of their own on the calendar. Schedule upgrade testing ahead of your business freeze rather than after it, and leave a gap between an upgrade window and a large release. Allow time to test customizations and address any upgrade issues before the next release. Check the upgrade dates and release notes that apply to your version before you lock the calendar, and confirm the timing for your instance.

Emergency changes need a separate route through approval

Define an emergency approval route in your process, including who may raise a request, who approves it and how it is recorded against the release. Emergency changes bypass normal schedules, so limit submission rights to authorized teams, and confirm the configured workflow and approvers on your instance before relying on any expedited path.

Record whether the work addresses an impact that has already occurred or one that is imminent, together with the risk and test evidence. Check for effects on systems outside the original plan.

Confirm which integrations, event-processing settings and change classification fields your instance uses. Document how unexpected changes should be reviewed and how related records should be linked. Name the approver, the reason and the affected release on the record itself, rather than relying on a message thread.

Frequently asked questions about change and release management

How do change requests link to a release?

Confirm how your instance supports associating change requests with releases and whether any dates are populated automatically. As a process recommendation, record the target release at approval and review it again when development finishes or scope changes.

What happens at a freeze date?

Define who approves freeze exceptions in your process. Review work that misses the freeze, agree a new release target and record the reason for deferral.

Who approves production moves?

Name the roles in the process. One possible split: the release manager confirms content and test evidence, a change approver confirms risk and timing, and the platform owner confirms technical readiness. Define how these checks apply to pipeline and manual moves, and where approvals belong in each workflow. If you want outside help designing these checks, see our ServiceNow change governance and release management support.

Does the same process work for pipeline and manual deployments?

You can use shared approval, freeze and release-tracking rules for pipeline and manual deployments. Confirm the workflow for each and decide how deployment evidence will be recorded and reviewed.