Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

USBE staff detail year-end Utrecs deadlines, SSID merge process and fatal-error checks

3541622 · May 27, 2025
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

Utah State Board of Education staff reminded local education agencies about Utrecs year-end deadlines, introduced a firm SSID merge deadline, explained the SSID merge ticketing process, and outlined fatal errors and warnings that can block records during ETL processing.

Utah State Board of Education staff reminded local education agency (LEA) data managers on May — during a state data training webinar — that year-end Utrecs/UTracks submissions must be finalized in time for the July 7 state freeze and that several pre‑submission deadlines now guarantee fixes will be applied before the year‑end processing.

The state advised LEAs to submit SSID merge requests, historical updates and respond promptly to any help‑desk follow up so merges and updates complete before finalization. Riley, a USBE staff member, said the deadline for historical update requests is Monday, June 23 at 5 p.m., and the deadline for year‑end finalization is Monday, July 7 at 5 p.m. Riley also announced a new deadline for year‑end SSID merge requests: Monday, June 16 at 5 p.m., saying that requests received with complete information by that date are guaranteed to be completed before the year‑end submission is finalized.

Why it matters: fatal errors and unresolved SSID issues can block student records during the state's ETL process, which affects rostering, reporting and funding. USBE staff urged LEAs to finalize early, maintain staff availability through the July 7 deadline and respond quickly to ticket requests so tickets do not auto‑resolve after seven days.

SSID merge process and ticketing Katrina, a USBE staff member who led the SSID training, reviewed the required fields and the ticketing workflow. She said all primary attributes — including first, middle and last name, birth date and the school ID to be kept — must match exactly across SSID lines for a merge to be allowed. Katrina advised searching by partial name fragments (three or four…

Already have an account? Log in

Subscribe to keep reading

Unlock the rest of this article — and every article on Citizen Portal.

  • Unlimited articles
  • AI-powered breakdowns of topics, speakers, decisions, and budgets
  • Instant alerts when your location has a new meeting
  • Follow topics and more locations
  • 1,000 AI Insights / month, plus AI Chat
30-day money-back on paid plans