ITIL Request for Change (RFC) Template

First, enter basic information regarding individuals proposing the change and the date when the proposal will be submitted. 

Select what type of change you are proposing from the drop-down list below. 

If you select "Other", be sure to elaborate in the text form field. 

Select a priority level for the proposal from the list below

Upload the prior change proposal below for reference.

Concisely describe the change in the form field below

Explain why the change should be implemented. 

Outline what you foresee the business impact being if this change is implemented.

List which services will be affected by the change, along with a short description of how the service will be affected during and after implementation.

Although its too early to confirm a time schedule for the change proposal, its good to make some estimates that give an idea of how long the process will take.

Answer questions like:

When do you think the change needs to be made?

How long do you anticipate the implementation process taking?

To maximize the chances of your proposal being approved and the change implemented within the time schedule you suggested, outlining clear counter-measures to neutralize any significant risks is absolutely critical. 

Review the list of risks and determine what counter-measures could be taken to mitigate them as effectively as possible. 

Risks of implementation: {{form.Risks_of_implementation}}

In case the change implementation fails, what is the back-out strategy to ensure services and business operations return to normal as soon as possible?

Describe below what steps should be taken in order to return to normal function if the change implementation fails. 

Next, attach a level of work effort that you anticipate for each personnel.

How many hours/days of work do you think will be required from each personnel resource?

Personnel resources: {{form.Estimation_of_required_personnel_resources}}

All of the information entered in this checklist is presented below so you can easily format it into a separate document if required by your organization. 

Basic details

Change owner: {{form.Change_owner_-_Name}}

Initiator of the RFC: {{form.Initiator_of_the_RFC_-_Name_(if_different_to_the_change_owner)}}

Change priority: {{form.Change_proposal_priority_level}}

Prior change proposal: {{form.Prior_change_proposal}}

Change proposal: 

Description of proposed change: {{form.Description_of_the_change}}

Reason for the change: {{form.Reason_for_the_change}}

Change evaluation: 

Business impact: {{form.Business_impact}}

Services that will be affected: {{form.Services_affected_by_the_change}}

Proposed time schedule: {{form.Detailed_time_schedule}}

Risks of implementation: {{form.Risks_of_implementation}}

Counter-measures: {{form.Counter-measures_to_risks_of_implementation}}

Back-out strategy: {{form.Back-out_strategy}}

Resource requirements:

Required personnel resources: {{form.Estimation_of_required_personnel_resources}}

Estimation of required work effort: {{form.Estimation_of_work_effort_required_by_each_personnel}}

Supporting documents: {{form.Supporting_document_#1}} {{form.Supporting_document_#2}}

Upload the final RFC document and/or link to it.

This is what will be submitted to change management. 

Submit the change proposal to change management, knowing that you have covered each and every aspect of the change, thereby maximizing your chances of approval and swift implementation. 

RFC file: {{form.Request_for_Change_(RFC)_form}}

RFC link: {{form.Link_to_Request_for_Change_(RFC)_form}}

For tracking purposes, you can also enter the link to the change record below.