Warning: Declaration of Jetpack_IXR_Client::query() should be compatible with IXR_Client::query(...$args) in /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php on line 91

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719
{"id":1548,"date":"2013-09-28T13:02:55","date_gmt":"2013-09-28T18:02:55","guid":{"rendered":"http:\/\/projectprofessionals.org\/?p=1548"},"modified":"2013-09-28T13:02:55","modified_gmt":"2013-09-28T18:02:55","slug":"managing-risk-of-delay-managing-contractor-schedules-part-13","status":"publish","type":"post","link":"https:\/\/projectprofessionals.org\/2013\/09\/28\/managing-risk-of-delay-managing-contractor-schedules-part-13\/","title":{"rendered":"MANAGING RISK OF DELAY \u2013 Managing Contractor Schedules (Part 13)"},"content":{"rendered":"

This McLaughlin & McLaughlin<\/b><\/a> post is the thirteenth (13th<\/sup>) in a series<\/strong><\/a> \u00a0of discussions regarding various aspects of time management as it relates to the risk of delay<\/span>.\u00a0 This post addresses managerial considerations for dealing with schedules prepared by contractors and submitted to owners or their agents (construction managers, managing contractors, advisors, etc.).<\/p>\n

Recently, Mr. Chris Carson authored an excellent article titled \u201cDealing with Contractors Schedules That Cannot be Approved.<\/i>\u201d<\/strong>\u00a0 This fine article was published in COST Engineering<\/b><\/i>(September\/October 2013).<\/p>\n

This article contains excellent advice for project teams regarding schedule management.<\/p>\n

Mr. Carson\u2019s article is, in reality two articles in one.\u00a0 While Mr. Carson\u2019s article presents a methodology for problematic situations (which he calls DSAB), the preamble and initial discussion for this article is highly useful and applicable to project management teams as they address the frontend of project planning and execution.\u00a0 This post summarizes the sage advice provided by Mr. Carson regarding frontend project management challenges as they relate to scheduling and time management.<\/p>\n

In order to summarize the article, we will follow Mr. Carson\u2019s structure.<\/p>\n

Introduction<\/span><\/strong> \u2013 Here the author observes that an approved contractor schedule (as well as updates) is in the best interests of the project.\u00a0 This contributes to alignment between stakeholders and serves to implement contractual requirements.\u00a0 Otherwise, owners and other stakeholders are increasing their risks relative to time performance on the project.<\/p>\n

Risks of Failing to Approve Schedules<\/span><\/strong> \u2013 Mr. Carson points to claims, manipulations and other undesirable outcomes.\u00a0 Further, her notes the problem for the contractor since there is not a baseline to measure project performance.\u00a0 (Sound project management requires solid baselines \u2013 Project Professionals comment).<\/p>\n

Reasons for Failure to Approve Schedules<\/span><\/strong> \u2013 The notion here is that the owner may not approve due to the failure of the schedule to model the project plan.\u00a0 Misalignments can be many and the article includes nine examples.\u00a0 These include:<\/p>\n