Size the network for the actual exam and concurrent population
College Board currently publishes different minimum bandwidth requirements for SAT and PSAT assessments versus AP exams. Its figures are 0.2 Mbps download and upload per simultaneous SAT or PSAT tester, and 1 Mbps download with 0.2 Mbps upload per AP tester. The exam type therefore changes the planning calculation.
At 200 simultaneous testers, those published minimums translate to 40 Mbps in each direction for SAT or PSAT, and 200 Mbps download with 40 Mbps upload for AP. This arithmetic describes the testing requirement before other building traffic and operating headroom are considered. It does not establish that every wireless room can deliver its share.
The school must also assess local device capacity and the path to the required services. Available internet bandwidth cannot compensate for a congested room, an inaccessible authentication path or traffic blocked by the network's configuration.
Prepare applications before the demand converges
Installing or updating the testing application on many devices at once adds traffic and setup work at the worst possible time. College Board's guidance explicitly warns that concurrent installations or updates can cause delays beyond the expected testing demand.
Device preparation should therefore reach an accepted state before test day, using the current requirements for the actual platform. A successful readiness check is useful evidence, but later application or operating-system changes can alter that state. The school should know what changed after the check.
The relevant traffic permissions should follow the testing provider's current instructions and the district's authorized configuration process. Broadly disabling security controls is not a substitute for understanding which supported connections the application requires.
The beginning and end deserve explicit coverage
College Board identifies the start and end of testing as periods of higher network demand. It also explains that students can continue through a momentary connection loss, while internet access is required at the start and end. The consequence is that a mid-test network observation may not represent the critical demand interval.
The support team should be available and able to observe the affected infrastructure during those periods. That includes the room-level wireless environment and the shared upstream path. A technician scheduled only for the opening can miss a submission problem later.
The test coordinator should control any adjustment to administration. Technical staff can explain the network condition and recovery options; they should not independently change exam procedures or tell students how to handle an interrupted test outside the approved process.
Escalation should distinguish device, room and service failures
One affected device, an entire room and several schools failing simultaneously suggest different scopes of investigation. The incident report should identify the observed pattern, affected stage and time so that the next action can be directed appropriately.
Proctors also depend on Test Day Toolkit, while students use Bluebook. Those are related but distinct paths. The support team should avoid assuming that a working student device establishes that the proctor's administration function is available.
The communication route should remain usable if the affected network is unavailable. The coordinator and technical lead need a practical way to exchange updates without relying entirely on the service under investigation.
Readiness is a coordinated operating state
The strongest testing-day plan combines prepared devices, representative network capacity and clear decision authority. It supports the full administration period, including submission, and gives technical staff a precise role within the test coordinator's process. That is what turns an installed exam application into a supportable testing environment.