Covenant Compliance the information (including detailed calculations) required in order to establish whether the Company was in compliance with the requirements of Section 10.1 through Section 10.9, inclusive, during the quarterly or annual period covered by the statements then being furnished (including with respect to each such Section, where applicable, the calculations of the maximum or minimum amount, ratio or percentage, as the case may be, permissible under the terms of such Sections, and the calculation of the amount, ratio or percentage then in existence); and
Covenant Compliance Certificate The Borrower shall, contemporaneously with the furnishing of the financial statements pursuant to Section 8.8, deliver to the Bank a duly completed compliance certificate, dated the date of such financial statements and certified as true and correct by an appropriate officer of the Borrower, containing a computation of each of the financial covenants set forth in Section 10 and stating that the Borrower has not become aware of any Event of Default or Unmatured Event of Default that has occurred and is continuing or, if there is any such Event of Default or Unmatured Event of Default describing it and the steps, if any, being taken to cure it.
Compliance Covenant The Company will not become a party to any Common Stock Change Event unless its terms are consistent with this Section 5.09.
Contractual and Operational Compliance Audits (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and
(b) use commercially reasonable efforts to conduct such audit during regular business hours and in such a manner as to not unreasonably disrupt the operations of Registry Operator. As part of such audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information reasonably necessary to demonstrate Registry Operator’s compliance with this Agreement. Upon no less than ten (10) calendar days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. ICANN will treat any information obtained in connection with such audits that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of Registry Operator in accordance with Section 7.15.
Policy Compliance Violations The Requester and Approved Users acknowledge that the NIH may terminate the DAR, including this Agreement and immediately revoke or suspend access to all controlled-access datasets subject to the NIH GDS Policy at any time if the Requester is found to be no longer in agreement with the principles outlined in the NIH GDS Policy, the terms described in this Agreement, or the Genomic Data User Code of Conduct. The Requester and PI agree to notify the NIH of any violations of the NIH GDS Policy, this Agreement, or the Genomic Data User Code of Conduct data within 24 hours of when the incident is identified. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification(s), the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.
Continued Compliance The Company shall comply with the Securities Act, the Securities Act Regulations, the Exchange Act and the Exchange Act Regulations so as to permit the completion of the distribution of the Public Securities as contemplated in this Agreement and in the Registration Statement, the Pricing Disclosure Package and the Prospectus. If at any time when a prospectus relating to the Public Securities is (or, but for the exception afforded by Rule 172 of the Securities Act Regulations (“Rule 172”), would be) required by the Securities Act to be delivered in connection with sales of the Public Securities, any event shall occur or condition shall exist as a result of which it is necessary, in the opinion of counsel for the Underwriters or for the Company, to (i) amend the Registration Statement in order that the Registration Statement will not include an untrue statement of a material fact or omit to state a material fact required to be stated therein or necessary to make the statements therein not misleading; (ii) amend or supplement the Pricing Disclosure Package or the Prospectus in order that the Pricing Disclosure Package or the Prospectus, as the case may be, will not include any untrue statement of a material fact or omit to state a material fact necessary in order to make the statements therein not misleading in the light of the circumstances existing at the time it is delivered to a purchaser or (iii) amend the Registration Statement or amend or supplement the Pricing Disclosure Package or the Prospectus, as the case may be, in order to comply with the requirements of the Securities Act or the Securities Act Regulations, the Company will promptly (A) give the Representative notice of such event; (B) prepare any amendment or supplement as may be necessary to correct such statement or omission or to make the Registration Statement, the Pricing Disclosure Package or the Prospectus comply with such requirements and, a reasonable amount of time prior to any proposed filing or use, furnish the Representative with copies of any such amendment or supplement and (C) file with the Commission any such amendment or supplement; provided that the Company shall not file or use any such amendment or supplement to which the Representative or counsel for the Underwriters shall reasonably object. The Company will furnish to the Underwriters such number of copies of such amendment or supplement as the Underwriters may reasonably request. The Company has given the Representative notice of any filings made pursuant to the Exchange Act or the Exchange Act Regulations within 48 hours prior to the Applicable Time. The Company shall give the Representative notice of its intention to make any such filing from the Applicable Time until the later of the Closing Date and the exercise in full or expiration of the Over-allotment Option specified in Section 1.2 hereof and will furnish the Representative with copies of the related document(s) a reasonable amount of time prior to such proposed filing, as the case may be, and will not file or use any such document to which the Representative or counsel for the Underwriters shall reasonably object.
Reporting Covenant Required Complies Quarterly consolidating financial statements Quarterly within 45 days Yes No Annual financial statement (CPA Audited) FYE within 150 days Yes No 10‑Q, 10‑K and 8-K Within 5 days after filing with SEC Yes No Quarterly Compliance Certificate Contemporaneously with delivery ofthe 10-Q and 10-K Yes No Annual operating budgets and annual financial projections FYE within 45 days Yes No
Reporting Covenants Required Complies Monthly Compliance Statement Monthly within 30 days Yes No Quarterly financial statements Quarterly within 30 days Yes No Annual financial statements (CPA Audited) FYE within 120 days Yes No 10-Q, 10-K and 8-K Within 5 days after filing with SEC Yes No Board approved projections FYE within 60 days Yes No
Compliance Audit LEA shall have the right but shall be under no obligation to conduct audit(s), from time to time, of Provider’s records concerning its compliance obligations as set forth in this Article V. Provider shall make such records and other documents available to LEA upon request.
CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.
