Overview & Purpose

Change requests may occur in many formsoral or written, direct or indirect, externally or internally
initiated, and legally mandated or optional. Changes may require expanding the scope or may allow
shrinking it. Most change requests are the result of:

An external event (e.g., a change in a government regulation)

An error or omission in defining the scope of the product (e.g., failure to include a required feature in
the design of a telecommunications system)
An error or omission in defining the scope of the project (e.g., using a BOM instead of a WBS)
A value-adding change (e.g., an environmental remediation project is able to reduce costs by taking
advantage of technology that was not available when the scope was originally defined)
Implementing a contingency plan or workaround plan to respond to a risk.

Scope change requests are an inevitable aspect of most projects and a mechanism for
accommodating changing circumstances, perceptions, and needs.

Scope Change Request Template

Document Information:

Category: Template

Pages (excluding cover): 1

Version: 1.0

Updated: July 2004

Other:
 Scope Change Request Template
Project Name Project Ref. No. Prepared By Date Prepared

Customer Business Unit / Dept. Contact Project Type (STD / ADV)
STD

Person(s) Requesting Change:

Change Number:
Detailed Description of Scope Change Requested:

Reason for Scope Change Requested:

Effect on Project Cost:

Projected Cost Overrun of approximately %
Estimated Cost Reduction of approximately %

Effect on Schedule:
Planned Project Completion Date:
New Project Completion Date:
Additional Remarks:

Approval Project Manager Date

Approval (Other) Date