Why would a bill that carefully protects churches, veterans’ events, and homeless shelters from an equal-treatment law forget to protect the contractors who run those same programs? That’s not a rhetorical question. It’s a gap sitting in the enrolled text of Florida’s new DEI law, and it’s worth understanding exactly where it is.
S1134, “Official Actions of Local Governments,” is now Chapter 2026-43, effective January 1, 2027. It bars counties and municipalities from funding, promoting, or officially implementing DEI initiatives, voids conflicting local ordinances and programs, prohibits DEI offices, exposes officials who violate the law to misconduct consequences, and lets citizens sue. It also requires local contractors and grant recipients to certify they won’t force their own employees, vendors, or volunteers into DEI-related training or programming.
Give the drafters real credit here, because this bill does something a lot of DEI bans don’t bother to do: it writes out its own exceptions in detail, instead of leaving them to be fought over in court later. Sections 1 and 2 list eight specific carve-outs, applying identically to counties and municipalities. Local governments can still comply with state and federal anti-discrimination law. They can still recognize federal and state holidays and patriotic observances. They can still support single-sex nonprofit programs serving the homeless or at-risk youth. They can still maintain monuments and memorials. They can still issue event permits and provide public safety services on a content-neutral basis. The statute separately states it doesn’t override Florida’s sex-separated facilities law, domestic violence shelter access, Title IX-style sports protections, or existing sex- and race-based public health access laws. Nonelected volunteer boards are exempt entirely.
That list does real work. A broad “no promoting identity-based programming” rule, without exceptions like these, would be an obvious target for a First Amendment or equal-protection challenge the first time it got applied to a veterans’ memorial event or a women’s shelter contract. Florida closed that door before anyone had to sue to open it.
Section 3 creates a new statute, s. 287.139, F.S., requiring any contractor or grant recipient doing business with a county or municipality to certify it won’t use local funds to make its own people “ascribe to, study, or be instructed using materials relating to diversity, equity, and inclusion,” as DEI is defined in the same law’s definitional section.
Read that certification requirement next to the exception list in Sections 1 and 2, and here’s the gap. Section 3’s cross-reference points only to the definition of DEI. It does not point to the eight carve-outs that protect the county or municipality itself when it runs one of those exempted programs directly. A vendor that operates a single-sex homeless-services program on its own time and its own dime, the exact activity Section 1 explicitly protects when a local government does it, has no equivalent protection written into the certification a contractor has to sign. A nonprofit that also organizes a federally recognized patriotic observance faces the same gap. The government’s own hands are protected. The hands of the people it contracts with are not, for the identical activity.
This isn’t a theoretical drafting nitpick. Local government contracting runs through vendors and grant recipients constantly, faith-based service providers, veterans’ organizations, community nonprofits that do exactly the kind of single-sex or observance-based programming Sections 1 and 2 went out of their way to protect. Under Section 3 as written, one of those organizations could sign the required certification, then get challenged by a competitor or a political opponent over programming the statute would call perfectly legal if the county ran it directly instead of contracting it out. That’s not a hypothetical abuse scenario dreamed up to score a point. It’s the plain textual consequence of one section cross-referencing a definition and the next section not cross-referencing an exception.
Nothing here suggests bad faith from the drafters. The far more likely story is that Sections 1 and 2 got their exception list built carefully, probably in direct response to the same First Amendment and equal-protection concerns raised about DEI bans in other states, and Section 3 got bolted on afterward without anyone going back to make sure the certification requirement matched the same map. That’s an ordinary drafting failure, the kind that happens in complex bills with multiple sections built at different points in the process. It doesn’t make the gap less real.
This is a genuinely good bill with one fixable flaw. Public bodies should stop sorting citizens and vendors by identity category, and this law does that well in Sections 1 and 2. The fix is narrow and specific: extend the same exception cross-reference from Sections 1 and 2 into Section 3, so a contractor engaged in activity the law would protect if the government did it directly gets the identical protection when a contractor does it instead. Same conduct, same protection, regardless of whose payroll runs it. Until that fix happens, any contractor running a program that fits one of those eight carve-outs should know exactly where the current law leaves them exposed.
This is our read of the bill. We encourage you to read it yourself and reach your own conclusions.
© 2026 InPublic Systems - All Rights Reserved.
Legislative and policy intelligence for conservative advocacy organizations.
(425) 298-6627