[{"_1":2,"_111":-5,"_112":-5},"loaderData",{"_3":4,"_26":27},"root",{"_5":6,"_17":10,"_18":19,"_20":21,"_22":10,"_23":-5,"_24":-5,"_25":10},"user",{"_7":8,"_9":10,"_11":10,"_12":-5,"_13":-5,"_14":15,"_16":-5},"roles",[],"isAuthenticated",false,"isPremium","planName","subscriptionStatus","featureFlags",{},"insightsBudget","isDevelopmentHost","userPreferences",{},"recaptchaSiteKey","6LcvOJcUAAAAAHsB-gPGfGktcRlKpH7OTIU_dMTD","isImpersonating","impersonation","affiliateStatus","isFreedomPortal","routes/v2/article/layout",{"_28":29,"_30":31},"notFound",true,"relatedArticles",[32,75,87,99],{"_33":34,"_35":36,"_37":38,"_39":40,"_41":42,"_43":44,"_45":46,"_47":48,"_49":50,"_51":52,"_53":54,"_55":56,"_57":58,"_59":60,"_61":62,"_63":64,"_65":66,"_67":68,"_69":70,"_71":72,"_73":56,"_74":56},"mediaId",6527709,"mediaKeyId","3541622-60e7d63dd3f0d63d90ac1d719a962b8c","parentId",3541622,"title","USBE invites LEAs to pilot Student Backpack API; offers new teacher email mapping for assessment rostering","audioSeconds",7320,"startMs",2700000,"endMs",10020000,"viewUrl","/Search/View?dp=1&key=3541622-60e7d63dd3f0d63d90ac1d719a962b8c&start=2700&end=10020","thumbnailUrl","https://assets.pipeline.soar.com/3541622-60e7d63dd3f0d63d90ac1d719a962b8c/thumbnail_2700000.jpg","articleUrl","/articles/6527709/Utah/USBE-invites-LEAs-to-pilot-Student-Backpack-API-offers-new-teacher-email-mapping-for-assessment-rostering","mediaUrl","https://secure.pipeline.soar.com/6527709-f3c8b98bb53dfe35e15182b1cb5588e5/orig.mp4?Expires=1770568624&Signature=JPxUVHrgp87KyyHxX6jXdUWx4wozh2AzgmzH7lLkGG-pW1H5zWcqYA5y0vRBY50SMN8TqpjzB7X9kUy56CQeIl77RXZFo7~KlBYAvhIJ~ZTEYrzX46ejdFtktxY3BjEW03N~NNifFzd-InFI-EHAmA~eVlkOotT7Fi8GoRhaqU2h2KRBlzXUDQ3ZYuzqbTc2Yz0nDHtNQ7PHIvCt6~wccFfiH4kiEEGk3Y3saGbXvN~LCDTAWdF97I~6OSMIfjoCUgWxh3J4fRZUVDNryidEquN1baYFJc-Jp8~C-7MNs8Qp8scw3ie9-wQpY43~ZWePJOA6zplXnLRYx5NccXensg__&Key-Pair-Id=KUT5TJCACFTXG","author","","date","2025-05-27T14:52:04Z","article","USBE staff provided an update on the Student Backpack API and an optional new teacher email mapping to improve test rostering and assessment account creation.

Mark (assessment/data staff) said Student Backpack API endpoints now expose student demographic information, summative attendance and assessment data and LEAs can manage their own tokens and secrets. He said Davis district has volunteered to pilot the API and USBE is recruiting additional LEAs and SIS vendors for early adoption. Mark encouraged LEAs that anticipate needing transfer or assessment updates for incoming students to volunteer so USBE can provide targeted implementation support.

Teacher email mapping for rostering
Cliff described an optional new field to add a teacher contact email on the course master record to reduce use of personal email addresses for assessment logins. The field is not required but USBE said it will assist districts in managing assessment accounts and keep personal teacher emails private. The mapping follows existing SIF fields and USBE said it will use teacher 1 email for assessments; teacher 2 and 3 values can also be sent but are not the primary rostering contact.

Next steps
USBE will share contact information for LEAs interested in piloting the Student Backpack API and will publish guidance on teacher email mapping. Staff offered to follow up individually with LEAs and SIS vendors about scheduling testing.","mediaType","Video","parentTitle","May 2025 LEA Data Meeting","oneSentenceSummary","USBE staff said Student Backpack API endpoints (demographics, summative attendance, assessment data) are available for LEAs to pilot, named Davis as an early adopter, and proposed an optional teacher email field for course master records to improve assessment rostering.","taxTitle","Utah State Board of Education, Utah Government Divisions, Utah Legislative Branch, Utah","taxId",7925,"location","Utah","headline","shortSummary",{"_33":76,"_35":36,"_37":38,"_39":77,"_41":78,"_43":79,"_45":80,"_47":81,"_49":82,"_51":83,"_53":84,"_55":56,"_57":58,"_59":85,"_61":62,"_63":64,"_65":86,"_67":68,"_69":70,"_71":72,"_73":56,"_74":56},6527713,"USBE clarifies packet credit reporting under HB199; educator license renewal reminder",59,2091000,2150000,"/Search/View?dp=1&key=3541622-60e7d63dd3f0d63d90ac1d719a962b8c&start=2091&end=2150","https://assets.pipeline.soar.com/3541622-60e7d63dd3f0d63d90ac1d719a962b8c/thumbnail_2091000.jpg","/articles/6527713/Utah/USBE-clarifies-packet-credit-reporting-under-HB199-educator-license-renewal-reminder","https://secure.pipeline.soar.com/6527713-a22cc4d9ec6e8929b89eb72e6d6d528b/orig.mp4?Expires=1770568624&Signature=c2etrYkWF7i2r65ILWYkAXHLTiiFq8KqfQnFavSK8zKZcu5IUazECJiO66QXFLrf7vdvtsdI4q4EwboL3oN3azWC3~AU0FglOsds-bPVs7QYR1RoYY08AAAettOIZWWErrYi31Jqnj34Lu2sEjKtskhWlaSUzkrMXZy39kUnSEq8rsngh3w5YEsrUcjli0RNTr90PQZcnOk2JOwhHZqh19zUoo40V2CD90lwUCOwavogLntPvD7TXiaAlve1ct1O7fr2ok~VoZsv5QZFL7zMHqyAV3FOtcFcgcKG7hVLDREikNAYn4~3O~N5yAWKxbba6kL9NdeESeVh3gmtL6fyFw__&Key-Pair-Id=KUT5TJCACFTXG","Kristen, from USBE teaching and learning licensing, briefed LEAs on new packet reporting required by House Bill 199 and reminded educators of a June 30 professional license renewal deadline.

Kristen said HB199 requires the state to collect and report the number of credits earned through packets, packet course core codes, and whether credits are credit‑recovery or original credit. She estimated that between 20 and 30 percent of students graduate with at least some packet credit, noting that “packet” means an instructional collection where a student largely directs their own learning with little or no teacher instruction and assessment is primarily completion based.

Key points on packet credits
- Original credit via a packet: An LEA may award original credit only if the packet adheres to state board rules and is approved by the LEA or USBE.
- Credit recovery via a packet: Typically coded as pass/fail and should not be used for grade replacement. Kristen emphasized board rule prohibits using packets for grade replacement; students seeking to replace a grade must retake the full course.
- Reporting codes: USBE will use code 18 for recovery and code 19 for original credit when reporting packets; generic codes exist for course placeholders (for example, half‑credit fine arts cases).

Guidance and timing
Kristen said USBE is preparing further guidance and packet approval instructions and expects that guidance to be available in about a month. Packet approval documentation for vendor packets will be required when packets originate outside an LEA.

License renewal reminder
Kristen also reminded educators to renew professional licenses before June 30. Monthly reminders have been sent; educators who have not worked in the past five years still need to log into USIMS and complete specified steps though they may not need to complete the renewal form itself.

Ending
USBE staff said they will publish packet approval guidance on the USBE website and will send clarifying guidance to LEAs when available.","USBE licensing staff reviewed House Bill 199 reporting requirements for packet credits, explained packet vs. credit recovery distinctions and said guidance on packet approval will be published within a month. Staff also reminded educators to renew professional licenses by June 30.",{"_33":88,"_35":36,"_37":38,"_39":89,"_41":90,"_43":91,"_45":92,"_47":93,"_49":94,"_51":95,"_53":96,"_55":56,"_57":58,"_59":97,"_61":62,"_63":64,"_65":98,"_67":68,"_69":70,"_71":72,"_73":56,"_74":56},6527718,"USBE outlines Utah Fits All (UFA) changes: new program manager, 993 school code and LEA responsibilities for cross‑enrollment checks",353,6973000,7326000,"/Search/View?dp=1&key=3541622-60e7d63dd3f0d63d90ac1d719a962b8c&start=6973&end=7326","https://assets.pipeline.soar.com/3541622-60e7d63dd3f0d63d90ac1d719a962b8c/thumbnail_6973000.jpg","/articles/6527718/Utah/USBE-outlines-Utah-Fits-All-UFA-changes-new-program-manager-993-school-code-and-LEA-responsibilities-for-crossenrollment-checks","https://secure.pipeline.soar.com/6527718-75af918d67bbb55a5384f6ec91a523ba/orig.mp4?Expires=1770568624&Signature=V5jqkmWgKpHsDf8DuYQwGFAJxK6G-U9fjJJlRmMLbTKYqejl7BdYdhlYiV0XdlQmliW0pClbodv5AXIFu6MEPO6wL4n~5juU5YVUP14GB6qoRfVw6s6v1qPAXjMOZwZDI~pt5lRSH3d2O3r0IR~eXRW4SyxodSn7cHMA70~bh2JSE~paHbbVPKleyzJf7Uxhqj6IHl-2FnXuyO0kMo8gwyRCIWo8QwGRvGqaE74XudeDJG8B8hngTdr19TKMfwQ11JV73dZVdURSUEyK45GB570gpUCK0xEOoXqcLj3W5v2v8oANISafGAd7gjZt-8kqqtQHJh4Cx0xq8tLpVMfamQ__&Key-Pair-Id=KUT5TJCACFTXG","The Utah State Board of Education told LEAs during a data webinar that Odysee (Odyssey) has replaced ACE as the program manager for the Utah Fits All (UFA) scholarship program and that LEAs will need to work directly with the new manager to validate scholarship eligibility and cross‑enrollment.

Cliff, a USBE staff member, said the contract with ACE ended on May 15 and Odysee is the new program manager. USBE has handed off contact information for awarded and applicant students to Odysee and urged LEAs to work directly with the program manager for provider qualification and cross‑enrollment resolution.

Key operational change: school code 993
USBE plans to use a dedicated school number (993) to identify UFA scholarship enrollments and will provide level‑2 warnings where a 993 enrollment appears to overlap with an enrollment at another LEA. Cliff said the 993 code is intended as an identifying mechanism, not as a full policy enforcement gate. If a student appears both as a 993 enrollment and an enrollment at another LEA, the system will issue a warning indicating a cross‑enrollment that must be resolved between the LEA and Odysee.

Cliff explained USBE’s role is shifting from acting as the primary verifier to facilitating communications: “Our intent is to be less the decider on things and more of the communicator,” he said, describing the legal direction that places primary responsibility on LEAs and the program manager to reconcile cross‑enrollments.

LEA workload and privacy concerns
Several LEA participants asked who must perform cross‑checks and when. Steven (LEA representative) asked whether each newly enrolling student must be checked with Odysee. Cliff and other staff said the legislation requires LEAs to participate in an enrollment‑validation process; the specific message flows and technical approach (LEA‑initiated checks, program‑initiated checks, or automated feeds) are still being negotiated with Odysee. USBE and Odysee will convene implementation discussions; Cliff said those conversations should occur in the coming weeks and USBE expects to facilitate a broader meeting for LEAs.

What stays the same and what to expect this year
Cliff said USBE will attempt an interim bulk exchange with the prior manager (ACE) to provide initial cross‑enrollment data during the transition, but eventually LEAs and Odysee must establish secure exchange methods (APIs or secure file transfers) individually. For the 2025–26 school year, USBE intends the 993 school to be available; LEAs that operate as UFA course providers should use school 993 for scholarship course rosters. Nonprovider districts should not use 993 for normal enrollments. Cliff said USBE will aim to include helpful detail in validation messages (for example, naming the other district where the student appears) to simplify follow up.

Assessment, transcript and record handling
Cliff and other staff explained that UFA students do not automatically become regular enrolled students in the state system; many data fields (attendance, grades, special education flags) are not intended to be routed to the state in the same way as public enrolled students. If a parent requests a transcript from an accredited provider, the provider LEA must produce that transcript in the standard manner, but USBE is not planning to ingest those grades as part of statewide student records for UFA awardees. Assessment rostering for a UFA student who takes an assessment at a LEA will be handled via standard test rostering protocols (and USBE plans rostering guidance updates for private/homeschool and UFA students next year).

Next steps and implementation meetings
Odysee is newly onboarded and implementation details remain under discussion. Cliff said USBE will facilitate meetings between Odysee and LEAs to determine the preferred technical approach for enrollment validation, and he expects clearer guidance within weeks.

Ending
USBE asked LEAs to prepare for additional implementation work: establish contact paths with Odysee if the LEA is a qualifying provider; be prepared for new validation messages tied to the 993 school code; and participate in planned follow‑up meetings to define the data‑exchange approach.","USBE staff said Odyssey is the new UFA program manager replacing ACE, described a new school code (993) to flag scholarship students, and warned LEAs they will have a larger role verifying cross‑enrollments with UFA awardees; technical and privacy details remain under discussion.",{"_33":100,"_35":36,"_37":38,"_39":101,"_41":102,"_43":103,"_45":104,"_47":105,"_49":106,"_51":107,"_53":108,"_55":56,"_57":58,"_59":109,"_61":62,"_63":64,"_65":110,"_67":68,"_69":70,"_71":72,"_73":56,"_74":56},6527723,"USBE staff detail year-end Utrecs deadlines, SSID merge process and fatal-error checks",2036,1044000,3080000,"/Search/View?dp=1&key=3541622-60e7d63dd3f0d63d90ac1d719a962b8c&start=1044&end=3080","https://assets.pipeline.soar.com/3541622-60e7d63dd3f0d63d90ac1d719a962b8c/thumbnail_1044000.jpg","/articles/6527723/Utah/USBE-staff-detail-year-end-Utrecs-deadlines-SSID-merge-process-and-fatal-error-checks","https://secure.pipeline.soar.com/6527723-51e962c0954b94cf58beebf1565b5801/orig.mp4?Expires=1770568624&Signature=SmR~gxGxNHkbhWRx8b0orCtYDaI9nEemp6uQiG2O7-8UMhlZOpyPoth20Zu9gXqrxK0hVKspcu-RnrOdYb0Vvttc9Je18WdW~LFNcYG1NOz9v9tWc5xMerQYzytd-3dUerKstMZ~RwXHm8sbjHqKAAXgvoPVd3smssinWjdTzTVRdAZ6DI8jizxRKMappcjFC~ayWDyOIeSyqw4fTG2wf3unEn4m-cBzCEzsA3azXUSalhkFAIJXWFVXDMOzyK5o~pMLkWrGJPR-ZMQ5J4m5~UJwJRQ~Tu~bGBpZttKp5m1nB9~DBLHgviPn-4d0adGZZz-xoJ9wMNuDdOa9eoDGyw__&Key-Pair-Id=KUT5TJCACFTXG","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 characters) to surface alternate spellings and then checking the student history to see which LEA created each SSID.

The SSID merge now must be submitted through the application help desk at schools.utah.gov (select “submit a request” → “SSID merge request”). The ticket form requires: the SSID to be kept (state will keep the lower SSID number when applicable), the SSID(s) to be merged away, the school ID to keep, the requesting LEA and a list of individuals (name and LEA) who granted permission to merge. Katrina said tickets typically take one to four hours to complete if no additional information is needed; if USBE requests more information the ticket will enter pending status and will automatically resolve after seven days unless the requester supplies the missing details.

Riley emphasized that timely responses to help‑desk queries are essential: “Please respond to comments on merge request tickets for more information in a timely manner so that ensures that your request gets done,” Riley said.

Fatal errors, warnings and courtesy reviews
Calista (staff) and Stephanie (staff) described the validations that can block records. They clarified two classes of fatal errors: level‑1 fatals (errors in the LEA's data) and level‑2 fatals (errors that arise when data are checked across systems, e.g., SSID checks or district cross‑checks). Calista noted a new validation (S1Dot368) requiring district of residence to be present and two new level‑2 validations that are now fatal: district of residence and invalid address.

USBE will run courtesy data reviews beginning the week of May 27 and expects to complete reviews by June 6. Reviews will be prioritized in the order LEAs finish their school year (USBE uses calendar submissions in Data Gateway to determine that order). The review letter will flag items that need verification and list items for information only.

Common checks LEAs should make before finalizing
USBE staff listed high‑priority checks for LEAs:
- Fix fatal errors and investigate warnings; do not alter accurate data merely to clear warnings.
- Verify enrollment and membership counts, average daily membership, and counts by grade. Most students should show about 180 membership days; unexpectedly low maximum membership counts may indicate SIS reporting problems.
- Review kindergarten type codes (full‑day FN vs. half‑day NN) used in WPU funding calculations and correct any large or unexpected shifts from prior years.
- Review incident reporting (disciplinary removals, SRO/LEO activity, bullying/cyberbullying/hazing/retaliation). USBE’s review threshold is low (roughly one incident per 50 students) and underreporting can affect risk scores and indicators in accountability reviews.

Kindergarten test and early numeracy requirements
Maureen, in assessment, said that kindergarten Acadience (reading-on‑grade‑level) status and early numeracy results are required this year for status and intervention for BOY/MOY/EOY assessment sessions. If an LEA cannot submit kindergarten intervention and status data through UTracks, USBE assessment staff will accept a limited, provided template (MoveIT upload) for kindergarten only; grade 1–3 data must continue to flow via UTracks. Stephanie and Maureen warned that leaving required k status or intervention blank for a kindergarten student with at least 20 days of membership will trigger a fatal error and block that student record from year‑end submission.

Graduation coding and special education flags
USBE staff also walked through exit and completion codes that affect cohorts and graduation rates, including new and less‑used codes (AS for adult education with an active IEP, IB for International Baccalaureate completers, RA/GA for 1% alternate diploma pathways). Cliff (staff) and others urged LEAs to finalize accurate exit codes now where possible to avoid submitting historical updates after the rollover.

District‑of‑residence validation fix
Cliff reported USBE has identified a caching issue that produced some false positive district‑of‑residence errors. He said IT is clearing caches and rolling fixes in batches; some LEAs have already seen fixes and USBE expects to complete the rollout early the following week. If an LEA still sees a district‑of‑residence discrepancy after the rollout, USBE asked the LEA to open a help‑desk ticket so developers can investigate.

Resources and next steps
USBE staff reiterated that LEAs can request a prioritized courtesy review by emailing datastatisticshelp@school.schools.utah.gov, and that technical help with Utrecs submissions should be addressed via the help desk. Staff said a June training will focus on the technical steps to finalize in Utrecs. Several staff offered direct follow‑up: Riley and Mark put contact details in the chat for LEAs interested in early adoption pilots for Student Backpack APIs and other integrations.

Ending
USBE said it will share slides, review letters and a recording of the webinar with attendees and follow up at a June meeting before the July year‑end finalization deadline.","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.","actionData","errors"]

Article not found

USBE invites LEAs to pilot Student Backpack API; offers new teacher email mapping for assessment rostering

USBE clarifies packet credit reporting under HB199; educator license renewal reminder

USBE outlines Utah Fits All (UFA) changes: new program manager, 993 school code and LEA responsibilities for cross‑enrollment checks

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