How Online Schools Coordinate State Testing at Temporary Sites

Every spring, K-12 online school students are required to sit for in-person state assessments. For traditional schools, this is a scheduling headache. For online schools, it's a full operational build from scratch, because their students don't have a building to show up to.

You're renting a hotel ballroom or convention center, managing rosters across multiple sessions, tracking accommodations, ordering Chromebooks from a vendor, staffing proctors who may have never met the students, and still handling whatever surprises show up at 8am on test day. Without a permanent site. Without the staff who know every kid by face.

Here's how this actually works, and where things tend to go sideways.

Why This Is Harder Than It Looks

Traditional schools have a permanent site and a student body that shows up every day. The staff know who needs extended time and who tends to show up late. That institutional knowledge doesn't exist for an online school on test day.

Students may be driving from 30 minutes away or two hours. Many have never met their proctor in person. The venue is a rented space that becomes a testing site for a week and then goes back to hosting corporate events. Proctors are often a mix of full-time staff and people hired just for the event.

That context matters, because it shapes every coordination decision you make. The problems break into four areas:

• Roster accuracy. The student list changes constantly. Students enroll and withdraw. Grade levels get corrected. Accommodations are added through IEP amendments. The roster you exported three weeks ago is almost never the one you need on test day.
• Session scheduling. Students can't all test at once. Rooms have capacity limits. Some students need separate testing environments. Different subjects have different testing windows. You're trying to satisfy all of those constraints at the same time, across multiple days.
• Device logistics. Most state assessments require Chromebooks. You have to figure out how many you need, order them from a vendor, coordinate delivery to the venue, and make sure accessible devices are available for students who need them.
• Day-of execution. Walk-ins happen. Students show up to the wrong session. A parent texts that their kid is running 20 minutes late. A proctor needs to know right now whether that student gets extended time.

Phase 1: Venue and Event Setup (3-5 Weeks Out)

Venue selection comes first. You need a space that can fit your full student population across multiple testing windows, with reliable internet, enough power outlets for simultaneous device use, at least one room that can be set up for accommodation testing, and enough square footage to maintain required distances between students.

Loading access matters too. Someone is delivering pallets of Chromebooks to this location.

Once you have a venue, you define the event structure: how many days, sessions per day, which grades test when, and how rooms will be organized. Get this right before you touch the roster. Everything downstream depends on it.

Phase 2: Roster Management (2-4 Weeks Out)

This is where most of the work happens. And where most of the errors happen.

The testing roster comes from your Student Information System. Pull it, clean it, and check it against your actual enrollment before you do anything else. The issues you'll typically find:

• Students with incorrect grade levels in the SIS
• Students who enrolled after the initial roster pull
• Students who withdrew but are still on the list
• Accommodations documented in the IEP system but missing from the testing roster
• Students eligible for multiple subjects with overlapping test windows

Once the roster is clean, you assign students to sessions. That means matching each student to a time slot, a room, and for students with accommodations, a specific testing setup.

Phase 3: Device Ordering (2-3 Weeks Out)

The Chromebook order calculation is trickier than it looks. You don't need one device per student. You need enough devices to cover the largest number of students testing at the same time, plus a buffer for failures, plus accessible devices for students who need them.

You can't do this calculation until session assignments are finalized. Which is why device ordering always happens after roster and scheduling, never before.

Get the quantities wrong in either direction and you have a problem. Under-order and students are sitting without devices. Over-order and you're paying for equipment that sat in a corner for three days.

Phase 4: Test Day

If the prep work was done right, test day should be execution, not firefighting. But it never goes entirely to plan.

Proctors need to know their room, their student list, and which students have accommodations. They need to check students in as they arrive, flag no-shows, and handle walk-ins. Walk-ins are students who show up without a session assignment, either because they missed their scheduled slot or because there was an administrative gap somewhere. A good walk-in process means no student gets turned away.

The situations that cause real problems on test day:

• Late arrivals. A student is 20 minutes out. The proctor needs to know whether to hold the session or start without them.
• Walk-ins. Someone shows up who isn't on the roster. This happens more often than coordinators expect, especially in the first year of a school's testing program.
• Accommodation mismatches. A student expected extended time. They weren't placed in the right session. Someone has to resolve this on the spot.
• Absent students. A student doesn't show. You need to reach a parent fast. That means contact information has to be accessible to whoever is managing the floor, not sitting in a spreadsheet on a coordinator's laptop in another room.

What Schools That Run This Well Actually Do

A few things show up consistently in testing programs that go smoothly:

• They freeze the roster at least 48 hours before test day. Any changes after that require explicit sign-off from whoever owns the testing program.
• They cross-check accommodation placements against the final schedule before anything gets printed or sent to proctors.
• They brief proctors the evening before, not the morning of. The morning of is too late to answer questions that affect setup.
• They have a documented walk-in process that every proctor knows. Not improvised at the door.
• They keep a log of every roster change so there's a clear record if a question comes up later, from a parent or from a state auditor.

When Spreadsheets Stop Working

For a school running 40 or 50 students at one testing event, a well-managed spreadsheet is probably fine. For anything larger, or for schools running multiple days with different sessions and rooms, the spreadsheet model has a structural problem.

Spreadsheets store data. They don't understand relationships. A student can be assigned to an incompatible room and the spreadsheet won't tell you. An accommodation can be on one tab but not reflected in the session assignment on another. A roster update can overwrite a manual change someone made to handle a specific student. None of these errors announce themselves.

The schools that have moved to coordination software built specifically for testing events report a pretty consistent result: fewer surprises on test day, and a clear paper trail when something needs to be explained afterward.

That's not a pitch. It's just what coordinators say when you ask them why they switched.

← Back to all articles