Broward County, Florida, selects ServiceNow to put AI agents to work for government employees

Broward County, Florida Government (Enterprise Technology Services Division); ServiceNow; Beyond20 · Local government (county IT service delivery) · Broward County, Florida, United States

ServiceNow

Publisher: ServiceNow Newsroom (Business Wire press release)
Original publication: 2026-11-09
Source retrieved: 2026-11-10
Event date: 2026-11-09

Read original source

What happened

ServiceNow announced on 2026-11-09 that Broward County, Florida's second-most populous county (more than 2 million residents), has gone live with ServiceNow IT Service Management and Workflow Data Fabric. The county's Enterprise Technology Services Division supports about 8,000 users across more than 800 departments and units, with more than 100 service catalog items and workflows plus integrations for collaboration, device management, identity and secure access. The release says the county has evaluated close to 35 AI use cases over the past year and a half, that ITSM uses AI to automate previously manual workflows, and that Workflow Data Fabric with AI Search connects information across departments. Early benefits are described only qualitatively as faster response times and more consistent, simplified workflows. Elite partner Beyond20 supported planning, configuration and testing. Independent context: Broward County Board of County Commissioners file 24-1492 (agenda and final action 2024-12-10) approved, 8-0, a sole-brand designation for ServiceNow ITSM and authorized an open-end reseller contract for an initial five-year term with five one-year renewals, a potential ten-year estimated amount of $10,000,000, after an August 2024 RFI drew two responses that ETS judged did not meet requirements.

Why it matters

Why now: this is a new, named large-county go-live announced today, which adds a second local-government reference alongside the archived Raleigh AI-agent results. It shows a common SLED path: an ITSM and data-integration foundation first, with AI agents framed as a later step. Despite the headline, the release names no AI agent in production and gives no measured outcome, so it is evidence of platform adoption and AI intent, not of AI effectiveness. The board record shows how a county justified sole-brand procurement for the platform.

Evidence and measured results

Opened the original ServiceNow Newsroom release (dated 11/09/2026) and read the full text, including county CIO and Beyond20 quotes. Opened Broward County Legistar file 24-1492 and read the full text of the motion and background. The release gives no baseline, sample, metrics, go-live date or contract value; the Legistar record predates the release and does not mention AI agents or Workflow Data Fabric specifically, only AI integration as a platform feature.

Limitations and uncertainty

Vendor press release; outcomes are qualitative and unmeasured. Headline references AI agents, but body describes ITSM automation and AI Search, with agents implied as future capability. Contract figure is a 2024 board estimate ceiling, not spend.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-10; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway

Customer problem: Large counties with hundreds of departments struggle to manage service requests and siloed data consistently before AI can help.
Stakeholders: County CIO
Enterprise technology services director
Purchasing director
County administrator
Department IT liaisons
Discovery questions: How many AI use cases have you evaluated, and which passed?
Is your service catalog and knowledge base ready for automation?
Which departmental data sources must connect before AI search is useful?
What procurement path did you use or plan for the platform?
Value hypothesis: Consolidating service management and departmental data first may let a county add AI automation later with fewer integration surprises; benefit size is unproven here.
Potential engagement: A fixed-scope AI use-case portfolio and readiness review covering catalog quality, data connections and baseline metrics.
Unsupported claims: AI agents are in production at Broward County
Measured response-time or cost savings
The $10,000,000 figure is actual spend
Results transfer to smaller counties

Pre-sales engineering

Role takeaway

Fit: Fits large local governments with central IT serving many departments and a fragmented data landscape.
Architecture and integration: ServiceNow ITSM with Workflow Data Fabric and AI Search; integrations for collaboration, device management, identity, secure access and ERP job, inventory and financial data.
Prerequisites: Clean service catalog and knowledge base
Identity integration with role-based entitlements
Department data source inventory
Pre-AI baseline metrics
Constraints: No AI model or data-residency detail given
Sole-brand dependency on one platform
Florida public-records obligations for AI-generated content
Security: Test that AI Search honors departmental entitlements and that AI processing of county data is logged and limited to approved models.
Proof of value: Measure response and resolution times before and after each AI feature
Entitlement tests on AI Search across at least two departments
Track automation rate on a defined set of catalog items

Delivery

Role takeaway

Work: Stabilize ITSM after go-live, establish baselines, then introduce AI features one use case at a time.
Dependencies: Partner support through configuration and testing
Department data owners
Identity and security teams
Ownership: County Enterprise Technology Services division, with department data owners for connected sources.
Skills and adoption: Train service desk staff and department liaisons to apply AI in existing roles, as county leadership describes.
Governance checkpoints: Use-case approval in the AI portfolio
Data classification review before connecting a source to AI Search
Post-launch metric review
Acceptance criteria: Proposed: documented baseline and post-change response time for targeted request types
Proposed: zero entitlement violations in AI Search access tests
Proposed: each AI feature has a named owner and approved use case
Risks: Benefits stay qualitative and unmeasured
Cross-department data overexposure through AI Search
Lock-in from sole-brand designation without exit terms

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

Pattern is ITSM plus Workflow Data Fabric and AI Search over cross-department data, integrated with identity, device management and collaboration tools; the board item also cites ERP synchronization of job data, inventory assignment and financial impacts. Any later AI agents would depend on the quality of these integrations and the service catalog.

Governance

Who approves, reviews and stays accountable for outcomes?

Evaluating about 35 AI use cases before scaling suggests a portfolio gate; agencies copying this should document which use cases were approved, deferred or rejected and why. Sole-brand designation concentrates platform dependency and should be paired with exit and data-portability terms.

Security and privacy

What data, permissions and controls need testing?

AI Search across departmental data raises access-control and data-classification questions: employees should see only records they are entitled to. The release gives no detail on data classification, logging, or which AI models process county data.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

County leadership frames the goal as helping employees apply AI in their existing roles; no training plan, workforce impact or accessibility detail is given.

Procurement

What should contracts, pricing and exit terms secure?

Sole-brand designation after an RFI with two non-qualifying responses, executed through an authorized reseller with a potential ten-year term, is a reusable procurement precedent for other Florida and large-county buyers; buyers should confirm whether AI features and consumption are inside the contracted SKUs.

Operating model

Which teams own the service once it runs?

A central ETS division serves 800-plus units through one catalog, so ownership of service catalog content, knowledge and data connections becomes the main operational lever for any later AI automation.

Publication history

2026-11-09ServiceNow · Issue 091 resources

Read preserved resource versions (JSON)

Stable resource ID: broward-county-servicenow-itsm-workflow-data-fabric-golive-20261109