SDLA Planning & Accountability Resource
Aligning the LCAP and SPSA
A shared planning approach that connects LEA priorities and resources with school-level needs, strategies, expenditures, implementation, and measurable outcomes.
In Plain Language: Alignment does not mean copying the same goal into two documents. It means that the LEA and each school use compatible evidence, priorities, language, measures, resource assumptions, and review routines while preserving the distinct purpose of each plan. The LCAP should explain the systemwide direction and support; the SPSA should show how an individual school responds to its own evidence and implements coherent strategies.
LCAP: LEA-level direction
The LCAP addresses the LEA’s students, schools, state and local priorities, educational-partner engagement, goals, actions, services, measures, and resources. It identifies systemwide and differentiated supports and explains how the LEA intends to improve outcomes.
SPSA: school-level action
The SPSA responds to the school’s comprehensive needs assessment, student groups, programs, improvement status, available resources, and implementation conditions. It translates aligned priorities into school-owned strategies and expenditures.
How the plans should relate
| Planning element | LCAP contribution | SPSA contribution | Alignment test |
|---|---|---|---|
| Evidence | Identifies LEA-wide patterns, student-group disparities, school differences, state priorities, Dashboard results, and system conditions. | Adds school-specific outcomes, classroom and program evidence, local experience, implementation information, and community knowledge. | Do the plans use compatible definitions and acknowledge material differences between LEA and school evidence? |
| Needs and priorities | Establishes system priorities and differentiated needs across schools and student groups. | Prioritizes the school’s needs through its comprehensive needs assessment and applicable program requirements. | Can the school’s priorities be understood within the LEA strategy without erasing legitimate local needs? |
| Goals | Defines broader outcomes and expected progress. | Defines school-level outcomes responsive to the school’s evidence. | Are goals mutually reinforcing, measurable, and free from unexplained contradictions? |
| Actions and strategies | Provides LEA-operated actions, services, infrastructure, staffing, professional learning, and differentiated support. | Defines the school’s strategies, implementation steps, and site-managed activities. | Is it clear what the LEA provides, what the school implements, and where joint work is required? |
| Resources | Identifies LEA-level funding, services, positions, contracts, and allocations. | Identifies applicable school allocations and planned expenditures. | Do both plans and the adopted budget agree about amounts, funding sources, beneficiaries, and ownership? |
| Measures | Uses systemwide and disaggregated metrics to assess progress. | Uses school-level outcome and implementation measures. | Can results roll up or be compared without changing definitions, populations, or time periods? |
| Engagement and governance | Applies LCAP educational-partner, advisory, public-review, and governing-body requirements. | Applies Schoolsite Council and other applicable school-planning requirements. | Were the correct participants involved in each process, with information moving in both directions? |
| Monitoring | Reviews system implementation, outcomes, resource delivery, and differentiated support. | Reviews whether school strategies occurred and produced the intended effect. | Do review routines surface problems early and produce documented corrections in both plans? |
A practical alignment cycle
- Set the planning architectureEstablish common definitions, data sources, roles, calendars, approval points, funding rules, and document-control practices.
- Review prior implementationCompare what the LEA and schools promised with services delivered, expenditures made, participation, outcomes, and unresolved barriers.
- Exchange evidenceProvide schools with timely disaggregated information and invite schools to return context, corrections, local measures, and implementation evidence.
- Reconcile prioritiesIdentify shared needs, school-specific needs, differentiated supports, program requirements, resource inequities, and issues requiring LEA action.
- Design coordinated workSeparate LEA actions, school strategies, and joint responsibilities; then connect each to measures, resources, and milestones.
- Crosswalk before approvalCompare goals, actions, services, allocations, expenditures, student groups, measures, and timelines across the draft plans and budget.
- Monitor togetherUse shared checkpoints to review implementation and outcomes, escalate barriers, correct data, and amend local work when warranted.
Use a shared crosswalk
| Field | What to record |
|---|---|
| Need and evidence | Need statement, affected students, baseline, data source, date, disaggregation, qualitative context, and known limitations. |
| Plan connections | LCAP goal and action, SPSA goal and strategy, applicable CSI/TSI/ATSI or Title I connection, and explanation of the relationship. |
| Responsibility | LEA owner, school owner, supporting departments, educational partners, approval body, and escalation route. |
| Resources | Funding source, planned amount, calculation, position or service, LEA allocation, school expenditure, and fiscal-system reference. |
| Implementation | Start date, milestones, service level, participating population, evidence of delivery, dependencies, and implementation risks. |
| Measurement | Metric definition, numerator and denominator when applicable, source system, frequency, target, reporting level, and responsible analyst. |
| Review decision | Progress, barriers, partner feedback, resource variance, decision to continue or revise, and person authorizing the correction. |
Special alignment conditions
A single-school district or charter school proposes to use the LCAP as the SPSA
Action: Apply Education Code section 64001(j) and current CDE guidance. Confirm that the LCAP includes applicable Title I, Part A expenditures and satisfies the required school-planning and educational-partner conditions.
Control: Do not assume that ordinary LCAP completion automatically satisfies every SPSA or federal schoolwide-program requirement.
A school is identified for CSI, TSI, or ATSI
Action: Confirm the current assistance status, applicable federal planning requirements, required needs assessment and evidence, approval path, and the correct CDE planning resource or template.
Control: Show how the school-improvement strategy and LEA support connect; do not hide the identified need inside a general LCAP action.
The LCAP and SPSA use different data for the same measure
Action: Compare definitions, populations, source systems, extraction dates, school attribution, time periods, suppression, and calculation methods. Preserve a documented reconciliation.
Control: Do not change a value merely to make the plans match; resolve whether the difference is valid or erroneous.
The SPSA includes an expenditure that does not appear in the expected allocation
Action: Reconcile funding source, amount, allowability, budget code, approval, carryover, procurement, and whether the service is LEA-managed or school-managed.
Control: A narrative reference is not evidence that funds were budgeted or spent as described.
A school priority does not appear in the LCAP
Action: Determine whether the issue is school-specific, emerging, already supported through a broader action, or evidence of a missing differentiated LEA response. Document the conclusion and next review point.
Control: Alignment does not require every SPSA activity to become an LCAP action, but significant recurring needs should not disappear at the LEA level without explanation.
Preapproval alignment check
- Current school program and CSI/TSI/ATSI status has been confirmed.
- LCAP and SPSA evidence uses reconciled definitions, dates, populations, and sources.
- Material school needs are represented or intentionally addressed through a documented differentiated route.
- LEA actions, school strategies, and joint responsibilities are distinguishable.
- Funding sources, allocations, positions, contracts, and expenditures reconcile with fiscal records.
- Measures include compatible definitions and can be reviewed at the appropriate level.
- Educational-partner, Schoolsite Council, advisory, public, and governing-body processes have not been collapsed into one another.
- Implementation owners, milestones, evidence, and correction routes exist beyond the adopted documents.
Official resources
- CDE: Planning for the LCAP and School Plan
- CDE: SPSA/LCAP Planning Summary
- CDE: 2026–27 LCFF and Title I, Part A Planning Crosswalk
- CDE: LCAP Template Instructions
- California Education Code § 52062 — School District LCAP Process
- California Education Code § 52068 — County Office LCAP Process
- California Education Code § 64001 — SPSA and LCAP-as-SPSA Conditions
Source review completed September 6, 2026. Verify current LCAP and SPSA templates and instructions, entity type, Title I schoolwide-program status, CSI/TSI/ATSI status, Schoolsite Council and educational-partner requirements, LCAP-as-SPSA eligibility, program and fiscal rules, local allocations, governing-body procedures, and the current planning calendar before acting. This operational introduction does not replace current official guidance or legal advice.