Major Planning, Accountability & Public-Reporting Outputs

In Plain Language: California attempted to streamline school planning, and the former Single Plan for Student Achievement eventually became the School Plan for Student Achievement. Yet consolidation did not eliminate the surrounding output environment. LCAPs, SPSAs, SARCs, improvement plans, local-indicator reports, federal addenda, safety plans, funding applications, and state accountability displays still serve different laws, audiences, levels, timelines, and approval processes. They may reuse the same data, but one output rarely substitutes for all the others.

Why the burden persists

Each output answers a different accountability question: What will the LEA do? What will the school do? What must the public know? What does the state display? What funding conditions apply? What evidence must be certified? Different purposes produce overlapping—but not interchangeable—documents and submissions.

What can be unified

Districts can unify definitions, source data, calendars, ownership, engagement evidence, measures, fiscal reconciliation, document control, and review routines. The goal is not to pretend there is one report; it is to produce many required outputs from one governed evidence environment.

The major output landscape

Output	Level and cadence	Primary purpose	Operational destination
Local Control and Accountability Plan (LCAP)	LEA; multiyear plan developed and acted upon through an annual cycle	Connect needs, educational-partner input, goals, actions, services, measures, and resources across LCFF priorities.	Local review and adoption, applicable external review or approval, prominent public posting, and ongoing implementation.
LCFF Budget Overview for Parents	LEA; annual component accompanying the LCAP	Provide an accessible fiscal overview and connect major resources with the LCAP.	Attached to and prominently posted with the LCAP.
LCAP Federal Addendum	Eligible LEA; initial approval and locally maintained updates as applicable	Address ESSA LEA-plan provisions for federal Title programs not fully covered in the LCAP.	CDE/SBE approval pathway and posting with the LCAP; applicability depends on ESSA funding.
School Plan for Student Achievement (SPSA)	Applicable school; one-year plan reviewed and updated annually	Connect the school’s needs assessment, goals, strategies, expenditures, implementation, and evaluation.	Schoolsite Council development, local governing-board or body approval, public access, and implementation.
CSI, TSI, or ATSI Plan	Identified school or LEA; conditional and status-dependent	Meet federal school-improvement planning requirements for the applicable assistance status.	Often addressed through the SPSA planning process; specific approval and support routes vary by status.
School Accountability Report Card (SARC)	Applicable school; annual and one year in arrears	Provide standardized public information about achievement, conditions, demographics, staffing, safety, resources, and expenditures.	Family notification, online and paper availability, publication, and CDE submission by February 1.
Dashboard Local-Indicator Results	LEA; annual self-reflection and reporting	Measure and publicly report performance on LCFF priorities for which state-level data are not collected.	Public governing-board presentation associated with LCAP adoption and LEA reporting through the Dashboard process.
California School Dashboard	State-produced display for LEAs, schools, and student groups; periodic release	Report performance on state and local indicators and support accountability and continuous improvement.	Published by CDE using state-calculated measures and locally reported indicators; relies heavily on LEA-certified source data.
Comprehensive School Safety Plan (CSSP)	School; reviewed, updated, and adopted annually	Address school risks, emergency readiness, required procedures, and a safe learning environment.	School development and public input, annual adoption, district or COE approval, implementation, and limited public reporting; tactical information requires careful protection.
Consolidated Application and Reporting System (CARS) submissions	LEA; multiple release windows and program-dependent forms	Apply for funding, certify assurances, submit budgets, report expenditures, and meet state and federal program conditions.	Electronic certification and submission to CDE through changing annual and program-specific windows.

Three kinds of output

Output type	Examples	Primary control
Locally developed plans and reports	LCAP, Budget Overview for Parents, SPSA, SARC, CSSP, applicable improvement plans	Content development, engagement, approval, accuracy, publication, accessibility, implementation, and revision.
Electronic applications, certifications, and submissions	CARS forms, LCAP Federal Addendum submission, local-indicator reporting, CALPADS certifications	User authorization, source reconciliation, workflow status, certification authority, deadline, submission receipt, amendment, and retained evidence.
State-produced downstream outputs	California School Dashboard, DataQuest reports, state accountability displays, downloadable public data	Upstream LEA data quality, certification, preview, correction opportunities, interpretation, and public communication.

