AB 693 directs the California Public Utilities Commission to redesign and run the California Advanced Services Fund (CASF) with an explicit focus on accelerating last‑mile broadband deployment, digital inclusion, and use of federal infrastructure dollars. The bill establishes several labeled accounts inside CASF—infrastructure, regional consortia, public housing, adoption, and federal funding—and instructs the commission to use the fund both to deploy infrastructure and to leverage federal and nonstate money through matching and technical assistance.
The measure also builds transparency and programmatic controls into CASF: it requires public posting of applications, monthly project reporting, opportunities for parties to demonstrate actual service levels, and structured regional and public‑housing grant programs. The changes steer state resources toward areas with the weakest service and toward adoption efforts while creating administrative obligations for applicants and the commission.
At a Glance
What It Does
Directs the CPUC to operate CASF through five internal accounts, prioritize funding for areas lacking adequate broadband, and coordinate with regional consortia to design and apply for projects. It makes CASF money available to match federal infrastructure grants and funds adoption and public‑housing connectivity programs.
Who It Affects
Facility‑based broadband providers seeking state grants, community consortia and local governments that support applications, public housing authorities and digital inclusion organizations, and contractors who perform funded work. The commission itself will face expanded administrative and reporting duties.
Why It Matters
The bill narrows where state dollars should go (targeting the weakest service areas and last‑mile builds), creates discrete pots for public housing and adoption, and links state spending to federal timelines—changing how California prioritizes and leverages broadband investments.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 693 sets concrete operational rules for the California Advanced Services Fund. It defines “unserved” for CASF purposes as areas with no facility‑based provider offering at least 25 Mbps downstream and 3 Mbps upstream (with a latency standard suitable for real‑time interactive apps), but adds an exception for projects using Rural Digital Opportunity Fund (RDOF) money to follow FCC RDOF standards.
The commission must aim to fund infrastructure projects that, by region, bring broadband access to the vast majority of households (the bill attaches a statewide deployment goal and makes the commission responsible for achieving it).
The statute directs grantmaking toward last‑mile projects that reach households unserved by facility‑based providers and prioritizes places with very low speeds or no connectivity (it singles out areas at or below 10/1 Mbps). Eligible projects must deliver infrastructure capable of at least 100 Mbps down / 20 Mbps up (or the then‑current FCC benchmark, whichever is higher).
The commission must award grants on a technology‑neutral basis and may consider the useful economic life of capital investments when evaluating proposals.Several programmatic buckets shape how money is used. The Broadband Infrastructure Grant Account covers last‑mile builds and allows funding for deployment costs, limited backhaul or lease expenses (capped term), and upgrades by existing providers.
The Rural and Urban Regional Broadband Consortia Grant Account funds consortia that assist applicants with project development and grant applications; consortia must perform annual audits and report activities and numbers of assisted applications. The Broadband Public Housing Account finances projects that deliver free broadband to low‑income communities where no qualifying free service exists.
The Broadband Adoption Account supports digital literacy and after‑school access but explicitly forbids using those funds to subsidize household broadband subscriptions.AB 693 also adds transparency and compliance mechanics: applicants and recipients must report monthly project details to the commission (including the name and contractor license number for contracts over $25,000, work locations, and anticipated dates), the commission must post pending applications and challenge deadlines on the CASF homepage, and parties can demonstrate actual service levels in contested application reviews. The bill includes a federal funding account with instructions to implement federal moneys consistent with federal requirements and specifies allocations from a prior $2 billion appropriation—dividing that pot between urban and rural counties with minimum per‑county allocations and an encumbrance deadline for those specific funds.
Finally, the statutory program has near‑term operational limits: the commission’s ability to collect a surcharge is capped for a defined period, and the section contains explicit inoperative and repeal dates that make the scheme time‑bounded.
The Five Things You Need to Know
The bill requires the commission to post every pending CASF application, application challenge deadlines, and amendments on the CASF homepage before publishing a corresponding draft resolution.
Applicants and any project recipients must report monthly and the CPUC must post those reports; contractors and subcontractors with contracts over $25,000 must be listed by name and contractor license number.
Grants under the Broadband Public Housing Account may finance networks that provide free on‑site broadband service to residents, and the commission will prioritize publicly supported housing developments that have not previously received such grants.
The Rural and Urban Regional Broadband Consortia are eligible for grants to assist applicants, are not required to have a certificate‑holding entity as the lead fiscal agent, and must submit annual audits showing activities and the number of project applications assisted.
The Broadband Adoption Account funds digital literacy, after‑school access, and community adoption programs but may not be used to subsidize household broadband subscription costs; the commission will tie payments to digital inclusion metrics (for example, residents trained or verified subscriptions).
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Deployment goal, 'unserved' definition, and prioritization
These paragraphs set the program’s strategic aim and the screening rules the commission must use when approving infrastructure grants. The statute defines ‘unserved’ for CASF as lacking any facility‑based provider at 25/3 Mbps (with an RDOF exception) and directs prioritization of locations that are effectively offline or only at 10/1 Mbps or worse. For implementers, that creates a two‑tiered eligibility and prioritization framework: a broad definition of unserved for basic eligibility and a sharper prioritization metric for scarce dollars.
Leverage, technical assistance, and household connection grants
The commission is instructed to use CASF to match or leverage federal programs and to provide technical assistance and planning support to local governments and providers. Notably, the bill allows direct household or property owner grants to cover the cost of connecting a single household to a network, but any connection infrastructure funded this way becomes part of the provider’s network. The commission can limit household grant amounts, require household contribution, and cap the aggregate awards for these household connection grants.
Accounts structure and infrastructure grant mechanics
The bill formalizes five internal accounts (Infrastructure, Consortia, Public Housing, Adoption, Federal Funding) and ties use rules to each. For infrastructure grants, the commission must be technology neutral, weigh useful life, and ensure projects are capable of delivering at least a 100/20 Mbps baseline or the then‑current FCC standard. The commission retains discretion on per‑project funding levels and may fund full or partial project costs—allowing flexible cost‑sharing but putting the onus on staff to justify funding percentages in light of competing priorities.
Regional consortia role and accountability
Consortia can include a wide set of regional stakeholders and do not need a certificate‑holding entity to act as fiscal lead. The statute finances consortia to help prepare applications and plans, but it also requires annual audits and reports documenting activities and the number of applications assisted—building a traceable record of consortia outputs that the commission can use to evaluate effectiveness.
Public housing and adoption programs
Public housing grants target low‑income communities and expressly authorize funding to connect networks that provide free on‑site broadband to residents; the commission should, where feasible, distribute awards to reflect statewide low‑income community distribution. Adoption funds are directed to local governments, libraries, schools, senior centers, and nonprofits for digital literacy and after‑school access, with payments tied to outcomes or metrics and a prohibition on using those funds to subsidize household broadband subscription fees.
Transparency, monthly reporting, and federal funding allocation
Recipients must report monthly on contractors and project schedules, and the CPUC must publish that information online. The bill also requires coordination with federal funding rules and implements a specific allocation scheme for a previously appropriated $2 billion: an initial $1 billion for urban counties and $1 billion for rural counties with per‑county minimum allocations and an encumbrance deadline for those funds. Those mechanics create both compliance tasks and hard project timelines tied to federal conditions.
Program time limits
The statute includes an inoperative date and a repeal date, making the program time‑bounded. That introduces an expiration on the particular statutory regime, meaning any long‑term program design or administrative investment must account for the near‑term statutory horizon unless legislators extend or replace the authority.
This bill is one of many.
Codify tracks hundreds of bills on Infrastructure across all five countries.
Explore Infrastructure in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Households in areas with weak or no broadband—by receiving priority for last‑mile builds and potential household connection grants that lower the upfront cost to connect a property.
- Public housing residents—because a dedicated account funds free on‑site broadband for low‑income communities, with priority for developments that have not yet received assistance.
- Regional consortia and local governments—these groups gain funded capacity to prepare stronger applications and comprehensive deployment plans, and to coordinate multi‑county strategies.
- Digital inclusion organizations and community anchors—eligibility for adoption grants and outcome‑based funding creates new revenue streams for training and public access programs.
Who Bears the Cost
- The California Public Utilities Commission—administrative burden rises substantially due to expanded grant oversight, frequent reporting, website publication duties, and auditing consortia.
- Providers and applicants—expect more onerous application, reporting, and documentation requirements (including contractor license disclosures) and potential cost‑sharing or limits on household grants.
- State funders and ratepayers—because the bill contemplates a surcharge (subject to a statutory cap for a period) and uses state appropriations to match federal funds, exposing state revenue to project success and timing risks.
- Contractors and subcontractors—must be disclosed publicly for contracts above $25,000, adding compliance steps and public visibility into project staffing and procurement.
Key Issues
The Core Tension
The central dilemma is between ambitious, high‑quality deployment targets and the practical economics of last‑mile work: pushing for high speeds and per‑county minimum allocations makes projects more expensive or redistributes funds in ways that can blunt reach to the highest‑cost, hardest‑to‑serve locations—forcing the commission to choose between speed/coverage objectives and cost‑effective prioritization.
The bill stacks policy objectives—accelerating deployment, maximizing technology life, prioritizing the most underserved, and coordinating federal funds—into a single program. That mix creates implementation choices the commission must resolve.
For example, using a 25/3 Mbps threshold to define unserved but a higher 100/20 Mbps deployment requirement forces tradeoffs at the application stage: projects that technically remove an area from the 25/3 definition may fail to meet the 100/20 target without more costly upgrades. Similarly, per‑county minimum allocations for large federal pots can move money to less costly near‑urban builds in small counties rather than to the very hardest, most expensive rural last‑mile stretches.
Operationally, monthly public reporting (including contractor license numbers) improves transparency but raises practical issues: data quality, contractor privacy concerns in small markets, and staff time needed to validate and publish large volumes of granular project data. The statute’s encumbrance deadlines and sunset clauses—paired with the requirement to align with one‑time federal funding timelines—create tight windows for project design, procurement, and construction that could disadvantage smaller applicants lacking rapid procurement capacity.
Finally, the bill leans on mapping and service demonstrations to adjudicate eligibility; where mapping is imperfect, the commission will face politically and technically fraught disputes over which areas genuinely qualify for scarce funds.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.