[CLIENT]

Document: Change Control Plan

Owner: CIO Services Project Office
Purpose
• To systematically control changes to the scope, schedule, cost and effort estimate of the
engagement.
• To describe how changes are identified, analyzed, monitored, and approved.
• To define the threshold for change and the required levels of approval.

Instructions for use

• Replace [CLIENT] with the client’s name. (Ctrl + h)
• Review the Change Control Process with [CLIENT]. Understand that resolution of
issues, changes in assumptions, and mitigation of risk or contingency plans may lead to change
requests.
• Confirm [CLIENT]’s threshold for change and required level(s) of approval. Complete
the table showing levels of authorized change approval with names, roles, and change threshold
information. Be sure to ask if multiple levels of approval need to be identified given [CLIENT]’s
financial policies.
• Copy the Change Request Form to a location where both the engagement team and
[CLIENT] can use it to initiate new requests.
• Create a separate log for summarizing change requests. Assign a team member—the
default is the program manager—to be responsible for tracking change requests and status.
• Before you distribute the completed Change Control Plan, delete this cover sheet.

47287004.doc EDS Confidential Page 1 of 4

[CLIENT]

Change Control Process

Identify change
[CLIENT] or CIO Services may identify changes. This plan primarily addresses changes to the
engagement scope or schedule, including changes to the estimated cost and effort.
• Scope change—Any tasks or deliverables requested by [CLIENT], or determined
necessary by CIO Services in addition to those described in the statement of work, including any
changes to assumptions
• Schedule change—Any event that would change the baseline schedule, engagement
duration, dependencies, or resources

A change request form is submitted to the CIO Services team. The request is assigned a number and
added to the change request summary log. The request is then assigned to a CIO Services team member
who completes an impact analysis for the change. The impact analysis is submitted to [CLIENT] and the
CIO Services program manager for approval. The impact analysis for the proposed change includes the
following:
• The impact the change will have on scope, schedule, cost, or estimated effort
• A detailed proposed solution, including alternatives if appropriate

Identify threshold for change

[CLIENT] and CIO Services must approve requests that include the following criteria:
• Involve a scope change.
• Cause the schedule to exceed any phase-end milestone date.
• Result in a cumulative impact of more than $10,000 on the total cost.
• Result in a cumulative impact of more than 5 percent on the total effort.

This ensures that all affected parties carefully consider each change request and that the appropriate level
of approval is obtained. After a change order is approved, the schedule or other components of the
engagement plan may require updating.

Levels of Authorized Change Approval

Approver Name Role Scope Schedule Cost Effort
[CLIENT] Project Manager any any $10,000 5%
CIO Services Program Manager any up to 2 weeks $10,000 5%
CIO Services Program Executive 2 weeks $20,000 10%

Document potential risks

If work on the solution to a change request proceeds without approval, then a corresponding entry must
be made in the Issue-Risk Management Plan. The risk of working on a solution before it is formally
approved is that the agreed upon estimated cost, effort, or schedule might not be met. Also, if the change
request is approved, but with modifications to the original, work may be duplicated.

47287004.doc EDS Confidential Page 2 of 4

[CLIENT]

Change Request Form

Change Request Information - Completed by requester for New status

Tracking Number: Request Type: Change

Requested By: Request Date:

Impact (Priority): High Medium Low

CIO Services Program Phone:

Executive:
Affected Component(s): Version/
Date:
Short Description:

Detailed Description:

Tracking/Impact Analysis Information - Completed by CIO Services engagement team

Assigned To: Assigned Date:

Proposed Solution:

Effect on Scope, Schedule,

Cost, and/or Effort:
Estimated Resolution Time Estimated
(hours): Resolution Date:

Approvals - Completed by [CLIENT] and CIO Services authorized approvers

Disposition: Approved Rejected Pending

Disposition Reason:

[CLIENT] Approver: Date:

CIO Services Approver: Date:

47287004.doc EDS Confidential Page 3 of 4

[CLIENT]

Change Request Summary Log

Effect on Scope,
Change Schedule, Cost
Request # Short Description and/or Effort Status Status Date

47287004.doc EDS Confidential Page 4 of 4