Many state workforce agencies have until September 30 to deploy Login.gov's enhanced identity verification platform. For most, that means standing up a system they have never built on before, with less runway than it looks like on a calendar.
What the enhanced offering actually asks of your agency
Login.gov's enhanced offering has two core technical requirements that are more involved than they first appear.
- IAL2 biometric proofing requires residents to submit a government-issued photo ID and a selfie that are matched biometrically. This is a significantly stronger fraud barrier than most states have been using, which is the point given the scale of UI fraud since 2020. It also means handling more sensitive personal data, with security and compliance implications that need to be built in from the start.
- Integrated USPS in-person proofing is required for residents who cannot or will not complete identity verification online. This is not a separate standalone service. It has to be woven directly into the Login.gov workflow. The integration is more technically complex than it sounds, and getting the user experience right matters enormously for residents who are often already frustrated by the time they reach this step.
Your agency also needs to provide a separate non-digital verification option for residents who cannot complete any digital process, and crossmatch identity data received from Login.gov against your own internal records. Both involve state-side integration work that the directive does not make obvious.
The timeline step most agencies miss
Before any of the technical work can go live, your agency has to complete a formal onboarding process with GSA. That involves executing an Interagency Agreement, completing a policy review, and configuring the partner portal before sandbox testing and production deployment can happen.
That process takes 8 to 10 weeks on its own.
It cannot wait until your technical approach is figured out. It has to run in parallel.
Agencies that have not started this yet are working against a window that is already closing.
In-person proofing is not a checkbox
Not every resident can verify their identity online. In states with large rural or aging populations, that is not an edge case. It is a significant share of the people your program exists to serve.
For these residents, USPS in-person proofing is not a backup option. It is the only option. And it has to work.
Building this pathway correctly means designing an experience for someone who just lost their job and is navigating a federal identity verification process for the first time.. The states with the largest rural and aging populations face the most exposure here. Because if the in-person pathway fails, those are the residents who fall through.
Agencies that treat this as a checkbox will find their most vulnerable claimants still hitting dead ends. That is both a compliance failure and a program failure. And it is the kind of failure that shows up in headlines.
What separates a Login.gov partner from a Login.gov builder
The Login platform is new to most state teams, the timeline is tight, and the work spans identity proofing, system integration, security compliance, and user experience design. There is a difference between a partner learning this platform and one that built it.
Fearless has been the prime contractor on GSA's Login.gov since 2019. We built the IAL2 biometric proofing capabilities. We built the USPS in-person proofing workflow and tested it across all 50 states. We rebuilt the Login.gov Partners site specifically to reduce friction for state teams adopting the platform. And we are designing every new feature and change going forward, which means your state's implementation will adapt to platform changes before most agencies even know they are coming.
September 30 is a compliance deadline. But what it is really about is making sure every resident who turns to your program can access it securely, regardless of how they connect to government services. That is worth getting right. And worth getting right on time.
The team that built Login.gov is ready to help your state deploy it. Let's talk.