Public Notice, Hearing, Adoption, Submission & Posting Requirements

In Plain Language: A public board action is not complete merely because the board voted in an open meeting. Before the vote, the district may need to post an agenda, make documents available for inspection, publish a hearing notice, provide written-comment opportunities, consult advisory groups, and hold a separate public hearing. After the vote, the district may need to submit the adopted output, post it prominently online, notify families or agencies, preserve the record, and verify that the public can actually reach it. Each step serves a different purpose and needs its own evidence.

The recurring misunderstanding

Districts often treat “72-hour notice” as the entire compliance test. It is usually the starting point for a regular board meeting—not a substitute for a program-specific hearing notice, newspaper publication, document-inspection period, advisory process, adoption sequence, filing deadline, or website-posting requirement.

The operational solution

Build one public-process checklist for each output. Name the authority, meeting type, notice method, posting locations, document version, public-comment route, hearing and adoption dates, submitter, recipient, public URL, accessibility review, confirmation, and retained evidence.

Five controls that should not be collapsed

Control	What it accomplishes	Evidence to retain
Notice and agenda posting	Tells the public when and where the body will meet and describes the business it will discuss or transact.	Final agenda, posting timestamp, physical location, website URL, screenshot or publication record, agenda description, and accommodation instructions.
Public inspection and comment	Gives the public meaningful access to the proposal and a route to comment before the decision.	Public-review copy, location and dates available, direct URL, comment instructions, accessible formats, written comments, and responses when required.
Public hearing	Creates the formal opportunity required by the applicable program or fiscal authority to receive recommendations and comments.	Hearing notice, agenda, proposal reviewed, staff presentation, public comments, minutes, recording, and revisions or responses.
Adoption or approval	Records formal action by the body authorized to approve the output.	Adoption agenda, complete final attachment, resolution or motion, vote, minutes, signed certification, and effective version.
Submission and publication	Delivers the adopted output to the required reviewer or system and makes it available to the public as required.	Submission receipt, email or system confirmation, approval correspondence, final public URL, posting date, accessibility check, notices, and archived copy.

Regular and special meeting notice

Meeting type	General posting rule	Operational cautions
Regular meeting	Agenda posted at least 72 hours before the meeting in a freely accessible public location and on the district website when applicable.	The online agenda must be reachable through the statutorily required prominent direct route or compliant agenda platform and be retrievable, downloadable, searchable, machine readable, and available without charge or reuse restrictions.
Special meeting	Call and notice generally delivered and posted at least 24 hours before the meeting, including physical posting in a freely accessible location and website posting when applicable.	The notice must specify the time, place, and business to be transacted or discussed. Other business may not simply be added at the meeting.
Emergency or other exception	Special statutory rules apply only when the defined conditions are met.	Do not use an exception as a routine cure for missed planning or late materials. Obtain qualified counsel and preserve the findings and procedure supporting the exception.

What the public should be able to find

The meeting: date, time, physical location, remote-access information when used, and instructions for public participation.
The business: a clear agenda description identifying the actual plan, report, hearing, approval, or adoption under consideration.
The document: the version being reviewed or adopted, available early enough and through the method required by the applicable authority.
The comment route: how to provide oral or written comments, applicable deadlines, and language, disability, or other access supports.
The accommodation route: how, to whom, and when a disability-related modification, accommodation, auxiliary aid, or service may be requested.
The final action: the adopted version, vote or resolution, effective reporting year, submission status, and final public location.

Common annual school-district examples

