Skip to main content
Vintage computer equipment: Our staff installing the latest upgrades.

SDLA Compliance Resource

Present Community School Plans, Progress and Outcomes Publicly

Bring the applicable community school plan, implementation evidence and outcomes to the school community and governing body, preserving how public input informs improvement.

  • LCAP & Accountability
  • Student Support
  • Fiscal & Budget
  • Governance & Board Approval
TimingAnnual local public-reporting cycle; follow the applicable CDE award/program instructions
Applies toParticipating CCSPP LEAs and schoolsites required to report publicly
Authority and scopeState program/award condition; the LEA schedules public meetings locally

In Plain Language: Bring the applicable community school plan, implementation evidence and outcomes to the school community and governing body, preserving how public input informs improvement.

Why this matters

A report sent to CDE does not by itself establish a public presentation or a current school-community record.

Primary ownership

Community-schools lead, site leaders and governing-board office

Required distinctions and controls

  • CDE’s official funding letter requires public presentation of implementation plans to the governing board and community. The applicable award and current reporting instructions govern additional annual progress/outcome requirements.
  • Separate public presentation from formal plan approval and from site/LEA Annual Progress Report submissions. Do not assign the PDF’s conflicting APR dates to this meeting.
  • Identify county or R-TAC meetings as assistance unless the LEA’s award explicitly requires them.

From plan and progress evidence to a public community school presentation: the SDLA ITO workflow

Public input should visibly shape the updated plan and the CDE reporting file. This SDLA ITO (Input, Transformation, Output) graphic shows how the applicable reporting requirements, the current plan, and privacy-safe outcome evidence become the meeting materials and minutes, the feedback record, and the improvement actions.

SDLA ITO: eleven steps from the applicable reporting requirements, the current plan, and privacy-safe outcome evidence, through mapping requirements to the calendar, assembling evidence, reviewing, presenting, and follow-up, to the meeting materials and minutes, the feedback record, and the improvement actions.
Read down each column, then move to the next: Input identifies what to collect; Transformation covers mapping requirements to the calendar, assembling evidence, reviewing, presenting, and follow-up; Output covers the meeting materials and minutes, the feedback record, and the improvement actions. Follow the applicable CDE award instructions; the LEA schedules public meetings locally.

Open the full-size workflow graphic

Recommended LEA workflow

  1. Map the applicable public-presentation and award reporting requirements to the local meeting calendar.
  2. Assemble the current plan, prior-year implementation, service access, spending context and privacy-safe outcomes.
  3. Review the evidence with schoolsite and partner owners and explain unavailable or incomplete measures.
  4. Present through the applicable school-community and governing-body processes and record input.
  5. Assign follow-up actions and connect the public record to the updated plan and CDE reporting file.

Evidence to retain

  • Meeting agenda and public materials
  • Plan and progress evidence
  • Presentation/minutes record
  • Feedback and improvement actions

Related calendar resources

Official guidance and help

Return to the Annual Compliance Calendar

Reviewed October 21, 2026. Confirm the current agency instructions, applicable funding year, recipient scope, local policy and final submitted or approved state before acting. Recommended preparation steps support the named requirement and do not create an additional statewide filing deadline.