Construction Delay | Forensic Delay Analysis | Expert Witness | Director at Planetal Limited
Programmes are an estimate of the time and sequence of the works. They forecast the events and are therefore theoretical. They can be well thought out and detailed, providing more surety but there is always the risk involved meaning they cannot be a certainty.
A Programme is an Estimate, Not a Certainty A programme is essentially a forecast—a plan for how to get from Point A to Point B. But in construction, it's rare for everything to go exactly as planned without some form of deviation. This is because construction projects are inherently complex, involving multiple interfaces, numerous unknowns, and various risks. One of the key considerations is getting your planned outputs right. While some maintain the same outputs for every job, others adjust based on specific site constraints. Keeping a record of the outputs achieved during delivery is a good idea, but it only becomes robust when the resource levels and constraints are also recorded. These factors are the driving considerations for what was actually achieved on-site. Sometimes, planned outputs may not be adequate—whether due to an error in estimation or unforeseen changes. Adjusting these outputs based on actual site production can provide a more realistic forecast of potential impacts or offer the necessary insight for mitigation decisions on-site. In essence, flexibility and accurate record-keeping are key to maintaining a programme that remains relevant and reflective of the realities on-site. #ConstructionManagement #ProjectPlanning #ProgrammeManagement #DelayAnalysis #ConstructionProjects #RiskManagement #PlanetalLimited
Plan the work then work the plan
DBA,FAICD, FAPE, GPCF, FPMCOS, MACS(Snr), CP, IP³, Grad DISC Consultant – Senior Planner and Senior Master Scheduler and Lead Project Controls
2moQuite correct Matthew, as it has been for the past 60 years or so. However folks who run projects now are not as concerned about the accuracy of worked performed, keeping proper and correct project data. It seems close enough is OK, we both know that is not so. Which certainly causes a great deal of pain when making a delay claim with poor documentation. Getting rid of the site clerk and their book of details saying what happened and when was so much better than the occasional entry into spreadsheet. It always been true that saving money by reducing rigour is always very expensive in the end