Output or process	Broad public-process picture	Common failure
LCAP — school district or COE	Complete required consultation and advisory review; make the proposal available; hold the required public hearing; adopt the LCAP at a later public meeting, not on the same day as the hearing; coordinate adoption with the budget; submit within the applicable period; and prominently post the complete adopted plan.	Using one meeting for hearing and adoption, incomplete attachment, missing advisory evidence, late submission, or posting the plan where it is difficult to find.
LCAP — charter school	Apply current charter-specific consultation, hearing, adoption, submission, and posting rules. Current CDE guidance allows the public hearing to occur at the same meeting as adoption if the hearing and opportunity for recommendations and comments occur before adoption.	Copying the district sequence without checking charter rules—or assuming charter flexibility eliminates the hearing, submission, or homepage-posting duties.
District budget	Make the proposed budget available for public inspection, publish the date, time, and place of the hearing and the inspection information through the required method, post the hearing agenda, hold the public hearing, adopt by the statutory deadline, and file the adopted budget.	Relying only on the board agenda when separate newspaper publication and inspection information are required.
Dashboard local indicators	Annually measure progress using the applicable requirements, report results as a non-consent item at the same public meeting at which the LCAP is adopted, and submit results through the current Dashboard process.	Placing results on consent, omitting the public presentation, missing the submission window, or failing to retain confirmation.
SPSA	Use the Schoolsite Council and applicable advisory process to develop the plan, obtain local governing-board or body approval, and maintain the SPSA as a public document. CDE states that statute does not impose one statewide SPSA approval deadline; the LEA must establish a compliant local timeline.	Treating SSC discussion as governing-board approval, approving a plan after expenditures begin without a controlled local process, or being unable to produce the final public version.
SARC	Complete and validate one report for each applicable school; publish and submit by February 1; notify parents of availability; provide online access when applicable and paper copies upon request.	Posting an old report as current, broken direct links, no family notice, inconsistent paper and online versions, or no submission confirmation.
Comprehensive School Safety Plan	Use the applicable school-level development and public-input process, review and adopt annually by March 1, forward the plan for district or COE approval, and meet related reporting duties while protecting tactical security information.	Treating the SARC safety-plan summary as the plan itself, missing annual adoption or approval, or publicly disclosing protected tactical content.

The LCAP and budget sequence for school districts

Before the hearingsComplete required development and advisory processes. Consult required educational partners, present the draft to applicable advisory committees, receive comments, prepare required written responses, and make the proposals available for review.
Notice the hearingsApply both meeting and program-specific notice rules. Post the regular-meeting agenda for the full 72 hours in the required physical and online locations. Complete the budget publication and inspection notice required by current fiscal guidance.
Hold the hearingsReceive public recommendations and comments. Identify the LCAP and proposed budget distinctly, preserve the materials presented, and document comments and responses or revisions.
Allow the sequence to advanceDo not adopt on the same day as the public hearings. Prepare the final LCAP, Budget Overview for Parents, action tables, proposed budget, and any required changes for the later adoption meeting.
Post the adoption agendaBegin a new, complete notice period. Identify the actual adoption actions and attach or clearly make available the final versions the board will consider.
Adopt in proper orderAdopt the LCAP before the budget when no effective LCAP or annual update covers the budget year. Complete both actions by the statutory deadline and preserve the votes and adopted versions.
SubmitDeliver the complete adopted documents to the correct recipient. Current 2026–27 CDE guidance requires LCAP submission within five days of adoption; districts submit to their COE.
Post and verifyProminently publish the complete adopted LCAP package. Confirm the homepage route, Budget Overview placement, full document order, accessibility, reporting year, direct download, and any required Federal Addendum posting.

Preflight: before releasing the agenda

Confirm whether the meeting is regular, special, emergency, advisory, school-level, or governing-board level.
Confirm every applicable authority and whether it requires a hearing, separate meeting, publication, inspection period, advisory review, written response, or particular agenda treatment.
Calculate the full notice period backward from the meeting time; do not count from the end of the workday.
Verify that the physical posting location remains freely accessible throughout the entire required period.
Verify that the online agenda appears through the required prominent direct link or compliant agenda platform and is freely downloadable and searchable.
Use an agenda description that identifies the real action: review, hearing, approval, adoption, amendment, certification, or informational presentation.
Attach or make available the correct document version and identify where the public may inspect it.
Include accessibility and accommodation instructions and confirm that documents are usable by people with disabilities.
Complete required newspaper, mailed, posted, direct, language-access, or program-specific notice separately from the Brown Act agenda.
Preserve contemporaneous evidence of every posting method, location, date, time, version, and person completing the action.

