Skip to main content

SDLA Compliance Resource

Designate and Approve a Dashboard Coordinator

The access-control step that gives a trained local official authority to enter local-indicator results and participate in Dashboard reporting and preview activities.

  • Local Indicators
  • Dashboard
  • Access
Date(s)Before the summer local-indicator reporting window
Applies toAll LEAs, including charter schools; no more than two approved Dashboard Coordinators per LEA

In Plain Language: Have the proposed coordinator submit the myCDEconnect registration, route the approval email to the correct superintendent or charter administrator/Main Authorizer, confirm approval and access, and establish a backup before the reporting window opens.

Why this matters

Completed self-reflection tools cannot be reported if access is unresolved. Stale School Directory contacts, filtered approval email, unapproved registrations, or a single unavailable coordinator can turn completed local work into “Standard Not Met.”

Primary ownership

Primary owner: accountability/LCAP lead. Approval owner: superintendent or charter school administrator/Main Authorizer. Partners: Dashboard coordinator, data governance, IT/email security, board office, and communications.

From a proposed coordinator to approved Dashboard access: the SDLA ITO workflow

The coordinator needs approved, tested access, and a backup, before the reporting window opens. This SDLA ITO (Input, Transformation, Output) graphic shows how the proposed coordinator, the authorizer's contact information, and the myCDEconnect registration become the registration and approval record, the access test, and the backup and reporting calendar.

SDLA ITO: eleven steps from the proposed coordinator, the authorizer's contact information, and the myCDEconnect registration, through contact verification, registration, approval, and access testing, to the registration and approval record, the access test, and the backup and reporting calendar.
Read down each column, then move to the next: Input identifies what to collect; Transformation covers contact verification, registration, approval, and access testing; Output covers the registration and approval record, the access test, and the backup and reporting calendar. Approve no more than two coordinators per LEA, before the summer reporting window.

Open the full-size workflow graphic

Operational workflow

  1. Verify the current authorizer and LEA contact information and identify no more than two coordinators.
  2. Submit the Dashboard Coordinator registration through myCDEconnect.
  3. Locate and complete the authorizer approval; whitelist system email if necessary.
  4. Test credentials and confirm the coordinator can access the correct LEA and reporting functions.
  5. Document primary/backup ownership, source-record location, board date, and reporting-window alert process.

Implementation pathway

Verify contacts
Register
Approve
Test
Assign backup

Evidence to retain

  • Coordinator selection and responsibilities
  • Registration submission
  • Authorizer approval
  • Access test/screenshots
  • Backup and reporting calendar
  • Contact/update records

Official guidance and help

Source review completed August 30, 2026. Verify current CDE, governing, Dashboard, school-plan, SARC, safety, instructional-materials, local-calendar, and legal instructions before acting.