Common use of Monthly Schedule Updates Clause in Contracts

Monthly Schedule Updates. On the 15th day of each month, the Contractor shall submit a Monthly Schedule Update using the same software used to prepare the Baseline Schedule. The Engineer will not submit the Engineer’s Monthly Estimate specified in 7-3.2 for processing until the Monthly Schedule Update has been submitted. The schedule may be emailed to the Engineer or submitted on a CD with 2 printed color copies on 11-inch x 17-inch sheets. Should the update not reflect the actual progress of the Work, the update will be returned to the Contractor for inclusion of the changes on the next update. Updates shall conform to 6-1.1.2 and the following: 1) Actual start and completion dates versus the original accepted Baseline Schedule shall be illustrated. 2) Deviations in the progress and sequence of the Work shall be identified and supported by a detailed narrative justification. The updates shall include necessary remedies and revisions to recover delays to the schedule to meet the original Contract milestones. 3) The data date shall be the 15th day of each month. 4) Change Order work scheduled after the Data Date that includes an approved time extension shall be shown as a Critical Path activity. Change Order work scheduled after the Data Date without an approved time extension shall be shown as a non- Critical Path activity. Change Order work performed prior to the Data Date shall be shown as an as-built activity. 5) The Required Completion Date milestone constraint date shall be adjusted to account for time extensions approved as of the Data Date. 6) The Scheduled Completion Date milestone constraint date shall be adjusted to match the Required Completion Date as of the Data Date. 7) Schedule updates shall only include changes related to a Time Impact Analysis (TIA) that has been accepted by the Engineer. Schedule updates shall not include changes related to a rejected TIA, or a TIA that is pending.

Monthly Schedule Updates. On the 15th 1st day of each month, the Contractor shall submit a Monthly Schedule Update using the same software used to prepare the Baseline Schedule. The Engineer will not submit the Engineer’s Monthly Estimate specified in 7-3.2 for processing until the Monthly Schedule Update has been submitted. The schedule may be emailed to the Engineer or submitted on a CD with 2 printed color copies on 11-inch x 17-inch sheets. Should the update not reflect the actual progress of the Work, the update will be returned to the Contractor for inclusion of the changes on the next update. Updates shall conform to 6-1.1.2 and the following: 1) Actual start and completion dates versus the original accepted Baseline Schedule shall be illustrated. 2) Deviations in the progress and sequence of the Work shall be identified and supported by a detailed narrative justification. The updates shall include necessary remedies and revisions to recover delays to the schedule to meet the original Contract milestones. 3) The data date shall be the 15th 1st day of each month. 4) Change Order work scheduled after the Data Date that includes an approved time extension shall be shown as a Critical Path activity. Change Order work scheduled after the Data Date without an approved time extension shall be shown as a non- Critical Path activity. Change Order work performed prior to the Data Date shall be shown as an as-built activity. 5) The Required Completion Date milestone constraint date shall be adjusted to account for time extensions approved as of the Data Date. 6) The Scheduled Completion Date milestone constraint date shall be adjusted to match the Required Completion Date as of the Data Date. 7) Schedule updates shall only include changes related to a Time Impact Analysis (TIA) that has been accepted by the Engineer. Schedule updates shall not include changes related to a rejected TIA, or a TIA that is pending.