Common use of Schedule Narrative Clause in Contracts

Schedule Narrative. ‌ 27 At each Project Schedule Submittal, Developer shall prepare and submit a stand-alone 28 Schedule Narrative with sufficient detail to explain the basis of the submitted Project Schedule 29 to ADOT. The Schedule Narrative must describe the activities, including how the activities 30 interrelate. Developer shall ensure that the Schedule Narrative includes the following 31 information: 32 A. A list of the activities on each Critical Path and a comparison of early dates and late 33 dates for activities designating times; 34 B. For the Project Schedule Submittals, include (a) Developer’s site management plan 35 (e.g., lay down, staging, traffic, and parking), (b) the use of construction equipment and 36 resources, (c) basis and assumptions for critical activity durations and logic, (d) 37 compliance with winter weather requirements, (e) any shifts, non-Business Days, and 38 multiple calendars applied to the activities, (f) the construction philosophy supporting the 39 approach to the Work outlined in the submitted Project Schedule, and (g) the reasons for 40 the sequencing of Work, including a description of any limited resources, potential 41 conflicts, and other salient items that may affect the schedule and how they may be 42 resolved; 43 C. For all subsequent schedule Submittals, the Schedule Narrative must recap progress 44 and days gained or lost versus the previous Progress Schedule, problems and delays 1 that have been experienced to date, the party responsible for the problems or delays, 2 and Developer’s plan to resolve the problems or bring the delayed activities back on 3 schedule, potential problems that may be encountered during the next period and the 4 proposed solutions (identify all potential problems and explain what action ADOT needs 5 to take and the date by which the action needs to be taken to avoid the problem), 6 describe changes in resources to be used on remaining Work and identify delays, their 7 extent, and causes. Each Schedule Narrative must also itemize changes in activities and 8 logic ties caused by each Supplemental Agreement, schedule recovery plans and 9 grouping of related Developer-initiated revisions; 10 D. The justification for any activity with a duration exceeding 20 Business Days; 11 E. The justification for any constraints used; 12 F. Developer’s approach used to apply relationships between activities, including a list of 13 activity relationships with lags and the justification for the use of each lag (e.g., all ties 14 are based on physical relationships between Work activities [such as “rebar must be 15 placed before concrete is placed”] or relationships are used to show limited resources 16 [such as “bridge two follows bridge one” because Developer has only one bridge crew]); 17 and 18 G. Challenges that may arise associated with Critical Path activities.

Schedule Narrative. ‌ 27 21 At each Project Schedule Submittal, Developer shall prepare and submit a stand-alone 28 22 Schedule Narrative with sufficient detail to explain the basis of the submitted Project Schedule 29 23 to ADOT. The Schedule Narrative must describe the activities, including how the activities 30 24 interrelate. Developer shall ensure that the Schedule Narrative includes the following 31 25 information: 32 26 A. A list of the activities on each Critical Path and a comparison of early dates and late 33 27 dates for activities designating contract times; 34 28 B. For the Project Schedule Submittals, include (a) Developer’s site management plan 35 29 (e.g., lay down, staging, traffic, and parking), (b) the use of construction equipment and 36 30 resources, (c) basis and assumptions for critical activity durations and logic, (d) 37 31 compliance with winter weather requirements, (e) any shifts, non-Business Days, and 38 32 multiple calendars applied to the activities, (f) the construction philosophy supporting the 39 33 approach to the Work outlined in the submitted Project Schedule, and (g) the reasons for 40 34 the sequencing of Work, including a description of Work and describe any limited resources, potential 41 conflicts, and other 35 salient items that may affect the schedule and how they may be 42 resolved; 43 36 C. For all subsequent schedule Submittals, the Schedule Narrative must recap progress 44 37 and days gained or lost versus the previous Progress Schedule, problems and delays 1 38 that have been experienced to date, the party responsible for the problems or delays, 2 39 and Developer’s plan to resolve the problems or bring the delayed activities back on 3 40 schedule, potential problems that may be encountered during the next period and the 4 41 proposed solutions (identify all potential problems and explain what action ADOT needs 5 42 to take and the date by which the action needs to be taken to avoid the problem), 6 43 describe changes in resources to be used on remaining Work and identify delays, their 7 44 extent, and causes. Each Schedule Narrative must also itemize changes in activities and 8 45 logic ties caused by each Supplemental Agreement, schedule recovery plans and 9 46 grouping of related Developer-initiated revisions; 10 1 D. The justification for any activity with a duration exceeding 20 Business Days; 11 2 E. The justification for any constraints used; 12 3 F. Developer’s approach used to apply relationships between activities, including a list of 13 4 activity relationships with lags and the justification for the use of each lag (e.g., all ties 14 5 are based on physical relationships between Work activities [such as “rebar must be 15 6 placed before concrete is placed”] or relationships are used to show limited resources 16 7 [such as “bridge two follows bridge one” because Developer has only one bridge crew]); 17 and 18 8 G. Challenges that may arise associated with Critical Path activities.

