Citizen Portal
Sign In

USBE expects final cohort 2025 graduation rate mid‑November; historical update guidance and December deadlines announced

6434541 · October 24, 2025

Get AI-powered insights, summaries, and transcripts

Subscribe
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

USBE staff said they plan to run the final 2025 cohort graduation-rate calculations in mid‑November after October finalization and recent historical updates. Staff reviewed when to file historical updates vs. S1X corrections and listed key dates for the December 1 submission and related deadlines.

David and a Utah State Board of Education data staff member summarized the timeline and guidance for the final graduation-rate calculation for cohort 2025 and offered guidance on historical updates.

Staff said the October data became available for official use only after the full ETL and production migration were completed; as a result, USBE expects to run the final graduation-rate calculations in mid‑November and to share move-it files and preview reports with LEAs for review. Staff emphasized that historical updates are a manual process that should be submitted at least two weeks prior to finalization; if a correction can be made by submitting an S1X record in UTrEx, staff will decline a historical-update ticket and ask the LEA to use the S1X process instead.

Key dates staff published for the December reporting period: the December 1 finalization window opens on Dec. 1; LEAs must finalize by 5 p.m. on Monday, Dec. 8 (the 7th falls on a weekend); the historical-update deadline is two weeks before finalization and falls on Monday, Nov. 24. Staff said USBE will start courtesy reviews for the December submission the week of Nov. 17 and encouraged LEAs to review the preview files quickly when USBE circulates them.

Staff offered to provide one-on-one assistance to LEAs that repeatedly need large numbers of historical updates and said they are available to advise whether a correction should be an S1X or a historical update to avoid wasted work.