Milestones Clause Samples
The Milestones clause defines specific project deliverables or stages that must be completed by certain deadlines during the course of an agreement. It typically outlines what constitutes each milestone, the criteria for completion, and any associated payments or obligations triggered by reaching these points. This clause ensures that both parties have a clear, shared understanding of progress expectations and helps manage project timelines by breaking the work into manageable, trackable segments.
POPULAR SAMPLE Copied 197 times
Milestones. Subject to the provisions of the SGIP, the Parties shall agree on milestones for which each Party is responsible and list them in Attachment 4 of this Agreement. A Party’s obligations under this provision may be extended by agreement. If a Party anticipates that it will be unable to meet a milestone for any reason other than a Force Majeure event, it shall immediately notify the other Parties of the reason(s) for not meeting the milestone and: (1) propose the earliest reasonable alternate date by which it can attain this and future milestones, and (2) requesting appropriate amendments to Attachment 4. The Party affected by the failure to meet a milestone shall not unreasonably withhold agreement to such an amendment unless: (1) it will suffer significant uncompensated economic or operational harm from the delay, (2) attainment of the same milestone has previously been delayed, or (3) it has reason to believe that the delay in meeting the milestone is intentional or unwarranted notwithstanding the circumstances explained by the Party proposing the amendment.
Milestones. Pursuant to the M-MIP Fast Track Process Section 9.1 and the Study Process Section 11.1, the Parties shall agree on milestones for which each Party is responsible and list them in Attachment 4 of this Agreement.
Milestones. 3.3.1. The NYISO shall provide the Developer with the Required Project In-Service Date that is set forth in the Public Policy Transmission Planning Report in accordance with Section 31.4.11 of Attachment Y of the OATT. Prior to executing and/or filing this Agreement with FERC, the NYISO and the Developer shall agree to the Critical Path Milestones and Advisory Milestones set forth in the Development Schedule in Appendix C to this Agreement for the development, construction, and operation of the Transmission Project by the Required Project In-Service Date in accordance with Section 31.4.12.2 of Attachment Y of the OATT; provided that any such milestone for the Transmission Project that requires action by a Connecting Transmission Owner or Affected System Operator to complete must be included as an Advisory Milestone.
3.3.2. The Developer shall meet the Critical Path Milestones in accordance with the Development Schedule set forth in Appendix C to this Agreement. The Developer’s inability or failure to meet a Critical Path Milestone specified in the Development Schedule, as such Critical Path Milestone may be amended with the agreement of the NYISO under this Article 3.3, shall constitute a Breach of this Agreement under Article 7.1.
3.3.3. The Developer shall notify the NYISO thirty (30) Calendar Days prior to the date of each Critical Path Milestone specified in the Development Schedule whether, to the best of its knowledge, it expects to meet the Critical Path Milestone by the specified date; provided, however, that notwithstanding this requirement:
(i) the Developer shall notify the NYISO as soon as reasonably practicable, and no later than fifteen (15) Calendar Days, following the Developer’s discovery of a potential delay in meeting a Critical Path Milestone, including a delay caused by a Force Majeure event; and
(ii) the NYISO may request in writing at any time, and the Developer shall submit to the NYISO within five (5) Business Days of the request, a written response indicating whether the Developer will meet, or has met, a Critical Path Milestone and providing all required supporting documentation for its response.
3.3.4. The Developer shall not make a change to a Critical Path Milestone without the prior written consent of the NYISO. To request a change to a Critical Path Milestone, the Developer must: (i) inform the NYISO in writing of the proposed change to the Critical Path Milestone and the reason for the change, including the occurrence of a ...
Milestones. In this section, please include information on each Milestone listed in the Cover Sheet, plus any additional significant milestones related to the project. Please state the status and progress of each Milestone. Provide the date of completion of completed Milestone(s) and the expected date of completion of uncompleted Milestone(s). The expected date is the current best estimate, and may change from time to time as better information becomes available. Please describe in detail any delays (actual or anticipated) beyond the scheduled Milestone dates. Describe the cause of the delay (e.g., governmental approvals, financing, property acquisition, design activities, equipment procurement, project construction, interconnection, or any other factor). Describe Seller’s Remedial Action Plan which shall include detailed plans to achieve the missed Milestone and subsequent Milestones.
Milestones. Because the invention is not yet commercially viable as of the Effective Date, ***** will diligently develop, manufacture, and sell Licensed Product and will diligently develop markets for Licensed Product. In addition, ***** will meet the milestones shown in Appendix A, and notify Stanford in writing as each milestone is met.
Milestones. Each Credit Party shall ensure the satisfaction of the following milestones (collectively, the “Milestones” and each a “Milestone”), unless waived or extended with the consent of the Required Lenders (which written consent may be provided via email, including by counsel to the Lenders):
(a) no later than one (1) calendar day after the Petition Date, the Debtors shall file a motion, in form and substance reasonably acceptable to the Required Lenders, seeking approval on an interim and final basis of the DIP Facility and the Adequate Protection (as defined in the Interim DIP Order);
(b) no later than three (3) calendar days after the Petition Date (or, to the extent such calendar day is not a Business Day, the next Business Day thereafter), the Debtors shall file a motion, in form and substance acceptable to the Required Lenders, seeking approval of bid procedures in respect of an Acceptable Sale Transaction for all or substantially all of the Debtors’ assets that shall include, among other things, notice and consent rights in favor of the Lenders for Asset Sales and going concern sales (the “Bidding Procedures Motion”);
(c) no later than five (5) calendar days after the Petition Date, the Bankruptcy Court shall enter the Interim Order;
(d) no later fifteen (15) calendar days following the Petition Date, the Debtors shall have filed an Acceptable Plan of Reorganization, an Acceptable Disclosure Statement and a motion to approve the Acceptable Disclosure Statement in form and substance acceptable to the Required Lenders;
(e) no later than twenty-five (25) calendar days following the filing of the Bidding Procedures Motion, the Bankruptcy Court shall enter an order approving the Bidding Procedures Motion in form and substance acceptable to the Required Lenders (the “Bidding Procedures Order”);
(f) no later than thirty (30) calendar days after the Petition Date, the Bankruptcy Court shall enter the Final Order;
(g) no later than thirty (30) calendar days following the Petition Date, the deadline for submission of non-binding indications of interest for some, all, or substantially all of the Debtors’ assets shall have occurred pursuant to the Bidding Procedures Order;
(h) no later than forty (40) calendar days following the Petition Date, the deadline for submission of binding bids for some, all, or substantially all of the Debtors’ assets shall have occurred pursuant to the Bidding Procedures Order;
(i) no later than forty-five (45) calendar days following the ...
Milestones. The Parties shall agree on milestones for which each Party is responsible and list them in Attachment 4 of this Agreement. A Party's obligations under this provision may be extended by agreement. If a Party anticipates that it will be unable to meet a milestone for any reason other than a Uncontrollable Force Event, it shall immediately notify the other Party of the reason(s) for not meeting the milestone and (1) propose the earliest reasonable alternate date by which it can attain this and future milestones, and (2) requesting appropriate amendments to Attachment 4. The Party affected by the failure to meet a milestone shall not unreasonably withhold agreement to such an amendment unless it will suffer significant uncompensated economic or operational harm from the delay, (2) attainment of the same milestone has previously been delayed, or (3) it has reason to believe that the delay in meeting the milestone is intentional or unwarranted notwithstanding the circumstances explained by the Party proposing the amendment.
Milestones. The parties agree:
Milestones. Financial Security Arrangements
Milestones. In-Service Date: Critical milestones and responsibility as agreed to by the Parties:
