USBE gives ADs operational checklist: rostering, participation codes, accommodations and reporting windows

State assessment staff used the meeting to walk local assessment directors through a range of operational items critical during spring testing windows — rostering and first‑contact surveys for DLM, participation and special‑circumstance codes, WIDA reporting schedules, Adam/Pearson proctor URL guidance, and accommodations timing.

Key operational guidance:
• DLM rostering: teachers must complete first‑contact surveys before testlets are delivered; district test coordinators are responsible for entering special circumstance codes and must click the in‑field save icon (not the page save) to persist entries. Staff noted DLM roster delays can be caused by SIS transfers and nightly vendor pulls.

• Parent opt‑out and invalidation: if parents opt a student out after partial testing, districts must email assessment staff with the student SSID so USBE/GRF can invalidate the partial test and prevent score reports from generating.

• Participation and codes: staff cautioned against premature use of ‘did not test’ (code 101) entries that can depress participation rates and urged ADs to validate codes before final windows; the federal participation denominator for OSEP reporting does not exclude parent opt‑outs.

• Adam/Pearson (Utah Aspire Plus): use the state LTR URL (ltr.adamexam.com) to generate proctor codes in real time; using the generic Adam URL causes proctor errors and help‑desk calls. Multi‑enrolled students can test at multiple associated schools but reporting remains tied to the school where they were originally rostered.

• WIDA and reporting windows: LEA data validation completed; LEAs will receive AMS reports in early May and printed reports to LEAs; score distribution to families must comply with the three‑week rule after scores are available.

Why it matters: operational errors in rostering, codes, or accommodations can cause testing interruptions, invalidations, inaccurate participation rates and federal reporting consequences. Staff repeatedly urged ADs to check rosters, coordinate with SIS teams, and contact USBE promptly when issues arise.

Provenance: operational checklist and Q&A across DLM, RISE, Adam, WIDA, and Utah Aspire Plus modules (DLM rostering discussion beginning SEG 909; Adam/Adam LTR guidance in the Adam segment; WIDA notes at SEG 1716).