Florida's Permitting Reset: HB 803, HB 927, and the New Operating Discipline for Local Government

HB 803 is considerably broader than the under-$7,500 exemption. The Florida Senate analysis describes a bill that revises the Florida Building Code framework, building permit requirements, inspections, private providers, uniform permit applications, inspection-fee calculations, and private-provider registration, and that establishes a shortened response timeframe for certain permit applications.

The bill also reaches beyond the items addressed below. Among other provisions, it prohibits homeowners' associations from requiring issuance of a building permit as a condition precedent to architectural review (amending s. 720.3035, F.S.), exempts certain temporary residential hurricane and flood protection barriers, and requires that offsite-constructed residential dwellings be permitted as of right in any zoning district where single-family detached dwellings are allowed. A complete legal review should account for the full bill. For local government operations, five areas warrant immediate attention.

A. The $7,500 exemption is not a "no process" provision

HB 803 requires a local government that issues building permits to exempt the owner of a single-family dwelling, or the owner's contractor, from obtaining a building permit for work valued at less than $7,500 on the owner's property (creating s. 553.79(1)(g), F.S.). The exemption carries material limits.

It does not apply to work on property partially or entirely located in a flood hazard area. It does not apply to electrical, plumbing, structural, mechanical, or gas work. And the statute prohibits dividing a construction project into multiple projects to evade the threshold.

The result is less a blanket waiver than a new screening process. At intake, a local government will need to determine:

• Whether the property is a single-family dwelling.
• The stated value of the work.
• The actual nature of the work.
• Whether any portion involves electrical, plumbing, structural, mechanical, or gas work.
• Whether the property is partially or entirely within a flood hazard area.
• Whether the owner or contractor has submitted the required written exemption request.
• Whether documentation establishes the nature and value of the work.
• Whether the project appears to have been divided to evade the threshold.

HB 803 requires the owner or contractor seeking the exemption to submit a written request to the local enforcement agency, together with a copy of the contract or other documentation demonstrating the nature and value of the work.

B. Review clocks now depend on front-end classification

HB 803 establishes a 5-business-day review category for certain building permit applications (amending s. 553.792, F.S.). The statute requires action within 5 business days after receipt of a complete and sufficient application where an applicant uses a local government plans reviewer to obtain listed permits for an existing single-family residential dwelling and the value of the work is less than $15,000. The listed categories are structural, accessory structure, alarm, electrical, gas, irrigation, landscaping, mechanical, plumbing, and roofing.

This is a timing rule, but its first-order effect is on intake. A local government cannot reliably track the correct deadline unless it can identify the application type, the work value, the property type, the completeness status, the use of a local government plans reviewer, and any waiver of statutory timeframes. The risk is not only missing a deadline. It is failing to recognize which deadline applied, and then missing it as a matter of law.

C. Private-provider projects require a distinct workflow

HB 803 formalizes private-provider coordination (amending s. 553.791, F.S.).

The bill requires local enforcement agencies, rather than merely authorizing them, to establish a registration system for private providers and private-provider firms operating in the jurisdiction. The system must permit electronic registration and updates, and the agency may not charge an administrative fee for registration or updates. Private providers and firms must register before contracting to provide services in the jurisdiction and must update their registration within 5 business days after a change in contact information, licensure, or insurance coverage.

The bill also constrains local building official review where a private provider has determined that plans, construction drawings, or related documents comply with applicable codes. In that circumstance, the local building official generally may not re-review those documents for code compliance, and is limited to determining compliance with local ordinances, floodplain management regulations, site review requirements, and other administrative or life-safety matters unrelated to building code compliance. Other forms and documents may be reviewed for completeness only.

This shifts the local government's function. For private-provider projects, the local role moves toward process integrity: verifying registration, confirming required documents, identifying local non-building-code review issues, applying the correct fee treatment, preserving notices, and maintaining a defensible record. Provenance matters. If the file does not capture that an application came through a private provider, the jurisdiction may lose the documentation it would need to defend a contested decision, because re-review is now restricted.

D. Fees become part of the compliance record

HB 803 also makes fee treatment more operationally sensitive.

The bill provides that inspection fees may not be based on the total cost of a project and may not exceed the actual inspection costs incurred by the local enforcement agency.

For commercial construction projects involving private providers, HB 803 requires permit fee reductions. Where a private provider is retained for plan review or building inspection services, the local enforcement agency must reduce the permit fee by at least 25 percent of the portion attributable to those services. Where a private provider is retained for all required plan review and building inspection services, the agency must reduce the total fee by at least 50 percent of the amount otherwise charged for those services. A failure to apply the required reduction carries consequences for the agency's ability to collect the fee.

Fee review should therefore be tied to the application record. Staff should be able to see whether a private provider is involved, which services are being performed privately, which portion of the fee is affected, how the reduction was calculated, and who approved it.

