About this template
Change request, tested-rollback plan, risk score, CAB checklist and a worked example for network engineers
What you get: Part A change request with exact-step table, pre-checks and post-checks. Part B rollback plan with measurable triggers, decision owner and deadline. Part C 6-factor risk score with handling by rating. Part D CAB / peer-review checklist. Part E post-implementation review. Part F fully worked example (VLAN trunk change).
Who it is for: Network engineers, sysadmins and small-team leads who write change requests and are tired of reviewers sending them back for missing rollback detail.
Files:
- Network-Change-Request-and-Rollback-Plan-Kit.docx (about 8 pages, Word)
How to use: Copy the document per change, replace the [BRACKETED] fields, delete the guidance lines, attach Part B. Use Part C to decide the review level.
What it is NOT: Not a full ITIL process, not tied to a ticket tool, no vendor commands. Vendor-neutral; adapt to your own policies. Not legal, compliance or professional advice.
Created with AI assistance and reviewed by the author.
Questions
What file type do I get?
One Word file (.docx), Network-Change-Request-and-Rollback-Plan-Kit.docx, about 8 pages long.
Can I edit it to fit my own policies?
Yes. It is a Word document. You copy it for each change, replace the [BRACKETED] fields and delete the guidance lines. It is vendor-neutral, so you adapt it to your own policies.
How do I start, and does it replace professional advice?
Copy the document for each change, fill in the [BRACKETED] fields, attach Part B (the rollback plan) and use Part C to decide the review level. It is a planning template and not legal, compliance or professional advice. Part F is a worked VLAN trunk example you can follow.
