The bill requires the Office of Management and Budget to revise the federal Standard Occupational Classification (SOC) to recognize Public Safety Telecommunicators as a protective service occupation. Sponsors frame the change as a correction to how federal statistical systems represent the lifesaving, high‑stress work performed by 9‑1‑1 call takers and dispatchers.
While the text contains no funding or programmatic mandates, relabeling this occupation in the SOC will change how federal agencies count and compare these workers, and could ripple into workforce planning, research, and any federal programs that rely on SOC crosswalks for eligibility or reporting.
At a Glance
What It Does
The Director of OMB must categorize public safety telecommunicators as a protective service occupation under the Standard Occupational Classification System and do so within 30 days after the bill’s enactment. The change is an administrative reclassification of how the occupation is listed in federal statistical frameworks.
Who It Affects
Public safety telecommunicators (9‑1‑1 call takers and dispatchers), federal statistical agencies (including BLS data programs), state and local public safety employers, workforce researchers, and programs that use SOC codes for eligibility or reporting. HR, payroll, and occupational databases that map to SOC will also be affected.
Why It Matters
SOC codes are the standard for federal employment statistics; moving telecommunicators into the Protective Service category alters occupational counts, affects comparability across datasets, and can change how policymakers and grantmakers view staffing needs and risk exposure for emergency services roles.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The SOC is the federal system that groups jobs for statistical collection and reporting. This bill directs the OMB Director to treat Public Safety Telecommunicators—people who answer emergency calls and dispatch responders—as part of the Protective Service occupations instead of whatever grouping they currently occupy.
That reclassification is administrative but consequential: it changes where these workers appear in federal tables, reports, and crosswalks.
Mechanically, the bill imposes a 30‑day timeline for OMB to make the categorization. In practice, OMB will need to issue guidance updating the SOC taxonomy and inform agencies that produce occupational statistics, like the Bureau of Labor Statistics, as well as downstream systems such as O*NET, the Occupational Employment Statistics, and other federal surveys that rely on SOC coding.Although the bill’s findings underline the high‑stress, lifesaving nature of telecommunicator work, the statute contains no funded programs, training requirements, or occupational standards.
Its immediate effect is visibility and alignment within federal data systems; any programmatic changes (for example, grant eligibility keyed to Protective Service codes) would be driven by other authorities using the updated SOC.Implementation will require coordination: federal statistical offices must update coding guidance, employers and HR systems will need to align their mappings, and researchers will have to account for the break in series when analyzing trends across the transition. Because the SOC is intended for statistical purposes, the change is framed as correcting an inaccurate representation, but it also creates practical downstream consequences that agencies and data users will have to manage.
The Five Things You Need to Know
Section 3 directs the OMB Director to categorize public safety telecommunicators as a Protective Service occupation under the Standard Occupational Classification System.
The bill imposes a 30‑day deadline from enactment for OMB to make the categorization—an unusually short timeline for a classification change.
The statutory findings explicitly state that the SOC is maintained solely for statistical purposes, and the bill contains no new funding, training, certification, or benefit provisions.
Reclassification is administrative: it alters where telecommunicators appear in federal data, but does not itself create new programmatic eligibility or regulatory obligations.
Federal statistical producers and downstream systems (like O*NET, BLS surveys, and agency crosswalks) will need to update mappings and documentation to reflect the new classification, creating transitional reporting issues.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Gives the bill its public name—the "Supporting Accurate Views of Emergency Services (911 SAVES) Act of 2025." This is purely nominal but signals Congressional intent to emphasize accuracy in occupational representation for emergency services roles.
Findings on the role and risks of telecommunicators
Lists Congress’s factual assertions: the life‑safety role of public safety telecommunicators, their involvement in child protection, hostage negotiations, active shooter coordination, and exposure to traumatic events that can drive PTSD risk. The findings serve two functions: they justify why Congress wants a classification change and they explicitly reiterate that the SOC exists for statistical purposes only, which frames the change as representational rather than regulatory.
OMB directive to reclassify telecommunicators
Directs the Director of OMB to categorize public safety telecommunicators as a Protective Service occupation under the SOC and sets a 30‑day deadline after enactment. Practically, this obliges OMB to issue a formal categorization and to notify the federal statistical community so that occupational coding, statistical publications, and agency crosswalks can be updated. The provision does not spell out technical coding rules, funding for implementation, or follow‑on actions by other agencies.
This bill is one of many.
Codify tracks hundreds of bills on Employment across all five countries.
Explore Employment 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
- Public safety telecommunicators — gain formal recognition in federal occupational statistics which can strengthen advocacy for resources, recruitment, and occupational research by aligning them with other Protective Service roles.
- Workforce researchers and policy analysts — obtain clearer, more coherent data series for analyzing emergency services staffing, injury/illness exposures, and sectoral labor trends once crosswalks are updated.
- Local and state public safety employers — benefit from improved comparability to peer occupations for recruitment benchmarks, staffing ratios, and grant applications that reference Protective Service statistics.
- Advocacy organizations and unions — can leverage the new classification to argue for tailored mental health, recruitment, or compensation policies by pointing to consistent federal recognition.
Who Bears the Cost
- Office of Management and Budget and federal statistical agencies — must act quickly to update taxonomy, documentation, and guidance within the 30‑day window, adding short‑term workload and coordination costs.
- Bureau of Labor Statistics and survey sponsors — will need to update coding manuals, retool data processing, and document breaks in series for longitudinal analyses.
- State and local HR and payroll systems — may need to change mappings between local job titles and SOC codes, incurring administrative and IT costs.
- Researchers, contractors, and data vendors — face transitional headaches as historical series are recoded or split, requiring metadata updates and potential reanalysis of trend lines.
Key Issues
The Core Tension
The central dilemma is between correcting a likely miscategorization to acknowledge the risk and skill of 9‑1‑1 telecommunicators—and thereby improving visibility and advocacy—and preserving the methodological care and stability of federal occupational classifications; a rapid administrative reclassification improves representation but risks introducing data breaks, unintended program effects, and implementation inconsistency.
The bill is narrowly targeted and administrative, but its effects are neither purely symbolic nor costless. The 30‑day deadline is aggressive compared with normal SOC review processes, which are typically multi‑stage and consultative.
That compressed timeline raises practical questions about whether OMB will issue a simple re‑labeling or a more detailed code reassignment that includes guidance for coders and survey instruments.
Another tension arises from the SOC’s stated purpose: although it is defined for statistical use, many federal, state, and private programs borrow SOC codes for licensing, funding, and eligibility rules. A reclassification intended as representational could unintentionally change how programs count Protective Service workers, shift grant demographics, or alter program metrics unless those programs explicitly decouple their rules from SOC alone.
Finally, because the bill does not set technical coding standards or provide funding, implementation quality will depend on interagency cooperation and the administrative capacity of statistical offices to produce clear crosswalks and documentation quickly.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.