(4) If, after receiving an extension, an LEA fails to submit the report by the designated date, the MSP fund transfer process shall be stopped and the procedures described in Section R277-484-7 shall apply.(5) An extension shall apply only to the specific reports and dates for which an extension was requested.
(6) The Superintendent may not extend deadlines for the following reports:
(a) AFR;
(b) APR;
(c) Mid-year or Final CACTUS or USIMS updates;
(d) a Financial Audit Report; or
(e) any UTREx updates.
(7) Notwithstanding Subsection (6)(e), if an LEA identifies significant errors in a UTREx update, the Superintendent may grant the LEA an extension of no more than eight calendar days to file a new update.
R277-484-7. Official Data Source and Required LEA Compatibility.
(1) The Superintendent shall load operational data collections into the Data Warehouse as of the submission deadlines specified.
(2) The Data Warehouse shall be the sole official source of data for annual:
(a) school performance reports required under Section 53E-5-204;
(b) determination of state and federal accountability reports; and
(c) submission of data files to the U.S. Department of Education.
(3) The Superintendent shall maintain a database of LEA and school:
(a) demographic information;
(b) openings;
(c) closures; and
(d) contact information for designated individuals.
(4)(a) An LEA shall use an SIS approved by the Superintendent to ensure compatibility with Board data collection systems.
(b) The Superintendent shall maintain a list of approved student information systems.
(5) Before the Superintendent granting approval for an LEA to initiate or replace a student information system that was not previously approved, the LEA shall:
(a) send written request for approval to the Superintendent no later than November 15 of the year before the year the LEA proposes to use the SIS for production software;
(b) submit documentation to the Superintendent that the new or modified student information system is SIF certified;
(c) submit documentation to the Superintendent that an SIF agent can meet the UTREx specifications profile for Vertical Reporting Framework (VRF) and eTranscripts;
(d) ensure that a new student information system can generate valid data collection by submitting a file to the Superintendent for review;
(e) ensure that the new student information system can generate the Statewide Student Identifier (SSID) request file by submitting a file to the Superintendent for review.
(6)(a) The Superintendent shall review documentation and grant or deny an LEA submission under Subsection (4) within 30 calendar days.
(b) [The Superintendent may require an]An approved replacement system [to]shall run in parallel to a state-approved system for a period of at least three months and be able to generate duplicate reports to previously generated information. (7) An LEA shall submit daily updates to the Board Clearinghouse using School Interoperability Framework (SIF) objects defined in the UTREx Clearinghouse specification.
(8) An LEA shall electronically submit all public high school transcripts requested by a public education post-secondary school if the post-secondary school is capable of receiving transcripts through the electronic transcript service designated by the Superintendent.
(9) [No later than June 30, 2017, a]An LEA shall ensure that data collected in the Utah Student Record Store for a Student Achievement Backpack is integrated into the LEA's SIS and is made available to a student's parent or guardian and an authorized LEA user in an easily accessible viewing format. (10) Failure to comply with any of the requirements of this Section R277-484-5 may result in a recommendation for corrective action in accordance with Rule R277-114.
R277-484-8. Adjustments to Summary Statistics Based on Compliance Audits.
(1) To allocate MSP funds and projecting enrollment, the Superintendent may modify LEA level aggregate membership and fall enrollment counts on the basis of the values in the Membership and Enrollment audit reports, respectively, when an audit report review team agrees that an adjustment is warranted by the evidence of an audit.
(2) An audit report review team shall make a determination under Subsection (1) within 60 working days of the authorized audit report deadline.
(3) The Superintendent may only adjust values downward if an audit report is received after an authorized deadline.
R277-484-9. Financial Consequences of Failure to Submit Reports on Time.
(1) If an LEA fails to submit a report by its deadline as specified in Board Reporting Deadline Table, consistent with procedures outlined in Rule R277-114, the Superintendent may recommend corrective action, including stopping the LEA's MSP funds transfer process, unless the LEA has obtained an extension of the deadline in accordance with the procedure described in Section R277-484-4.
(2) The Superintendent may recommend loss of up to 1.0 WPU from Kindergarten or Grades 1-12 programs, depending on the grade level and aggregate membership of the student, in the current year Mid-Year Update for each student whose prior year immunization status was not accounted for in accordance with Section 53G-9-302 as of June 15.
(3) An LEA that fails to meet data quality standards may be required to submit a corrective action plan and comply with additional reporting requirements consistent with Section 53G-6-213 and Rule R277-114. KEY: data standards, reports, deadlines
Date of Last Change: [May 8,] 2026 Notice of Continuation: June 16, 2026