Abstract
Delay analysis methods, as used on construction projects, are now well established. The intent of this paper is to enhance the understanding of the implementation of these methods. Delay analysis on projects generally relies on programs (schedules) both in as-planned and as-built forms, and combinations of these two forms. The paper discusses some of the deficiencies in the current use of such programs in delay analysis. The paper draws attention to the representational nature of these programs and the implications of this. It is remarked that the as-planned and updated versions are no more than models of project workflow while the as-built version can, in the extreme case, be anything the contractor wants it to be. In this paper, it is argued for the first time that in any consensus between owner, contract administrator and contractor of as-planned and as-built status for delay analysis purposes, at any stage of a project, there is need not only for agreement on information at the project and activity levels as is common industry practice, but also for disclosure of lower level information, in order to get closer to a rational delay analysis.