The FCC’s 2016 Lifeline order moved eligibility decisions from carriers to a verifier fed by benefit records
Released April 27, 2016, the FCC’s Lifeline order created a National Verifier to decide eligibility in place of carriers. Later matching notices had benefit agencies answer yes or no on enrollment. In our reading, their records became another program’s front door.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
Released April 27, 2016, the FCC’s Lifeline order created a National Verifier to decide eligibility in place of carriers. Later matching notices had benefit agencies answer yes or no on enrollment. In our reading, their records became another program’s front door.
- The week The order was not unanimous.
- The decision: who determines eligibility The order explained why it moved the decision.
- The data: which programs and what the verifier checks The current rule matches the 2016 list closely.
- The agreements: how other agencies share their records The order did not describe the legal mechanism for each data connection.
- The fallback: when the database says no The order provided for manual review from the start.
- How the change reaches different agencies A SNAP agency holds the records the order expected to rely on most.
- Objections, in order That is true, and the order chose those programs because of it.
- Checks a state agency data or privacy lead could run List every external program that queries your benefit records, including any Lifeline match.
- With hindsight The verifier took longer to arrive than the order expected.
The week
On Wednesday, April 27, 2016, the Federal Communications Commission released an order in its Lifeline proceeding. [1] The Commission had adopted it on March 31, 2016. [1] Its full title was a Third Report and Order, Further Report and Order, and Order on Reconsideration, numbered FCC 16-38. [1]
The order was not unanimous. Its cover page records that Chairman Wheeler and Commissioners Clyburn and Rosenworcel issued separate statements, and that Commissioners Pai and O’Rielly dissented and issued separate statements. [1]
Lifeline supports discounted communications service for low-income consumers. The order’s executive summary described its central change as a transition from primarily supporting voice service to supporting broadband. [1] It allowed support for standalone fixed and mobile broadband and set minimum service standards. [1] It also set a transition for gradually reducing voice support. [1]
The second item in the executive summary is the subject of this article. The order created a National Lifeline Eligibility Verifier, which it said would transfer the responsibility of eligibility determination away from Lifeline providers. [1] The Commission said that taking eligibility out of the hands of the parties that stand to benefit financially from a finding of eligibility was critical to preventing waste, fraud and abuse. [1]
The order explained the background. It said Lifeline providers had been primarily responsible in most states for determining eligibility and enrolling subscribers. [1] Depending on the state, eligibility could be established by documents a subscriber gave a provider, by approval of a state administrator, or by a check against a state database. [1] The order called this a patchwork that had enrolled qualified subscribers but also opened opportunities for waste, fraud and abuse. [1]
The order also narrowed the qualifying programs. It allowed entry based on participation in SNAP, Medicaid, SSI, Federal Public Housing Assistance, the Veterans Pension benefit program and the Tribal qualifying programs. [1] It kept the alternative of income at or below 135 percent of the federal poverty guidelines. [1] It said programs such as SNAP and Medicaid had program integrity and enrollment procedures whose fraud prevention capabilities Lifeline could draw on. [1]
The order described the verifier as more than technology. It said the National Verifier would be a system relying on both people and technology. [1] At its center would be a Lifeline Eligibility Database containing records of all subscribers the verifier deemed eligible. [1] It would have both electronic and manual methods for eligibility determinations. [1]
The order directed the Universal Service Administrative Company, which administers the program, to procure the verifier under the oversight of the Wireline Competition Bureau and the Office of Managing Director. [1] It set milestones. USAC was to submit a draft plan before December 1, 2016. [1] The Commission expected deployment in at least five states by December 31, 2017, in 20 more during 2018 and in all states and territories by December 31, 2019. [1]
The order also set an annual budget of $2.25 billion for the program. [1] It directed the Bureau to report to the Commission if disbursements in a year exceeded 90 percent of that level. [1]
The 2016 order’s executive summary led with bringing broadband into the program. [1] For agency data leaders, the more lasting change was the decision about who decides. The Commission moved eligibility determinations away from the companies paid to serve subscribers and gave them to a national verifier run by the program administrator. [1] It said that verifier would rely on other programs’ databases, owned by states, federal agencies and others. [1]
Our argument is that this made other agencies’ records part of Lifeline’s front door. The order said programs like SNAP and Medicaid already had strong integrity procedures that Lifeline could draw on. [1] The matching notices that followed show what drawing on them meant: source agencies receiving applicants’ identifying data and answering yes or no on enrollment. [3] [4] [5] In our reading, a state benefits agency’s data quality became a factor in whether its residents could get a telephone or broadband discount.
We take the question in four parts:
- The decision: who determines eligibility, and why the Commission moved that decision.
- The data: which programs and databases the verifier relies on, and what it checks.
- The agreements: the legal and privacy arrangements under which other agencies share their records.
- The fallback: what happens when a database cannot confirm an applicant.
The parts do not overlap. The first is governance, the second content, the third the legal channel and the fourth the exception path. After them we look at how the change reaches different agencies, take the objections in order and end with checks a state agency’s data, privacy or program integrity lead could run.
The decision: who determines eligibility
The problem the Commission described
The order explained why it moved the decision. It said that before 2008, Lifeline was a traditional wireline voice program and eligibility was necessarily determined by providers. [1] It said the program had become a multi-provider program with wireline, wireless and broadband service. [1]
The order said modern providers have varied business models and some have a greater financial interest in the eligibility decision, because the more subscribers they enroll, the more support they receive. [1] It said commenters had urged removing eligibility determinations from the entity serving the subscriber. [1]
What providers gained
The order presented the change as good for providers too. It said removing eligibility determinations from providers would lower their costs of verification and reduce their risk of verification-related enforcement actions. [1] It said that would make the program more attractive to providers and increase competition. [1]
It recorded commenters’ estimates that provider compliance costs most likely exceeded $600 million a year, attributing that figure to the commenters. [1] It said multi-state providers had to use and comply with several state eligibility systems. [1] A central verifier would replace that patchwork with one point of verification. [1]
In our reading, that alignment explains why commenters supported the change, as the order recorded. Providers shed a costly duty and its enforcement risk. The program gained a neutral decision-maker. The cost moved to the administrator and, through data agreements, to the agencies whose records answer the questions.
Separation of duties
In control terms, the order applied separation of duties. The party that benefits from a decision should not make it. A footnote in the order, citing a commenter, noted that SNAP separates eligibility functions, handled by a state agency, from retailer functions. [1] The verifier was meant to give Lifeline the same separation.
For a government audience, this is a transferable part of the order. Any program that pays an intermediary per enrollment faces the same question. The order’s answer was a neutral verifier. [1]
The verifier’s other jobs
The order gave the verifier more than one role. It would determine eligibility, allow providers to verify a subscriber’s status, provide access to authorized users and serve as the default basis for support payments. [1] It would also check that a subscriber was not a duplicate of an existing subscriber, reinforcing the one-per-household rule. [1]
The order said only after a full review could a provider claim support for a subscriber. [1] It declined to adopt a pre-approval process that would let providers claim support before review was complete. [1] The order said commenters had argued that completing full reviews would reduce waste, fraud and abuse, and that it agreed. [1] In our reading, that choice traded speed for integrity.
Payment follows the database
The order tied money to the verifier’s records. It said the verifier would be the default basis for determining support payments, with providers paid based on the records of claimed subscribers in the eligibility database. [1] Payment and eligibility would draw on the same list.
That design changes the incentive. A provider can be paid only for a subscriber the verifier has found eligible and the provider has claimed. [1] In our reading, it moved the program’s financial control point from provider attestations to a database the administrator runs.
Budget pressure
The same order set a budget. It established an annual budget of $2.25 billion and directed the Bureau to report if disbursements in a year exceeded 90 percent of that level. [1] It said it expected the Commission to act within six months of such a report. [1]
A budget makes integrity a fiscal issue as well as a fraud issue. Each ineligible subscriber consumes funds that could support an eligible one. In our reading, the verifier and the budget were two halves of one fiscal design.
Internal controls
The order specified the control framework. It directed USAC to create written procedures for all functions, processes, quality control standards and internal controls. [1] Subject to approval, USAC was to use GAO’s Green Book as a guide. [1]
It also required a reporting and internal controls component. That component would coordinate audits of internal controls, survey satisfaction with verifier personnel and produce reports to providers, USAC and the Commission. [1] The order said reporting would include data analytics and fraud prevention. [1]
Why the decision mattered to other agencies
Once eligibility moved to a central verifier, the verifier needed evidence. The order’s answer was the programs that already establish need. [1] That made the agencies running SNAP, Medicaid, SSI and housing assistance central sources of evidence for a program they do not run. They had not asked for that role. The order assigned it by design.
The data: which programs and what the verifier checks
The qualifying programs
The order streamlined qualifying programs to those it said have substantial automation and electronic processes in place. [1] It named SNAP, Medicaid, SSI, Federal Public Housing Assistance and the Veterans Pension benefit program, plus Tribal programs. [1] It kept an income path at or below 135 percent of the poverty guidelines. [1]
The current rule matches the 2016 list closely. As checked on November 16, 2026, section 54.409 lists Medicaid, SNAP, SSI, Federal Public Housing Assistance and the Veterans and Survivors Pension Benefit. [8] It keeps the 135 percent income test and separate Tribal-specific programs. [8] It also now includes a provision for survivors who request a line separation and face financial hardship. [8]
The income path
Not every applicant qualifies through a program. The order kept an income path at or below 135 percent of the federal poverty guidelines. [1] The current rule keeps it. [8]
The income path is harder to automate. A program enrollment check asks one agency one question. An income check needs evidence of household income, which no single benefit database holds. In our reading, that is why the order steered the program toward enrollment-based eligibility, where a database can answer, and left income as a path that leans on documents.
Who owns the data
The order acknowledged that the databases belong to others. It said the program databases checked should include those owned by states, by federal entities or by other entities. [1] It gave SNAP as an example of a program using state-owned databases and SSI as one using Social Security Administration databases. [1]
So the verifier’s inputs are split by program. For SNAP, the record holder is a state agency. For Medicaid, the order did not specify, and later notices show a federal route through CMS. [5] For housing assistance, later notices show HUD systems. [3] Each owner has its own data definitions, refresh cycles and quality problems.
What the verifier checks
The order said both manual and electronic approaches would apply program rules, including identity verification as necessary. [1] Electronic certification would rely on communications between the verifier and other systems. [1] The order said it envisioned at least near real-time results from the electronic process. [1]
The order set a long-term goal of determining eligibility for most subscribers electronically. [1] It said electronic certification would generally have lower long-run costs than labor-intensive manual review. [1] That goal put the burden of success on the source databases. If they did not answer, the manual path would grow.
The eligibility database
At the center was the Lifeline Eligibility Database. The order said it would contain records of all subscribers deemed eligible by the verifier. [1] It would hold, at a minimum, a list of subscribers whose eligibility had been confirmed and a list of claimed subscribers. [1]
The order also envisioned populating the database from state databases already in use by providers in some states. [1] It permitted USAC to integrate or repurpose the existing National Lifeline Accountability Database, used to prevent duplicates, in whole or in part. [1]
One per household
The verifier also enforces a household limit. The order said it would check that a subscriber is not a duplicate of an existing subscriber, reinforcing the one-per-household rule. [1] The current rule says a qualifying consumer must not already receive Lifeline, and no one else in the household may be subscribed. [8]
That check depends on identity and address data. Two adults at one address may be one household or two, depending on how they share income and expenses. A benefit agency’s address data can feed that judgment indirectly, through the enrollment answer. In our reading, address quality matters twice: once for the match and again for the household test.
Testing before going live
The order required a development environment. It said the verifier must include one that interested parties could use to test components before the live date and as functions were added. [1] For a source agency connecting a database, that is where interface problems would surface before they affect applicants.
The order also directed USAC to develop a plan for meaningful collaboration with potential users, including states and Tribal Nations. [1] It encouraged a stakeholder committee to advise on implementation, including IT requirements and electronic eligibility pathways. [1]
Security requirements
The order set security expectations by reference to federal standards. It required USAC to ensure the verifier complies with applicable laws and federal guidance, naming the Federal Information Security Management Act, NIST publications and the Privacy Act. [1] It said the verifier must follow NIST guidance for secure, encrypted methods of obtaining, transmitting, storing and disposing of information. [1]
It added limits on access. The order directed that access to consumer and provider data be limited and subject to secure authentication for verifier personnel, providers and other users. [1] For a source agency, those requirements describe the environment its data would enter.
The agreements: how other agencies share their records
The Privacy Act channel
The order did not describe the legal mechanism for each data connection. The Federal Register shows what followed. Beginning in 2017, the FCC published notices under the Privacy Act announcing computer matching programs between the FCC, USAC and other agencies. [3] [4] [5]
Each notice cited the 2016 order as authority, along with section 254 of the Communications Act and the Lifeline rules. [3] [4] [5] Each quoted the order’s statement that the verifier was to increase the integrity and improve the performance of the program for a range of participants. [3] [4] [5]
HUD
The notice published August 11, 2017, announced a matching program with the Department of Housing and Urban Development. [3] It named HUD’s Enterprise Income Verification System, its Inventory Management System and its Tenant Rental Assistance Certification System as the participating systems. [3] It said the program would begin on September 11, 2017, unless comments required otherwise. [3]
Four state agencies
The notice published October 10, 2017, announced a matching program with four non-federal agencies. [4] They were the Colorado Office of Information Technology, the Mississippi Department of Human Services, the New Mexico Human Services Department and the Utah Department of Workforce Services. [4] It said the program would begin on November 9, 2017, unless comments required otherwise. [4]
The selection lines up with the first launch. USAC’s launch table lists Colorado, Mississippi, New Mexico and Utah among the six states in its June 2018 launch, with Montana and Wyoming. [7] The notice and the table together show state agencies’ data agreements preceding the states’ entry into the verifier. [4] [7]
CMS
The notice published July 29, 2019, announced a matching program with CMS. [5] It named the Transformed Medicaid Statistical Information System, T-MSIS, as the participating system. [5] It said the purpose was to verify Lifeline eligibility by establishing that applicants or subscribers are enrolled in Medicaid. [5]
That route matters for state Medicaid agencies. T-MSIS is a CMS system fed by state data. In our reading, a state’s Medicaid submissions to CMS became, through this match, one of the sources the verifier relied on for its residents’ Lifeline eligibility.
The system of records
Each match draws on a published system of records. The August 2017 HUD notice said USAC’s records reside in the Lifeline system of records, FCC/WCB-1, and that the FCC was publishing an update reflecting the new uses. [3] The October 2017 notice said the August 15, 2017, update reflected the new uses involved in the matching program. [4]
The CMS notice cited the same system of records for the FCC side. [5] For the CMS side, it cited the T-MSIS system of records, System No. 09-07-0541. [5] Each match therefore rests on two published notices, one for each party’s records.
Dates and comment periods
The notices set start dates tied to comment periods. The HUD notice set comments due on or before September 11, 2017, and said the match would commence that day unless comments required otherwise. [3] The four-state notice set comments due on or before November 9, 2017, with the same structure. [4]
For a source agency, those dates mark when its data begins flowing to the verifier. In our reading, an agency’s own privacy office should treat the FCC’s notice as a trigger to confirm its side of the arrangement is documented too.
Why the Privacy Act route matters
The matching notices make each connection public. They name the participating agencies and systems, the categories of individuals and records, and the purpose. [3] [4] [5] They give the public an address for comments. [3] [4]
For a source agency, that publicity is a discipline. Its role in another program is on the record, with the data elements listed. In our reading, an agency that reads its own name in such a notice should be able to show the matching agreement, the legal basis for disclosure and the controls on its side.
What the agencies share and return
The notices described the data. The records sent included the applicant’s full name, physical and mailing addresses, partial Social Security number or Tribal ID number and date of birth. [3] [4] [5] The same elements were sent for a qualifying person in the household, if different from the subscriber. [3] [4] [5]
The response was minimal. The notices said the source agency would respond either yes or no that the individual is enrolled in a qualifying program. [3] [4] The CMS notice said CMS would compare the data elements to T-MSIS records and respond yes or no on Medicaid enrollment. [5]
Why a yes-or-no answer matters
A yes-or-no answer is a privacy choice. It reveals no benefit amounts, case notes or other program details. In our reading, it is a sound design for a match whose only purpose is to confirm enrollment.
It also concentrates the risk in the match itself. A no can mean the person is not enrolled, or that a name, date of birth or address does not match the agency’s record. The notices do not say how such mismatches are distinguished. [3] [4] [5] For the applicant, the result is the same: the electronic path fails and the manual path begins.
Who is in the match
The notices listed the categories of individuals. They included applicants, current and former subscribers and people who enable another household member to qualify. [3] [4] [5] They also included minors whose status qualifies a parent or guardian, and people acting for a provider who have enrolled individuals. [3] [4] [5]
That last category is notable. It brings provider agents into the system of records. In our reading, it reflects the order’s concern about enrollment practices, since the records can show who enrolled whom. [1] [3]
The fallback: when the database says no
Manual review
The order provided for manual review from the start. It said manual certification would use human review of documents and other information. [1] Subscribers would be able to submit information through methods such as mail and an online portal. [1]
The order directed the verifier to maintain information on acceptable documentation for identity and eligibility. [1] It acknowledged the diversity of documentation across states, territories, Tribal Nations and eligibility portals. [1] It asked USAC to consider how to address misuse of documents, giving SNAP cards lacking identifying information as an example. [1]
The applicant’s experience
The order set expectations for subscribers. It said the verifier should let potential subscribers apply directly, obtain information about providers and resolve issues through dispute resolution. [1] It said communications should use various modes, such as mail, telephone, text and email, and suit the mode the subscriber used. [1]
It also addressed time. The order said both manual and electronic processes should finish in a reasonable time and balance quick decisions with accurate reviews. [1] It named time of review as the first performance component for the verifier. [1]
Where the burden falls
When a database cannot confirm an applicant, the applicant must produce proof. For an eligible person whose agency record is incomplete or out of date, the cost of the agency’s data problem lands on them. In our reading, that is the main consequence of building a front door on other programs’ records.
The order recognized part of this. It said the verifier should facilitate participation by third parties, such as schools and community-based organizations, to help subscribers with eligibility questions. [1] Those helpers absorb some of the burden the manual path creates.
Help desk and languages
The order required a help desk able to handle inquiries from subscribers, providers, states and aggregators. [1] It said the help desk must at a minimum be able to interact in multiple languages and for specified periods. [1]
That matters when the electronic check fails. An applicant told that a database could not confirm enrollment needs to know what to send instead. The help desk is the verifier’s side of that conversation. The benefit agency, which holds the proof, is the other.
Documents and retention
The order said the verifier would retain the eligibility information collected during determinations. [1] It said providers would not be required to retain eligibility documentation for subscribers the verifier found eligible. [1] Providers that had determined eligibility themselves still had to keep their records. [1]
In our reading, that shift reduced the number of places holding copies of applicants’ benefit documents. It concentrated them with the verifier, under the federal security requirements the order named. [1]
Measuring the fallback
The order asked for measurement. It directed USAC to develop a performance management system for the verifier and listed components to evaluate, starting with time of review. [1] It required a reporting component that would produce reports to providers, USAC and the Commission. [1]
The documents we cite do not say whether no-match rates are shared with source agencies. In our reading, an agency providing data should ask for them. A spike in failed matches from one state or one field is a data quality signal the source agency cannot see on its own.
Recertification
The verifier’s role continued after enrollment. The order listed recertification of subscribers among the verifier’s functions. [1] It also made recertification a rolling process. [1] Each recertification is another database check, and another chance for a mismatch.
States that kept their own process
The order did not force every state into one model. It required states that had opted out of the National Lifeline Accountability Database to provide existing subscriber information to USAC by December 1, 2016. [1] A footnote named those states as California, Texas, Oregon and Vermont. [1] The order also directed USAC to consider partnerships with states that already determined eligibility, subject to Bureau approval. [1]
As checked on November 16, 2026, USAC’s National Verifier page names Oregon and Texas as the opt-out states. [6] It says consumers there benefit from state database connections available in those states. [6]
How the change reaches different agencies
A state SNAP agency
A SNAP agency holds the records the order expected to rely on most. It may be asked to enter a matching agreement and answer enrollment queries. Its data quality, including address currency and name formats, affects the share of its residents who pass the electronic check. It would also need to account for the match in its own privacy notices and agreements.
A state Medicaid agency
A Medicaid agency’s route may run through CMS. The 2019 notice used T-MSIS, which holds state-submitted data. [5] A state with gaps or delays in its T-MSIS submissions could, in our reading, see those gaps show up as failed Lifeline checks for its residents.
A public housing agency
Housing assistance enrollment ran through HUD systems in the 2017 notice. [3] A local public housing agency that reports tenant data to HUD contributes to those systems. The accuracy of its reporting can affect a tenant’s Lifeline check, even though the agency has no role in Lifeline.
A state IT office
Colorado’s match ran through its Office of Information Technology rather than a program agency. [4] That shows another model: a central state IT office acting as the data provider for program data. In our reading, such an office takes on the duties of a data steward for records it does not own.
A Tribal government
The order kept Tribal qualifying programs and directed the verifier to support access by Tribal governments. [1] The matching notices include Tribal ID numbers as an alternative to partial Social Security numbers. [3] [4] [5] A Tribal program’s records may be smaller and less automated, which makes the manual path more important for its members.
A county human services department
Where counties administer SNAP or Medicaid, county caseworkers enter the data the state shares. In our reading, a county’s data entry practices reach a federal communications program through the state’s match, two steps removed.
A state public utility commission
State commissions have their own Lifeline roles. The order directed USAC to prepare outreach packets for state public utility and public service commissions as part of its training plan. [1] It directed USAC to consider partnerships with states that already determined eligibility, with Bureau approval. [1]
For a commission that had run its own process, the verifier meant a choice between partnership and handing over. As checked on November 16, 2026, two states, Oregon and Texas, remain opt-out states with their own database connections. [6]
A community organization or library
The order wanted third parties involved. It said the verifier would facilitate participation by organizations such as schools, community-based organizations and digital literacy groups, to help subscribers with eligibility questions. [1] It said organizations without a financial interest in Lifeline benefits could improve both integrity and participation. [1]
A public library or community nonprofit helping residents apply becomes part of the fallback path. When the database says no, a resident may turn to those helpers next. In our reading, a state agency that wants its residents served should make sure such helpers know how to get proof of enrollment quickly.
A federal benefits agency
The order cited SSI as a program using Social Security Administration databases. [1] A federal agency asked to support a match would follow its own Privacy Act procedures, including published notices and agreements. The FCC’s notices show the form those took on the FCC side. [3] [5]
Objections, in order
1. Other agencies’ data was built for their own programs, not for Lifeline
That is true, and the order chose those programs because of it. It said their integrity procedures were what Lifeline could draw on. [1] The objection is better read as a caution: the match inherits each program’s definitions and errors, and the verifier must plan for both.
2. A yes-or-no match is too thin to prevent fraud
A yes-or-no answer confirms enrollment, which is the eligibility test the rule sets. [8] The order paired it with identity verification and duplicate checks. [1] Fraud prevention also rests on separating the decision from the provider, which the order did directly. [1]
3. Central verification slows enrollment
The order acknowledged the trade-off. It declined a pre-approval process and required a full review before providers could claim support. [1] It named time of review as a performance measure. [1] Whether review times were acceptable is an empirical question the documents we cite do not answer.
4. States already had good systems
Some did, and the order said so. [1] It directed USAC to consider partnerships with states that already determined eligibility. [1] As checked on November 16, 2026, Oregon and Texas remained opt-out states with their own database connections. [6] The national model did not erase state ones.
5. Privacy risk outweighs the integrity gain
The matching notices limit what is shared and returned. [3] [4] [5] The order required compliance with FISMA, NIST guidance and the Privacy Act. [1] Risk remains in the transfer of identifiers. In our reading, that risk is the price of an electronic path; the alternative is applicants mailing benefit documents, which carries its own privacy risk.
6. This is the FCC’s problem, not a state agency’s
The FCC set the rules, but the data came from state and federal agencies under published matching programs. [3] [4] [5] An agency that agrees to answer queries takes on duties under those agreements. Its residents’ success at the electronic check depends on its records.
7. Central checks just move the fraud to identity
The order anticipated identity risk. It said both manual and electronic methods would apply program rules, including identity verification as necessary. [1] The matching notices use identifiers such as partial Social Security numbers and dates of birth. [3] [4] [5] Identity fraud remains possible, but the order’s design separates it from the provider’s financial interest, which was the risk GAO described. [1] [2]
Checks a state agency data or privacy lead could run
Agreements inventory
List every external program that queries your benefit records, including any Lifeline match. For each, record the agreement, the published notice and the renewal date.
Match fields
Compare the fields an external match uses, such as name, address, partial Social Security number and date of birth, with your own data standards. [3] [4] [5] Record known quality issues in each.
Response design
Confirm your responses disclose only what the agreement allows, such as a yes or no on enrollment. [3] [4]
Mismatch analysis
If the matching partner shares error or no-match rates, review them by field. Look for patterns that point to your data, such as stale addresses.
Manual path support
Confirm residents can quickly obtain proof of enrollment from your agency for manual review. The order expected documents to fill gaps. [1]
Test environment
If your agency connects to an external verifier, confirm you have tested in a development environment before go-live, as the order required the verifier to offer. [1]
Proof for residents
Publish how residents can obtain a letter or online proof of enrollment. When an electronic match fails, that proof is what the manual path needs. [1]
Rule watch
Check the current qualifying programs in 47 CFR 54.409 and USAC’s pages before relying on any earlier description. [6] [8]
With hindsight
The verifier took longer to arrive than the order expected. The order set an expectation of at least five states by December 31, 2017, 20 more during 2018 and all states and territories by December 31, 2019. [1] USAC’s launch table lists its first group, the June 2018 launch, with a soft launch on June 18, 2018, and a hard launch on November 2, 2018. [7]
The table lists later launches through 2019. The October 2019 launch lists a hard launch of January 22, 2020, with Puerto Rico’s on June 23, 2020. [7] The December 16, 2019, launch lists a hard launch of March 24, 2020. [7] The December 20, 2019, launch for Oregon and Texas lists a hard launch of November 18, 2020. [7]
As checked on November 16, 2026, USAC’s National Verifier page says all states and territories have been launched. [6] It describes the verifier as Lifeline’s centralized application system, which determines whether consumers are eligible. [6] It says service providers in all 56 states and territories, except the opt-out states, must use it when helping consumers apply. [6]
GAO examined the program soon after the order. Its report, GAO-17-538, was published May 30, 2017, and publicly released June 29, 2017. [2] GAO said Lifeline’s structure relied on more than 2,000 eligible telecommunications carriers to implement key functions such as verifying eligibility. [2] It said this complex control environment was susceptible to fraud, waste and abuse, because companies may have financial incentives to maximize enrollment. [2]
GAO also tested the data. GAO matched subscriber data to benefit data. [2] It said it was unable to confirm whether about 1.2 million of the 3.5 million individuals it reviewed, or 36 percent, participated in a qualifying program as stated on their applications. [2] It noted that the 2016 order called for a third-party national verifier by 2019. [2]
In our reading, that finding supports the order’s central choice. GAO’s method was a match against benefit data, the same kind of check the verifier was built to run. [2] The matching notices that followed set up connections of that kind, with HUD in 2017, four state agencies in 2017 and CMS in 2019. [3] [4] [5]
The qualifying programs held steady. As checked on November 16, 2026, section 54.409 lists Medicaid, SNAP, SSI, Federal Public Housing Assistance and the Veterans and Survivors Pension Benefit, plus Tribal-specific programs and the income test. [8] It added a path for survivors who requested a line separation and face financial hardship. [8]
The opt-out list narrowed. The 2016 order’s footnote named California, Texas, Oregon and Vermont as opt-out states. [1] USAC’s page, as checked on November 16, 2026, names Oregon and Texas. [6]
What held up is the separation of duties. The order took the eligibility decision away from the companies paid per subscriber. [1] GAO’s findings the next year described the risk the order had targeted. [2] As checked, USAC’s page describes the verifier as the system that determines eligibility. [6]
What held up less well is the timetable. The order expected eligibility to be determined through the verifier in all states and territories by December 31, 2019. [1] USAC’s own table lists hard launch dates in 2020 for several groups of states and territories. [7] In our reading, building connections to numerous agencies’ systems, each under a Privacy Act agreement, took longer than the order planned.
For agency leaders, the case shows how a data-sharing role can arrive from outside. No benefit agency asked to become part of Lifeline’s front door. The order and the agreements that followed made them so. [1] [3] [4] [5] In our view, any agency whose enrollment records are trusted elsewhere should assume the next program will ask to rely on them too, and should know how good those records are.
Spotted an error? Tell us and we will check it and correct the article where needed.