|
|
The “Written” and “Unwritten” Rules |
| |
Cost-Loaded Schedules |
| |
To Cost-Load or Not to Cost-Load
|
| |
Correlation with the Schedule of Values |
| |
Updating the Schedule vs. Approving the Payment Application |
| |
Handling Changes in Cost-Loaded Schedules |
| |
Float Games |
| |
How to play them
|
| |
How to stop them |
| |
Impacts of Changes on the Schedule |
| |
"Activity" vs. "Schedule" Impact |
| |
Clarify or Hide true Cause-Effect |
| |
Dealing with "Changes" without an "Approved Change
Order"
|
| |
One schedule or "Two"? |
| |
Handling all CO delay components |
| |
"Mitigation" of Delay |
| |
Contractor’s "responsibility" to mitigate
|
| |
Different approaches for different projects |
| |
Use and Abuse
|
| |
Tying Responsibilities to the Schedule |
| |
The Schedule as Documentation |
| |
The Job Meeting Agenda |
| |
Correlating the Complete Project Record |
| |
Dealing with Delay Claims |
| |
Supported and Unsupported Delay "Analysis" |
| |
Presenting Delay Impacts |
| |
Reviewing and Evaluating Delay Impacts |
| |
Negotiating and Resolving Time Impacts
|
| |
"Understandings": Conditions for Approval |
| |
Strategic Schedules in Litigation and Arbitration |
| |
Simplified Cause-Effect Demonstration |
| |
Six Requirements for Presentable Evidence |