{"id":37084,"date":"2016-11-29t14:15:17","date_gmt":"2016-11-29t19:15:17","guid":{"rendered":"\/\/www.deco-dalles.com\/?p=37084"},"modified":"2020-01-14t12:19:32","modified_gmt":"2020-01-14t17:19:32","slug":"10-reasons-why-construction-schedules-fail","status":"publish","type":"post","link":"\/\/www.deco-dalles.com\/10-reasons-why-construction-schedules-fail\/","title":{"rendered":"10 reasons why construction schedules fail"},"content":{"rendered":"

this post was originally published on the\u00a0repone\u00a0blog<\/a>.<\/em><\/p>\n

cpm schedules invariably become erroneous, despite best practices, when the rest of the team isn\u2019t pulling their own weight. the integrity of the schedule may have nothing to do with why it became useless or meaningless, or as i like to say, a recorder more than a predictor of the critical path and progress. if the project is large and has multiple prime contractors, its schedule is all the more susceptible to deprecation.<\/p>\n

“a cpm schedule ceases to achieve its intended purpose once it becomes a recorder, rather than a predictor.<\/p><\/blockquote>\n

quite often, schedule failure is predictable. even so, it may seem inevitable. however, for every obstacle to success, there is a solution, or workaround. sometimes it\u2019s bad medicine, and tough to take. it\u2019s up to the scheduler to do everything he can to maintain the integrity of the project schedule. the foregoing is intended to highlight the most challenging obstacles to schedule success, and offer solutions.<\/p>\n

why construction cpm schedules are overlooked, disregarded, misunderstood and deemed useless.<\/h2>\n

 <\/p>\n

1. vote of no confidence<\/h3>\n

many construction professionals scoff at cpm schedules, perhaps as a response to past experiences, or more often, the vote of no confidence is merely intended to mask inexperience that would compromise one\u2019s image.<\/p>\n

recognize that cpm is a science that is generally not well understood by non-schedulers. ignore deconstructive criticism, or take it as an opportunity for a teaching moment.<\/p>\n

2. lapses in reporting<\/h3>\n

so many contractors think they can get by with a baseline, and subsequently as few updates as possible. perhaps they simply aren\u2019t being compelled enough by the cm or owner.<\/p>\n

maintain your demand every month for proper update backup, even if it may not be forthcoming. impress upon the contractor the importance of maintaining monthly updates, especially as it pertains to claims. claims that have reporting gaps are more likely to be downgraded by reviewers.<\/p>\n

3. reporting error and omissions<\/h3>\n

many contractors don\u2019t maintain accurate records of their progress, and are forced to guess at actualized dates. such guesswork may come back to haunt them if the owner has different dates. others simply don\u2019t follow basic instructions. finally, believe only a cpm baseline<\/a> is needed.<\/p>\n

all of the above can be avoided with due diligence. impress upon your client the importance of maintaining the schedule properly, if for no other reason than to be prepared in the event of a claim.<\/p>\n

4. lack of leadership at the executive level<\/h3>\n

despite their mighty mbas, engineering degrees, and exalted certifications, many big muckety-mucks never see a proper gantt chart for the projects under their stewardship. they may consider themselves \u2018bottom-line\u2019 folks – as if that denoted cpm expertise. it doesn\u2019t.<\/p>\n

the scheduler will always be kept (by the gc or cm) as far removed as possible from project executives, because their untainted knowledge is a liability. indeed, cpm executive briefs don\u2019t seem to reach their intended audience before they are obsolete. these circumstances are out of the scheduler\u2019s control.<\/p>\n

as a project starts to lose traction, offer solutions, and request access to higher level team members who might help streamline the process, or facilitate recovery or mitigation schedules. i offer webex conferences<\/a> to my clients because they seem to gain higher comprehension with the graphics and discussion format.<\/p>\n

5. politics<\/h3>\n

not infrequently do gcs and cms unduly skew progress reports to their advantage, or to obfuscate some other reality. they also will manipulate and seek to influence your reports to their liking, or tailored to the end-user. finally, they may simply not issue your reports to the stakeholders.<\/p>\n

for the first part, it\u2019s your integrity on the line when you become aware of a discrepancy. you have to do what you feel is right, and let the reporter know. insofar as the latter, there is nothing the scheduler can do to force the issue with stakeholders, or even induce him to publish your schedule, as he should.<\/p>\n

6. miscomprehension<\/h3>\n

construction management team members who are ignorant of cpm<\/a> can be detrimental to the process when they prove to be unwilling students – too proud to learn. they also lack technical and analytical insight. for example, as a project goes south, the schedule may be referred to as being \u201cuseless, obsolete,\u201d or worse, as if the integrity of the schedule was contingent on its timeliness.<\/p>\n

again, you have to educate your audience as to the difference between projected progress, and actual progress, and how tha information is disseminated into a schedule update.<\/p>\n

7. lack of intended purpose<\/h3>\n

many contractors think of the schedule has an unnecessary project requirement. a such, they plan only to go through the motions, giving the minimal effort, and making you work harder.<\/p>\n

remind the contractor that maintaining the schedule is like keeping any asset that improves in value, in proportion to its integrity, and that in the event that a disruption claim is considered, nothing short of a properly maintained schedule will suffice.<\/p>\n

8. ceding project control<\/h3>\n

cpm schedulers and estimators are project controllers<\/a>. no one else, regardless of what their title is. despite this fact, project managers often mistakenly try to micromanage schedule development<\/a>, instead of facilitating it. in other words, they are taking \u2018control\u2019 of the \u2018project\u2019: which should be your job. the results are often disastrous.<\/p>\n

frequent, but gentle reminders usually induce project managers to be more cpm friendly. let them know when they cross the line, or when they think outside the box, and endeavor to educate them as to best practices.<\/p>\n

9. rejection<\/h3>\n

many schedule reviewers delight in rejecting your schedule submittal. sometimes as a matter of legal posturing: i.e., they believe that in rejecting any given schedule they gain some contractual leverage by deeming the contractor non-compliant.<\/p>\n

if your schedule integrity<\/a> is intact, and you have jumped through all the hoops in the specifications, it simply isn\u2019t appropriate for a reviewer to outright reject a schedule based on menial technicalities, or demand a recovery schedule, when there are compensable delays.<\/p>\n

if this is the pattern, you have to realize that the reviewer is sandbagging for your disruption claim. it may even be to your detrimen<\/span>t to issue a recovery schedule or pre-emptive claim schedule – tipping your hand. indeed, it may be better to discontinue publishing updates – protecting your client. that\u2019s right: i said \u201cstop publishing updates\u201d: or rather, you issue them to your contractor, and he withholds them from a contentious reviewer until such time as an impartial reviewer can be installed.<\/p>\n

10. willful negligence<\/h3>\n

you can lead a horse to water<\/em> \u2026 a contractor may have no intention of maintaining the schedule from the get-go. this condition is one that the scheduler can do little to change, other than be persuasive in the best way he thinks he can without ostracizing his client. besides, perhaps no one at the executive level will object to the absence of schedule updates and reports, as they don\u2019t seem to understand, or review them in a timely manner.<\/p>\n

 <\/p>\n

 <\/p>\n

\"learn<\/a><\/span>