Florida's AI Bill of Rights Failed Again. Here's What That Means for Your Firm.
Florida's House didn't just reject the AI Bill of Rights. It didn't even show up.
On Day 1 of the April 28 special session, House Speaker Daniel Perez made clear that no AI bills would be filed in the House. Not tabled. Not amended. Not debated. The session will run through May 1 focused on redistricting only. The AI Bill of Rights is dead for 2026.
Governor DeSantis's SB 482 had passed the Florida Senate 35-2 in February. The House killed it in March without a floor vote. DeSantis forced a special session specifically to bring it back. Perez refused again — on the first day, before any floor proceedings.
Here is what that outcome tells you about AI regulation right now, and what it actually means for your compliance obligations.
What Happened in Florida and Why
The story is not complicated once you see the political structure.
Florida House Speaker Daniel Perez has opposed SB 482 from the beginning, citing alignment with the Trump administration's position: AI regulation belongs at the federal level, not state legislatures. When SB 482 passed the Senate with near-unanimous bipartisan support in February, Perez simply refused to schedule a House floor vote. The bill died without being read.
DeSantis called the special session to force the issue. Perez held firm — and eliminated the question entirely by declining to file AI bills in the House at all.
The stated reason: federal preemption. The Trump administration supports legislation — including proposals like the TAKE IT Act — that would establish a single federal AI framework and explicitly override state AI laws. House Republicans have used that argument as cover to block DeSantis's consumer protection bill twice, aligning themselves with an AI industry that has contributed substantially to Florida political campaigns.
The practical result: Florida joins a growing list of Republican-controlled states that are deferring state AI regulation to a federal framework that does not yet exist.
The Political Pattern That Now Matters for Your Firm
Florida is not an isolated case. It is the most visible example of an emerging divide in how states are approaching AI regulation.
States passing AI laws: Washington, Oregon, Georgia, Colorado, New York, California, Illinois — all have enacted AI laws or are on the verge of signing them. Most have Democratic-leaning legislatures or governors willing to move ahead of federal action.
States deferring: Florida, Texas, and a number of Republican-controlled states are explicitly waiting for federal regulation, citing the preemption argument. Several states have seen AI bills advance and stall on the same dynamic.
For professional services firm owners, this pattern is information — not comfort.
Here is what the divide means in practical terms:
Your compliance obligation is not driven by your firm's state. It is driven by your clients' states.
A Florida accounting firm with clients in Colorado, Washington, and Oregon has active compliance obligations in all three of those states — regardless of what Florida does. State AI laws apply based on where your clients are located. Florida failing to pass AI regulation does not affect your compliance posture in states that have.
The States That Are Still Live
Florida's failure does not change any of these:
| State | Law | What's Required | Effective Date |
|---|---|---|---|
| Colorado | ADMT (SB 24-205) | High-risk AI impact assessments; client-facing disclosure; deployer obligations | June 30, 2026 |
| Washington | HB 2225 | Chatbot disclosure at start of every client interaction | June 22, 2026 |
| Oregon | SB 1546 | Same as Washington; private right of action ($1,000/violation) | Jan 1, 2027 |
| Georgia | SB 540 | Chatbot disclosure; parental controls for minors | Pending Gov. Kemp signature |
| Illinois | AEIA | Disclosure for AI use in employment/hiring decisions | Enacted; active |
| New York | Multiple bills | Employment AI decision disclosure | Enacted; active |
Colorado's June 30 deadline is now the most urgent active compliance date in the country for professional services firms. Washington's effective date is June 22 — one week earlier.
If you have been watching the Florida special session and waiting to see how the political winds blow before building your AI compliance program, those deadlines are not waiting with you.
What the Federal Preemption Argument Actually Means for Planning
The argument that killed Florida's bill — federal preemption is coming, so states shouldn't act — deserves a clear-eyed look as a planning assumption.
The case for waiting: If Congress passes a broad federal AI framework with preemption language, it could override the existing patchwork of state laws. Compliance work done now might need to be recalibrated.
The case against waiting:
- No federal AI disclosure framework has passed as of this writing. Congress has proposed several; none have reached final passage.
- Even if a federal framework passes, it will almost certainly require the same core obligation that state laws already require: disclosure that a client is interacting with AI. The fundamental compliance posture does not change.
- Several enacted state laws — including Colorado's ADMT and Oregon SB 1546 — include private right of action provisions. Non-compliance between now and any federal preemption date is a live liability risk, not a deferred one.
The practical planning posture: Build a basic AI disclosure framework now, designed to be portable. One standard disclosure template. One engagement letter paragraph. One annual review cycle. That framework will satisfy any federal standard that follows, because federal requirements will almost certainly require the same core disclosure that state laws already do.
You are not building for Florida. You are building for your client states.
What Florida-Focused Firms Should Actually Do
If the majority of your clients are in Florida and you were holding on to see what happened before taking action:
The immediate compliance pressure is lower. There is no Florida AI law effective July 1. You have one fewer state deadline to hit this summer.
What you still have is compliance obligations in every other state where your clients are located. And an AI landscape that will not stay static.
Here is the practical action for a Florida-based firm:
Step 1: Map your client states. Where do your clients actually come from? List your top three client markets by revenue or client count. That list tells you which AI laws are live compliance requirements for your firm today.
Step 2: Check your exposure in those states. If any of your top three client markets include Colorado, Washington, Oregon, Georgia, Illinois, or New York — you have an active compliance obligation right now, regardless of what Florida does.
Step 3: Build the minimum viable compliance framework. This is three things:
- A one-sentence disclosure at the start of every client-facing AI interaction
- One paragraph added to your engagement letter covering AI use in service delivery
- A 30-minute annual review cycle to catch new state laws as they're enacted
That framework, built once, is your portable compliance posture for the patchwork of state laws that currently exist and for any federal framework that follows.
Step 4: If you have no multi-state client exposure — your firm is genuinely Florida-only — then your immediate compliance pressure is low. The professional standard is still to add an AI disclosure to your client agreements. It costs 15 minutes and demonstrates good-faith practice when the conversation inevitably comes up with clients or professional liability insurers.
What Comes Next
Florida killing this bill twice tells you something about Republican-state AI regulation timing. But it does not tell you that AI compliance will not come to Florida-based firms.
The trajectory is clear: more states will pass AI laws, a federal framework will emerge in some form, and the baseline disclosure obligation — tell your clients when they're interacting with AI — will become a universal professional standard within the next 12-24 months.
The firms that will handle this most efficiently are not the ones who waited. They are the ones that built a simple, portable compliance framework now — one that adapts as the standards evolve — rather than scrambling to retrofit their client agreements, chatbot platforms, and service delivery documentation under deadline pressure.
Florida's House bought Florida-focused firms a temporary reprieve. It is breathing room, not a permanent exemption.
What to do this week:
Map your clients by state. If any of your top three client markets have enacted AI laws (check the table above), start with the multi-state AI compliance guide. The Colorado and Washington deadlines are in June — they are the active priority now.
If your firm is genuinely Florida-only: open your engagement letter template and add one paragraph disclosing that you use AI-assisted tools in service delivery. Fifteen minutes. You are ahead of the compliance gap before it reaches Florida.
Published April 28, 2026. Florida AI regulation developments will be tracked in future issues of The Crossing Report. Subscribe here.
Related reading:
Frequently Asked Questions
Does Florida failing to pass AI regulation mean I don't need to worry about AI compliance?
No. Florida firms serving clients in states that have enacted AI laws — Colorado, Washington, Oregon, Georgia, Illinois, New York — are still subject to those states' compliance requirements. State AI law compliance is based on where your client is located, not where your firm is headquartered. A Florida accounting firm with clients in Colorado still faces the ADMT compliance deadline of June 30, 2026.
What is the federal preemption argument that killed Florida's AI Bill of Rights?
Florida House Speaker Daniel Perez — aligned with the Trump administration's position — argued that AI regulation should happen at the federal level rather than state by state. The Trump administration has supported legislation that would establish a single federal AI framework and potentially preempt state laws. This argument gave House Republicans cover to block DeSantis's bill twice.
If federal AI regulation passes, does it replace state AI laws already enacted?
It depends on the preemption language in any federal bill that passes. Broad preemption would override state laws like Colorado's ADMT, Washington HB 2225, and others already enacted. Narrow preemption (setting a floor, not a ceiling) would allow states to keep stricter laws. As of this writing, no federal AI disclosure framework has passed, and none of the enacted state laws have been superseded. Your compliance obligations under enacted state laws remain active.
Which states are most urgent for professional services AI compliance right now, given Florida's failure to pass?
Colorado (ADMT, effective June 30, 2026) and Washington (HB 2225, effective June 22, 2026) are the most urgent active deadlines. Oregon SB 1546 takes effect January 1, 2027. Georgia SB 540 is pending Governor Kemp's signature. Illinois and New York have active employment AI disclosure requirements. For most professional services firms with multi-state client exposure, Colorado and Washington are the immediate priorities.
Should Florida-focused firms still build an AI compliance program?
Yes, for two reasons. First, your compliance obligation is driven by where your clients are, not where your firm is. If you have clients in any state that has enacted AI disclosure laws — and most multi-state firms do — you need a compliant disclosure program. Second, federal regulation is coming in some form. Firms that build a basic AI disclosure framework now (one engagement letter paragraph, one chatbot disclosure template) will adapt to federal requirements at minimal additional cost. Waiting means doing the same work under time pressure later.
Get the weekly briefing
AI adoption intelligence for accounting, law, and consulting firms. Free to start.
Related Reading
This is the kind of intelligence premium subscribers get every week.
Deep analysis, cross-sector patterns, and the frameworks that help professional services firms make the crossing.