Why one plan does not replace the others

Different level: the LCAP is an LEA plan, while the SPSA and SARC operate at the school level.
Different function: a plan describes intended improvement work; a report card publishes standardized conditions and results.
Different audience: governing bodies, educational partners, families, CDE reviewers, program staff, auditors, and the general public need different evidence.
Different authority: LCFF, ESSA, school-accountability, safety, funding, and program rules create separate requirements.
Different time: planning, source-data certification, state calculation, fiscal reporting, publication, and annual evaluation occur on different calendars.
Different granularity: a districtwide measure can conceal school or student-group differences required in another output.
Different governance: Schoolsite Council development, advisory review, public hearing, governing-board action, electronic certification, and state approval are not interchangeable.

Build one governed output system

InventoryName every applicable output. Record authority, purpose, level, population, cadence, deadline source, destination, public status, and conditional triggers.
AssignSeparate accountable ownership from contributing work. Name the executive owner, process owner, data owners, fiscal reviewer, program reviewers, approver, submitter, publisher, and backup.
MapConnect each output to its source evidence. Record systems of record, definitions, reporting periods, transformations, certified snapshots, local narratives, and known limitations.
CalendarTrack dependencies, not only final deadlines. Include source availability, extraction, school review, corrections, engagement, fiscal close, approval, publication, submission, amendment, and archive dates.
ReconcileCompare overlapping claims before release. Explain valid differences and correct errors across LCAP, SPSA, SARC, Dashboard, CARS, CALPADS, budget, and local communications.
CertifyPreserve the exact approved and submitted state. Keep the artifact, version, source snapshot, authorization, receipt, public URL, and later correction history.
UseReturn the outputs to operational decision-making. Public reporting should feed needs assessment, resource allocation, implementation review, and the next planning cycle.

Suggested output-register fields

Field group	Fields to maintain
Identity	Stable output ID, official name, acronym, entity or school, reporting year, version, and current status.
Applicability	Authority, entity type, funding or program trigger, school-status trigger, population, and documented applicability decision.
Timing	Cycle, source-availability dates, internal milestones, official deadline and source, approval date, publication date, and amendment window.
Ownership	Accountable executive, process owner, contributing offices, data steward, reviewer, certifier, publisher, and backup.
Evidence	Systems of record, extracts, certified snapshots, definitions, reporting periods, fiscal records, engagement evidence, and local narratives.
Governance	Required council, advisory, public, governing-body, state-review, approval, or certification steps.
Delivery	Submission system, recipient, confirmation, public URL, accessibility check, language access, paper availability, and archive location.
Correction	Issue, affected outputs, authority, resolution, amended version, resubmission, republication, and notification.

Cross-output reconciliation questions

Do LCAP and SPSA goals, actions, measures, services, and expenditures describe a coherent strategy at the correct level?
Do SARC narratives and tables agree with certified source data and explain differences from LCAP or Dashboard displays?
Do local-indicator results presented to the governing body match what was submitted for Dashboard publication?
Do CARS applications, budgets, expenditures, assurances, and the LCAP Federal Addendum support the same federal-program story?
Can each public number be traced to its definition, reporting period, population, calculation, source snapshot, and approval?
When one source is corrected, is there a controlled method to identify every downstream output that may also require review?
Can another qualified employee locate the current instructions, source files, working papers, status, credentials, approvals, and submission evidence?

Official starting points

Source review completed September 6, 2026. This overview intentionally identifies major output families rather than every California school or district reporting obligation. Verify entity type, school inventory, funding, program participation, assistance status, current templates, deadlines, submission systems, approval and publication requirements, data definitions, language and accessibility duties, and local governance before acting. Use current official instructions and qualified program, fiscal, data, and legal review for each applicable output.