Search

Search bills, members, committees and pages...

B 26-0546

District of Columbia CouncilIntroduced

Summary

B 26-0546, the E911 Modernization Amendment Act of 2025, was introduced in the Council on Dec 15, 2025 by Sen. Christina Henderson (I) with 1 co-sponsor. It last saw action on Mar 18, 2026: Public Hearing Held.


Record

Text

B 26-0546 has 1 co-sponsor.

b260546/introduced.txt
COUNCIL OF THE DISTRICT OF COLUMBIA
The John A. Wilson Building
1350 Pennsylvania Avenue, NW
Washington, D.C. 20004
Christina Henderson Committee Member
Councilmember, At-Large Facilities
Chairperson, Committee on Health Human Services
Transportation and the Environment
Statement of Introduction
E911 Modernization Amendment Act of 2025
December 15, 2025
Today, along with Councilmember Matthew Frumin, I am introducing the E911 Modernization
Amendment Act of 2025. This legislation would update and strengthen the District’s emergency
communications system by modernizing the 911 and 311 telecommunications fees, clarifying the
allowable uses of the Emergency and Non-Emergency Number Telephone Calling Systems Fund,
and establishing an updated service fee structure that reflects the real costs of operating a 21st-
century emergency response system.
For more than two decades, the District’s Emergency and Non-Emergency Number Telephone
Calling Systems Fund has supported core 911 operations, including call handling and routing.
While this foundation has been critical, the technological landscape and the expectations of
residents have evolved significantly. Across the country, jurisdictions are transitioning to Next
Generation 911 (NG911), an Internet Protocol based system that enables voice, text, photos, video,
and precise geolocation. These capabilities are essential for delivering accurate, real-time
information to emergency responders and for ensuring that residents can reach 911 using the
communication methods they rely on every day.
The Office of Unified Communications (OUC) has already made progress toward transitioning to
a modern emergency communications system and has demonstrated a strong commitment to this
work. Each year, OUC handles hundreds of thousands of emergency and non-emergency calls,
and its infrastructure must be equipped to support rapid call routing, improved resiliency, enhanced
cybersecurity protections, and seamless coordination across public safety agencies. The proposed
funding will allow OUC to continue and expand its modernization efforts, helping the District
remain a leader in emergency response technology and service delivery. These critical upgrades
require sustained and dedicated funding, rather than one-time grants or unpredictable general fund
allocations, to ensure the system keeps pace with evolving technology and the needs of District
residents.
This legislation would:
• Modernize outdated definitions by updating statutory terms to include wireless, wireline, VoIP,
IP-based, and prepaid wireless services, and by adding definitions for “access line,” “family or
shared plan,” and “Next Generation 911.”
• Update the E911 Fund’s allowable uses by explicitly authorizing funding for Next Generation
911 infrastructure, IP-based networks, GIS systems, cybersecurity, multimedia-to-911
COUNCIL OF THE DISTRICT OF COLUMBIA
The John A. Wilson Building
1350 Pennsylvania Avenue, NW
Washington, D.C. 20004
capabilities, and training, and by directing OUC to develop and maintain a Districtwide NG911
implementation and readiness plan.
• Revise the 911 surcharge structure by establishing a uniform $1.00 monthly fee per access line
across non-prepaid technologies, converting the PBX fee to a per-trunk model, and increasing
the prepaid wireless surcharge from 2% to 5%.
• Strengthen oversight and accountability by requiring annual reporting on revenues,
expenditures, performance metrics, and NG911 progress, and by mandating an annual
independent audit conducted by the Chief Financial Officer.
• Ensure long-term sustainability by requiring a triennial review of the surcharge that considers
inflation (CPI-U), call volume trends, modernization costs, and overall system needs.
The Council has prioritized the modernization and integrity of the District’s emergency response
system through prior oversight and legislative action. This bill would advance that commitment
by ensuring that OUC has the resources to build a resilient, technologically advanced, and reliable
emergency communications network that meets national standards and serves residents with the
urgency and accuracy they deserve.
With this legislation, the District takes an important step toward a safer and more responsive public
safety system. A strong and sustainable E911 infrastructure is foundational to every emergency
response. I look forward to working with my colleagues, OUC, public safety agencies, and
telecommunications partners to move this bill forward and ensure the District’s emergency
communications system is equipped for the future.
_________________________ _____________________________
Councilmember Matthew Frumin Councilmember Christina Henderson
A BILL
_______________
IN THE COUNCIL OF THE DISTRICT OF COLUMBIA
___________________
To amend the Emergency and Non-Emergency Number Telephone Calling Systems Fund Act of
2000 to modernize the District’s 911 and 311 telecommunications tax and fees, to update
the structure and allowable uses of the Emergency and Non-Emergency Number Telephone
Calling Systems Fund, and to establish an updated service fee on telecommunication
services to support the District’s emergency communications system, including call routing,
technology upgrades, staffing, and operations..
BE IT ENACTED BY THE COUNCIL OF THE DISTRICT OF COLUMBIA, That this act
may be cited as the “E911 Modernization Amendment Act of 2025.”
Sec. 2. The Emergency and Non-Emergency Number Telephone Calling Systems Fund Act
of 2000, effective October 19, 2000 (D.C. Law 13-172; D.C. Official Code § 34-1801 et seq.), is
amended as follows:
(a) Section 602 (D.C. Official Code § 34-1801) is amended as follows:
(1) A new paragraph (1A) is added to read as follows:
“(1A) “Access line” means a wireline, Voice over Internet Protocol (“VoIP”) line,
wireless telephone number, trunk, or other communication path that can initiate a 911 call.
(2) A new paragraph (2B) is added to read as follows:
“(2B) “Family or shared plan” means a telecommunications service plan offered by a
provider under a single customer account that includes multiple individual access lines or mobile
numbers, whether the plan is marketed as a family plan, shared plan, multi-line plan, group plan, or
any similar offering that allows two or more users to share voice, text, data, or billing features. Each
individual access line or mobile number capable of accessing or connecting with the District’s 911
system shall be considered a separate line for purpose of assessing the tax or fee under this chapter.”
(3) Paragraph (5) is amended to read as follows:
“(5) “Local exchange service” means a telecommunications service provided within an
exchange area, including VoIP, wireless services, interconnected Internet Protocol (“IP”)-based
services, and any voice-capable telecommunications service that enables connection to 911.”
(4) A new paragraph (5A) is added to read as follows:
“(5A) “Next Generation 911” means an IP-based, secure, and resilient emergency
communications system designed to enhance and modernize the District’s 911 system, including
enabling the transmission of voice, text, data, video, and geolocation information between the public
and public safety answering points and among emergency response agencies.”.
(5) Paragraph (6C) is amended to read as follows:
“(6C) “Provider” means a person that provides wireline, wireless, VoIP, or prepaid
telecommunications services to consumers within the District.”.
(b) Subsection 603(c) (D.C. Official Code § 34-1802(c)) is amended to read as follows:
“(c) Money in the Fund shall be used for the following purposes as it relates to the District’s
911 system:
“(1) Planning, implementing, operating, maintaining, and modernizing the District’s
911 system, including the next generation 911 infrastructure;
2
“(2) Internet Protocol-based emergency services networks;
“(3) Call-handling equipment;
“(4) Geolocation and geographic information systems;
“(5) Cybersecurity;
“(6) Text and multimedia communications capabilities;
“(7) Personnel training;
“(8) Developing, maintaining, and implementing a Districtwide next generation 911
implementation and readiness plan to ensure that OUC’s operations, infrastructure, and systems meet
national next generation 911standards and operational requirements; and
“(9) Necessary costs associated with personnel, technology hardware, software and
software maintenance, contractual services, public outreach, training, supplies, and equipment
required to support the District’s 911 system.”.
(c) Section 604(a) (D.C. Official Code § 34-1803(a)) is amended to read as follows:
“(a)(1) There is imposed upon all providers that enable end users to initiate a 911 call or
communication to the District’s 911 system, a $1.00 tax calculated based on each individual line,
voice channel, or equivalent sold or leased in the District of Columbia.
“(a)(2) For interconnected VoIP service, as defined by 47 C.F.R. § 9.3, $1.00 for each line,
trunk, or path that can access to, connect with, or interface with 911 service based on primary place of
use.
“(2) The PBX fee per station shall be converted into a per-trunk fee based on a ratio of 15 PBX
stations to one PBX trunk.”.
(b) Section 604b (D.C. Official Code § 34-1803.02) is amended as follows:
3
“(A) Subsection (a)(1) is amended by striking the phrase “A prepaid wireless E911
charge of 2.0% of the sales price per retail transaction occurring in the District shall be collected by
the seller from the consumer, and remitted to the District.” and inserting the phrase “A prepaid
wireless E911 charge of 5.0% of the sales price per retail transaction occurring in the District shall be
collected by the seller from the consumer, and remitted to the District.” in its place.
“(B) Subsection (f) is repealed.
(c) Section 605a (D.C. Official Code § 34-1804) is amended to read as follows:
“Sec. 605a Reporting.
“(a) (1) By February 1, 2027, and annually thereafter by December 31, the Mayor shall submit
to the Council a report on the Fund, that shall include the following information:
“(A) The total revenue collected during the preceding fiscal year, disaggregated
by wireline, wireless, Voice over Internet Protocol (“VoIP”), and prepaid sources;
“(B) The Fund balance at the beginning and end of the fiscal year;
“(C) An itemized list of all expenditures from the Fund, including capital,
operational, and personnel costs;
“(D) A description of the status of all ongoing and planned next generation 911
projects or system upgrades, including implementation timelines, key milestones, and anticipated
costs;
“(E) An assessment of the sufficiency of surcharge revenue to meet the
District’s operational and modernization needs, including any recommended adjustments to surcharge
rates; and
4
“(F) A summary of performance indicators for the Office of Unified
Communications, including call-handling metrics, technology performance indicators, and next
generation 911 readiness benchmarks.
“(2) By April 1, 2027, and annually thereafter by April 1, the Chief Financial Officer
shall conduct an audit and submit an audit report to the Mayor and the Council detailing all revenues
deposited into, and expenditures made from, the Fund, which shall include:
“(A) Verification of the surcharge amounts collected and remitted by providers
and sellers;
“(B) Evaluation of internal controls to prevent misuse, diversion, or improper
expenditure of funds;
“(C) Assessment of compliance with the authorized uses described in section
603(c);
“(D) Review of procurement practices associated with next generation 911 and
911 system upgrades; and
“(E) Identification of any material weaknesses, irregularities, or deficiencies,
and recommendations for corrective action.
“(b) Beginning October 1, 2029, and every 3 years thereafter, the Mayor shall conduct a
comprehensive review of the tax imposed by this act. By December 31, 2029, and by December 31
each subsequent review year, the Mayor shall submit to the Council a written recommendation
indicating whether the rates should be adjusted based on the following factors:
“(1) The Consumer Price Index for All Urban Consumers for the Washington-
Arlington-Alexandria Metropolitan Area, including the cumulative percentage change
in the index since the prior rate adjustment, which shall serve as the minimum
5
recommended increase to the surcharge unless the Mayor determines that a different
adjustment is warranted based on operational need or fiscal impact;
“(2) Call volume trends and overall system demand;
“(3) Costs associated with next generation 911 upgrades and lifecycle replacements;
“(4) Personnel and training requirements;
“(5) Long-term capital planning for emergency communications infrastructure; and
“(6) Availability of federal grants or matching fund requirements.”.
Sec. 3. Fiscal impact statement.
The Council adopts the fiscal impact statement in the committee report as the fiscal impact
statement required by section 4a of the General Legislative Procedures Act of 1975, approved
October 16, 2006 (120 Stat. 2038; D.C. Official Code § 1-301.47a).
Sec. 4. Effective date.
This act shall take effect following approval by the Mayor (or in the event of veto by the
Mayor, action by the Council to override the veto) and a 30-day period of congressional review as
provided in section 602(c)(1) of the District of Columbia Home Rule Act, approved December 24,
1973 (87 Stat. 813; D.C. Official Code § 1-206.02(c)(1)).
6

As introduced, Bill 26-546 would modernize the District’s 911 and 311 telecommunications tax and fees. It would update the structure and allowable uses of the Emergency and Non-Emergency Number Telephone Calling Systems Fund. It would also establish an updated service fee on telecommunication services to support the District’s emergency communication system.

Sponsors

Sen. Christina Henderson (I) sponsors B 26-0546, and 1 member has co-sponsored it.

Committees

B 26-0546 went before 1 committee: Judiciary and Public Safety.

Judiciary and Public Safety
Judiciary and Public Safety
Referred to · Dec 16, 2025 · 28 Bills

History

B 26-0546 has taken 6 actions since Dec 15, 2025, the latest on Mar 18, 2026.

ChamberAction
Mar 18, 2026
Council
Public Hearing Held
Feb 27, 2026
Council
Notice of Public Hearing Published in the DC Register
Feb 24, 2026
Council
Notice of Public Hearing Published in the DC Register
Dec 19, 2025
Council
Notice of Intent to Act on B26-0546 Published in the DC Register
Dec 16, 2025
Council
Referred to Committee on Judiciary and Public Safety

Votes

B 26-0546 has not gone to a roll call.


Source: lims.dccouncil.gov · legiscan.com