Lifeline

National Lifeline Accountability Database (NLAD)

State Agency Access

State agencies (such as state public utility commissions, state service commissions, and state agencies), with the exception of the NLAD opt-out states (California, Oregon, Texas, and Vermont), that regulate telecommunications service providers in their state have the ability to access basic Lifeline Program subscriber information in NLAD for their own state.

Each state agency may establish up to five NLAD user accounts. A user account is established by completing and submitting to USAC an NLAD User Access Request. Each person requesting a user account must fill out an NLAD Access Request and the state commissioner must sign each request. (By signing the request worksheet, the commissioner certifies that they have read, and agree to, the NLAD Access Agreement.) USAC will review the request, grant access as appropriate, and assign the user account.

Every quarter, all state users will be required to reauthorize their accounts. State commissioners may assign a delegate, using the NLAD Access Request worksheet, to reauthorize users' accounts each quarter. In situations where a delegate has been assigned, USAC will verify that the commissioner who signed the original request worksheet has not changed since the last reauthorization process. If there has been a change, USAC will need authorization from the current commissioner to reauthorize the agency's accounts. In this situation, USAC will send a reauthorization request to the current state commissioner via email (from NLADQuestions@usac.org). The commissioner must reauthorize state users, confirming that they should retain access to their accounts, within two weeks of the request.

NLAD Access Agreement

On logging in to NLAD, each user will be prompted to agree to the NLAD Access Agreement. State commissioners are also agreeing to the NLAD Access Agreement by signing NLAD Access Request forms.

Access NLAD by clicking the 'Log In' button.

Log In

Print the NLAD Access Agreement.

NLAD Access Benefits

Detailed Subscriber Information

Using the "Detail Subscriber Lookup" feature, users can search for a subscriber to determine if the subscriber is already listed in NLAD.

Enter a subscriber's:

  • First and last name
  • Date of birth
  • Last 4 digits of Social Security Number (SSN)
  • Primary address

If the subscriber has a record in NLAD, the following information will display:

  • Duplicate resolution status
  • SAC (Study Area Code)
  • SAC name
  • Subscriber telephone number
  • Service provider's marketing name
  • Service provider's customer service number

In cases where more than one carrier is claiming a subscriber in NLAD and the subscriber is undergoing the duplicate resolution process, the "Detail Subscriber Lookup" function will return all current carriers associated with that subscriber.

Please note that this functionality is not available to users accessing NLAD via API.

Subscriber Identity Verification

The subscriber identity verification process allows the user to confirm whether the subscriber is eligible for Lifeline benefits and may be enrolled in NLAD. If the subscriber is not eligible, NLAD will return the specific rejection reason(s) preventing enrollment in NLAD.

List of rejection reasons that would prevent enrollment in NLAD:

  • Duplicate subscriber: Subscriber matches an existing subscriber
  • Duplicate address: Subscriber's primary address matches an existing subscriber's address
  • Duplicate phone number: Subscriber's phone number matches an existing subscriber's phone number in NLAD
  • Subscriber under 18: Subscriber is not eligible for a Lifeline Program benefit because of age
  • Subscriber identity could not be found
  • Subscriber failed third-party identity verification
  • Subscriber date of birth could not be validated
  • Subscriber name or SSN4 could not be validated
  • Address unrecognized: (failed Address Matching Service)
  • This subscriber is currently undergoing duplicate resolution processing
  • Duplicate subscriber in process (subscriber is undergoing duplicate resolution)