it-infrastructure/Forms/Change-Requests/FRM-CHG-001-Request-For-Change.md

Request for Change (RFC)

Form ID	FRM-CHG-001	Revision	1.0

---

Change Request Information

Field	Entry
RFC Number	RFC-[YYYY]-[####]
Date Submitted
Requester Name
Requester Department
Requester Email
Requester Phone

Change Classification

Change Type:

• Standard (Pre-approved, routine)
• Normal (Requires CAB approval)
• Emergency (Critical, time-sensitive)

Change Category:

• Hardware
• Software/Application
• Network
• Database
• Security
• Cloud Infrastructure
• Other: _______________

Priority:

• Critical (Must be completed ASAP)
• High (Within 1 week)
• Medium (Within 2 weeks)
• Low (Within 30 days)

Change Description

Summary

Provide a brief description of the proposed change (1-2 sentences)

Detailed Description

Describe the change in detail, including what will be modified

Reason/Business Justification

Why is this change necessary? What business need does it address?

Impact Assessment

Affected Systems

System/Application	Environment	Impact Level
	☐ Prod ☐ Test ☐ Dev	☐ High ☐ Med ☐ Low
	☐ Prod ☐ Test ☐ Dev	☐ High ☐ Med ☐ Low
	☐ Prod ☐ Test ☐ Dev	☐ High ☐ Med ☐ Low

Affected Users/Groups

Dependencies

List any dependencies on other systems, changes, or external parties

Risk Assessment

What could go wrong?

Likelihood of failure:

• Low
• Medium
• High

Impact if failure occurs:

• Low - Minor inconvenience
• Medium - Degraded service
• High - Service outage
• Critical - Data loss or security breach

Overall Risk Level:

• Low
• Medium
• High

Implementation Plan

Proposed Change Window

Field	Entry
Start Date/Time
End Date/Time
Estimated Duration
Maintenance Window Required?	☐ Yes ☐ No

Implementation Steps

Step	Action	Responsible	Est. Time
1
2
3
4
5

Pre-Implementation Checklist

• Backup completed
• Stakeholders notified
• Test plan documented
• Rollback plan documented
• Required access/permissions confirmed

Rollback Plan

Rollback Trigger Criteria: Under what conditions will rollback be initiated?

Rollback Steps:

Step	Action	Responsible	Est. Time
1
2
3

Estimated Rollback Time:

Testing Plan

Test Environment:

• Already tested in Dev
• Already tested in Test/Stage
• Production verification only

Test Cases:

Test	Expected Result	Pass/Fail
		☐
		☐
		☐

Communication Plan

Notifications Required

• End users
• Help desk
• Management
• External parties
• None required

Notification Details

Audience	Method	Timing	Responsible

Approvals

Technical Review

Field	Entry
Reviewer Name
Date
Decision	☐ Approved ☐ Rejected ☐ More Info Needed
Comments
Signature

CAB Review

Field	Entry
CAB Meeting Date
Decision	☐ Approved ☐ Approved w/Conditions ☐ Deferred ☐ Rejected
Conditions (if any)
CAB Chair Signature

Management Approval (if required)

Field	Entry
Approver Name
Date
Signature

Post-Implementation

Results

Field	Entry
Implementation Date
Actual Start Time
Actual End Time
Status	☐ Successful ☐ Partial ☐ Failed ☐ Rolled Back

Issues Encountered

Lessons Learned

PIR Required?

• Yes (Schedule date: _________)
• No

Closure

Field	Entry
Closed By
Date Closed
Final Status	☐ Successful ☐ Failed

---

Form FRM-CHG-001 Rev 1.0 - Request for Change