Change control in a project

What is it?

Change control is the process through which all requests to change the approved baseline of a CSCS project or programme are captured, evaluated and then approved, rejected or deferred. A lack of change control is a common cause of project delay or failure. 

Why is it important? 

To ensure that we are not changing things in the project or programme that don't need to be changed. This helps avoid disruption to services and ensures the efficient use of resources. This enables CSCS to deliver projects on time, budget and to agreed quality levels that have been agreed with customers.

How do CSCS use change control? 

All CSCS projects should be delivered to an agreed Scope of Work (SoW), which has been signed off by the project executive, senior user and project team.  Change control helps to manage the requests submitted to alter the baseline project scope and assess the impact these may have on the project as a whole. Consideration will be given to impact on agreed timelines and quality, as well as additional resources or costs which may result from the requested change.

CSCS will look to review change requests submitted against the agreed project or programme of works. Priority and impact of the request will be assessed, as will any associated dependencies and a decision will be made to approve, reject or defer the request. If approved, any expected impact to the current planned works would be discussed with the customer.

How should I log a change to a CSCS project or programme? 

A CSCS Project Change request form must be submitted to the CSCS Project Team. This request will then be reviewed and a decision communicated back as to whether the change has been accepted, rejected or deferred. Additional information may be requested to support the request once submitted and to help inform the decision.