Schedule Narrative. ‌ 27 17 At each Project Schedule Submittal, Developer shall prepare and submit a stand-alone 28 18 Schedule Narrative with sufficient detail to explain the basis of the submitted Project Schedule 29 19 to ADOT. The Schedule Narrative must describe the activities, including how the activities 30 20 interrelate. Developer shall ensure that the Schedule Narrative includes the following 31 21 information: 32 22 A. A list of the activities on each Critical Path and a comparison of early dates and late 33 23 dates for activities designating times; 34 24 B. For the Project Schedule Submittals, include (a) Developer’s site management plan 35 25 (e.g., lay down, staging, traffic, and parking), (b) the use of construction equipment and 36 resources, (c) basis and assumptions for critical activity durations and logic, (d) 37 27 compliance with winter weather requirements, (e) any shifts, non-Business Days, and 38 28 multiple calendars applied to the activities, (f) the construction philosophy supporting the 39 29 approach to the Work outlined in the submitted Project Schedule, and (g) the reasons for 40 30 the sequencing of Work, including a description of any limited resources, potential 41 31 conflicts, and other salient items that may affect the schedule and how they may be 42 32 resolved; 43 33 C. For all subsequent schedule Submittals, the Schedule Narrative must recap progress 44 34 and days gained or lost versus the previous Progress Schedule, problems and delays 1 35 that have been experienced to date, the party responsible for the problems or delays, 2 36 and DeveloperXxxxxxxxx’s plan to resolve the problems or bring the delayed activities back on 3 37 schedule, potential problems that may be encountered during the next period and the 4 38 proposed solutions (identify all potential problems and explain what action ADOT needs 5 39 to take and the date by which the action needs to be taken to avoid the problem), 6 40 describe changes in resources to be used on remaining Work and identify delays, their 7 41 extent, and causes. Each Schedule Narrative must also itemize changes in activities and 8 42 logic ties caused by each Supplemental Agreement, schedule recovery plans and 9 43 grouping of related Developer-initiated revisions; 10 44 D. The justification for any activity with a duration exceeding 20 Business Days; 11 45 E. The justification for any constraints used; 12 1 F. Developer’s approach used to apply relationships between activities, including a list of 13 2 activity relationships with lags and the justification for the use of each lag (e.g., all ties 14 3 are based on physical relationships between Work activities [such as “rebar must be 15 4 placed before concrete is placed”] or relationships are used to show limited resources 16 5 [such as “bridge two follows bridge one” because Developer has only one bridge crew]); 17 6 and 18 7 G. Challenges that may arise associated with Critical Path activities.

