Operational Compliance Rubric Sample Clauses

Operational Compliance Rubric. Data Sources: Periodic observation of enrollment lottery, and if applicable, any corrective action plans issued by the SDE not related to special education, ELL, or college and career readiness (as these are captured elsewhere), or formal notification of late reports or enrollment violations. Operational Compliance Rubric Exceeds Standard The school has met standard for 3 or more consecutive years. Meets Standard Required reports are submitted accurately and on time. The school maintains a compliant enrollment process. No correct action plans were issued by the SDE this year. Approaches Standard The school was informed of or became aware of non-compliance and action to correct the issue was taken within 30 days. Does Not Meet Standard The school was informed of or became aware of non-compliance and action to correct the issue was not taken within 30 days. FINANCIAL MEASURES NEAR TERM HEALTH
Sample 1Sample 2Sample 3See All (28)
AutoNDA by SimpleDocs
Operational Compliance Rubric. Data Sources: Periodic observation of enrollment lottery, and if applicable, any corrective action plans issued by the SDE not related to special education, ELL, or college and career readiness (as these are captured elsewhere), or formal notification of late reports or enrollment violations.
Sample 1Sample 2Sample 3See All (5)
Operational Compliance Rubric. Exceeds Standard The school has met standard for 3 or more consecutive years, including the most recently completed school year. Meets Standard • Required reports are submitted accurately and on time. • The school maintains a compliant enrollment process. • No correct action plans were issued by the SDE this year. Approaches Standard The school was informed of or became aware of non-compliance and action to correct the issue was taken within 30 days. Does Not Meet Standard The school was informed of or became aware of non-compliance and action to correct the issue was not taken within 30 days. FINANCIAL MEASURES NEAR TERM HEALTH
Sample 1Sample 2Sample 3See All (5)
Operational Compliance Rubric. Data Sources: Periodic observation of enrollment lottery, and if applicable, any corrective action plans issued by the SDE not related to special education, ELL, or college and career readiness (as these are captured elsewhere), or formal notification of late reports or enrollment violations. Operational Compliance Rubric Exceeds Standard The school has met standard for 3 or more consecutive years, including the most recently completed school year. Meets Standard • Required reports are submitted accurately and on time. • The school maintains a compliant enrollment process. • No correct action plans were issued by the SDE this year. Approaches Standard The school was informed of or became aware of non-compliance and action to correct the issue was taken within 30 days. Does Not Meet Standard The school was informed of or became aware of non-compliance and action to correct the issue was not taken within 30 days. FINANCIAL MEASURES NEAR TERM HEALTH
Sample 1

Related to Operational Compliance Rubric

  • 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.

  • General Compliance This Agreement is intended to comply with Section 409A or an exemption thereunder and shall be construed and administered in accordance with Section 409A. Notwithstanding any other provision of this Agreement, payments provided under this Agreement may only be made upon an event and in a manner that complies with Section 409A or an applicable exemption. Any payments under this Agreement that may be excluded from Section 409A either as separation pay due to an involuntary separation from service or as a short-term deferral shall be excluded from Section 409A to the maximum extent possible. For purposes of Section 409A, each installment payment provided under this Agreement shall be treated as a separate payment. Any payments to be made under this Agreement upon a termination of employment shall only be made upon a “separation from service” under Section 409A. Notwithstanding the foregoing, the Company makes no representations that the payments and benefits provided under this Agreement comply with Section 409A, and in no event shall the Company be liable for all or any portion of any taxes, penalties, interest, or other expenses that may be incurred by the Executive on account of non-compliance with Section 409A.

  • 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

  • FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:

  • ADA Compliance A. The Americans with Disabilities Act (42 U.S.C. § 12101, et seq.) and the regulations thereunder (28 C.F.R. § 35.130) (“ADA”) prohibit discrimination against persons with disabilities by the State, whether directly or through contractual arrangements, in the provision of any aid, benefit, or service. As a condition of receiving this Agreement, the Company certifies that services, programs, and activities provided under this Agreement are and will continue to be in compliance with the ADA.

  • CEQA Compliance The District has complied with all assessment requirements imposed upon it by the California Environmental Quality Act (Public Resource Code Section 21000 et seq. (“CEQA”) in connection with the Project, and no further environmental review of the Project is necessary pursuant to CEQA before the construction of the Project may commence.

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

  • Program Compliance The School Board shall be responsible for monitoring the program to provide technical assistance and to ensure program compliance.

  • Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

  • PCI-DSS Compliance Merchant shall be in full compliance with rules, regulations, guidelines and procedures adopted by any Card Association or Payment Network relating to the privacy and security of Cardholder and Card transaction data, including without limitation the most up-to-date version of the Payment Card Industry Data Security Standard (PCI-DSS), as amended from time to time by the Payment Card Industry Security Standards Council. Detailed information pertaining to aforementioned requirements may be found at xxxxx://xxx.xxxxxxxxxxxxxxxxxxxx.xxx. Additional information regarding security requirements may be found on the Card Association’s respective web sites.

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