Exhibit D - Change Control Sample (1).pdf

PDF 63 KB Posted

Attached to
Bank Reconciliation Services
Solicitation number
RFP-124435
Issued by
Richmond City, Roanoke City, Virginia

About this file

This document is a Change Control Process exhibit provided by the Virginia Department of the Treasury in support of its Request for Proposals for bank reconciliation services. The exhibit establishes the formal procedures by which either the buyer or seller may initiate modifications to the project scope, deliverables, resource allocation, or other contractual plans. A change request may be submitted at any time by either party with reasonable justification and must be documented if the proposed change will delay the schedule by more than five days, materially increase or decrease the project scope, or cause estimated effort to vary by more than ±5 percent. The initiating project manager is responsible for managing the change control process, with the receiving project manager required to analyze and respond to all change requests within five business days. All change requests must be reviewed by project leadership and presented to project sponsors for final approval prior to commencement of any associated work.

The change control form requires detailed documentation including the client name, project name and number, request name and number, reason for change, cost impact, seller and client effort in hours, unit costs in Canadian dollars, extended costs, and schedule or scope implications. Both the seller and client must formally approve, reject, or cancel each change request through authorized signatories. This standardized process ensures that all modifications are properly assessed for impacts on the project before proceeding, maintaining control over project scope, budget, and schedule throughout the contract term.

View the file

Other files

Show all 14

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Appendix A - Change Control Process In the event that the Buyer or Seller determines that the Scope of this project/ proposal requires modification, they will use the following Change Control Process. This ensures that change requests are properly reviewed, assessed for impact on the project, and approved prior to proceeding. A change is defined as a change to requirements, deliverables, estimates, resource allocation, or other plans that have an impact on the Project/SOW or estimated effort in this SOW varies more than +/- 5%. The initiating Project Manager is responsible for managing the Change Control Process.

CHANGE REQUEST

Client Name:

Project Name: Project #:

Project: Date Issued:

Project Manager: Date Due:

Request Name: Request #:

Reason for Change Prepared by:

Details of Change Prepared by:

Cost Amount Prepared by:

Activity

Seller Effort (Hrs)

Client Effort (Hrs)

Unit Cost

(CAD$)

Extended Cost (CAD $

Total Estimate (based on current contracted hourly rates)

Schedule / Scope Implications Prepared by:

(A)pproved / (R)ejected / (C)ancelled (A)pproved / (R)ejected / (C)ancelled

Name: Name:

Authorised Signatory:

Authorised Signatory:

The change control process can be initiated at any time by either party if there is a reasonably good faith belief that such change is required. The party that identifies the need for a change will begin the process by issuing a Change Request. The receiving Project Manager(s) will then analyze the change within five business days, identify the impacts, review, and agree on potential actions to be taken prior to documenting the proposed change. Each party shall return their comments or approvals of the any Change Request within five business days. A Change Request is to be documented and processed if the change will:

- delay the schedule by more than 5 days

- materially increase or decrease the Project Scope or budget.

Change Requests will be reviewed with the project leadership and presented to the Project Sponsors for final approval. Work associated with Change Requests will not be commenced until formal approval is achieved.

File details come from the government source that posted it. Updated .