Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Test Appeals Data Cleanup topic
No spam. Unsubscribe anytime.
USBE explains test appeals, discrepancy resolution and participation‑code deadlines for RISE
Summary
USBE staff walked LEA users through the TIDE appeals workflow, when to create appeals, how appeals are processed, and the timeline and options for participation-code submission and data cleanup after test windows close (participation codes due June 9).
USBE presenters outlined the TIDE-based test-appeal process, how LEAs should resolve discrepancies after testing, and participation-code deadlines for the 2025 summative window.
Elise Fry explained that appeals interrupt the normal flow from submission to reporting and are used in several cases: to reopen a writing test accidentally submitted, to reopen a student segment incorrectly exited, to invalidate a test for academic‑dishonesty reasons, or to apply a parental exclusion after testing. Appeals must be created in TIDE and are subject to a two-step process: creation and then review/processing by an LEA-level user. Fry emphasized that invalidating a test removes the test opportunity entirely and cautioned staff to choose the correct appeal reason and review the submitter's rationale before approving.
On timing, Fry said appeals should be submitted at least one day before the end of the testing window so a student could still complete an opportunity if appropriate. She also recommended LEAs check appeals frequently during windows—daily or hourly for larger LEAs—and noted TIDE supports bulk uploads for batch appeal creation.
Fry described post-testing data-cleanup tools in TIDE. LEA users can run a discrepancy resolution report to find students who were eligible but never tested and assign appropriate participation codes (absent, parental exclusion, etc.). She said participation codes should be entered throughout the testing window rather than only afterwards, but the training gave a final submission deadline of June 9 for participation codes (the trainer said the Monday after the window close is typical and confirmed June 9 in the session).
Fry also clarified force‑completed tests: if a student started but did not finish, the system will force complete the opportunity at window close and generate a score; an LEA user can later enter a participation code (for example, a medical emergency) if the student remains active in the system.
