TechLiteracy Assessment Guidelines and Recommendations

Assisting Students

  • Proctors may not help students with the assessment itself. They may only help students log in and begin.
  • Proctors may help students with any hardware or internet connectivity issues during the assessment. Students should be instructed to tell the proctor immediately if any technical problems arise during the assessment. Technical problems should be recorded in the Proctor notes section in the management system.
  • Proctors may pronounce words in the question item on the assessment. Proctors may not provide definitions for any words.
  • Students must follow the same rules for the TechLiteracy Assessment test that they follow for any graded test or exam: no looking around, no talking, no comparing answers, etc.
  • Right-clicking and keyboard shortcuts are not acceptable forms of responding to items in the assessment. All answers must be made with traditional left-click mouse actions.
  • Your district may choose to follow student IEP guidelines or other accommodations such as reading aloud for ELL students as indicated for any standardized assessment.

Assessment Management

  • Testing irregularities should be noted in the “Proctor Notes” section of the management system. Examples of testing irregularities include: fire alarms, loss of internet connectivity, student becomes ill, cheating, hardware failure, special announcements during assessment, etc. It is a good idea to include the date, time, and student username (if applicable) of each entry. All of your notes will be stored in this section, and are visible on class reports.
  • You can monitor the progress of your students during the assessment via the Learning.com platform. To do this, log into your teacher account, click on the “Classes” icon, select the class and assessment event you’d like to monitor, and regularly click the “Refresh” button to see the up-to-date progress of your students reflected in progress bars beside each student’s name.
  • When a student has submitted a test for scoring, you will see a check mark under the Submitted column, as well as an option to reset the test if a student has submitted the test prematurely. To reset the test, click the “Reset” button. The student will be able to log back in and complete the test.

Assessment Completion

  • The assessment is in one part and should be given over one 45–50 minute session.
  • If a student begins but does not complete the assessment during the initial test period, click the Exit (X) button in the student’s assessment window and his or her answers will be saved. The student will be able to log back into the assessment and pick up where he or she left off as long as they continue testing within the scheduled assessment time window.
  • If a student begins but does not complete the assessment and does not return to complete and submit it later, their answers will be saved but a score report will not be produced for that student.

Testing Environment

  • Proctors should ensure that the testing environment is free of distracting noises or interruptions.
  • The TechLiteracy Assessment may be proctored in a variety of settings, including, but not limited to labs, libraries, mobile wireless labs, and classroom computers.
  • Determine a way to ensure students that finish the assessment early do not disrupt the rest of the class.

Recommended scenarios are in green. Never recommended scenarios are in orange.

It is recommended that there be one District Coordinator who executes the User Import Tool district upload, creates proctor accounts, checks district progress using the progress reports, and certifies completion of testing events for the district.

It is recommended that School Coordinators be designated at one or more individual school buildings and create classes, enroll students, and schedule assessment events. There can be several School Coordinators in a district. They can also proctor events and impersonate proctors at their school sites.

It is recommended the Coordinators set up classes and assessment events for proctors by impersonating each proctor. Viewing existing classes and events is identity-dependent. Proctors can only see classes and administer assessment events that have been set up under their name.

It is recommended that students should be divided into logical class groupings of no more than 35-40 students per class.

Do not create one large “class” at a particular school that contains all students in a particular grade level at the school who will be tested. If classes have more than 35-40 students, proctoring challenges will emerge such as ability to monitor progress, run reports, and provide a controlled environment for testing.

It is recommended that proctors have individual accounts with unique usernames.

Do not set up more than one proctor with the same username and password. This can cause data loss if more than one person logs in at the same time.

It is recommended that assessment events are only assigned to each student once.

Do not set up duplicate events (same class, same students, same or overlapping Assessment window). If an assessment is assigned in multiple classes, students could choose the wrong event and score reports, progress, and data will also be incorrect.

It is recommended that proctors print the login information for students before the testing period to ensure all students are enrolled in the correct assessment class and to ease the login process.

Do not proctor events without login information (Class Rosters or Login Cards) printed for students.

Webpage