Postflight: after the board acts

Confirm the motion, resolution, vote, reporting year, and adopted attachment match the intended action.
Save a locked copy of the exact document adopted—not a later working draft with the same filename.
Obtain signatures, certifications, minutes, or other authorization required for submission.
Submit to the correct recipient or system within the applicable period and preserve the receipt.
Respond to reviewing-agency questions and track revisions without overwriting the adopted baseline.
Post the complete final output at the required website location and label its year and status clearly.
Test the public URL while logged out, on mobile, and without relying on staff-only permissions.
Verify accessibility, document order, download behavior, language access, and paper-copy availability where applicable.
Update the annual output register with adoption, submission, approval, publication, amendment, and archive evidence.

Decision routes

The agenda was posted 72 hours early, but the building was locked overnight

Action: Treat the physical-posting requirement as unresolved and immediately consult qualified counsel about whether the meeting should be postponed and renoticed. Preserve the actual access conditions and timestamps.

Control: A website posting does not erase the separate requirement for a freely accessible physical location when that requirement applies.

The agenda is online, but only inside several menus or behind an account

Action: Correct the posting route using the current statutory direct-link or compliant agenda-platform requirements and evaluate whether a new notice period is necessary.

Control: “Technically somewhere on the website” is not the same as prominently and freely accessible in the required open format.

The plan attachment changes after the agenda is posted

Action: Determine whether the change is clerical or material, when and to whom the revision was distributed, whether the public received timely access, whether the agenda description still covers the action, and whether program-specific review must be repeated.

Control: Preserve both versions and the distribution record; do not silently replace the attachment.

The district wants to hold the LCAP hearing and adoption on the same date

Action: For a school district or COE, schedule adoption at a later public meeting consistent with the applicable Education Code sequence. Apply a new agenda-posting period for the adoption meeting.

Control: Do not borrow the current charter-school approach for a district or COE.

A final deadline is approaching and the notice period was missed

Action: Escalate immediately to the superintendent, board office, responsible program and fiscal leaders, receiving agency, and qualified counsel. Identify lawful scheduling and notice options and document the response.

Control: Do not backdate evidence, abbreviate the notice period, invent an emergency, or describe an inaccessible posting as timely.

The board adopted the document, but the wrong version was posted or submitted

Action: Preserve the adopted, posted, and submitted files separately; compare them; identify whether correction, board action, resubmission, republication, or notice is required; and obtain direction from the reviewing agency and counsel.

Control: Do not overwrite the evidence or assume that matching filenames prove identical content.

What can happen when the process fails?

A Brown Act challenge, demand to cure or correct, invalidation risk, injunction, or other legal remedy may be raised depending on the violation and circumstances.
The county office, CDE, authorizer, auditor, or another reviewer may require correction, additional evidence, resubmission, or a revised public process.
An LCAP-related Uniform Complaint Procedures review may find that required consultation, committee presentation, written response, hearing, adoption, or posting steps were not completed.
A plan, budget, application, or report may be considered late, incomplete, inaccessible, unsupported, or not properly adopted.
Funding, approval, accountability status, audit results, or eligibility for assistance may be affected under the rules governing the particular output.
Even when an action is not invalidated, the district can lose public trust and institutional knowledge when it cannot prove what was posted, reviewed, adopted, submitted, and published.

Official resources

Source review completed September 6, 2026. Verify the current Brown Act, Education Code, entity type, legislative-body status, regular or special meeting type, agenda and packet rules, physical and online posting locations, hearing and public-inspection requirements, advisory processes, accessibility and language access, output-specific adoption sequence, annual deadline, submission recipient, publication location, records-retention practice, local board policy, county guidance, and qualified legal advice before acting. This broad operational overview does not cover every exception or substitute for counsel.