Skip to content

Network & Security Support · Deliverable

Network Change Records Filed in Your ITSM.

Change records filed in your ITSM system for all network modifications

Part of Network & Security Support. Last reviewed October 2026.

Quick answer

What is Network Change Records Filed in Your ITSM?

Network change records are entries in your IT service management system that describe each modification to network equipment, including the plan, risk, approval, backout, execution times, and outcome. Deploris engineers follow your change process, create or update the records, and attach evidence so every change is traceable afterward.

WHAT THE WORK COVERS

What Network Change Records Filed in Your ITSM includes.

  • 01Creation or update of change records in your ITSM tool, such as ServiceNow or Jira Service Management, using your change types and templates
  • 02Implementation plans written step by step, with the devices, interfaces, and configuration lines affected by the change
  • 03Risk and impact statements, the maintenance window, and the backout plan with a clear trigger for when to use it
  • 04References to the approval from your change advisory board or change manager, recorded before any work begins
  • 05Execution timestamps, the engineer who performed the change, and notes on anything that differed from the plan
  • 06Closure notes with attached evidence, such as configuration diffs, test results, and photos, plus links to related incident or project tickets

HOW WE DELIVER IT

How it is delivered.

  1. 1

    Align on your process

    We learn your change categories, approval path, naming rules, and required fields, and agree who creates records and who approves them for this engagement.

  2. 2

    Prepare before the window

    The engineer drafts the implementation and backout plans, and your change manager approves them. No device is touched on a change that has not been approved.

  3. 3

    Execute and annotate

    During the window, start and end times are recorded, deviations are noted in the record, and the backout plan is used if its trigger conditions are met.

  4. 4

    Close with evidence

    After validation, we attach configuration diffs and test results, mark the outcome, and close or hand the record back to you per your process.

INPUTS AND OUTPUTS

What you provide and what you receive.

You provide

  • ITSM access with a user account or an agreed integration that lets our engineers create and update change records
  • Your change process documentation, including categories, approval rules, and blackout calendars
  • Names of the change manager and approvers who sign off on work in scope
  • Related ticket numbers for the incident, project, or request that the change supports

You receive

  • Complete change records for each network modification, with plan, approval reference, and backout details
  • Execution times and engineer names tied to each record
  • Attached evidence such as configuration diffs, test results, and photos
  • A summary list of all changes made during the engagement, matched to the closeout report

WHEN IT FITS

When this is the right deliverable.

Scenario 01

Your policy requires an approved change for every device modification, and contractors have previously made changes that never appeared in the ITSM tool.

Scenario 02

You are running a multi-site rollout and need one consistent change record per site so that your CAB can review progress and exceptions.

Scenario 03

An audit needs a clear trail from each configuration change back to an approval and a person, which supports your compliance evidence.

WHERE WE DELIVER

Delivered in 75+ metros across 11 countries.

Local, vetted engineers deliver this work on site across the United States and Western Europe, coordinated by one engagement manager.

QUESTIONS

Frequently asked questions.

Do you file network change requests in our ITSM system?
Yes, when you provide access. Engineers create or update records using your templates and categories, or draft the content for your change manager to submit if you prefer to keep creation in-house. Both approaches are set out in the written scope.
Which ITSM platforms can your engineers work in?
We work in the platform you use, commonly ServiceNow or Jira Service Management, and we follow your fields and workflow. If your tool is less common, we can supply the content in a structured template for your team to enter.
Do you make network changes without an approved change record?
No. Work on production devices starts only after the approval reference is recorded, except where your own emergency change procedure applies and you authorize it. In that case, the record is completed immediately afterward with the full details of what was done.
What evidence do you attach when closing a network change?
Typically a before and after configuration comparison, the test results that confirm the change worked, execution timestamps, and photos for physical work. The attachments are chosen to satisfy your closure requirements and let a reviewer reconstruct what happened.

QUOTE

Request a quote.

Share a few details and we will come back with the next steps.

Get started

Need engineers on site? Tell us where.

Tell us the sites, the scope and the timeline. We reply with a written plan.

Go to

Saved and recent pages stay on this device. Press ? for keyboard shortcuts.

Keyboard shortcuts

Search the site
/ or Ctrl K
Show this list
?
Switch light, dark or system theme
t
Save or unsave this page
s
Go to the home page
g then h
Go to services
g then s
Go to coverage
g then c
Go to the contact form
g then q

Shortcuts are off while you type in a field.