E. Electronic submission and standardized applications become requirements

HB 803 also moves the permitting process toward standardized forms and electronic handling.

By July 1, 2027, the Florida Building Commission must adopt uniform commercial and residential building permit applications for statewide use (amending s. 553.77, F.S.). To the extent feasible, those applications must be capable of integration with existing building permit software used by local governments and must account for local amendments to the Florida Building Code.

In the nearer term, the bill requires local enforcement agencies to accept certain electronic submissions, including electronically submitted affidavits from private providers. For single-trade plan reviews, it permits a private provider to use an automated or software-based plans review system designed to determine compliance with one or more applicable codes, including the National Electrical Code and the Florida Building Code.

These provisions should be read precisely. The statute does not provide that software replaces public officials, and it does not resolve questions of professional responsibility, local discretion, or legal sufficiency. It does establish that electronic submission and standardized application formats are now part of the compliance baseline.

HB 927 has drawn less public attention than HB 803, but it may be equally significant for planning, zoning, engineering, and development services teams. It amends the county and municipal development-permit provisions (ss. 125.022 and 166.033, F.S.) and creates a new statutory framework for development preapplication consultation services (s. 163.3169, F.S.), with qualified contractors and qualified contractor firms available to support specified review functions.

HB 927 requires counties and municipalities of a specified size to make development preapplication consultation services available at an applicant's request. It also authorizes the use of qualified contractors or qualified contractor firms to fulfill those services and requires a local-government-maintained registry to supplement staff resources for preapplication consultation, preliminary plat review, and administrative approval of plats or replats. As enacted, the program applies to counties with populations of 75,000 or greater and municipalities with populations of 10,000 or greater, and covered jurisdictions must establish their programs by January 1, 2027, unless a substantially similar program already exists under the statute's terms.

The statute also includes scope limitations. The definition of "local government" excludes any county subject to s. 380.0552, the Florida Keys Area of Critical State Concern, and the section contains carve-outs for certain historic properties. The covered "permit" is defined narrowly under s. 163.3169 as certain site plan, development plan, or subdivision approvals. The statute's definitions also limit the relevant land development regulations by excluding building permits and plans subject to the private-provider statute, s. 553.791.

HB 927 also reaches preliminary plat and planned-community workflows. If a governing body fails to adopt the required expedited building-permit program, or fails to update or modify an existing program, by the applicable statutory deadline, an applicant gains an unconditional, self-executing right to use a qualified contractor of its choosing, free of conflict of interest, to perform the technical review and certification needed to support issuance of up to 75 percent of the building permits for a residential subdivision or planned community before the final plat is recorded. In that circumstance, the local government may not condition, delay, restrict, or obstruct the applicant's use of the qualified contractor, though it may still apply neutral, generally applicable requirements that do not materially impair that use.

A. Preapplication review becomes a statutory workflow

HB 927 requires covered local governments to make development preapplication consultation services available at an applicant's request. At a minimum, the program must identify the information a permit application must contain and provide for the review and precertification of completeness of the application and related documents, including site engineering plans, site plans or their functional equivalent, or plats, for compliance with existing land development regulations.

This is not an informal meeting requirement. It is a structured process with defined inputs, completeness review, document review, and consequences for inaction.

If an applicant elects to use the process, the local government must confirm receipt, verify completeness, and provide written notification that all required information has been submitted, or identify deficiencies with particularity, within 5 business days. If the application is deficient, the applicant has 30 days to cure by submitting the required information. If the local government fails to issue the written notification within 5 business days, the application is deemed complete by operation of law, without conditions, and the local government must process it for final action.

B. HB 927 creates final-action pressure

After receipt of a complete application under the HB 927 process, the local government must approve, approve with conditions, or deny the application within 45 days. The covered "permit" category is limited by s. 163.3169 to certain site plan, development plan, and subdivision approvals that are administratively reviewable under objective standards.

The consequence is substantial. If the local government fails to take final action within 45 days, the applicant may provide written notice. If the local government then fails to respond within 10 days, the application is deemed approved by operation of law, without conditions. Approval by operation of law does not relieve the applicant from complying with other applicable federal, state, and local requirements.

That framework raises the stakes for development review administration. A covered jurisdiction will need to know, on a current basis:

• Which applications are in the HB 927 lane.
• When the complete application was submitted or deemed complete.
• Whether the completeness or deficiency notice issued within the statutory window.
• Whether the application has been treated as complete.
• When the 45-day final-action period began.
• Whether the applicant has provided written notice after missed final action.
• Whether the 10-day response period has begun.
• What action was taken, by whom, and when.

C. Qualified-contractor registries require governance, not a list

