Skip to main content
It is the third week of SBAC testing. Are we having fun yet?

SDLA Compliance Resource

Upload the Current LCAP to the California School Dashboard

Post the correct current-year LCAP to the Dashboard, in addition to required website posting and submission to reviewing authorities.

  • LCAP & Accountability
  • SIS & Data Systems
TimingAnnual/current-year requirement; exact 2026 upload window pending primary notice
Applies toSchool districts, county offices of education and charter schools under their respective EC 52065(c) pathways
Authority and scopeState statutory duty under EC 52065(c); CDE administrative window must be verified separately

In Plain Language: Post the correct current-year LCAP to the Dashboard, in addition to required website posting and submission to reviewing authorities.

Why this matters

Keep the allocation, reporting cycle, responsible entity and receiving system explicit. A county planning date, a historical portal window and a statutory deadline are different kinds of evidence.

Ownership and recipient

Responsible owner: LEA LCAP lead with authorized Dashboard Coordinator/Authorizer. Recipient: California School Dashboard performance overview through the CDE-designated process.

Requirement, applicability and cycle controls

  • EC 52065(c)(1)(A): district plan must be board-adopted and county-superintendent-approved under the referenced statutory pathway.
  • EC 52065(c)(1)(B): COE own-plan posting follows county-board adoption and the applicable state approval pathway. This is distinct from the COE’s district-review function.
  • EC 52065(c)(1)(C): charter plan must be governing-body-adopted and submitted to its chartering authority and county superintendent, or only to the county if the county board is the chartering authority. Do not invent district-style county LCAP approval for charters.
  • CDE must notify LEAs and ensure compliance under EC 52065(c)(2). A historical 2024 CDE upload notice establishes the process, not the 2026 cutoff or component list.
  • Website posting, submission for statutory review and Dashboard upload are separate completion states. One does not prove the others.

Operational workflow

  1. Confirm the LEA type, current school year and correct final adopted/approved/submitted plan.
  2. Retrieve the issuing CDE cycle-specific notice and verify window, authorized role, file format and component order.
  3. Reconcile the upload PDF with the final public and approved plan; avoid obsolete drafts.
  4. Complete the designated upload and retain the receipt or saved state.
  5. Check the Dashboard public link for the correct year and complete file; reconcile any correction.

Evidence to retain

  • Applicable CDE notice
  • Final current-year plan and entity-specific adoption/approval/submission evidence
  • Upload confirmation
  • Public Dashboard link verification

Sources and authority

Authority and source-version guide · Annual Compliance Calendar

Targeted source/conflict review: October 21, 2026. Pending items above are unresolved verification questions, not confirmed statewide deadlines. Local preparation steps do not create new statewide filings.