Florida Sunshine Law (Sec. 286.011, F.S.): What Agenda Notice Actually Requires in 2026

Florida's Sunshine Law is among the oldest, broadest, and most aggressively interpreted open meetings statutes in the United States. Section 286.011, Florida Statutes — the operative text — is short enough to read in under five minutes. The body of attorney general opinions, case law, and procedural rules built on top of it is not.

For a clerk, the practical question is rarely "does the Sunshine Law apply." It does. The question is what a posted agenda has to contain, when it has to be posted, how it has to reach the public, and what happens when one of those elements is missing. This piece walks the law as it operates in 2026, with particular attention to the points where the printed-paper era of the original statute now collides with electronic posting, accessibility expectations, and a public that increasingly reads agendas on a phone.

The Statute Itself — Read It Once

Sec. 286.011 has three operative requirements:

1. All meetings of any board or commission of any state agency, authority, or any agency, authority, board, or commission of a county, municipal corporation, or political subdivision, at which official acts are to be taken or at which public business is to be transacted or discussed, must be open to the public.
2. Reasonable notice of all such meetings shall be given.
3. Minutes shall be promptly recorded and shall be open to public inspection.

The constitutional foundation sits one layer above the statute. Article I, Section 24 of the Florida Constitution, adopted by voters in 1992, makes the open-meeting and public-records rights state constitutional rights. That elevation matters: a board that argues "we substantially complied with the statute" must also reckon with a constitutional right of access that is harder to limit by procedural workaround.

Enforcement is genuinely teeth-y. A knowing violation of Sec. 286.011 is a second-degree misdemeanor for each member who participates, punishable by up to 60 days in county jail and a $500 fine. A non-criminal infraction — a violation without the "knowing" element — carries a civil penalty up to $500. And under Sec. 286.011(4), F.S., the Attorney General or any private party can sue to enforce compliance and recover attorney's fees.

What "Reasonable Notice" Has Come to Mean

The statutory phrase is "reasonable notice." The statute itself does not define it. Two sources fill the gap.

The first is the Florida Attorney General's Government-in-the-Sunshine Manual, updated annually. The 2025 edition treats notice as a function of three factors: the importance of the meeting, the public's reasonable expectation of when meetings occur, and the practicality of the method used. Routine, regularly scheduled meetings need less specific notice than special or emergency meetings. A school board's monthly meeting on the second Tuesday is itself a form of standing notice; an unscheduled budget workshop is not.

The second is appellate case law, most importantly Yarbrough v. Young (Fla. 1st DCA 1985) and the line of cases that followed. The doctrinal rule those cases settled is that notice must be sufficiently early and sufficiently public that a reasonable, interested member of the community could attend. Posting an agenda on a courthouse bulletin board the morning of a 9:00 a.m. meeting does not satisfy that standard for a routine meeting; courts have generally treated 24 to 72 hours as the floor for non-emergency action.

The AG has also said, in AGO 2009-26 and related opinions, that an agenda — separate from the notice of meeting itself — must list, with sufficient particularity, the items the body intends to act on. "Other business" or "miscellaneous" as a standing agenda item does not give the public meaningful notice of what will be considered. When a board takes action on a matter not described on the agenda, that action is vulnerable to a Sunshine Law challenge unless emergency procedures were followed.

The 2013 Amendment: Sec. 286.0114, F.S.

Sec. 286.011 sets the openness baseline. Sec. 286.0114, added by Ch. 2013-227, Laws of Florida, goes further: it gives the public a statutory right to be heard before a board or commission takes official action on any proposition.

For a clerk, the practical effect is that the agenda must do two things simultaneously. It must list the propositions on which the body will act, and it must build in the structural opportunity for public comment on those propositions before the vote. An agenda that lists an ordinance for adoption but provides no public comment opportunity, or that puts comment after the vote, is structurally non-compliant — even if the meeting was noticed correctly.

There are exceptions. Sec. 286.0114(3) carves out ministerial acts, emergency situations, quasi-judicial proceedings (which have their own due-process structure), and meetings exempt from Sec. 286.011 by statute. But the exceptions are narrower than they read on first pass, and the burden of fitting an action within one of them falls on the body invoking the exception.

The Digital Posting Gap

Sec. 286.011 was enacted in 1967. It was written for an era when "notice" meant a physical paper posting at the seat of government and a notice published in a newspaper of general circulation. Most of the procedural infrastructure built on top of it — agenda templates, posting locations, newspaper publication — still reflects that era.

