Common use of Recovery Schedule Clause in Contracts

Recovery Schedule. ‌ 37 Unless otherwise directed in writing by ADOT, if ADOT’s review of the Monthly Progress 38 Schedule indicates a late completion of the Work, or should Critical Path items shown on the 39 Monthly Progress Schedule Submittal slip by 28 or more days beyond any milestone, Developer 40 shall prepare a Recovery Schedule which displays how Developer intends to reschedule those 41 activities to regain compliance with the milestones and the Agreement. Whenever a Recovery 42 Schedule is required, Developer shall provide the following information:

Appears in 3 contracts

Samples: apps.azdot.gov, apps.azdot.gov, apps.azdot.gov

AutoNDA by SimpleDocs

Recovery Schedule. 37 20 Unless otherwise directed in writing by ADOT, if ADOT’s review of the Monthly Progress 38 Schedule indicates a late completion of the Work, or should Critical Path items shown on the 39 22 Monthly Progress Schedule Submittal slip by 28 or more days beyond any milestone, Developer 40 23 shall prepare a Recovery Schedule which displays how Developer intends to reschedule those 41 24 activities to regain compliance with the milestones and the Agreement. Whenever a Recovery 42 25 Schedule is required, Developer shall provide the following information:

Appears in 3 contracts

Samples: apps.azdot.gov, apps.azdot.gov, apps.azdot.gov

Recovery Schedule. ‌ 37 22 Unless otherwise directed in writing by ADOT, if ADOT’s review of the Monthly Progress 38 Schedule indicates a late 23 completion of the Work, Work or should if Critical Path items shown on the 39 Monthly Progress Schedule Submittal slip 24 by 28 or more days Days beyond any milestone, Developer 40 shall prepare a Recovery Schedule which displays 25 demonstrates how Developer intends to reschedule those 41 activities to regain compliance with the 26 milestones and the AgreementContract Documents. Whenever a Recovery 42 Schedule is required, Developer shall 27 provide the following information:: 28 Transmittal letter;

Appears in 1 contract

Samples: apps.azdot.gov

Recovery Schedule. 37 25 Unless otherwise directed in writing by ADOT, if ADOT’s review of the Monthly Progress 38 Schedule indicates a late completion of the Work, or should Critical Path items shown on the 39 27 Monthly Progress Schedule Submittal slip by 28 or more days beyond any milestone, Developer 40 28 shall prepare a Recovery Schedule which displays how Developer intends to reschedule those 41 activities 29 activities, to regain compliance with the milestones and the Agreement. Whenever a Recovery 42 30 Schedule is required, Developer shall provide the following information:: 31 A. Transmittal letter 32 B. Time-scaled network diagram

Appears in 1 contract

Samples: apps.azdot.gov

Recovery Schedule. 37 22 Unless otherwise directed in writing by ADOT, if ADOT’s review of the Monthly Progress 38 Schedule indicates a late completion of the Work, or should Critical Path items shown on the 39 24 Monthly Progress Schedule Submittal slip by 28 or more days beyond any milestone, Developer 40 25 shall prepare a Recovery Schedule which displays how Developer intends to reschedule those 41 activities 26 activities, to regain compliance with the milestones and the Agreement. Whenever a Recovery 42 27 Schedule is required, Developer shall provide the following information:

Appears in 1 contract

Samples: apps.azdot.gov

AutoNDA by SimpleDocs

Recovery Schedule. 37 26 Unless otherwise directed in writing by ADOT, if ADOT’s review of the Monthly Progress 38 Schedule indicates a late completion of the Work, or should Critical Path items shown on the 39 28 Monthly Progress Schedule Submittal slip by 28 or more days beyond any milestone, Developer 40 29 shall prepare a Recovery Schedule which displays how Developer intends to reschedule those 41 30 activities to regain compliance with the milestones and the Agreement. Whenever a Recovery 42 31 Schedule is required, Developer shall provide the following information:

Appears in 1 contract

Samples: apps.azdot.gov

Recovery Schedule. 37 25 Unless otherwise directed in writing by ADOT, if ADOT’s review of the Monthly Progress 38 Schedule indicates a late completion of the Work, or should Critical Path items shown on the 39 27 Monthly Progress Schedule Submittal slip by 28 or more days beyond any milestone, Developer 40 28 shall prepare a Recovery Schedule which displays how Developer intends to reschedule those 41 29 activities to regain compliance with the milestones and the Agreement. Whenever a Recovery 42 30 Schedule is required, Developer shall provide the following information:

Appears in 1 contract

Samples: apps.azdot.gov

Time is Money Join Law Insider Premium to draft better contracts faster.