Notification by Contractor Sample Clauses

Notification by Contractor. Contractor shall notify LCOG in writing as soon as Contractor knows, or should reasonably know, that a force majeure event (as defined in the Contract Documents) has occurred that will delay completion of the Scope of Work. Said notification shall include reasonable proofs required by LCOG to evaluate any Contractor request for relief under the Contract Documents. LCOG shall examine Contractor's notification and determine if the Contractor is entitled to relief. LCOG shall notify the Contractor of its decision in writing. LCOG's decision regarding whether or not the Contractor is entitled to force majeure relief shall be final and binding on the parties.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
Notification by Contractor. The Contractor shall notify the Architect/Contract Administrator of the occurrence of any of the events referred to in such of the following provisions as are applicable for the purposes of this Contract:
Sample 1Sample 2Sample 3
Notification by Contractor. A. Notify the OAR of: 1. Need for testing. 2. Intent to work outside regular working hours. 3. Request to shut down facilities or utilities. 4. Proposed utility connections. 5. Required observation by OAR, Designer, or inspection agencies prior to covering Work.
Sample 1Sample 2
Notification by Contractor. Contractor shall notify LTD in writing as soon as Contractor knows, or should reasonably know, that a force majeure event (as defined in the Contract Documents) has occurred that will delay completion of the Scope of Work. Said notification shall include reasonable proofs required by LTD to evaluate any Contractor request for relief under the Contract Documents. LTD shall examine Contractor's notification and determine if the Contractor is entitled to relief. LTD shall notify the Contractor of its decision in writing. LTD's decision regarding whether or not the Contractor is entitled to force majeure relief shall be final and binding on the Parties.
Sample 1Sample 2
Notification by Contractor. B·5 ·1 The Contractor shall notify the Architect/Contract Administrator of the occurrence of any of the events referred to in such of the following provisions as are applicable for the purposes of this Contract: ·1 paragraph B·1·2; ·2 paragraph B·1·6; ·3 paragraph B·2·2; ·4 paragraph B·2·5; ·5 paragraph B·3·2; ·6 paragraph B·4·2.
Sample 1
Notification by Contractor. Contractor shall notify SAMTD in writing as soon as Contractor knows, or should reasonably know, that a force majeure event (as defined in the Contract Documents) has occurred that will delay completion of the Scope of Work. Said notification shall include reasonable proofs required by SAMTD to evaluate any Contractor request for relief under the Contract Documents. SAMTD shall examine Contractor's notification and determine if the Contractor is entitled to relief. SAMTD shall notify the Contractor of its decision in writing. SAMTD's decision regarding whether or not the Contractor is entitled to force majeure relief shall be final and binding on the parties.
Sample 1
Notification by Contractor. Contractor shall provide prompt notification to Facility if it cannot provide rehabilitation services or Therapists in a timely fashion so that the Facility can arrange alternate sources for these services.
Sample 1
AutoNDA by SimpleDocs
Notification by Contractor. The Administrator is not required to pay reimbursement to a Contractor under this section for qualified M&R, unless the Contractor— (i) Notifies the Administrator of the intent of the Contractor to obtain the qualified M&R, by not later than 90 days before the date of the performance of the qualified M&R; and (ii) Includes in such notification: (A) A description of all qualified M&R that the Contractor should reasonably expect may be performed; (B) A description of the vessel’s normal route and port calls in the United States; (C) An estimate of the cost, with supporting documentation, of obtaining the qualified M&R described under paragraph (h)(1)(ii)(A) of this section in the United States; and (D) An estimate of the cost, with supporting documentation, of obtaining the qualified M&R described under paragraph (h)(1)(ii)(A) of this section outside the United States, in the country in which the Contractor otherwise would undertake the qualified M&R.
Sample 1

