1) The document describes a procedure for reconstructing a baseline program from a later updated program when the original baseline is unavailable in soft copy format. 2) It involves removing progress information and actual dates from the updated program, resetting durations and the data date, and rescheduling to align with the hard copy baseline through iterative forward and backward passes. 3) The goal is to derive a networked baseline program that can be used for delay analysis by fitting the updated program logic and dates to match those in the hard copy baseline as closely as possible.

1. Greig Consulting, Norway and the UAE
W: GreigConsulting.Com, E: David@Greig.Com, T: 00 47 45418061,
No Networked Baseline?
Then Create One by Untangling a Later Update!
A paper by David Greig of Greig Consulting
Delay analysts are frequently frustrated when a client does not retain a
softcopyversionof theirbaseline programme. Here,David Greig of Greig
Consulting examines how a networked baseline programme can possibly
be constructed by rolling backwards a later produced update programme.
Introduction
Baseline programmes are often considered an essential prerequisite for conducting delay
analysis exercises or simply for assessing the value that a damage caused. If however, a
baseline programme is not available in soft copy format1
, but a later update programme2
is, it
may be possible to remove update data from the update and so roll it backwards to reconstruct
a networked baseline programme upon which the update was likely based.
Procedure
Typically, when updating a programme, project planners do not alter the activity Original
Duration3
(OD) nor change the activity to activity logic4
(SS Start-to-Start, FF Finish-to-Finish
1 If a programme is onlyavailable in hard copy of fixed PDF only the information thatis visuallyrecorded can be
deduced. It is common thatsuch hard copy will include:(Early) Start and (Early) Finish dates and Total Float and
perhaps identifycertain inter-activity linkage only.
2
Updated programmes are usually,though not always,prepared based on earlier update programmes or the
original baseline programme.
3
An activity mightbe executed in a longer period than planned. However,the planning software usuallyretains
the OD unless specificallyaltered.
4
The actual sequence ofworks is usually,to some degree,variantfrom the originallyplanned,usuallythe la g
period is different, though less so,the activity link type.

2. Greig Consulting, Norway and the UAE
W: GreigConsulting.Com, E: David@Greig.Com, T: 00 47 45418061,
or FS Finish-to-Start) to reflect revised works sequences or logic changes.Similarly, Variations
works, if added, are often incorporated as stand-alone Fragnets5
.
AACE No. 29R-03 (2.1, D, 3)6
provides a general procedure to recreate the baseline
programme by such a process, which I have modified and extended as follows:
i) Establish an updated programmein soft copy format, closet to project commencement.
ii) Identify all activities with Activity Progress >0%, remove any Actual Start (AS) status
and Actual Finish (AF) status. (Note: The dates may during this step).
iii) Set all activities to illustrate 0% Progress Completion.
iv) Set all activity Remaining Durations (RD) to equal to the Original Duration (OD)7
.
v) Set the programme’s Data Date (DD) to the start of the project. (i.e. Such as the Notice
to Proceed).
v) Re-schedule the programme.
v) Compare the programme dates and Total Float period to those on the hard copy of the
baseline programme and identify any variances (if any).
vi) If necessary, adjust the programme, by altering the activity durations and logic to
create a best-fit to the hard copy version of the Baseline Programme. Initially,
concentrate only on the early dates, and start at the beginning of the programme and
working forwards in time8
, rescheduling after each alteration working through until
completion. Once the correct Completion Date is established (by the early dates),
work backwards from the end altering the activity link lag periods such that only the
Late Dates and periods of Total Float (after each reschedule) are affected though do
not implement any significant changes that alter the Early Dates9
.
vii) When presenting the Recreated Baseline Programme in soft copy format narrate its
origins and composition per the procedure described herein.
Note: Before commencing the above process it might to worthwhile to establish exactly how
variant the Update Programme is from the Baseline Programme. Though the latter is only
available in hard copy format one should establish through visual desktop analysis only what:
i) activities have been added, if any;
ii) which activities have been removed, if any,
iii) which activity IDs have altered;
5 A fragnetis a self-contained routine,or mini-programme,often introduced into a programme to representa
specific elementchanged works.
6
https://web.aacei.org/
7
The Original Durations are often recorded on the hard copy (or PDF) of the Baseline Programme,thus adopted
directly if the Update Programme activity Original Durations are different.
8
This practise is referred to as conducting a Forward Pass.
9
This practise is referred to as conducting a Backward Pass.

3. Greig Consulting, Norway and the UAE
W: GreigConsulting.Com, E: David@Greig.Com, T: 00 47 45418061,
iv) activity descriptions that have been altered, or;
v) whether the WBS or Activity Codes have been altered.
Such variances, if significant, it might well mean it is not possible to attain a meaningful
recreated Baseline Programme. But heh, sometimes it’s fun to just try!
About Us
Greig Consulting routinely undertake the above procedure in order to derive at a workable
networked Baseline Programme which is then used as the basis for delay analysis. If you
would, like assistance to undertake such an exercise, to prepare a detailed delays analysis,
full claim preparation or review, please call David Greig on +47 45418061 or email us on
Info@GreigConsulting.Com.
May 2020