Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Data Submission topic
No spam. Unsubscribe anytime.
USBE warns: October 1 submission has no extensions; LEAs must clear fatal errors and download reports immediately
Summary
At the Utah State Board of Education monthly data meeting, USBE staff reminded Local Education Agencies that the October 1 data submission deadline has no statutory extensions and outlined steps LEAs must take to resolve validation errors, download October reports, and meet SSID and address validation deadlines.
The Utah State Board of Education’s data team told LEA data managers that the October 1 student-data submission deadline must be met without extensions and explained the steps LEAs should take to avoid losing funding or having records excluded.
USBE staff said the finalizer for October data will be available in the week before October 1 and that the submission window closes on Monday, October 6 at 5 p.m. LEAs were urged to finalize early when possible because the system is slow close to the deadline and there is no statutory extension for the October submission requirement.
Why it matters: October 1 enrollment counts feed funding and accountability calculations. USBE staff said finalized October 1 data — not subsequent daily feeds — determine counts used for state funding and graduation-rate calculations.
Key takeaways and required steps
- No extensions: USBE reiterated a statutory requirement that the October 1 submission be finalized by the legislated date; LEAs must plan accordingly. USBE said the state will not accept late finalizations as an extension.
- Finalizer window and download of reports: The finalizer is expected to open in the days before October 1 and close on October 6 at 5 p.m. Staff advised LEAs to download all October UTREx reports immediately after finalizing because archived files may not reflect the exact finalized dump later.
- Errors that block finalization: LEAs must clear level‑1 fatal errors (student-record fatals, school/district record fatals and certain course-level fatals) and level‑2 fatals such as permanent exit, student-level inconsistencies, dual kindergarten, invalid address, or invalid district-of-residence. Level‑2 fatals do not stop daily rostering but will prevent a school or district from being included in the finalized October 1 count until resolved.
- SSID merges and deadlines: To guarantee completion of SSID merge requests, LEAs should submit merge tickets by 5 p.m. two weeks before the final deadline (the team specified Monday, September 22 in this meeting’s schedule). LEAs must respond promptly to help-desk follow-ups.
- Address and district-of-residence validation: USBE recommends validating addresses via the Utah Geospatial Resource Center (UGRC). If a physical address is not UGRC-valid, LEAs should attach geocodes. LEAs should use UGRC’s district-boundary tool for district-of-residence corrections.
- Reports LEAs must download: USBE highlighted five October reports available from UTREx (consolidated membership, school summary, SPED dropout summary, student district-of-residence for charters, students-not-attending-district-of-residence for districts) and recommended saving CSVs (student-level) and PDFs (aggregate) immediately after finalizing.
- Finalizer errors: If an LEA receives a finalizer error when pressing the finalize button, USBE staff said LEAs must resubmit a new daily upload and then press finalize again; simply pressing finalize a second time will not correct an error caused by an earlier submission problem.
Staff note: USBE will run courtesy data reviews and email LEAs flagged items; LEAs were asked to review those letters promptly because the counts USBE pulls reflect the state of UTREx on the review day and may differ if the LEA updates data later.
Ending: USBE staff provided contact emails and encouraged LEAs to reach out early for help clearing fatal errors and completing SSID merges to avoid last‑minute rework and to ensure students and schools are included correctly in the October 1 finalizer.
