USBE details test‑delivery procedures, session security and proctor responsibilities

USBE staff used the RISE training webinar to demonstrate the Test Delivery System (TDS) workflow for creating test sessions, approving students, monitoring progress and handling interruptions.

Why it matters: correct use of TDS and adherence to test security steps reduce misadministrations and protect assessment integrity; several features exist to prevent accidental summative administration.

Session creation and approvals: Presenters instructed test administrators to create sessions less than 20 minutes before starting to avoid timeouts and to provide the generated session ID to students. For summatives, the interface requires the administrator to type the word "summative" to confirm they intend to administer a summative test. Frey said the approval step requires staff to verify each student's selected test and accommodations before admitting them and that "students need to be denied entry individually" if they chose the wrong test.

Monitoring and actions: The TDS proctor view displays progress, test settings (standard or custom) and actions such as pause, deny, print on request and stop session. Pausing an individual student's test is appropriate for short interruptions; stopping a session pauses all in‑progress tests and requires creation of a new session ID for students to resume. Frey emphasized a 20‑minute inactivity rule: sessions close after 20 minutes of inactivity and paused tests follow the pause rules for resuming.

Print‑on‑request and PII: Print‑on‑request is available only for students who require it per IEP/504; printed materials must be sent to a monitored printer and securely destroyed after the session. Any printed rosters or session snapshots containing personally identifiable information must be stored securely and destroyed when no longer needed.

Student verification and tools: Students must confirm personal information and selected settings before beginning; Frey advised staff not to allow students to proceed if their demographic information or accommodations are incorrect. Global test tools (notepad, notes, highlighter, strikethrough, mark‑for‑review, masking, glossary and zoom) were reviewed and proctors were told that student notes and notepads are saved on submission and may trigger a required follow‑up process if language in notes is "alarming in nature."

Security best practices and proctoring: Frey recommended two proctors per session for test security (one may be roaming with a communication protocol) and told administrators to have scripted procedures from the TAM ready at the start of sessions. She also recommended setting testing windows in TIDE to limit which tests appear to teachers and reduce accidental summative administration.

Ending: USBE said additional training on appeals and summative administration will be included in upcoming winter sessions and directed attendees to the TAM and help desk for technical and policy support.