Schedule Narrative. ‌ 27 At 20 With each Project Schedule Submittal, Developer shall prepare and submit a stand-alone 28 Schedule 21 Narrative with sufficient detail to explain the basis of the submitted Project Schedule 29 to ADOT. The 22 Schedule Narrative must shall describe the activities, including how the activities 30 interrelate. Developer shall 23 ensure that the Schedule Narrative includes the following 31 information: 32 A. : 24 A list of the activities on each Critical Path and a comparison of early dates and late 33 dates for 25 activities designating times; 34 B. For the Project Schedule Submittals, include (a) ; 26 Include Developer’s site management plan 35 (e.g., lay down, staging, traffic, and parking), (b) the use 27 of construction equipment and 36 resources, (c) basis and assumptions for critical activity durations 28 and logic, (d) 37 compliance with winter temperature and weather related requirements, (e) any shifts, non-non- 29 Business Days, and 38 multiple calendars applied to the activities, (f) the construction philosophy 30 supporting the 39 approach to the Work outlined in the submitted Project Schedule, and (g) the reasons 31 for 40 the sequencing of Work, including a description of any limited resources, potential 41 conflicts, 32 and other salient items that may affect the schedule and how they may be 42 resolved; 43 C. For all subsequent schedule Submittals, the Schedule Narrative must recap ; 33 Recap progress 44 and days gained or lost versus the previous Progress Schedule, ; identify 34 problems and delays 1 that have been experienced to date, the party responsible for the problems 35 or delays, 2 delays and Developer’s plan to resolve the problems or bring the delayed activities back on 3 36 schedule, ; describe potential problems that may be encountered during the next period and the 4 37 proposed solutions (identify all potential problems and explain what action Developer feels 1 ADOT needs 5 to take and the date by which the action needs to be taken to avoid the problem), 6 ; 2 describe changes in resources to be used on remaining Work Work; and identify delays, their 7 extent, 3 and causes. Each Schedule Narrative must shall also itemize changes in activities and 8 logic ties 4 caused by each Supplemental Agreement, schedule recovery plans and 9 grouping of related Developer-5 Developer initiated revisions; 10 D. ; 6 The justification for any activity with a duration exceeding 20 Business Days; 11 E. The justification for any constraints used; 12 F. Developer’s approach used to apply relationships between activities, including a list of 13 activity relationships with lags and the justification for the use of each lag (e.g., all ties 14 are based on physical relationships between Work activities [such as “rebar must be 15 placed before concrete is placed”] or relationships are used to show limited resources 16 [such as “bridge two follows bridge one” because Developer has only one bridge crew]); 17 and 18 G. Challenges that may arise associated with Critical Path activities.

Schedule Narrative. ‌ 27 At each Project Schedule Submittal, Developer shall prepare and submit a stand-alone 28 Schedule Narrative with sufficient detail to explain the basis of the submitted Project Schedule 29 to ADOT. The Schedule Narrative must describe the activities, including how the activities 30 interrelate. Developer shall ensure that the Schedule Narrative includes the following 31 information:‌ 32 20 A. A list of the activities on each Critical Path and a comparison of early dates and late 33 21 dates for activities designating contract times; 34 22 B. For the Project Schedule Submittals, include (a) Developer’s site management plan 35 23 (e.g., lay down, staging, traffic, and parking), (b) the use of construction equipment and 36 resources, (c) basis and assumptions for critical activity durations and logic, (d) 37 25 compliance with winter weather requirements, (e) any shifts, non-Business Days, and 38 26 multiple calendars applied to the activities, (f) the construction philosophy supporting the 39 27 approach to the Work outlined in the submitted Project Schedule, and (g) the reasons for 40 28 the sequencing of WorkWork and describe, including a description of any limited resources, 29 potential 41 conflicts, and other salient items that may affect the schedule and how they 30 may be 42 resolved; 43 31 C. For all subsequent schedule Submittals, the Schedule Narrative must recap progress 44 32 and days gained or lost versus the previous Progress Schedule, problems and delays 1 33 that have been experienced to date, the party responsible for the problems or delays, 2 34 and Developer’s plan to resolve the problems or bring the delayed activities back on 3 35 schedule, potential problems that may be encountered during the next period and the 4 36 proposed solutions (identify all potential problems and explain what action ADOT needs 5 37 to take and the date by which the action needs to be taken to avoid the problem), 6 38 describe changes in resources to be used on remaining Work and identify delays, their 7 39 extent, and causes. Each Schedule Narrative must also itemize changes in activities and 8 40 logic ties caused by each Supplemental Agreement, schedule recovery plans and 9 41 grouping of related Developer-initiated revisions; 10 42 D. The justification for any activity with a duration exceeding 20 Business Days; 11 43 E. The justification for any constraints used; 12 44 F. Developer’s approach used to apply relationships between activities, including a list of 13 45 activity relationships with lags and the justification for the use of each lag (e.g., all ties 14 1 are based on physical relationships between Work activities [such as “rebar must be 15 2 placed before concrete is placed”] or relationships are used to show limited resources 16 3 [such as “bridge two follows bridge one” because Developer has only one bridge crew]); 17 and 18 4 G. Challenges that may arise associated with Critical Path activities.