The bill directs the Secretary of Transportation, through NHTSA, to establish a grant and technical‑assistance program—within 180 days of enactment—to help States build systems that collect voluntary emergency contact information for inclusion in driver’s license and identification records. States receiving assistance must ensure participation is voluntary, implement robust data security protections, restrict access to authorized emergency personnel during emergencies, and not require displaying the information on the physical card.
This matters to state motor vehicle agencies, emergency medical and law enforcement responders, and vendors that operate DMV data systems because it creates a new federal incentive to add personally sensitive data to administrative records. The bill leaves important design choices and funding details to implementation, so states will face tradeoffs between accessibility for responders and privacy, interoperability, and the cost of building secure, auditable access systems.
At a Glance
What It Does
The bill requires the Secretary of Transportation, acting through NHTSA, to set up a program within 180 days to provide grants or technical assistance to States to develop voluntary emergency contact information systems tied to driver’s license/ID records. It conditions assistance on voluntary enrollment, robust data security, restricted emergency‑only access, and a prohibition on printing the contact info on the physical ID card.
Who It Affects
Primary implementers are state motor vehicle agencies and their IT contractors; authorized emergency personnel (EMS, law enforcement, fire) who would access the data; and vendors of DMV systems and identity databases. Congressional oversight and NHTSA technical staff will also be involved through reporting and assistance obligations.
Why It Matters
The program creates a federal carrot to standardize how emergency contact data is collected and accessed across jurisdictions, potentially improving response to incapacitated drivers. At the same time it raises privacy, security, interoperability, and operational questions because the statute sets outcomes but not technical standards, access protocols, or funding levels.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill tasks NHTSA with standing up a grant and technical‑assistance program within 180 days to help States add a voluntary emergency contact field to driver’s license and ID systems. Assistance can be financial (grants) or advisory (technical help), but the statute does not appropriate funds or set award formulas—leaving NHTSA to define eligibility, application procedures, and award terms when it implements the program.
States that accept assistance must meet four conditions: collect emergency contact information only on a voluntary basis; build “robust” data security protections; restrict access to authorized emergency personnel and limit use to emergencies; and ensure the information need not and shall not be required to appear on the printed or physical license/ID. Those requirements establish policy goals but stop short of mandating specific cryptography, authentication, logging, or retention policies.The Secretary must report to Congress within one year after enactment with information on implementation and any technical assistance provided.
The bill defines “State” to include the 50 States plus the District of Columbia and U.S. territories (Puerto Rico, Guam, U.S. Virgin Islands, American Samoa, Northern Mariana Islands), so the program extends to jurisdictions with very different DMV capacity and connectivity.Because the statute prescribes outcomes rather than technical standards, States will choose how to operationalize access controls (for example, online portals, EMS kiosks, or phone hotlines), how to authenticate emergency personnel, and how to integrate the data with existing DMV workflows. Those implementation choices will determine whether emergency contacts are genuinely useful to first responders or create new privacy and security vulnerabilities.
The Five Things You Need to Know
NHTSA must establish the grant/technical‑assistance program within 180 days of enactment.
Assistance may be provided as grants or technical assistance; the bill does not appropriate funding or set award criteria.
States receiving assistance must make provision of emergency contact information voluntary, implement robust data security, restrict access to authorized emergency personnel for emergency use only, and not display the information on the physical ID card.
The Secretary must submit a report to Congress on implementation and any technical assistance provided no later than one year after enactment.
The statutory definition of “State” explicitly includes the 50 States, D.C.
Puerto Rico, Guam, U.S. Virgin Islands, American Samoa, and the Northern Mariana Islands.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Provides the Act’s name, the "To Inform Families First Act of 2025." This is purely formal but signals the bill’s policy focus on family notification and emergency response rather than licensing standards.
Program establishment and deadline
Directs the Secretary of Transportation, through NHTSA, to establish a program to assist States in developing systems to collect emergency contact information for inclusion in driver license/ID records. The 180‑day deadline pressures NHTSA to publish program structure quickly, which means the initial guidance will shape state approaches and vendor procurement cycles.
Forms of assistance—grants and technical help
Permits NHTSA to award either grants or technical assistance. In practice, technical assistance can range from model data schemas and access protocols to on‑site IT support; grants would cover development and procurement costs. The provision does not state funding levels, matching requirements, or prioritization criteria, so NHTSA will decide those when it issues program guidance.
Conditions on State recipients
Sets four conditions for States that take assistance: voluntary participation; robust data security; access restricted to authorized emergency personnel for emergency use only; and no requirement to display the contact on the physical card. These are outcome requirements—States must translate them into authentication mechanisms, authorization roles, audit logs, and UI choices. The clause banning display on the physical card pushes States toward electronic access solutions, which raises practical concerns about offline access and responder workflows.
Reporting requirement and definition of State
Requires the Secretary to provide Congress with an annual report on implementation and technical assistance starting not later than one year after enactment. It also defines “State” to include U.S. territories and D.C. The report requirement creates an accountability touchpoint, but the bill limits the report's content to implementation and assistance details—there is no statutory requirement for outcome metrics such as access frequency, opt‑in rates, or security incidents.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation 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
- Emergency medical and rescue personnel: gain an authoritative, single‑source way to find next‑of‑kin or emergency contacts for incapacitated individuals, potentially speeding notifications and medical decisionmaking.
- Families and listed contacts: if systems work and access is timely, listed contacts are more likely to be informed quickly when an incident incapacitates a loved one.
- State motor vehicle agencies (DMVs): receive federal technical help or grants to modernize DMV IT systems and add functionality they might not otherwise prioritize.
- Public safety agencies and 911 systems: can gain a reliable data field to cross‑reference during critical incidents, improving situational awareness and follow‑up.
- DMV IT vendors and integrators: new procurement opportunities to build secure access portals, authentication systems, and audit/logging features for state clients.
Who Bears the Cost
- State motor vehicle agencies: must design, procure, and operate secure systems, add staff training, and integrate workflows—costs that may exceed grant amounts and create ongoing maintenance burdens.
- State budgets/taxpayers: if NHTSA provides limited grants or purely technical assistance, States will fund implementation, hosting, and cybersecurity operations going forward.
- Vendors and contractors: must implement higher security, logging, and access control requirements, increasing development and certification costs.
- Authorized emergency personnel and agencies: will need training, credentials, and operational changes to authenticate and access the data in time‑sensitive situations.
- Privacy and civil‑liberties monitors: will need resources to audit and respond to access misuse, given increased centralization of sensitive personal contacts in DMV records.
Key Issues
The Core Tension
The central tension is between improving emergency response by centralizing voluntary contact data in a trusted administrative database and protecting individual privacy and system security: the bill incentivizes States to make the data accessible to responders but leaves open how to tightly control access, authenticate users, and fund secure implementations—solving one problem (access) risks creating another (privacy and security exposures).
The bill sets outcome‑level requirements (voluntary, robust security, emergency‑only access, non‑display on card) but omits practically every implementation detail that determines whether those outcomes are meaningful. It does not specify technical standards for encryption, authentication, logging, retention, or identity proofing, leaving it to NHTSA and States to define what “robust” means.
That gap creates both flexibility and legal uncertainty: States can tailor systems to local needs, but inconsistent standards increase the risk of security gaps and interstate interoperability problems.
Another unresolved issue is funding and eligibility. The statute authorizes a program but contains no appropriation language, no grant formulas, and no priorities (for example, for rural or low‑capacity jurisdictions).
As a result, poorer or smaller jurisdictions could struggle to deploy secure, connected access for first responders even though they are explicitly covered by the definition of "State." Operationally, the prohibition on displaying emergency contacts on physical cards favors electronic access mechanisms; in low‑connectivity or mass‑casualty settings, responders may lack a reliable path to retrieve the data, undermining the bill’s practical benefit. The statute is also sparse on governance: it does not define “authorized emergency personnel,” set audit or penalty regimes for misuse, or require public reporting of opt‑in rates or breaches, all of which matter to privacy risk and public trust.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.