Skip to main content

SDLA Compliance Resource

Plan Around Scheduled CAASPP and ELPAC System Downtime

A continuity control for pausing dependent testing, scoring, reporting, and configuration work and verifying restoration before resumption.

  • CAASPP & ELPAC
  • System Downtime
  • Continuity
Date(s)Calendar planning windows include January 15–19 and April 9–12, 2027; verify exact systems, start/end times, and changes on the live status page
Applies toCoordinators and users of TOMS, TDS, CERS, interim, scoring, data-entry, and related systems

In Plain Language: Treat scheduled downtime as system-specific. Check the live schedule, identify which workflows depend on each affected system, finish or pause work safely, and verify restoration before resuming.

Why this matters

A calendar label can conceal different start times and affected tools. Scheduling testing, hand scoring, uploads, or deadlines against stale downtime information creates avoidable disruption.

Primary ownership

Primary owner: LEA assessment coordinator with technology lead. Partners: sites, test administrators/examiners, curriculum, EL and special education, communications, and help desk.

From the downtime schedule to a verified restart: the SDLA ITO workflow

Downtime is system-specific: map what depends on each affected system, then check health before resuming. This SDLA ITO (Input, Transformation, Output) graphic shows how the live status page, the affected systems, and local schedules and deadlines become the status capture and system inventory, the schedule changes and communications, and the post-restoration verification.

SDLA ITO: eleven steps from the live status page, the affected systems, and local schedules and deadlines, through mapping dependencies, pausing or rescheduling, communicating, and restoring, to the status capture and system inventory, the schedule changes and communications, and the post-restoration verification.
Read down each column, then move to the next: Input identifies what to collect; Transformation covers mapping dependencies, pausing or rescheduling, communicating, and restoring; Output covers the status capture and system inventory, the schedule changes and communications, and the post-restoration verification. Planning windows include January 15–19 and April 9–12, 2027; verify them on the live page.

Open the full-size workflow graphic

Operational workflow

  1. Review the live schedule and record exact affected systems and local-time boundaries.
  2. Map testing, scoring, reporting, training, and deadline dependencies.
  3. Move work or establish a safe pause/communication plan; avoid starting sessions near shutdown.
  4. During downtime, communicate status without encouraging repeated logins or duplicate submissions.
  5. After restoration, verify system health, saved work, queues, and pupil status before resuming.

Implementation pathway

Live schedule
Dependency map
Pause/reschedule
Communicate
Restore/verify

Evidence to retain

  • Dated status-page capture
  • Affected-system inventory
  • Local schedule changes
  • User communications
  • Post-restoration verification

Official guidance and help

Source review completed August 30, 2026. Verify current California requirements, CAASPP and ELPAC manuals, live system status, local policy, pupil records, and final system state before acting.