Florida law has bolted electronic posting onto that structure through several specific statutes, but it has not replaced the underlying paper model. Sec. 50.0211, F.S., as substantially amended in 2022 and refined since, now authorizes electronic publication of legal notices in lieu of newspaper publication for many local governments — but with specific procedural prerequisites including a one-time published notice, a finding of cost-effectiveness, and the use of a publicly accessible website meeting certain criteria. Sec. 189.015, F.S., separately governs special district notice. The result is a layered scheme in which "posting" can mean four or five different things depending on the type of body, the type of meeting, and what the body's enabling statute provides.

For most clerks, this is the practical state of play:

• The notice of meeting — date, time, location, body name — is published according to whatever statute or charter binds the body, and may be electronic if the body has properly opted in under Sec. 50.0211 or the equivalent.
• The agenda is a separate document. There is no single statutory deadline for agenda posting that applies to all bodies; specific bodies have specific rules (school boards under Ch. 1001 are stricter; municipalities under home rule vary widely). The "reasonable notice" standard of Sec. 286.011 supplies the default floor.
• The agenda packet — staff reports, ordinances, exhibits — is not always required to be posted in advance, but the Public Records Act (Ch. 119, F.S.) makes it available on request the moment it is provided to a board member. Functionally, that means it has to be ready for release before the meeting.

The clerks who run cleanly under this regime publish all three together, on the same page, on a schedule the public can predict — typically the Thursday or Friday before a Monday or Tuesday meeting. The clerks who get into trouble post the notice on time and the agenda late, or post the agenda but make the packet available only at the meeting.

Where the Agenda-Specificity Rule Bites

Two patterns produce most of the Sunshine Law complaints clerks see in 2026, and both involve agenda specificity rather than notice timing.

1. Consent agendas with bundled action

The consent agenda is a useful device for moving uncontroversial items in a single vote. It becomes a problem when items of substance — a multi-year contract, a personnel decision, an easement granting development rights — are quietly placed on consent. The public's "reasonable notice" argument under Sec. 286.011 strengthens considerably when the agenda describes a consent item in generic terms ("ratification of administrative actions") rather than naming the specific contract or decision. AG opinions have made clear that "with sufficient particularity" is the standard, not "with bureaucratic abbreviation."

2. Walk-on items and after-agenda action

An agenda item added at the dais — sometimes called a walk-on, sometimes a "matters not on the agenda" insertion — is the most common source of Sunshine Law challenges. The doctrinal rule is straightforward: action on a matter not previously noticed and listed with particularity is presumptively invalid, absent a genuine emergency and a recorded finding to that effect. The 2013 amendment in Sec. 286.0114 reinforced this by tying the right to be heard to the specific propositions on which the body intends to act. If a proposition appears for the first time at the dais, the public had no opportunity to be heard on it.

Two procedural protections handle these cases cleanly: a written agenda-amendment procedure adopted by the body (typically requiring a supermajority and a recorded finding), and the practice of carrying a non-noticed item to the next regular meeting rather than acting on it.

Notice + Accessibility: The Intersection That Did Not Exist in 1967

The Sunshine Law does not, by its own text, require that an agenda be readable by assistive technology. Florida does not have a state-law analog to Colorado's HB 21-1110 imposing WCAG 2.1 AA conformance on local government digital content. But two doctrines push toward the same practical result.

The first is Title II of the federal ADA, which applies to every Florida local government and requires effective communication regardless of disability. A meeting agenda that cannot be read by a blind constituent's screen reader is a Title II problem before it is anything else — and the U.S. Department of Justice's 2024 final rule under Title II tightens that expectation by adopting WCAG 2.1 Level AA as the technical standard for state and local government web content.

The second is the "reasonable notice" standard itself. If the only practical way to access an agenda is a scanned PDF that a screen reader treats as a blank page, a complainant has a respectable argument that notice was not reasonable as to them. The combination of Sec. 286.011's openness right, Article I, Section 24 of the constitution, and the federal effective-communication obligation does work that no single statute does alone.

The implication for clerks is that the digital format of the agenda matters even where the Sunshine Law itself does not address it. Posting on time is necessary but not sufficient; posting in a format the public can actually consume is part of what "reasonable notice" has come to mean in practice.

Cure and Remediation

A defective agenda or notice is not always fatal to the underlying action. Florida courts have recognized a doctrine of "cure" or "remediation" — most clearly articulated in Tolar v. School Board of Liberty County (Fla. 1981) — by which a board can revisit an action taken in violation of the Sunshine Law in a properly noticed open meeting where the entire matter is reconsidered de novo. The action ratified in the cure meeting then becomes the operative decision.

