Change Request Form ©

For [Project Name]

Document Control

Document Information
©

Information
Document Id [Document Management System #]
Document Owner [Owner Name]
Issue Date [Date]
Last Saved Date [Date]
File Name [Name]

Document History

Version Issue Date Changes

[1.0] [Date] [Section, Page(s) and Text Revised]

Document Approvals

Role Name Signature Date

©

Project Sponsor

Project Review Group

Project Manager ©

Quality Manager
(if applicable)

Procurement Manager
(if applicable)

Communications Manager
(if applicable)

Project Office Manager

(if applicable)

©2003 Method123 Ltd. All rights reserved. i

Template Guide

What is a Change Request Form?

A Change Request Form (CRF) is a document which is completed by a member of a project

to request a change. CRFs may be used to formally log any type of change request;
however, the most frequent types of requests are for changes to the project's:

 Scope
 Deliverables
 Timescale
 Resources. ©

Change Request Forms typically include:

 Summary project information

 A description of the proposed change to the project
 A list of the business and system drivers requiring the change to take place
 The benefits and costs of implementing the change
 An overview of the impact of implementing/not implementing the requested change
 An approval section.

When to use a Change Request Form

CRFs are used during the ‘Execution’ phase of the project (i.e. the phase within which the
products are constructed) as part of the Change Management Process. The CRF should be
completed by the Change Requester and formally distributed to the Change Manager for
review. The Change Manager will determine whether or not the form provides adequate
information to submit to the Change Review Group for approval. The Change Manager may
either request that more information be provided or initiate a Feasibility Study to further
investigate the implications of the change proposed. Following the completion of either of
these activities, the change documentation will be presented to the Change Review Group
for approval. The Change Manager will monitor the status of the Change Request and
communicate the final decision of the Change Approval Group to the Change Requester. ©

How to use this template

This document provides a guide on the topics usually included in a CRF. Sections may be
added, removed or redefined at your leisure to meet your particular business circumstance.
Example tables, diagrams and charts have been added (where suitable) to provide further
guidance on how to complete each relevant section.

©2003 Method123 Ltd. All rights reserved. 1

Change Request Form

PROJECT DETAILS

Project Name: Name of the project against which the change is being requested
Project Manager: Name of the project manager responsible for implementing the change

CHANGE DETAILS ©

Change No: Unique identifier for the change (as per Change Register)
Change Requester: Name of person who is requesting the change
Change Request Date: Date on which this form is completed
Change Urgency: © Urgency for undertaking the change

Change Description: Change Drivers:

Brief description of the change requested List any drivers which necessitate this change

Change Benefits: Change Costs:

Describe the benefits associated with the change Describe the costs associated with the change

IMPACT DETAILS

Project Impact:
Describe the impact on the project if this change is / not implemented

APPROVAL DETAILS ©

Supporting Documentation:
Reference any supporting documentation used to substantiate this change

Submitted by Approved by

Name: Name:

Signature: Date: Signature: Date:

__________________ ___/___/____ __________________ ___/___/____

Any documentation to support this change should be attached to this document

PLEASE FORWARD THIS FORM TO THE CHANGE MANAGER

©2003 Method123 Ltd. All rights reserved. 2