119-S-3199 Investigative Journalist Impact Analysis

Summary

- What the bill does: Directs federal stakeholders to study or convene on transmitting geolocation (including dispatchable location) with 988 calls—an evolution beyond today’s 988 georouting regime that uses approximate, aggregated cell‑based data for call routing but withholds precise coordinates. (govinfo.gov)

- Headline impacts if implemented: (1) operational gains from faster, more local connections and cleaner transfers to 911; (2) fiscal pressure on carriers and crisis centers to implement and sustain new capabilities; (3) systemic risk that aggressive location mandates could chill help‑seeking if privacy isn’t credibly protected. (docs.fcc.gov)

Economic Effects

Likely cost centers and market effects, drawing on existing 988 rules and federal data.

• Carriers: Nationwide CMRS providers are already bound by the FCC’s 988 georouting rule (30 days after Dec. 12, 2024 for nationwide carriers; 24 months for non‑nationwide), so incremental compliance for routing‑level location is largely sunk. Any shift toward transmitting dispatchable geolocation for 988 would create new capex/opex for integration, security, and compliance. (law.cornell.edu)
• 988 network administrator and local crisis centers: More in‑state routing concentrates volume locally, requiring staffing, training, secure IT, and data‑management investment. HHS reported >8 million 988 contacts in 2025, and GAO found sizable unspent federal 988 balances—signaling both scale and absorption challenges that will shape any new mandate’s funding model. (hhs.gov)
• State and local budgets: KFF shows sustained contact growth and improved answer times since launch, implying recurring operating costs for centers as call/text/chat load rises—costs that could increase if centers must handle location data securely. (kff.org)
• 911/PSAP interop: If precise 988 location is ever captured, technical work will be needed to pass it to PSAPs’ NG911 environments and CADs; NENA’s 9‑1‑1/988 Interactions standard describes current transfer/data‑sharing expectations, and NTIA’s NG911 cost study frames the broader systems context. (nena.org)
• Small/rural providers and centers: FCC’s georouting order acknowledges timeline flexibility and solicits cost evidence—an indicator that smaller CMRS providers and rural crisis centers could face proportionally higher per‑user costs to meet any future geolocation obligations. (docs.fcc.gov)

Social Effects

Documented implications for communities and vulnerable populations.

• Access and timeliness: Georouting connects callers to local resources rather than area‑code centers, which stakeholders and FCC found beneficial while protecting privacy; this tends to shorten handoffs to nearby services and reduce misroutes from out‑of‑state numbers. (docs.fcc.gov)
• Trust and privacy: The FCC expressly declined to require precise geolocation for 988 because of privacy and chilling‑effect concerns. Civil‑society comments urged bright‑line limits and transparency if any geolocation is contemplated. The balance between crisis response and confidentiality will determine uptake among wary groups. (docs.fcc.gov)
• Crisis escalation risk: Only a small share of contacts trigger emergency activation; media synthesis of network data suggests ~1% “involuntary rescues.” While rare, such outcomes can be traumatic and disproportionately feared by marginalized groups—making privacy posture central to equity. (cbsnews.com)
• Deaf/Hard‑of‑Hearing users: 988’s direct ASL videophone service expands access but also presents unique routing/location challenges for video and relay services that the proposal flags for evaluation; implementation choices must not degrade accessibility. (samhsa.gov)

Environmental Effects

Direct environmental effects are limited; most changes are software, policy, and data‑handling rather than new physical plant.

• Network‑side modifications to support 988 routing/location generally reuse existing mobile core and Lifeline platforms, not new towers—so incremental energy/material impacts should be minimal relative to baseline telecom operations. This is consistent with FCC framing of georouting as cell‑based, aggregated data passed to the Lifeline’s centralized platform. (docs.fcc.gov)
• If future policy required secure storage/processing of richer location data, data‑center loads would rise modestly; no authoritative body has flagged significant environmental externalities specific to 988 geolocation to date. (Inference based on current regulatory documents.) (law.cornell.edu)

Temporal Analysis

What likely happens when.

• Near term (0–12 months after enactment): Federal stakeholders scope legal authority, privacy guardrails, standards, and cost‑recovery pathways. Work would build on the existing georouting rule and the Lifeline’s centralized routing architecture. Expect minimal user‑visible change beyond continued georouting refinement. (law.cornell.edu)
• Medium term (12–36 months): If legal/process consensus emerges, pilots could test privacy‑preserving ways to convey more granular location from 988 to 911 during active rescues, aligned with NENA’s interop guidance. Budget capacity at states/centers remains the gating factor. (nena.org)
• Long term (36+ months): Any shift toward dispatchable 988 location will succeed or fail on public trust; sustained increases in 988 usage since 2022 indicate demand, but uptake could plateau if people perceive new surveillance risks. (kff.org)

Unintended Consequences

Risks and secondary effects to watch.

• Scope creep: Without codified limits, carriers or third parties could repurpose 988‑related data—an outcome privacy advocates asked the FCC to preclude. (epic.org)
• Equity trade‑offs: If location mandates raise operating costs that states can’t absorb, uneven implementation could widen access gaps between well‑funded and resource‑constrained jurisdictions. (gao.gov)
• ASL/VRS edge cases: Location solutions built for voice may not translate cleanly to direct video or relay; mishandled, this undercuts accessibility gains for Deaf/HoH callers. (samhsa.gov)
• Data‑handling liability: Richer location data increases breach/compliance risk for centers and vendors, requiring upgraded controls and contractual safeguards. (Risk inferred from FCC/CFR posture on minimizing precise data.) (law.cornell.edu)

Assessment

Bottom‑line, non‑advocacy judgment.

Neutral. The proposal is a measured next step that could smooth 988→911 handoffs and reduce misroutes, with manageable near‑term costs where georouting infrastructure already exists. But any move toward dispatchable location must hard‑wire privacy protections—or the system risks eroding trust that 988’s growth has painstakingly built. (law.cornell.edu)

Sourcing

Primary rules, official data, and standards underpinning this analysis.

• FCC Third Report & Order on 988 georouting (privacy rationale; centralized routing; no precise geolocation). (docs.fcc.gov)
• 47 CFR §52.202 (georouting requirements; definitions; compliance timelines). (law.cornell.edu)
• SAMHSA/HHS program metrics and announcements (network scale; 2025 contact volume; ASL service). (hhs.gov)
• KFF analysis of 988 utilization trends (growth; answer times). (kff.org)
• GAO on 988/COVID behavioral‑health funding (unspent balances; absorption constraints). (gao.gov)
• NENA Standard for 9‑1‑1/988 Interactions (transfer/data‑sharing frameworks). (nena.org)
• 911.gov on dispatchable location under Kari’s Law/RAY BAUM’s Act (baseline for 911). (911.gov)
• Context on rare emergency activations/involuntary rescues. (cbsnews.com)
• Bill text reference (Reported in Senate version details on membership/scope, including ASL expertise). (govinfo.gov)