Change Management Process

Information Issue
considered by the Engineer to
have no impact on the Contract
Conditions

Actions by
Engineer

Actions by
Contractors

K
E
Y

Request
for Change reviewed
by Project Team
(Project Manager,
Engineer & Cost
Engineer)

Rejected and or
further information
required

Review and agree

time cost and
other associated
impact with
relevant parties

Budget Control
Actions by
Project Team

Site Instruction
Actions by
Employer

CVI
or
RFI

Approval Request
Form

Approved by
Employer

Other as
appropriate

Actions by
Any party

Request
for Change

Proforma
document
Reviewed by
Contractor

Variation

Any general issue identified by

any party that is considered a
change to an established contract
and or budget allocation

No Variation

Information Issue
Considered by the Engineer to have
an impact on the Contract
Conditions

Reviewed by
the Engineer

Issue
Engineers
Instruction

Incorporate into
Works

Change
Request

Change

Raise

Engineers
Instruction

Agreed
Value of
Instruction

Engineers
Instructions

Rejection by
Employer
alternative solution
requested

THE CHANGE MANAGEMENT PROCESS

WHY CHANGE MANAGEMENT?
1. LOG ALL CHANGES TO THE DESIGN AND IDENTIFY WHO ORIGINATED THEM
2. ASSESS THE COST AND TIME AFFECT ON EACH CONTRACT PRIOR TO INSTRUCTION
3. OBTAIN CLIENT APPROVAL PRIOR TO INSTRUCTION
4. PROVIDES DATA FOR REAL TIME COST REPORTING
5. PROVIDES DATA FOR MANAGEMENT REPORTING AND ANALYSIS OF CHANGE

Documentation Flow

PM

R.F.C.
(REQUEST FOR CHANGE)

CLIENT, PM, QS,

ENG.

ENGINEER

CLIENT, QS, CONT

A.R.F.

E.I.

A.V.I.

(APPROVAL REQUEST
FORM)

(ENGINEERS
INSTRUCTION)

(AGREED VALUE OF
INSTRUCTON)

CHANGE

PM

R.F.C.

A.R.F.

C.C.I.

(REQUEST FOR CHANGE DESIGN)

(APPROVAL REQUEST
FORM - DESIGN)

(CONSULTANT CHANGE
DESIGN)

Instructions
Pending Value

Instructions
Pending Value

Impact on Cost Report

COST
REPORT
CONTRACT
VALUE

Instructions
Agreed Value