PRESCRIBED OCCURENCES Sample Clauses

PRESCRIBED OCCURENCES. (a) No Target Prescribed Occurrence occurs between the Announcement Date and the commencement of the Bid Offer Period (inclusive).
AutoNDA by SimpleDocs

Related to PRESCRIBED OCCURENCES

  • Material Occurrences Promptly notify Agent in writing upon the occurrence of (a) any Event of Default or Default; (b) any event, development or circumstance whereby any financial statements or other reports furnished to Agent fail in any material respect to present fairly, in accordance with GAAP consistently applied, the financial condition or operating results of any Borrower as of the date of such statements; (c) any accumulated retirement plan funding deficiency which, if such deficiency continued for two plan years and was not corrected as provided in Section 4971 of the Code, could subject any Borrower to a tax imposed by Section 4971 of the Code; (d) each and every default by any Borrower which might result in the acceleration of the maturity of any Indebtedness, including the names and addresses of the holders of such Indebtedness with respect to which there is a default existing or with respect to which the maturity has been or could be accelerated, and the amount of such Indebtedness; and (e) any other development in the business or affairs of any Borrower which could reasonably be expected to have a Material Adverse Effect; in each case describing the nature thereof and the action Borrowers propose to take with respect thereto.

  • Accidents and Dangerous Occurrences The Hirer must report all accidents involving injury to the public to a member of the Village Hall management committee as soon as possible and complete the relevant section in the Village Hall’s accident book. Any failure of equipment belonging to the Village Hall or brought in by the Hirer must also be reported as soon as possible. Certain types of accident or injury must be reported on a special form to the local authority. The Hall Secretary will give assistance in completing this form. This is in accordance with the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 1995 (RIDDOR).

  • Name Collision Occurrence Management 6.1. No-­‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-­‐Activation Period ends.

  • Regulatory Approvals; No Defaults (a) No consents or approvals of, or waivers by, or filings or registrations with, any Governmental Authority are required to be made or obtained by HCBF or any of its Subsidiaries in connection with the execution, delivery or performance by HCBF of this Agreement or to consummate the transactions contemplated by this Agreement, except as may be required for (i) filings of applications and notices with, and receipt of consents, authorizations, approvals, exemptions or nonobjections from, the SEC, NASDAQ, state securities authorities, the Financial Industry Regulatory Authority, Inc., applicable securities, commodities and futures exchanges, and other industry self-regulatory organizations (each, an “SRO”), (ii) filings of applications or notices with, and consents, approvals or waivers by the FRB, the FDIC and applicable state banking agencies, the Office of the Comptroller of the Currency (the “OCC”), the Florida Office of Financial Regulation (the “FOFR”) and other banking, regulatory, self-regulatory or enforcement authorities or any courts, administrative agencies or commissions or other Governmental Authorities and approval of or non-objection to such applications, filings and notices (taken together with the items listed in clause (i), the “Regulatory Approvals”), (iii) the filing with the SEC of the Proxy Statement-Prospectus and the Registration Statement and declaration of effectiveness of the Registration Statement, (iv) the filing of the Articles of Merger and the filing of documents with the OCC, applicable Governmental Authorities, and the Secretary of State of the State of Florida to cause the Bank Merger to become effective and (v) such filings and approvals as are required to be made or obtained under the securities or “Blue Sky” laws of various states in connection with the issuance of the shares of CenterState Common Stock pursuant to this Agreement and approval of listing of such CenterState Common Stock on the NASDAQ. Subject to the receipt of the approvals referred to in the preceding sentence and the Requisite HCBF Shareholder Approval, the execution, delivery and performance of this Agreement and the consummation of the transactions contemplated hereby by HCBF do not and will not (1) constitute a breach or violation of, or a default under, the articles of incorporation, bylaws or similar governing documents of HCBF or any of its respective Subsidiaries, (2) violate any statute, code, ordinance, rule, regulation, judgment, order, writ, decree or injunction applicable to HCBF or any of its Subsidiaries, or any of their respective properties or assets, (3) conflict with, result in a breach or violation of any provision of, or the loss of any benefit under, or a default (or an event which, with or without notice or lapse of time, or both, would constitute a default) under, result in the creation of any Lien under, result in a right of termination or the acceleration of any right or obligation under any permit, license, credit agreement, indenture, loan, note, bond, mortgage, reciprocal easement agreement, lease, instrument, concession, contract, franchise, agreement or other instrument or obligation of HCBF or any of its Subsidiaries or to which HCBF or any of its Subsidiaries, or their respective properties or assets is subject or bound, or (4) require the consent or approval of any third party or Governmental Authority under any such Law, rule or regulation or any judgment, decree, order, permit, license, credit agreement, indenture, loan, note, bond, mortgage, reciprocal easement agreement, lease, instrument, concession, contract, franchise, agreement or other instrument or obligation.

  • Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include:

  • Happen After We Receive Your Letter When we receive your letter, we must do two things:

  • Happen After We Receive Your Letter When we receive your letter, we must do two things:

  • De-commissioning due to Emergency 17.6.1 If, in the reasonable opinion of the Concessionaire, there exists an Emergency which warrants de-commissioning and closure of the whole or any part of the Bus Terminal, the Concessionaire shall be entitled to de- commission and close the whole or any part of the Bus Terminal to Users and passengers for so long as such Emergency and the consequences thereof warrant; provided that such de-commissioning and particulars thereof shall be notified by the Concessionaire to the Authority without any delay, and the Concessionaire shall diligently carry out and abide by any reasonable directions that the Authority may give for dealing with such Emergency.

  • Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-­‐level domain name, or (B) block those second-­‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.

  • Reporting Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.

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