any project controls professional knows that during the course of a project multiple versions of a project schedule will be created. schedules are often created at different levels. it usually takes a few iterations to get to an agree-upon baseline. then there are progress schedules, scenario schedules, mitigation schedules, and perhaps even a recovery schedule. but what about ghost schedules? there might even be a ghost schedule.
what is a ghost schedule?
ghost schedules are essentially versions of a schedule that are not shared with the entire team. you could say they are kept in secret.
in a 2015 report by navigant consulting, the authors reveal that ghost schedules are most often produced in order to view the timeline of a project in terms of an earlier target finish date. then the ghost schedule can be used to influence the project participants to back the new timeline or to influence other key project decisions. it can often be the case that a scenario schedule, a schedule built to explore a hypothesis or to demonstrate other possible timelines, becomes a ghost schedule when it continues to be maintained and progressed concurrently with the progress schedule.
you might have heard ghost schedules by some of their other names: concurrent schedule, shadow schedule or alternate schedule.
since ghost schedules are used in the background, they can be controversial. a ghost schedule is clearly not the contract schedule. it can be maintained by the owner, or by the contractor or even by a subcontractor. although a ghost schedule can used for analysis and decision-making, it’s not a document that is shared with the entire project team, making it’s use a bit of a slippery slope. however, it seems generally accepted that ghost schedules exist on a large majority of projects.
what are some common situations that lead to the creation of a ghost schedule?
referring back to navigant’s report, there are many situations that lead to the spawning of a ghost schedule. here’s a synopsis of some of the more common reasons broken down by the user of the ghost schedule. these are high-level summaries and for more on each situation, i would refer you back to navigant’s report which has more detail.
contractor ghost schedules
- owner refuses to approve early completion schedule set forth by the contractor. thus, the contractor creates a ghost schedule to track and target and early complete date.
- owner & contractor disagree on the execution of, or updates to the contract schedule. as a result, the contractor maintains an independent schedule, while updating the contract schedule to the owner’s requirements.
- the contractor is attempting to finish earlier than the contract schedule in order receive early completion benefits, but does not inform the owner. the contractor in this case will maintain an early completion ghost schedule throughout the life of the project.
owner ghost schedules
- owners become unsatisfied with the contractor’s schedule updates. they create their own ghost schedule and update it with more accurate data.
- owners decide to maintain a copy of the contract schedule independently from the contractor. here, the owner has empowered itself with a schedule that can be used to analyze project decisions and test scenarios.
what are the pros and cons of ghost schedules?
<edit sept 2, 16> maintaining both a ghost schedule and the original schedule has some major implications. first, it’s not easy. just maintaining the current schedule is usually a significant effort on its own, depending on the size of the project. so maintaining a 2nd copy is going to be a challenge, one that may lead to lots of frustration and extra effort, but a what cost? there is strong likelihood that the two schedules will eventually deviate to a significant degree, rendering the ghost schedule unusable.
then there’s the confusion factor. project controllers are already awash in data and scenario projects, and adding more may not lead to the clarity that decision-makers expect. personally, i’m not a fan of maintaining a ghost schedule.
on the other hand, we know that ghost schedules are out there, and that there are many situations in which an alternate schedule is created and maintained independently during a project. a schedule is really a collection of data, or a dataset in it terms. in today’s big data world, using a dataset to evaluate or forecast scenarios or other outcomes empowers the user. it becomes a tool for decision-making. it’s easy to copy data and we do it all the time. but what we have to keep in mind is that the originating dataset is bound by a legal contract and an understanding by the team.
if used at all, ghost schedules should be used as a tool to help facilitate a mutually beneficial outcome for the project, not as a tool that promotes secrecy and obstructs open communication between owners, contractors, subcontractors and other stakeholders.
what are your thoughts on the use of ghost schedules?