Related to Notification by Contractor

  • Termination by Contractor Contractor may, at its option, terminate this Contract upon the failure of MPS to pay any amount, which may become due hereunder for a period of sixty (60) days following submission of appropriate billing and supporting documentation. Upon said termination, Contractor shall be paid the compensation due for all services rendered through the date of termination including any retainage.

  • Termination by ICANN (a) ICANN may, upon notice to Registry Operator, terminate this Agreement if: (i) Registry Operator fails to cure (A) any fundamental and material breach of Registry Operator’s representations and warranties set forth in Article 1 or covenants set forth in Article 2, or (B) any breach of Registry Operator’s payment obligations set forth in Article 6 of this Agreement, each within thirty (30) calendar days after ICANN gives Registry Operator notice of such breach, which notice will include with specificity the details of the alleged breach, (ii) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator is in fundamental and material breach of such covenant(s) or in breach of its payment obligations, and (iii) Registry Operator fails to comply with such determination and cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction. (b) ICANN may, upon notice to Registry Operator, terminate this Agreement if Registry Operator fails to complete all testing and procedures (identified by ICANN in writing to Registry Operator prior to the date hereof) for delegation of the TLD into the root zone within twelve (12) months of the Effective Date. Registry Operator may request an extension for up to additional twelve (12) months for delegation if it can demonstrate, to ICANN’s reasonable satisfaction, that Registry Operator is working diligently and in good faith toward successfully completing the steps necessary for delegation of the TLD. Any fees paid by Registry Operator to ICANN prior to such termination date shall be retained by ICANN in full. (c) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator fails to cure a material breach of Registry Operator’s obligations set forth in Section 2.12 of this Agreement within thirty (30) calendar days of delivery of notice of such breach by ICANN, or if the Continued Operations Instrument is not in effect for greater than sixty (60) consecutive calendar days at any time following the Effective Date, (ii) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator is in material breach of such covenant, and (iii) Registry Operator fails to cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction. (d) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator makes an assignment for the benefit of creditors or similar act, (ii) attachment, garnishment or similar proceedings are commenced against Registry Operator, which proceedings are a material threat to Registry Operator’s ability to operate the registry for the TLD, and are not dismissed within sixty (60) calendar days of their commencement, (iii) a trustee, receiver, liquidator or equivalent is appointed in place of Registry Operator or maintains control over any of Registry Operator’s property, (iv) execution is levied upon any material property of Registry Operator, (v) proceedings are instituted by or against Registry Operator under any bankruptcy, insolvency, reorganization or other laws relating to the relief of debtors and such proceedings are not dismissed within sixty (60) calendar days of their commencement, or (vi) Registry Operator files for protection under the United States Bankruptcy Code, 11 U.S.C. Section 101, et seq., or a foreign equivalent or liquidates, dissolves or otherwise discontinues its operations or the operation of the TLD. (e) ICANN may, upon thirty (30) calendar days’ notice to Registry Operator, terminate this Agreement pursuant to Section 2 of Specification 7 or Sections 2 and 3 of Specification 11, subject to Registry Operator’s right to challenge such termination as set forth in the applicable procedure described therein. (f) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator knowingly employs any officer who is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such officer is not terminated within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing, or (ii) any member of Registry Operator’s board of directors or similar governing body is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such member is not removed from Registry Operator’s board of directors or similar governing body within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing. (g) ICANN may, upon thirty (30) calendar days’ notice to Registry Operator, terminate this Agreement as specified in Section 7.5. (h) [Applicable to intergovernmental organizations or governmental entities only.] ICANN may terminate this Agreement pursuant to Section 7.16.

  • TERMINATION BY MPS - BREACH BY CONTRACTOR If Contractor fails to fulfill its obligations under this Contract in a timely or proper manner, or violates any of its provisions, MPS shall thereupon have the right to terminate it by giving five (5) days written notice before the effective date of termination of the Contract, specifying the alleged violations, and effective date of termination. The Contract shall not be terminated if, upon receipt of the notice, Contractor promptly cures the alleged violation with five (5) days. In the event of termination, MPS will only be liable for services rendered through the date of termination and not for the uncompleted portion, or for any materials or services purchased or paid for by Contractor for use in completing the Contract.

  • Termination by Client Without prejudice to any rights or remedies of the Client, the Client may, by at least seven (7) days’ notice in writing to Deswik, terminate this Agreement if: (a) Deswik breaches its obligations under this Agreement and: (i) the breach is not capable of remedy; (ii) if capable of remedy, the breach is not remedied within 30 days of receipt of written notice by Deswik requiring the breach to be remedied; or (b) an Insolvency Event occurs in respect to Deswik.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!