HB 927 requires local governments to establish and maintain a registry of at least four qualified contractors or two qualified contractor firms to supplement staff resources for preapplication consultation, preliminary plat review, and administrative approval of plats or replats. A qualified contractor or firm hired under the statute may not have a conflict of interest. By January 1, 2027, covered jurisdictions must have the registry in place. A local government may satisfy the minimum numbers through an agreement with another local government to use qualifying public employees, but it may not add its own employees to its own registry. If a local government fails to establish or maintain the registry, an applicant may retain a qualified contractor or firm of the applicant's choosing, provided there is no conflict of interest.

The registry is a compliance control, not just a list. HB 927 requires local governments to establish and maintain the registry, address conflicts of interest, and provide qualified contractors or firms access to reasonably necessary public records and information, while preserving limits for confidential or exempt records and proprietary software or vendor agreements.

That creates concrete administrative obligations:

• Who determines whether a contractor or firm qualifies.
• How conflicts of interest are disclosed and checked.
• Who maintains the registry, and how often it is updated.
• How applicant-selected professionals are documented.
• How staff provide the necessary public records without disclosing confidential or exempt material.
• How proprietary software limitations are handled.

HB 803 and HB 927 should not be implemented in isolation.

HB 399, now Chapter 2026-7, includes a substantial set of land use and development changes, with provisions taking effect on different dates. Among them, HB 399 requires development permit and development order application fees to reasonably relate to the direct and reasonable indirect costs of review, processing, and final disposition, and provides that the fee may not be based on a percentage of construction costs, site costs, or project valuation. HB 399 also adds requirements concerning compatibility analysis, mitigation measures, written findings for certain denials on compatibility grounds, and off-site construction parity, an area also addressed by HB 803. The fee provisions take effect January 1, 2027.

SB 1614, now Chapter 2026-126, takes effect July 1, 2026 and revises the use of excess Florida Building Code enforcement funds. Existing law restricts building-code enforcement fee revenue to carrying out the local government's responsibilities in enforcing the Florida Building Code. SB 1614 removes the authority to use excess funds to pay for construction of a building that houses the local government's building code enforcement agency. Any excess funds that may not be carried forward must remain tied to authorized building-code enforcement purposes, such as fee rebates or reductions, technology hardware and software upgrades, and training.

These measures point in a consistent direction. Fees, review timelines, completeness determinations, compatibility findings, private-provider coordination, and building-code enforcement resources are becoming more tightly bound to statutory compliance. The implementation work will cross departments. Building, planning, zoning, engineering, finance, legal, IT, and administration will each hold a piece of the same matter.

Most local governments will not struggle because they are unaware of the new laws. They will struggle because permitting work is composed of small classification decisions that carry legal consequences.

A residential project may appear to fall under the $7,500 exemption but include electrical work. A project may be valued below $15,000 yet fall outside the statutory categories that trigger the 5-business-day building permit timeframe. A private-provider submission may be routed into ordinary plan review, creating unnecessary re-review and a timing exposure. A development application may trigger HB 927's preapplication process without being identified as such. A fee may be calculated under prior logic even though a private provider is performing plan review or inspections. A staff member may reach the correct conclusion, yet the file may not record the basis for it.

That is the core problem. These laws do not only require local governments to know more rules. They require those rules to be applied consistently at the point of intake, routing, review, notice, fee calculation, and final action.

In practice, every application should resolve four questions early:

1. What is this application?
2. Which statutory or local workflow applies?
3. What clock, notice, fee, and recordkeeping requirements follow?
4. Who is responsible for the next action?

Once the first answer is wrong, everything downstream becomes harder, and the error is preserved in the record.

The most useful implementation plan is organized by workflow, not by bill number.

Intake controls. Update public-facing and staff-facing intake forms so the system captures the facts needed to classify the application. For HB 803, that includes project value, work type, property type, flood hazard status, private-provider involvement, commercial versus residential classification, and whether the applicant is requesting an exemption. For HB 927, that includes development review category, the applicant's election of preapplication consultation services, qualified contractor or firm involvement, and plat or replat status.

Classification rules. Create decision trees for the most common scenarios: under-$7,500 residential exemption requests; under-$15,000 existing single-family permit applications; private-provider plan review; private-provider inspections; commercial private-provider fee reductions; HB 927 preapplication consultation; preliminary plat review; administrative plat or replat approval; and development permit and development order fee review. The decision tree does not replace legal judgment. It ensures the right questions are asked before legal judgment is required.

Clock management. Map every statutory clock to its trigger event. A deadline is useful only if staff know when it starts, what pauses it, what notice is required, what happens after resubmittal, and what consequence follows if the local government does not act. For each clock, identify the triggering event, the responsible department, the responsible staff role, the required notice, the escalation point, the consequence of inaction, and the record to preserve.