The mechanics matter. A cure meeting must be more than a vote-to-ratify; it must be a full reconsideration where the public has notice, the propositions are listed with particularity, public comment is taken, and the body acts as if the prior decision did not exist. Half-measure cures — a single-item "ratification" vote with no real deliberation — are routinely struck down.

For a clerk discovering a Sunshine Law issue after the fact, the practical sequence is: notify the body's attorney, identify the specific defect, decide between rescission and cure, place the item on the next meeting's agenda with full notice and packet materials, and document the procedural history in the minutes. None of those steps require new software. All of them require an agenda workflow that can describe an item with particularity, route the packet to the public on time, and create a clean record.

What a Compliant Florida Agenda Workflow Actually Looks Like

Stripping out the doctrinal and constitutional layers, a Florida clerk running a clean Sunshine Law operation in 2026 typically has these elements in place:

• A standing schedule for regular meetings, adopted by the body and published on a permanent page of the agency's website, so the date and time of routine meetings are themselves a form of standing notice.
• A documented notice deadline for non-emergency meetings — most commonly seven days for special meetings, longer for budget hearings and other items that have their own statutory notice requirements. The deadline is policy, not statute, but having it written and followed defends "reasonable notice" if challenged.
• An agenda template that names each action item with particularity. Not "Old Business — Item 3," but "Adoption of Ordinance 2026-04 amending Chapter 22 of the City Code regarding short-term rentals."
• A consent agenda standard that excludes contracts above a stated dollar threshold, personnel actions, and any item likely to draw public interest. Consent is for ministerial unanimity, not controversial items in disguise.
• A walk-on procedure requiring a supermajority and a recorded finding of emergency, with a default of carrying non-noticed items to the next meeting.
• A public comment slot before action on each item (or grouped public comment with the proposition open to be heard), satisfying Sec. 286.0114.
• An accessible posting: agenda, packet, and notice on the same page of the website, posted on a predictable schedule, in a format the public can actually open and read — including users on phones and users of assistive technology.
• Minutes captured promptly and made available within the same posting workflow, satisfying both Sec. 286.011(2) and Ch. 119 requests for the underlying records.

None of these are new in 2026. What is new is the operational reality that all of them can be true at once only if the agenda pipeline is structured rather than improvised. A workflow built on emailed Word files, ad-hoc PDF assembly, and a website update done by hand the morning of the meeting can satisfy any one of these requirements; it will reliably satisfy all of them only by accident.

What to Audit This Quarter

If you are a Florida clerk reading this and trying to decide where to spend the next two weeks, three audits produce more compliance benefit per hour than anything else:

1. Pull last quarter's agendas and grade each action item for particularity. Anything you cannot, on its face, explain to a member of the public — without opening the staff memo — is a candidate for redrafting. The bar is not "the staff understood it"; the bar is "a reader of the agenda alone understood what would be decided."
2. Trace the publication chain for one regular meeting from start to finish. When did the notice appear? When did the agenda appear? When did the packet become available? Was the packet retrievable by a member of the public without a login, a phone call, or a public records request? Mismatches between these dates are where complaints originate.
3. Read the AG's Sunshine Manual chapter on agenda particularity and walk-on items. It is shorter than this post. Compare what it describes to what your last special meeting actually did. Many agencies find at least one procedural habit that does not survive scrutiny — usually a consent agenda practice or a walk-on rule.

The Sunshine Law Rewards Boring

Most Sunshine Law trouble in Florida is the product of small, accumulated procedural drift — not malice, rarely even negligence, more often the slow erosion of habits that began as documented practice and became improvisation. The agencies that go years without a meaningful complaint tend to look slightly over-procedural to an outside observer: agendas are posted on the same day every cycle, items are named the same way every time, consent is reserved for the same narrow category of actions, walk-ons are rare and documented when they occur.

That predictability is the Sunshine Law's actual standard, even though the word "predictable" appears nowhere in Sec. 286.011. "Reasonable notice" is, in practice, notice the public can rely on without checking the calendar. "Sufficient particularity" is, in practice, an agenda item description that does not require translation. "Right to be heard" is, in practice, a public comment slot the chair does not have to remember to call.

The clerks who run those agendas every week, year after year, are doing the law's actual work. Section 286.011 is the floor underneath that work, not a substitute for it.

Sources: Florida Statute Sec. 286.011 (Public meetings and records) · Florida Statute Sec. 286.0114 (Public meetings; reasonable opportunity to be heard) · Florida Constitution, Article I, Section 24 · Florida Attorney General — Government-in-the-Sunshine Manual · AGO 2009-26 on agenda specificity · First Amendment Foundation — Sunshine Law resources · Florida Statute Sec. 50.0211 (Electronic publication of legal notices)