Change Management and Request Tracking
Key Takeaways
- Change management reduces risk by requiring clear scope, impact analysis, approval, scheduling, communication, testing, and rollback planning.
- Request tracking creates an audit trail for who requested work, who approved it, what changed, and whether the result was successful.
- Standard, normal, and emergency changes have different approval and timing requirements.
- A change window limits planned disruption and gives teams a clear time to validate or roll back.
- Post-change review captures lessons learned and updates documentation, baselines, and runbooks.
Networks are shared systems. A small change to a route, VLAN, firewall rule, wireless controller, or DHCP scope can affect many users. Change management provides a repeatable process for making changes with less risk and better accountability.
Change Record Contents
| Field | Purpose |
|---|---|
| Requester | Identifies who asked for the change |
| Business reason | Explains why the change is needed |
| Scope | Defines devices, services, locations, and users affected |
| Risk and impact | Describes what could go wrong and who may be affected |
| Implementation plan | Lists the steps to make the change |
| Test plan | Defines how success will be verified |
| Backout plan | Defines how to restore the previous state |
| Schedule | Establishes a maintenance window |
| Approver | Confirms authorization |
| Communication plan | Tells stakeholders what to expect |
Good request tracking also captures timestamps, comments, attachments, approvals, related incidents, and final outcome. The ticket becomes evidence that the change was authorized and performed according to process.
Change Types
| Change type | Description | Example |
|---|---|---|
| Standard change | Low-risk, pre-approved, repeatable work | Add an access switchport using an approved template |
| Normal change | Planned change that needs review and approval | Replace a branch firewall |
| Emergency change | Urgent work to restore service or reduce immediate risk | Block an actively exploited inbound path |
Emergency changes should still be documented. The approval may be expedited, but the organization still needs a record of what happened, why, who approved it, and what follow-up is required.
Risk and Impact Analysis
Risk analysis considers probability and consequence. Impact analysis identifies who or what may be affected. A change to a core switch is usually higher risk than changing one unused access port. A firewall rule change for a payment application may have higher business impact than a lab VLAN adjustment.
Questions to ask:
| Question | Why it matters |
|---|---|
| What systems depend on this path? | Reveals hidden impact |
| What is the failure mode? | Supports backout planning |
| Can the change be tested first? | Reduces uncertainty |
| Who must be notified? | Prevents surprise outages |
| What evidence proves success? | Avoids vague completion criteria |
Maintenance Windows and Communication
A maintenance window is an approved time for planned work. The window should align with business needs, support availability, vendor access, and rollback time. Communication should identify expected impact, start time, end time, contact path, and whether users need to take action.
Post-Change Review
After a change, operators should validate service health, update diagrams and IPAM, close the request with evidence, record deviations from the plan, and capture lessons learned. If the change caused an incident, the review should identify what failed in planning, testing, communication, or execution.
Practical Scenario
A team plans to migrate a branch from one ISP to another. A strong change request includes circuit details, affected users, routing changes, firewall updates, DNS or DHCP changes if needed, test steps, provider contacts, a communication plan, a maintenance window, and a rollback plan to restore the old circuit if validation fails.
Common Exam Traps
| Trap | Better exam reasoning |
|---|---|
| "Emergency changes do not need documentation." | They still need records and follow-up review. |
| "Approval alone makes a change safe." | Planning, testing, communication, and rollback are also needed. |
| "Close the ticket as soon as commands are pasted." | Validate service health and attach evidence before closure. |
| "Change management only applies to outages." | It applies to planned, standard, normal, and emergency work. |
Quick Drill
Choose the best process item:
- Know who authorized a firewall change: request tracking and approval record.
- Restore service if the new configuration fails: backout plan.
- Limit planned disruption to a known time: maintenance window.
- Confirm the change achieved the intended result: test and validation plan.
- Capture what should be improved next time: post-change review.
A planned routing change could disconnect a remote office if it fails. Which item should be included before approval?
Which details belong in a network change request? Choose two.
Select all that apply
A critical firewall rule must be added immediately to contain an active threat. What type of change is this most likely to be?