Notice quality. These statutes place repeated weight on written notices, specificity, deficiencies, completeness, and timing. Generic deficiency language is less useful in this environment. Local governments should review templates for incomplete-application notices, deficiency notices, approval with conditions, denials, private-provider document completeness notices, HB 927 completeness or deficiency notices, applicant notices after missed final action, and fee determination records.

Fee logic. Fee schedules should be reviewed with finance and legal counsel. The question is not only whether the dollar amount is correct, but whether the file can establish why that amount was charged. At a minimum, a local government should be able to document whether the fee is tied to review, inspection, administration, or another category; whether a private provider affected the fee; whether plan review, inspections, or both were privately performed; whether a commercial project required a percentage reduction; whether inspection fees reflect actual local government inspection cost; and whether development permit or order fees reasonably relate to review, processing, and final disposition costs.

Records and audit trail. The application file should tell the story without reliance on staff memory. A complete record should show what was submitted, when it was submitted, how the application was classified, which workflow applied, what notices were sent, which deadlines applied, what fees were charged, who reviewed the file, what decision was made, and why. That record is both a legal-defense tool and a management tool. It allows leadership to see where bottlenecks occur, which application types create confusion, where applicant submissions are incomplete, and where staff need additional support.

Local governments do not need to resolve every implementation issue at once. They do need a disciplined sequence.

First 30 days: identify the decision points. Begin by mapping where the new laws touch existing workflows. Do not begin with software configuration or public FAQs. Begin with classification. Which applications might trigger the new exemption? Which might trigger the 5-business-day building permit category? Which submissions involve private providers? Which commercial projects require fee review? Which development applications might fall under HB 927? Which forms fail to capture the necessary information? The output should be a short internal issue map, reviewed by building, planning, finance, legal, and IT.

Days 31 to 60: update forms, templates, and queues. Update intake questions, document checklists, public guidance, staff templates, and review queues. The goal is to make the correct path visible as early as possible. Staff should not have to discover a statutory issue after the application has already been assigned to the wrong reviewer.

Days 61 to 90: test real scenarios. Use recent applications to test the new workflow. Run a minor residential repair, a low-value trade permit, a private-provider commercial project, a development preapplication, and a plat-related application through the new classification process. For each, ask three questions. Did we capture the facts needed to classify it? Did the correct deadline, notice, fee, and reviewer path appear? Would the final record explain the decision six months later? If not, the process is not ready.

By January 1, 2027: operationalize HB 927 and the related fee changes. For covered jurisdictions, HB 927's preapplication consultation and qualified-contractor framework requires additional work before January 1, 2027, including registry governance, conflict-of-interest procedures, public-records access rules, application completeness workflows, final-action tracking, and procedures for applicant notices that can trigger deemed-approved consequences. HB 399's development permit and order fee provisions make 2027 a natural deadline for reviewing fee methodology and documentation.

Only after the legal and operational picture is clear does the technology question become useful, and the right framing for it is narrow.

AI should not be presented as a replacement for building officials, planners, inspectors, engineers, code officials, or local government attorneys. That is the wrong model, and it invites the wrong questions. The better model is decision support.

Much of the permitting work that precedes final judgment is document-heavy, repetitive, classification-dependent, and time-sensitive. AI-assisted systems can help by surfacing missing information, identifying likely workflow paths, comparing submitted materials against applicable requirements, drafting clearer review comments, tracking statutory deadlines, and preserving a fuller record of review activity.

The governing principle is explainability. A useful system should help staff see what was reviewed, which requirement may apply, what issue was flagged, where the supporting material appears, what judgment remains for staff, and what record will be preserved.

That distinction is the entire point. Speed without a record is not modernization. Speed with structure, traceability, and human review is. The strongest local governments will not adopt these tools merely to move faster. They will adopt them to make review more consistent, more transparent, and easier to manage.

HB 803 and HB 927 are part of a broader shift in local government permitting.

The State is asking local governments to move faster, reduce friction, accommodate private-sector review capacity, standardize intake, justify fees, preserve records, and manage statutory timelines with greater precision. Those expectations are difficult to meet with static PDFs, email inboxes, spreadsheet trackers, and informal staff memory.

The next phase of permitting modernization will require approaches that connect legal requirements to daily operations: intake, classification, routing, review, notices, fees, deadlines, and final action. That is the real meaning of Florida's 2026 permitting reset. It is not only that certain rules are changing. It is that permitting compliance is becoming an operating discipline.

Florida local governments should treat HB 803 and HB 927 as implementation projects, not as legal updates alone.

The work ahead is practical: revise intake, map decision trees, update notices, review fee logic, separate private-provider workflows, prepare qualified-contractor registries, train staff, and ensure that each application file can establish what happened and why.

The jurisdictions that adapt best will not be the ones with the longest legal memo. They will be the ones that translate legal requirements into repeatable workflows. That is where modern permitting is headed: faster review, clearer records, better use of staff time, and systems that support, rather than replace, public-sector judgment.