Artifact: Request for Change
Relationships
RolesResponsible: Modified By:
TasksInput To: Output From:
Description
Main Description

Requests for Change (RFCs) are triggered for a wide variety of reasons, from a wide variety of sources. RFCs can be concerned with any part of the infrastructure or with any service or activity. The following items are normally included in both paper and electronic RFC forms:

  • RFC number (plus cross reference to Problem report number, where necessary)
  • description and identity of item(s) to be changed (including CI identification(s) if Configuration Management system is in use)
  • reason for Change
  • effect of not implementing the Change
  • version of item to be changed
  • name, location and telephone number of person proposing the Change
  • date that the Change was proposed
  • Change priority
  • impact and resource assessment (which may be on separate forms where convenient)
  • CAB recommendations where appropriate (which may be held separately, with impact and resource assessments, where convenient)
  • authorization signature (could be electronic)
  • authorization date and time
  • scheduled implementation (Release identification and/or date and time)
  • location of Release/implementation plan
  • details of Change builder/implementer
  • back-out plan
  • actual implementation date and time
  • review date
  • review results (including cross-reference to new RFC where necessary)
  • risk assessment and management
  • impact on business continuity and contingency plans
  • status of RFC - e.g. 'logged', 'assessed', 'rejected', 'accepted', 'sleeping'.