How to document Schedule Delays (Under Construction)

Owned by Sean Connaghan (ITD)
Last updated: Mar 01, 2018
2 min read

Problem

How to properly document delays in the schedule due to vendor performance/availability/communication 

Solution

Baseline duration should be an expectation based on the vendor and the house type.  This is customizable on the template level so you do not need to come up with a one size fits all.

Once a schedule is created the task should represent when you are expecting the vendor to show up and when they should be 100% complete.


If the vendor is delayed you will do one the following:

  • If the vendor DOES NOT communicate that they cannot hit the date = Issue = No Show
  • If the vendor DOES communicate that they cannot hit the date = Issue = Vendor availability


Task is always moved to when the vendor actually shows up, when that happens the issue is closed capturing the amount of time lost. (this is often overlooked)

Once the vendor shows up the clock starts and does not stop until they are finished.  That should be the actual duration of the task.  A PJM is able to close a task and open an issue for punch list items (PJM discretion).

 Doing it this way gives you the following information.

  • No show issue with an age of 3 day = Vendor did not communicate with PJM and 3 days were lost
  • Baseline duration of 2 and an actual duration of 4 = Vendor took 4 days to perform their work, it it should have only taken 2, PJM lost 2 days.


In summary this vendor cost the PJM 4 days on this specific house.

Important things to know
  1. Durations should be monitored on key phases/tasks
  2. Divisions have the ability to use SchedulePro DART tables to create custom reports