Probity Event Notice Sample Clauses

Probity Event Notice. (a) The Assessor must give notice to TfNSW as soon as it becomes aware that a Probity Event has occurred or is likely to occur (Probity Event Notice); and
AutoNDA by SimpleDocs
Probity Event Notice. (a) Provider must notify RMS as soon as it becomes aware that a Probity Event has occurred or is likely to occur; and
Probity Event Notice. (a) Provider must notify TfNSW as soon as it becomes aware that a Probity Event has occurred or is likely to occur; and

Related to Probity Event Notice

  • Default Notice As soon as possible and in any event within two days after the occurrence of each Default or any event, development or occurrence reasonably likely to have a Material Adverse Effect continuing on the date of such statement, a statement of the chief financial officer of the Borrower setting forth details of such Default and the action that the Borrower has taken and proposes to take with respect thereto.

  • SUSPENSION & TERMINATION FOR DEFAULT Enterprise Services may suspend Contractor’s operations under this Master Contract immediately by written cure notice of any default. Suspension shall continue until the default is remedied to Enterprise Services’ reasonable satisfaction; Provided, however, that, if after thirty (30) days from such a suspension notice, Contractor remains in default, Enterprise Services may terminate Contractor’s rights under this Master Contract. All of Contractor’s obligations to Enterprise Services and Purchasers survive termination of Contractor’s rights under this Master Contract, until such obligations have been fulfilled.

  • Dissolution Event If there is a Dissolution Event before the termination of this Safe, the Investor will automatically be entitled (subject to the liquidation priority set forth in Section 1(d) below) to receive a portion of Proceeds equal to the Cash-Out Amount, due and payable to the Investor immediately prior to the consummation of the Dissolution Event.

  • Extraordinary Event Registry Operator will use commercially reasonable efforts to restore the critical functions of the registry within twenty-­‐four (24) hours after the termination of an extraordinary event beyond the control of the Registry Operator and restore full system functionality within a maximum of forty-­‐eight (48) hours following such event, depending on the type of critical function involved. Outages due to such an event will not be considered a lack of service availability.

  • Contract Renegotiation, Suspension, or Termination Due to Change in Funding If the funds DSHS relied upon to establish this Contract or Program Agreement are withdrawn, reduced or limited, or if additional or modified conditions are placed on such funding, after the effective date of this contract but prior to the normal completion of this Contract or Program Agreement:

  • Default Events (a) Any material breach of the Funding Agreement by the Recipient, including those set out below, will be an event of default (“Default Event”):

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